Premiere CS6 on Windows 7 makes QT 10-bit crazy in "Max Bit Depth"


summary:

 

problem: 10-bit qt-cineform footage in premiere cs6 on windows 7 looked ok sequence in 8-bit mode crazy (mostly noise) when same sequence in "maximum bit depth" mode.

 

solution: re-wrap footage avi-cineform (or else use premiere cs5.5 or different nle).

 

detail:

 

this problem occured on 2 different machines, each running windows-7 (64-bit), each machine having different update-versions of premiere cs6.  problem absent when imported same footage cs5.5 (5.5.2, 003, mc 258762).

 

i recorded 10-bit footage sony ex3 camera via sdi quicktime (.mov) file containing video encoded in cineform (cfhd) 10-bit format.  recorder (a cinedeck) records qt, not avi.

 

in premiere cs6, footage looked expected when processed in 8-bit mode.  when same sequence had "maximum bit depth" setting enabled, image (from preview , render) appeared noise.  last thing 1 wants discover prior final render...

 

the same footage looked fine, 10 bits of information being used, both in earlier premiere cs5.5 , in sony vegas 12 (in equivalent mode, "32 bits, video levels").  verified "all 10 bits used" expanding levels-range (by increase in gamma , minimum level in fast color corrector) , inspecting result (for dark regions of image) in waveform (yc) monitor in reference window.

 

a "dit-craft" workaround:

convert footage qt avi, best achieved re-wrapping (not transcoding).  in case did via convert function of cineform tool hdlink.

 

conclusion:

 

cs6 on windows 7 doesn't qt containing 10-bit cineform, or maybe (i wonder) 10-bit anything?  quicktime version 7.7.2 on 1 machine , 7.7.3 on other.  latest version of qt 7.7.4 next tried updating 1 of machines made no difference.

 

questions:

 

can else confirm this?  happen in new "premiere pro cc" version?

following brief "moment" of (unjustified) doubt (but justified requirement verify),  seems "re-wrap work-around" does work, , hdlink does re-wrap provided its "force re-wrap" option enabled in cineform's hdlink (otherwise re-encodes 8-bits).

 

my issues niggling ones hdlink, in terms of mentioned setting-requirement , (repeatable) crash/freeze issue @ end of processing, requiring process-abort (from windows' task manager).  fortunately ugly state of affairs not appear harm generated avi file, other fail update windows explorer , file's accessed/modified timestamps @ end of processing.

 

in practice, avi file generated process found playable windows media player , importable premiere cs6, appeared expected in both 8-bit , "max bits" modes, latter receiving full 10 bits of levels information.

 

so problem solved!  verified!

 

just record, "moment of doubt" , resolution of it:

<<<

oops... need verify, time, whether workaround worked...

 

following overnight conversion, result seemed 8-bits.  view supported file-size reduction (39gb 31gb, proportion = 8/10) , 8-bit-like levels-banding when viewed on premiere's waveform/yc monitor on premiere cs6 test sequence in max bits mode.

 

...in case quick test suggesting re-wrapping had fixed problem in fact misleading, because not changing container (qt->avi) encoding , bit depth...  result of test neutral...

 

so re-try hdlink conversion, time hdlink's "force re-wrap" option selected in preferences.

 

<some time passes...>

 

this time, took 45 minutes complete , furthermore cpu (4-core) load tiny, 1 or 2%, opposed around 16% overnight "unwanted re-encode" process.  both of factors supportive of prospect re-wrapping indeed happening time...

 

then hdlink failed terminate properly.  after 30 further minutes, there no change, , no cpu load it, elected abort process.

 

the resulting avi file of same size qt original, interpreted correctly when premiere in "max bits mode" , verified containing useful 10 bits of information (via banding in premiere waveform/yc monitor, comparing , without "max bits mode") .

>>>

 

this "video detective" can hopefully "case closed", i'll "leave files open" few days more in case further issues show up.

 

regardless, still helpful hear of similar experiences or alternative solutions.



More discussions in Premiere Pro CC


adobe

Comments

Popular posts from this blog

Thread: gpg: Conflicting Commands

Adobe Acrobat Pro , Terminal Server Use

when i try using AE CC 3d camera tracker after the first step it says "Analysis solve failed." help?