Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Large REDCINE X Project Crashing....

A

Aaron Hucker

Well-known member
Joined
Sep 1, 2008
Messages
124
Reaction score
0
Points
0
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?
 
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.
 
Aaron Hucker said:
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.
Click to expand...

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.
 
Ok so my math may be off.


1.7TB (roughly, to be safe) of 4K 2:1 RC36 24fps.
 
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.
 
Nicholas Shields said:
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.
Click to expand...

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.
 
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.
 
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.
 
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
 
Thanks for the input...

Just for the record (although I guess I should have stated it before) I am very aware this is BETA, however, that doesn't mean I should sit back and think that I am asking anything out of what I would consider 'ordinary' for a program of this nature. And as Nick pointed out, data rates are going to be higher, so the demands on the program/cpu/memory are going to be higher.

As requested, here are the specs of my machine.
OSX 10.5.8
2x 3.2 GHz Quad-core Intel Xeon
8 GB 800 MHz DDR2 RAM
2TB OWC MERCURY ELITE PRO FIREWIRE RAID.

Here is a step by step on how this all came about, just incase others try to re-create this.

1. Load individual folders of footage into Bin 1 (Each folder represents a day of shooting) Making all of my footage in Bin 1.
2. Save Project.
3. Close RCX.
4.Open RCX and Open Project.
5. Drop any clip in Player and start grading
6. Crash.

Anyone from RED have any insight to this?

Thanks.
 
Quite possibly it's the drive itself. You're saying you've got 1.7 TB of R3D's on a 2TB drive. Formatting that drive takes up about 140 gigs, so your drive capacity is actually 1.86 TB. The standard rule of thumb is to leave the drive with about 20% of empty space, otherwise you risk drive failure. Which means your 2 TB drive is really only good for about 1.5/1.6 TB of storage before you start running into potential performance issues.

Also is it a brand new, previously unused drive, and if not, did you reformat it before using it for your current project, or just delete what was previously on it?

Finally there is the issue of how the R3D's were transferred onto the drive in the first place. I always transcode from drives whose R3D's were pulled directly from the camera drives/CF cards with dedicated software like ShotPut Pro or R3D Data Manager, I never just "drag and drop" R3D's.

Sorry if this all sounds off topic or condescending, but having 1.7 TB on a 2 TB drive is a red flag that says there's basic data management issues you may not be aware of.
 
Aaron Hucker said:
As requested, here are the specs of my machine.
OSX 10.5.8
2x 3.2 GHz Quad-core Intel Xeon
8 GB 800 MHz DDR2 RAM
2TB OWC MERCURY ELITE PRO FIREWIRE RAID.
Click to expand...

Another big no-no in my opinion is using RAID 0 for backing up R3D's. The whole idea behind backing up is having everything on physically separate drives so that if one fails, the other is still good. With RAID 0, if one of those 2 raided-together drives inside that enclosure fails, you lose everything on both drives, effectively doubling the chances of failure. RAID 0 is the opposite of what you want for backing files up, it's really for editing bandwidth, not security. And since it's FireWire 800 anyway, it's redundant, because it's not going to go any faster than FW 800 does.
 
I understand it may be a full drive issue, it is something I'll look into.
The drive was brand new, and freshly formatted for the project. The R3D's are exact duplicates of the original ones on the RED DRIVE.

As for the backup comment... I never mentioned that I had only one copy of the R3D's and they were on a RAID 0, so wherever you are drawing these conclusions from is beyond me, but you can refrain if you don't mind staying on topic.

Joe, I appreciate if you're are sincerely trying to help, but this isn't a question of wether or not I understand the concept of R3D data management, I have been working with Our RED ONE and ALL of its files since May 2008, I think it's safe for me to say I understand how our files work in MY work environment. However, I do not quite fully understand the problems I am encountering with a NEW piece of Beta software.

I'll continue to run tests on what amounts work, and, in the meantime I'll believe that I am doing us all a favor but pushing RCX to the limits with the amount of footage I am placing in it on external drives, because I wont be the only person who's expecting this to be possible.
 
Aaron Hucker said:
I never mentioned that I had only one copy of the R3D's and they were on a RAID 0, so wherever you are drawing these conclusions from is beyond me, but you can refrain if you don't mind staying on topic.
Click to expand...

And I never said that you only had one copy. The conclusion is drawn from the fact that the drive is a "2TB OWC MERCURY ELITE PRO FIREWIRE RAID", so you're formatted to either RAID 0 or RAID 1, and 1.7 TB wouldn't fit if it was RAID 1, hence RAID 0. And I am staying on topic - the topic is "Large REDCINE X Project Crashing....", and the reason you're crashing is probably the drive.
 
Best thing to do is to turn on verbose logging, load the project and then please send us the log file.
 
You must log in or register to reply here.
Back
Top