Click here to go to the first RED TEAM post in this thread.   Thread: REDCINE-X Professional 13.21174 - Avid Export Failed with RED ONE Material

Reply to Thread
Results 1 to 4 of 4
  1. #1 REDCINE-X Professional 13.21174 - Avid Export Failed with RED ONE Material 
    Hi Everyone,

    We have just noticed a fairly major bug with REDCINE-X Professional - or at least, we assume it's a bug.

    REDCINE-X Pro works FANTASTICALLY for exporting Avid MXF/AAF material when you shoot with an EPIC or Scarlet. Everything works as advertised. In goes an R3D, out goes an MXF, AAF and ALE - easy!

    However, we have just noticed that it doesn't work with RED ONE material - and we were forced to render out DNxHD36 Quicktimes.

    We have tried a variety of different machines (running both 10.6.8 and 10.7.3) - and went back a few versions of REDCINE-X Pro to see if it was a new bug - but couldn't get it to work. We also tried removing REDCINE-X Pro completely (i.e. trashing preferences), as well as installing it as a fresh install on another machine.

    In this example, we're running REDCINE-X Professional 13.21174 Beta on a MacPro with a RED Rocket, on 10.6.8. The test footage we're using is from a RED ONE with a MYSTERIUM-X sensor, recorded at 4096x2304 REDcode 9:1 on the 31.6.16#31 firmware.

    When exporting an Avid AAF & MXF file (1080p/25 DNxHD 36 8-bit) - instead of creating the usual AAF file, and generating an ALE - it just gives you an XML file (see below for contents of file) along with the MXF. However, when you try and open the MXF files within Avid - they're corrupt.

    By corrupt I mean, that when you view the newly created MXF files in Avid's Media Tool - the duration for each media file is 12:00:00:00, and then when you try and view the Master Clip in the viewer Avid says "Exception: The sequence or one of its source elements is too long to be played". The first frame of the video is visible - but everything else after the first frame is corrupt. The file sizes of the MXF's look decent - so it must be doing the debayering correctly - but screwing up at the end.

    Has anyone else noticed this? Has anyone been able to get Avid AAF & MXF exports to work out of REDCINE-X when using RED ONE material?

    Again - EPIC and Scarlet footage works fine! We do this on a near daily basis - however, RED ONE footage just seems to fail for no apparent reason.

    Any information would be greatly appreciated!

    Thanks for your time!

    Best Regards, Chris!

    ----

    XML FILE THAT IS CREATED WHEN USING THE AVID MXF & AAF PRESET:


    <?xml version="1.0" encoding="ISO-8859-1" ?>
    <AmtMediaAttributes>
    <format>
    <mediaFormat>Compressed</mediaFormat>
    <signalStandard>SS_274M_P</signalStandard>
    <dropFrame>kAVXFalse</dropFrame>
    <compressionType>Avid::HD::DNxHD</compressionType>
    <dnxhdMbitsPerSecond>36</dnxhdMbitsPerSecond>
    <dnxhdComponentBits>8</dnxhdComponentBits>
    </format>
    <timecode>01:42:14:03</timecode>
    <bitRateMode>CONSTANT BIT RATE</bitRateMode>
    <framesPerSecond>25</framesPerSecond>
    <storedHeight>1080</storedHeight>
    <storedWidth>1920</storedWidth>
    <audioTracks>1</audioTracks>
    <audioBits>24</audioBits>
    <audioBitRate>48000</audioBitRate>
    <audioCompressionType>Avid::PCM::Uncompressed</audioCompressionType>
    <tapeName>A001_C001_04205A</tapeName>

    <extendedAttributes></extendedAttributes>
    </AmtMediaAttributes>

    ----

    LOG FILES:


    REDCINE-X PROFESSIONAL Build 13.21174 Beta Mac 64bit Public Release
    MacOSX Snow Leopard 64 Little Endian
    Using R3DSDK version 4.4 build 20A03 dated 20120314
    Using Qt version 4.8.0, compiled against 4.8.0
    RedRocket: 0 Decode ( Driver: 1.4.19.0 Firmware:1.1.16.5 Serial#: 31110331 ) PCIExpress( Ok: True Speed: 250 Width: 64 Count: 8 ) Status(4720, 43.000000 41.000626, 1.001556 1.561868 2.489631 3.258824 5.187274 12.182498 0)
    Maximum memory percentage changed to: 75%
    REDCINE-X PROFESSIONAL Build 13.21174 Beta Mac 64bit Public Release
    OpenGL Information
    Vendor: NVIDIA Corporation
    Renderer: NVIDIA GeForce GT 120 OpenGL Engine
    Version: 2.1 NVIDIA-1.6.36
    SL Version: 1.20
    GL Initialized using shader based rendering.


    redexport Apr 16 2012 15:21:57 Mac 32bit Public Release
    redexport: init msg received.

    Avid Output Filename: /Users/assistanteditortwo/Desktop/a001_c001_04205a
    redexport: total setup time = 1369 ms
    redexport: frame: 0
    redexport: frame: 1
    -- REMOVED ALL THE FRAMES IN BETWEEN TO KEEP POST SIZE DOWN --
    redexport: frame: 1331
    redexport: stop msg received.
    Avid Exporter::exportAudio - Samples Read: 2557440 Samples Written: 2557440 /NumAudioChan = 2557440 Expected Samples: 2555520
    Reply With Quote  
     

  2.   This is the last RED TEAM post in this thread.   #2  
    There's a known bug with exporting 25 fps clips with audio to Avid in REDCINE-X PRO.

    We hope to have this fixed in the near future.
    Reply With Quote  
     

  3. #3  
    Thanks for the update Grant.

    As a workaround we are now exporting the MXF material without audio, doing a separate BWF export to get the audio out, then auto-syncing in Avid. Seems to work fine.

    We've been using REDCINE-X Professional since it's release, and have only just noticed this! How funny! I didn't release it's been going on for so long:

    http://www.reduser.net/forum/showthr...l-doesn-t-work
    Reply With Quote  
     

  4. #4  
    Fixed in REDCINE-X Pro Build 14. Thanks RED!
    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