Click here to go to the first RED TEAM post in this thread.   Thread: Redcine-X Error When Trying to Export - HELP

Reply to Thread
Results 1 to 5 of 5
  1. #1 Redcine-X Error When Trying to Export - HELP 
    Senior Member
    Join Date
    Jan 2011
    Location
    San Francisco
    Posts
    815
    Attempt to export all clip from the bin to ProRes 4444.

    Note: The .r3d clips have had LUTs applied to them in camera.

    Redcine X gives me error: "Transcode error type 0" and stops the Export.

    Redcine X Release Build 15



    This is all the info I have right now from the client (they are the one having the issue).

    Hoping to have a fix for them by tomorrow.

    Any help would be GREATLY appreciated.

    I'll try to get more info about the workflow if needed.

    Thanks!
    Daniel Soderberg
    Last edited by Daniel Soderberg; 08-16-2012 at 10:28 PM.
    Reply With Quote  
     

  2. #2  
    Senior Member
    Join Date
    Jan 2011
    Location
    San Francisco
    Posts
    815
    Anyone???
    Reply With Quote  
     

  3.   Click here to go to the next RED TEAM post in this thread.
  #3  
    Red Team
    Join Date
    Sep 2009
    Location
    Irvine, CA
    Posts
    638
    Hard to say without verbose log files. Have them send to redcinex at red if you can.
    They should also try rolling back to Build14 if the need is urgent.

    Thanks,
    David
    Reply With Quote  
     

  4. #4  
    Senior Member
    Join Date
    Jan 2011
    Location
    San Francisco
    Posts
    815
    Thanks David!

    It looks like the issue was that there was only about 1 GB of space available on my clients main drive -_-
    After clearing up space on the main drive where Redcine X is installed, problem went away. Good to know one thing that error can mean.
    Reply With Quote  
     

  5.   This is the last RED TEAM post in this thread.   #5  
    Red Team
    Join Date
    Sep 2009
    Location
    Irvine, CA
    Posts
    638
    Thanks Daniel,

    Still send logs if you can -- thats exactly the type of error for which we should be providing a clear message, and I'd like to know exactly why that didn't work as intended.

    Thanks,
    David
    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