Lots of “Sorry, but a serious error…” from Prem Pro 1.5

[John Baum]

I get that with the 5.1.2 drivers. When I went to the 5.2 drivers the decklink refused to render anything. Previews or final. Trying to wrap up a few jobs so I can try and troubleshoot.

[Yves De muyter]

Yep.

-Yves

[Matt Dowling]

Bill,

Can you give us some more detail of exactly what you were doing when these errors occurred? Otherwise it makes it difficult for us to try and replicate this and see if there is indeed something we can do about it.

thanks,

Regards,

Matt
Blackmagic Design

[Matt Dowling]

Yves,

Are you seeing the same issue as Ghobil? You cant render anything? We have been unable to reproduce anything like this. Could it be an unistall/reinstall thing?

thanks,

Regards,

Matt
Blackmagic Design

[Bill Buchanan]

Luke:

The project at hand has literally thousands of clips in the library (all 10-bit uncompressed), and am just starting to cut the show. So, at this point the timeline is virtually empty. The 39mb project file loads fine–takes about 7 minutes. The crashes occur a split second after I place a shot on the timeline. Or, if the crash doesn’t occur after the shot is placed, it will when I try to adjust its length. I might add that I have just booted up the system in the morning.(Now I am wondering whether my loading the project before the all the “processes” listed in Task Manager have finished loading might be the culprit)

When I re-open the project, it will usually crash again as before. But today, for example, after two or three times re-opening the project, it did not crash, and I’ve been working with it all day, without another crash.

Since all I was doing was capturing while V5.1 was installed, I don’t really know if the crashing would have happened with that driver or not.

I will uninstall/reinstall 5.2 and/or go back to 5.1 to see if that fixes the problem, since I recall doing that many months ago with a previous version with which I was getting lots of crashes, and that exercise seemed to fix the problem.

I will post the results of the uninstall/reinstall and other experiments shortly.

Bill Buchanan
Buchanan Film Co.

[Bill Buchanan]

Matt:

I uninstalled and reinstalled 5.2 and Viola! I can’t make the app crash. So, all’s well at the moment. Also, no rendering problems whatsoever. RT effects, etc. work very well, too.

Bill Buchanan
Buchanan Film Co.

[Bill Buchanan]

Oops. Spoke too soon. Fired up the sys this morning, opened the project, placed a clip on the timeline and was immediately greeted by, “Ha Ha Ha, a serious error has…”
I’m going to uninstall 5.2 and re-install 5.1 to see what happens. Will post results later.

Bill Buchanan
Buchanan Film Co.

[John Baum]

I had some time to look into this problem and here is a copy of the email I am sending support:

I have now had some time to explore this further and it seems the problem is related to footage that has a key or alpha channel. Any project that has a key of any kind, whether uncompressed avi

[Dominic Osborne]

I can’t even get premiere to use the 5.2 drivers. They are installed, quite clearly, but no presets available in Prem or realtime output.

Maybe I need to try unistalling and reinstalling too.

[Matt Dowling]

That’s really interesting – thanks for such a detailed post, it will really help us out to track this down – we will check it out.

Cheers,

Regards,

Matt
Blackmagic Design