-
5.2.2 some question
Hi Luke and Matt,
5.2.2 is really great, it works much better and faster than all the other drivers before.
Many thanks….But i have two remarks:
First: Even when 5.2.2 is the best driver ever, Premiere crashes very offen, much more than with the
latest stable dirver on my machine (4.7.5) Any idea?Second: I have several Decklink Cards…and with the Extreme and 5.2.2 there is no video and audio-out (for monitoring) while capturing! When i put the Decklink Pro in my machine there
-
15 Replies
-
Claus-Peter:
Experiencing frequent crashing like you and others with the BMD driver v5.1+/PremPro1.5 combo, I finally found a solution that absolutely prevents that pesky “…a serious error…” from occurring:
Simply open a new project and set all your preferences, but go no further. That’s right. Do not capture or import any footage. If you must capture anything, do not exceed two or three short clips. If you do succeed at capturing those clips without a crash, DO NOT attempt to place any of them on the timeline. By limiting your editing activities to staring at the PremPro interface and keeping yours off the keyboard and mouse, those silly crashes will fade from memory.
Bill Buchanan
Buchanan Film Co. -
I improved stability by setting the windows sound drivers to anything but decklink (NVIDIA onboard audio in my case), and toggling the “use default devices only”.
I have other problems on HD pro card, cutting to DV from 8 bit clips (NTSC) causes a glitch on the sdi output during playback or scrubbing. SD plus card seems fine.
-
Very Clever, Bill. By all acounts, your simple method should do away with numerous problems, such as bad sound, improper cuts, and credits that contain misspells. You need to coin a term, similar to “The Ken Burns Effect”. I really think you have something there. I’ll pass it on to my editors.
Steve Wargo
-
Hi Bill,
I am at a bit of a loss as to what is happening on your system. After reading your post, i set up a 1080/59.94 YUV project, imported an EDL with 200 clips, captured and then placed all 200 clips on the timeline at once at hit play – no problems. The clips varied in duration from 2 frames to 5 mins.
I placed them on the timeline at least 20 times on different video tracks each time as well – never had a serious error occur.
The systems this was tested with:
Dual core Opteron x2
Tyan, Thunder K8WE motherboard – on board SCSI RAID disabled in BIOS
3 ware 8 port SATA RAID card striped RAID 0 with 8 SATA 2 disks
nVidia Quadro FX 1300
2 GB ECC RAM
DeckLink HD PRO
HD D5 deckThen we tested on the absolute bare minimum system we have (P4 32 bit PCI, single ATA disk) but in NTSC this time.
Same results.Not being able to reproduce this error makes it very difficult for us to try and diagnose what is going on with your system.
I totally believe what you are saying – but we can not reproduce this on any of the systems here from the fastest to the slowest.Regards,
Matt
Blackmagic Design -
Hi Claus-Peter,
Can you tell me when it crashes? Are you capturing, playback, import or is it completely random?
Regarding the Extreme during capture – the test that we did for Bill below was using an Extreme in the bare minimum machine and it was monitoring during capture.
Cheers,
Regards,
Matt
Blackmagic Design -
Hi Matt,
the crash happend when i copy and paste, or when i speed up, or when i apply a effekt on a clip.
Not everytime…when i work a day, it happends 5 or 6 times.
(it do not happend when i capture, play-out)I
-
Hi,
a problem more..the projectmanager doesn
-
Question:
Could there be a codec problem, most all of my clips are captured with 4.7.5
and now i -
Hi Claus-Peter,
4.7 is that long ago now, so much code has changed since then. Also the feature set and hardware requirements have changed a great deal – more features take more machine resources.
5.1.1 drivers were certified by Adobe for Premiere Pro 1.5 and for OpenHD (www.openhd.org) Adobe absolutely put our drivers through their paces and we worked very closely with them to get our drivers to a standard that passed their strict requirements. A big part of passing certification in Adobe’s eyes was the project manager feature. If we didnt pass that then certification would not have been given. The majority of the code for 5.2.2 is exactly the same code as the certified 5.1.1
Do you see any of the issues you have reported with 5.1.1? Or is this only showing up in 5.2.2? As something in the newer code may have changed something.
We have more than ten thousand customers using Premiere Pro ranging from the home enthusiast to hollywood guys doing feature film FX work with 4:4:4 using Blackmagic FrameLink for DPX workflows, After Effects and of course Premiere Pro – honestly we are not getting reports of issues like this.
Cheers,
Regards,
Matt
Blackmagic Design -
Here is what I do when it seems “only I am having problems”… it is a bit time consuming but it certainly can yield results.
1/ unplug your system hard drive.
2/ By a new hard drive and install it in your machine as the system drive.
3/ install your windows XP + SP2 onto the new hard drive
4/ install Premiere Pro 1.5
5/ install the latest BMD drivers
6/ open Premiere and see if all your problems are goneIt is amazing how a zillion problems vanish with a totally fresh instal… but you notice I recommend not even going anywhere near the original system drive because there are many system settings buried deep in there somewhere so you know a new hard drive is totally free of them. What you do after you dertermine your “hardware is now deemed ok” is up to you; I normally go seek and destroy because I now know ‘I’ have a problem and it is in the operating system somewhere…. but for those that don’t want to delve into all the inner workings of the operating system may choose to keep the new drive in the machine and remove and reformat the old one. I may be stating the obvious to most people here but Microsoft would charge you $35 for that info after 3 weeks of umming and ahhing…
Reply to this Discussion! Login or Sign Up