-
Blackmagic Releases Decklink 6.6 – Incl. support for Mac OS10.5
Hi everyone,
I just noticed that Blackmagic has released Decklink 6.6 this morning, for PC and Mac (including support for 10.5 Leopard).
From the blackmagic website:
Mac Version:
“This software update adds: Support for Mac OS X 10.5 Leopard, Support for Adobe Premiere Pro CS3 v3.1, Project presets for Adobe Premiere Pro CS3 v3.1, Analog input anti-alias filter control on DeckLink HD Extreme, Improved Digital Betacam support in Final Cut Studio 2, and general stability and performance improvements. Please check the included “read me” for more information.”
PC Version:
“This software update adds: Sony Vegas 8 support (Beta), improved support for Adobe Creative Suite 3 Production Premium, Analog input anti-alias filter control on DeckLink HD Extreme and various stability and performance improvements. Please check the included “read me” for more information.”
Hopefully this update with address some of the minor issues I’ve experienced with the new Eclipse :o)
Oliver Trenouth
Media Developer / Editor
National Media Museum, UK -
5 Replies
-
How very strange
-
Hmmm…. and what is with Premiere CR3 P2/MXF-Support? Is it working?
Rudi
-
More question than answers
-
with the 6.6. it was possible for me to update the firmware of a dl hd studio.
before it was a firmware update loop.i have the impression, that the hdmi connection is more stable now.
best regards
thomas -
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.
Reply to this Discussion! Login or Sign Up