REDCode Header Layout

[Gavin Greenwalt]

12/14/07 4k 24fps File Header Layout:

------

Many more to come.

Watch this -> <- space.

 

[Kevin Halverson]

Here is what I have determined for the RDVS section (ReD Video frame Size) of the footer:

Following RDVS (ASCII) there are a group of 4 byte entries for each frame that represent the frame size.

Example

[52 44 56 53] [XX XX XX XX] [XX XX XX XX] [XX XX XX XX]

Where each [XX XX XX XX] is a frame size in bytes followed by the next frame size in bytes.

 

[Kevin Halverson]

Similar to the RDVS section, the RDVO section (ReD Video frame Offset) of the footer:

Following RDVO (ASCII) there are a group of 4 byte entries for each frame that represent the frame offset.

Example

[52 44 56 4f] [XX XX XX XX] [XX XX XX XX] [XX XX XX XX]

Where each [XX XX XX XX] is the frame offset in bytes followed by the next frame offset in bytes.

 

[Gavin Greenwalt]

Yep and RDVO is the position of each of those frames. and the last chunk of data is the position of the RDVO, RDVS, RDAS and RDAO indexes.

There's a picture coming. Don't worry.

 

[Kevin Halverson]

With these two groups of pointers, any in and out frame can be identified and all that is required after building the new output file is to add the correct entries to the RDVO and RDVS sections.

 

[Kevin Halverson]

This structure to the file system really makes sense. All that is needed is to keep track of the end of frame offset pointers for each frame and then write out the footer information after the last frame is finished.

Can't wait to see how they block the audio. I suspect that we will see the addition of a REDA entry in the header followed by a group of audio samples. I am betting audio samples in COB format with channels in a repeating pattern based upon the number of active channels. There may also be a channel active and sample rate entry.

Once I can see a .r3d with enabled audio I am in very familiar territory as I have spent the last 20+ years designing high end audio hardware.

 

[Kevin Halverson]

OK, this was fun, but I have to get up early tomorrow to go to Warner Ranch.

Thanks Gavin and everyone, a lot was learned tonight.

 

[Kevin Halverson]

Fun stuff, but a lot of work.

Off to the real job.

 

[Gavin Greenwalt]

Once I can see a .r3d with enabled audio I am in very familiar territory as I have spent the last 20+ years designing high end audio hardware.

GREAT! Because like I said this is the first time I've ever spent any time in a Hex editor beyond following very specific instructions for registry editing so I have no clue as to what I'm doing except "Hmmm that looks different.... but the same over here."