it is less intensive...
i run both workflows...
with cineform i can get realtime playback of 4k through PPro(one layer of video in the timeline) with 1 core i7
redcode is based on jpeg 2000
cineform something else....
they are both wavelet encoded, but i think cineform is more optimised for intel
another workflow plus for cineform is, i can convert a 4k DPX sequence to cineform and edit real time in 4k with just a 2 hard drive raid 0 setup...all with active metadata coolness
so whereas it is a hassle to convert redcode to cineform....it is a solution for more then just redcode....there still will be filmscans for the forseeable future
how long it takes to convert from red to cineform ? is it faster than the usual debayer.
and from cineform to any other output codec ? Does cineform help bypass the super slow debayering process ?
And since RED ROCKED decodes the 4K files in real time, encoding to Cineform also benefits since the long part of the process has been the debayering.
So if I have only Cineform it will still take ages for REDCINE to convert from R3D to Cineform ?
What about from Cineform to whatever format i want the final output to be ?
I would convert R3D to cineform through there utility not redcine
and for output cineform has command line utilty for DPX output,.... Any other format you'll have to run through your editor or AE ect
but it is faster to convert R3D to cineform than debayering R3d files to whatever format you wish ?
And how long does it take cineform to transform into DPX or other formats if using the editor ? Is it the same as debayering R3Ds ?
|« Previous Thread | Next Thread »|