Click here to go to the first RED TEAM post in this thread.   Thread: Large REDCINE X Project Crashing....

Reply to Thread
Page 1 of 2 12 LastLast
Results 1 to 10 of 17
  1. #1 Large REDCINE X Project Crashing.... 
    Senior Member
    Join Date
    Sep 2008
    Posts
    117
    Build 104.
    20+Hours of R3D footage on External Firewire Drive.
    Loaded All footage into bin 1
    Dropped one clip on timeline, started playing with controls and it crashes.
    Happened 3 times in a row now.

    I have the crash report that opens after a program crashes if that helps.

    Any suggestions RED team?
    Reply With Quote  
     

  2. #2  
    Senior Member
    Join Date
    Mar 2009
    Location
    Burbank, Ca
    Posts
    465
    Quote Originally Posted by Aaron Hucker View Post
    Build 104.
    20+Hours of R3D footage on External Firewire Drive.
    Loaded All footage into bin 1
    Maybe don't import 2 terabytes of R3D's into the program at once...

    All that stuff is on one external FireWire drive?
    Reply With Quote  
     

  3. #3  
    Senior Member
    Join Date
    Sep 2008
    Posts
    117
    Its a OWC Mercury Elite Pro 2TB RAID Drive, now, I understand it's Firewire so Performance isn't going to be impressive.

    The program should be able to handle that amount of footage. If it's a drive issue, thats a different story, yet both are reasons why I am here asking for an answer.
    Reply With Quote  
     

  4. #4  
    Senior Member
    Join Date
    Mar 2009
    Location
    Burbank, Ca
    Posts
    465
    Quote Originally Posted by Aaron Hucker View Post
    Its a OWC Mercury Elite Pro 2TB RAID Drive, now, I understand it's Firewire so Performance isn't going to be impressive.

    The program should be able to handle that amount of footage. If it's a drive issue, thats a different story, yet both are reasons why I am here asking for an answer.
    You say you have 20+ hours of R3D's on a 2TB drive, but RC36 4k 2:1 at 24fps runs at about 100 gigs an hour, 4k 16:9 about 130 gigs/hour.
    Reply With Quote  
     

  5. #5  
    Senior Member
    Join Date
    Sep 2008
    Posts
    117
    Ok so my math may be off.


    1.7TB (roughly, to be safe) of 4K 2:1 RC36 24fps.
    Reply With Quote  
     

  6. #6  
    Don't you love it when you're asking for help and get skepticism and tangental discussion instead - it's the best. It's like asking Howard Stern for directions to the mall.
    Reply With Quote  
     

  7. #7  
    Senior Member
    Join Date
    Mar 2009
    Location
    Burbank, Ca
    Posts
    465
    Quote Originally Posted by Nicholas Shields View Post
    Don't you love it when you're asking for help and get skepticism and tangental discussion instead - it's the best. It's like asking Howard Stern for directions to the mall.
    The point being that the problem probably wouldn't be occurring were you not a) using beta software, b) importing 2 terabytes at once, and c) trying to implement a workflow that doesn't really make sense in the first place.
    Reply With Quote  
     

  8. #8  
    With all due respect Joe, a) the thread/forum is about making Redcine X better - so putting it through it's paces and asking about it pretty much par for the course, b) a program that transcodes footage shouldn't be crippled by how much you throw at it - what's going to happen when the new cameras are release and the data rates go through the roof? c) without anything other than the original post, how do you know whether or not the workflow makes sense? If you can't be constructive and contribute, don't waste your calories.

    Nick.
    Reply With Quote  
     

  9. #9  
    Member Frederick Giles's Avatar
    Join Date
    Jul 2009
    Location
    Fredericton, NB
    Posts
    55
    I think we need some more info, what computer are you using? how much of the hard drive is used up using the footage? the drive may not have enough free space to perform adequately. Have you tried editing with a smaller amount of footage? I can't imagine trying to grade and transcode 20 hrs of footage without doing some smaller tests first.
    Reply With Quote  
     

  10. #10  
    I, for one, have privately tried to 'break' REDCine-X by opening up entire shows, just so that I would know how much I can open with a client standing over my shoulder waiting for playback / review. I have been very pleasantly surprised that I'm consistently able to open up entire shows worth of R3Ds (typically either commercials or music videos) with 30-50 rolls of R3Ds and not had a crash. It's likely due to the sheer volume of data you're trying to open, or perhaps to the limitations of your harddrive and hardware (you're suddenly having REDCine-X request a huge amount of data, and your drive, CPU, and RAM all have to be able to keep pace and feed it).

    I'd be interested to see what happens if you simply highlighted each R3D folder individually and then performed a "get info" operation, thus causing your system to access all of that data at once. My guess is that your system might also crash if you're using the same hardware.

    In any case, we all certainly want to be able to rely on REDCine-X to handle large volumes of data when necessary. But we also have to be reasonable about the fundamental limitations of our hardware and of software throughput in general.

    Best,

    - Jordan
    Jordan Livingston

    Leading a double life...

    IATSE Local 600 ICG DIT
    www.DIGILOID.com

    Independent Filmmaker
    www.JLPMOVIES.com
    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