Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

B16 Quicktime Codec broken

Jeremy Neish

Well-known member
Joined
Jan 3, 2007
Messages
279
Reaction score
0
Points
16
Location
Provo, UT
Website
www.rivetal.com
Sorry if this has been brought up before, I searched and couldn't find it.

We were slow upgrading to build 16 due to some projects still being finished up in 15. Now that we've upgraded we've run into a major problem that is adversely effecting our workflow.

The QuickTime codec for build 16 does not play nice with "unapproved" QuickTime savvy apps. The whole point of QuickTime is to build an architecture in which any program can read (and usually write) movies, no conversions needed. And this was the way the pre-16 codec worked. But now only seemingly "approved" apps are working properly with the Red reference movies. And even those don't work 100% correctly. Specifically the _H and _F movies come out all high contrast and colorful, where as the _P and _M files work fine.

This puts a huge cramp in our quick turn, industrial projects where in the past we've just used the _H files and dropped them straight into AE or compressor, now that doesn't work and we are forced into a much more time consuming workflow that just won't work for some of our project timelines.

QuickTime Player, seems to work fine:
QT_Codec_Broken_qtplayer.jpg



Final Cut Pro mostly works, note the corrupted _H thumbnails in both icon view and the timeline, but once you open the clip it looks fine:
QT_Codec_Broken_FCP.jpg



After Effects, completely broken with _H and _F files:
QT_Codec_Broken_AE.jpg



Compressor, also completely broken with _H and _F files:
QT_Codec_Broken_compressor.jpg



Adobe Premiere can't work with the _H or _F ref movies either.

Presumably most other quicktime savvy apps will fail like JES Deinterlacer, QTSync, etc...

I've tried this on multiple workstations and MacBook Pros. All seem to behave the same.

This need to be addressed as soon as possible, we wasn't expecting to lose an entire workflow option with the build 16 upgrade.

Thanks,
Jeremy
Rivetal, Inc.
 
This turned out to be the way some applications access the codec changed with one of the quicktime updates. The new component is being tested right now and should be released in a few days if not sooner.
 
Back
Top