Click here to go to the first RED TEAM post in this thread.   Thread: Redcode transcodes..

Reply to Thread
Results 1 to 6 of 6
  1. #1 Redcode transcodes.. 
    Senior Member david farland's Avatar
    Join Date
    Dec 2006
    Location
    Sydney
    Posts
    1,509
    Couple of questions....

    1. During colour corrections, compositing, etc of an online tiff/dpx file, is the inherent robustness of the image derived from the redcode source image rather than from these various ‘lossless’ codecs /wrappers?

    2. With regards to image quality and robustness, is any redcode to 3rd party codec transcode more optimal than another?

    Thanks,

    Dave
    Reply With Quote  
     

  2.   Click here to go to the next RED TEAM post in this thread.
  #2  
    1) derived from the clean raw data from the sensor and sensible compression for recording

    2) we've only really tried conversion to ProRes so far. And that worked great. Internally, a lot of our transcodes have been to 16bit tiffs, which is very high quality, but large files.

    Graeme
    www.red.com - 5k Digital Cinema Camera
    Science enables stories. Stories drive science
    FLUT™, Image Processing, Colour Science and Demosaic Algorithms, REDRAY 4K delivery
    Reply With Quote  
     

  3. #3  
    Graeme when do you expect the REDCode to be unleashed upon the world? Are you going to hold out on the codec until the cameras are released? When will we get more information about REDCode? Right before NAB I asked when we could see it available as a stand alone product and I hoped NAB would answer that question but alas we know nothing more in relation to stand alone REDCode purchases.

    Here is what I would like to see in my workflow:

    REDCode RAW Capture.
    Transcode to a robust intermediate such as 40MBs REDCode RGB (I say this because I assume an internal codec RAW Debayering is much much much slower than an RGB redcode decode)
    This way I could stay inside of REDcode throughout the data pipeline without any worries about generational loss.
    Gavin Greenwalt || im.thatoneguy
    im.thatoneguy[at]gmail.com | Straightface Studios | VFX & Animation
    Canon Scarlet-X package available to rent in Seattle, WA
    Reply With Quote  
     

  4.   Click here to go to the next RED TEAM post in this thread.
  #4  
    I'd certainly render to REDCODE RGB at some point, but I'd not be doing it straight away - I don't think there'd be an advantage there unless you're working on 4k as 4k right from the start. I can see your point about offloading the demosaicing process into baking it into the RGB, but then you've got 3x the decode time on the codec.

    Graeme
    www.red.com - 5k Digital Cinema Camera
    Science enables stories. Stories drive science
    FLUT™, Image Processing, Colour Science and Demosaic Algorithms, REDRAY 4K delivery
    Reply With Quote  
     

  5. #5  
    So wait REDCode RGB has 3x the decode time as REDCode RAW? Hmmm.. well it's a moot point because I'll be using REDCode (if you ever offer that blasted stand alone codec) about 98% of the time with RGB originated material and never see RAW files myself.
    Gavin Greenwalt || im.thatoneguy
    im.thatoneguy[at]gmail.com | Straightface Studios | VFX & Animation
    Canon Scarlet-X package available to rent in Seattle, WA
    Reply With Quote  
     

  6.   This is the last RED TEAM post in this thread.   #6  
    Well, if REDCODE RGB is 4:4:4, REDCODE RAW, for the equivalent resolution is :4:, and hence has 1/3 of the data to decode, but 2/3 to "create". REDCODE RGB encodes 3x the data, but creates none. Which is quicker? - don't know yet.

    Graeme
    www.red.com - 5k Digital Cinema Camera
    Science enables stories. Stories drive science
    FLUT™, Image Processing, Colour Science and Demosaic Algorithms, REDRAY 4K delivery
    Reply With Quote  
     

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts