R3d Files structure

[William Wedig]

Hi all,

I was going to do some tests with the FCP support and was wondering if anyone knew a fast place to grab some zipped files with the most current file structure for how the Red stores it's r3d files.

I looked on Red Relay, but didn't see anything right away. Did I miss some somewhere?

Thanks.

 

[jbeale]

Shawn Nelson has a few R3Ds from build 14, although build 15 is current I don't know if the R3D file structure changed between 14 and 15.

http://redrelay.net/owners/0027/

 

[Thom Steinhoff]

The structure is not published but some who have reverse engineered it have said it is very well laid out, unencrypted and logical.

Red has discouraged this as it is still a bit in flux. That will change when they release an SDK in the next few months.

 

[Gavin Greenwalt]

No more help with R3D Files. I've learned my lesson.

 

[Yannick Sadler]

R3D file structure

R3D file structure

The structure is not published but some who have reverse engineered it have said it is very well laid out, unencrypted and logical.

Yes, I can confirm. From my own tests and software I have written the structure is base on the same approach as a Quicktime file with the atoms. They just use their own codes to identify blocks of data in place of standard QT code. Information like meta-data is unencrypted et easily extractable.

I see a few places where they might make some changes before releasing the SDK. Like the fact that block of video data are not of a constant length (nearly the the same but not quite) and it would help faster file seeking if those were padded so they all get the same length. That way you can predict where frame X is going to start in the file without going through all the headers of previous frames.

 

[jbeale]

That way you can predict where frame X is going to start in the file without going through all the headers of previous frames.

I think you're missing something . But the Red team has made it quite clear that they want to finish Redcode and support their own software, vs. dealing with the support consequences of unofficial 3rd-party programs. So I'll say no more.

 

[Yannick Sadler]

But the Red team has made it quite clear that they want to finish Redcode and support their own software, vs. dealing with the support consequences of unofficial 3rd-party programs. So I'll say no more.

That's what I was saying, things are going to move a bit. That's why I'm not giving away my tools yet.

 

[William Wedig]

Cool glad to know

Really all I wanted was a place to download some .zip files which opened to form a .RDC folder with an R3d and qt ref files. I found one on RedRelay (which was listed as being a r3d file but the link was to a .zip file).

Thanks guys!

 

[Alex Carr]

If I have a clip I've downloaded that the .R3d has been renamed, how can I create a valid structure for Crimson / Final Cut Log & Transfer. It seems neither want to work very well, however everything is smooth when files are untouched...

I dont ever have any plans to change the files around, I just have a few files that dont work well, One way or the other there has to be some sort of fix? Is there any way Red Alert / Redcine can export XML that might reveal original camera info & clip name?

On Files that the R3d hasn't been renamed I can copy the file name and create the folder, Final Cut will then import them normally...