Activity › Forums › Blackmagic Design › New HyperDeck 2.5 Beta software available now.
-
New HyperDeck 2.5 Beta software available now.
Frank Gonzales replied 13 years, 9 months ago 16 Members · 34 Replies
-
Dan Nethery
February 19, 2012 at 12:37 amJuan Salvo is right, the only way to make it auto start stop with a sony F3 over SDI is to set the camera to Rec Run for TC and set the shuttle to “When SDI Timecode Runs”. Then to punch record, then stop it.
After that the shuttle runs like a champ!
-
Mike Squires
February 19, 2012 at 12:48 amChecked it out, it imports into Premiere Pro CS5.5 perfectly.
-
Juan Salvo
February 19, 2012 at 12:54 amI get a massive gamma shift with DNxHD qts on fcp vs avid. And it seems to jump in fcp depending on playback. I suspect this is standard behavior for DNxHD, but is anyone else seeing this? It looks great in Avid though and is a huge improvement over Xdcam from f3. Will probably use qt wrapper even for avid workflow, as qt on hyperdeck supports more audio (16 vs 4 channels.)
-
Juan Salvo
February 19, 2012 at 12:55 amWeird. I can’t get it to import into cs5.0 at all. Are you running lion or snow leopard?
-
Bo Skelmose
February 19, 2012 at 1:09 pmGuess only CS 5.5 support AVID DNxHD Mov files – CS5 do not. I cannot imort them into CS5 but play them with quicktime player.
Avid Codec 2.3.7 installed.
Now I just need to upgrade to the newest Adobe CS package to make it work.
This update is great and makes the shuttle2 a very usefull recorder. Thanks BM. -
Lee Schneider
February 19, 2012 at 5:47 pmThe DNxHD QuickTime is a nightmare in Final Cut and completely unusable. Any effect or even just a fade to black causes you to render. And there is a big gama shift from when the playhead is still to when playback is started. Maybe it’s just me, but thats what I got. I converted to file to ProRes, and it worked great.
Lee
-
Greg Booth
February 19, 2012 at 7:37 pmHi,
I believe the reason why the MOV file does not import into PPro CS5 is because of how the Audio Track is stored in the MOV file.
The Audio is stored as one Audio Track with multiple interleaved Mono Channels identified with QuickTime SoundDescription Version 2 – and it seems that PPro CS5 doesn’t understand this Audio format in a MOV file but PPro CS5.5 does understand this Audio format in a MOV file and can import the MOV file.
If the Audio was stored as one Audio Track per One Mono Channel identified with QuickTime SoundDescription Version 0 then PPro CS5 would probably import the MOV file fine.
Hope that helps!
Cheers,
GregCalibrated Software
Reply to this Discussion! Login or Sign Up