-
Has 6.2 Poisoned my Multi-Bridge?
I’m running an Intel MacPro 3GHZ, 5GB RAM, off a 140mbps RAID to do Uncompressed SD via BM Multibridge. I upgraded to the 6.2 drivers before getting FCS2 in the mail. The first thing I noticed was dropped frames when playing back rendered BM 10bit or 8bit timelines (whether I had external video on or off). Annoying! So I figured that maybe it had something to do with installing BM 6.2 before FCS2. So, I uninstalled 6.2 and re-installed 6.1, then final cut just crashed everytime I tried playing back a 8 or 10 bit sequence.
Later, after installing FCS2 and re-installing 6.2 drivers, guess what: final cut still crashes on playback of 8 and 10 bit.
So I was glad to find a post that suggested that I go into system settings > effects handling > turn 8 and 10 bit uncompressed to “None” which is a great idea (why should FCP handle the Uncompressed BM files anyway?) After changing the effects handling for 8 and 10 bit to “None” it still didn’t end my final cut crashes. I guess this works with Decklinks, but I have a Multibrigde.Any other suggestions anyone?
Is it possible that the rumored Decklink 2GB barrier bug has infiltrated all the 6.2 drivers?
Do I have to wait for OSX Leopard?
-
5 Replies
-
[IndieSoon] “So I was glad to find a post that suggested that I go into system settings > effects handling > turn 8 and 10 bit uncompressed to “None” which is a great idea (why should FCP handle the Uncompressed BM files anyway?) After changing the effects handling for 8 and 10 bit to “None” it still didn’t end my final cut crashes. I guess this works with Decklinks, but I have a Multibrigde.”
Actually Uncompressed files are Apple, not BM. And you want FCP to handle them or else you won’t get RT Effects. Only the 4:4:4 codec is BM. Other than that BM codec is legacy.
I don’t know what your issue is. But after this an many other issues, I think its safe to say that people should not upgrade to FCS2 until they release an update that fixes the numerous issues.
Sean
-
I’m on G5 quad hardware with 4gb of ram to a multibridge extreme and everything is working with fcs2 just fine except for 2 small things related to motion 3.
1) .motn files (8 second slates) I always render in fcp used to take
just a few seconds to render with fcp 5.04, in fcp6 it takes 12 minutes.Definitely a flaw there.
2) video output from motion 3 works well in all modes except 10-bit.
I get no signal to the monitor, so its on RGB right now to make it work. -
Point well taken; the effects handling switch didn’t solve the problem anyway. But, the issue definately isn’t FCS2; my issues started before I installed FCS2. The problem undeniably began when I installed Multibridge 6.2, so if anything, people should be wary and create a clone of their boot drive before trying 6.2.
-
[Borjis] “I’m on G5 quad hardware with 4gb of ram to a multibridge extreme and everything is working with fcs2 just fine except for 2 small things related to motion 3.”
You just haven’t found them yet.
– It seems Photo-JPEG and other RGB codecs are unusable in FCP 6 – at least with BM hardware. There’s a gamma shift during playback (you’ll find a discussion of it on here)
– DV50 NTSC footage that was captured in FCP 5 is unusable in FCP 6.
– The new “Mixed Format” feature doesn’t add 3:2 pulldown when putting 23.98 footage on a 29.97 timeline (instead it adds 2:2:2:4 pulldown which is bad).
– The Blackmagic Easy Setups for ProRes that came with 6.2 drivers. They’re all set to 8-bit instead of 10-bit. A mistake they made which was mentioned here. Easy to fix yourself of course, but that’s assuming you even know about it.
Sean
-
How do you change the ProRes from 8bit to 10bit?
Reply to this Discussion! Login or Sign Up