[Sam Goetz]

I’m seeing the same exact bug. BIG PROBLEM. We had to downgrade to the 6.4 drivers to fix it.

capturing from any type of deck (digi-beta, beta, dv-cam) eventually results in this message: “a new tape has been inserted” as you scrub around the tape. makes any kind of significant capturing impossible.

I didn’t see it on all of my systems so my thinking is that it’s a result of the 6.6.2 Drivers w/ the HD PCIe Pro cards.

BUT DO NOT UPGRADE TO 6.6.2 if you have these cards. They WILL BUG OUT. BM, PLEASE PLEASE PLEASE GET YOUR DRIVERS FIGURED OUT. THERE HASN’T BEEN A STABLE BUILD FOR FCP 6, YET.

[Sam Goetz]

Haven’t seen the multibridge bug, but we never convert A2D via Decklink (we’ve got a hardware solution in our rack for that). Totally wouldn’t be surprised if there was a bug there.

STILL, the gamma shift is DEFINITELY a NEW issue. Everything w/ Photo-Jpeg worked fine in FCP 5 – 5.14. We use photo-jpeg as an archiving codec and have over 1 TB of data encoded in it. It’d be horrible for us if we had to recompress all of those movies just because FCP can no longer properly play it down….

Any word BM? I’d love a response on this, even if it’s merely “blame fcp 6” kind of a response.

[Sam Goetz]

Having exactly the same issues here…. waiting a bug fix anxiously, as do A LOT of photo-jpeg work here.

[Sam Goetz]

I’m still seeing two major bugs with the 6.6 drivers.

1.) Downconverting 720p HD to SD on output is broken. 720p native playback is fine, but when the “output processing” is set to SD downconversion in the Decklink Systems Preferences playback is glitched out (crazy stuttery w/ rapid scaling) and usually results in a complete freeze of FCP.

2.) Photo-Jpeg playback is buggy. The gamma changes from when the playhead is parked to when you’re actually playing down. Hit play and your image “pops” to a different gamma, hit stop and the the image “pops” back. Applying effects or transitions across photo-jpeg material will result in a gamma pop between rendered and non-rendered material.

Both of these issues have been acknowledged as existing bugs by BM, but still remain unfixed in the new drivers. Hopefully we’ll see these issues fixed relatively soon. Till then, I’d stick with the older drivers if you plan on doing either of these two workflows above.

Sam

p.s. These are FCP 6 bugs, not sure if either of these things happen in earlier versions of FCP. They do happen across various different BM cards and computer types.

[Sam Goetz]

The new drivers (6.5.1) appear to have solved this problem. Try ’em out.

I feel your pain, though. This problem enraged me daily for almost a year.

[Sam Goetz]

WOW! Well, it seems that BM has FINALLY fixed this problem with their new drivers. Specifically the 6.5.1 drivers.

Initial testing on my end resulted in frame accurate layoffs with absolutely no tinkering. Of course this is only after a few tests and who knows if something will pop up in the next couple of days. But for now, I’m very happy.

Thank you BM!

p.s. There still is a terrible HD downconversion bug that came up with the 5.4 drivers that has yet to be fixed. I will be posting about that soon…

[Sam Goetz]

This is not a computer monitor issue. The gamma shift shows up on external monitors, and even worse, it is burned onto the image when you render. IE round tripping from FCP Capture, to PC AE FX, back to FCP Edit will result in a shot that is much darker than where you started.

Any other people seeing this? Should I be resigned NOT to use BM 10-bit for cross platform work?! I thought that one of the shining points for Blackmagic was their ability to work cross platform….. what’s happening here?? Any workarounds?

Sam

[Sam Goetz]

Hey Jon,

Indeed, this annoying issue has been well documented on the Cow, but not mentioned recently. It is, as you noted, a confirmed issue and fixes have been promised for some time, but to no avail. There are some simple, yet frustrating, work arounds that will consistently fix the problem. For more info see this thread :

https://forums.creativecow.net/readpost/124/866188

Thanks for bringing it up again. And maybe just maybe we’ll see a fix with the new drivers soon. PLEASE!

[Sam Goetz]

I see no such crash report…. maybe that’s because it’s more like a “freeze” than a “crash.” Basically, I get the spinning volleyball of death, and even after waiting 10 minutes or more nothing happens so I’m forced to do a force quit. I don’t think logs are created when you force quit.

Apologies for the confusion. It’s a freeze not a crash…

[Sam Goetz]

Where would the crash log be?