IMO .RSX needs to go away as soon as possible, and be replaced by a "side-car" XML file in the .RDC and here is my case:
Today, we started processing a LARGE job which was shot with multiple Red cameras, on several workstations with RED Rocket cards. PLINY, who heads up the post at Offhollywood, immediately noticed that the meta-data for the media (collected via RedCSV) indicated that all footage was shot in the same color space/gamma space - yet RocketCine-X showed different color space/gamma space settings for the cameras.
We finally figured out that Rocketcine-X defaults to the .RSX - NOT the meta-data. This really reads like a recipe for disaster to me - and it got me all wound up again on an issue that is near and dear to my heart. I want .RSX to go away and I want an XML riding with my R3D. Inside that XML ... I want a LUT.
Another example - I gave a presentation with Dennis Radeke form Adobe on RED Adobe workflows recently. During the Q&A - a gentleman (who it turns out works at DELUXE) asked "does Adobe support .RSX?" The answer was "no". But let's look at the question again -
What he really was asking was ... "is there a RED 'look' file that I can set in a RED software utility that will carry across 3rd party (Adobe) post workflow solutions?"
The answer is ... sadly ... no.
There have been a few mentions from the RED on some threads about standarising a "look" file spec in the SDK - and I know I have personally banged my spoon on my high-chair for a UNIFIED FILE SPEC between camera and RED software utilities for a long time.
When the new color science appeared in Build 20 - I was sure we'd see a "look" file spec that allowed us to move from camera to software - and software to camera. But we continue to move forward with .RSX. Third parties (Clipfinder, etc.) build tools that work with .RSX.
Suddenly ... a "short term" solution becomes "default standard" - and everyone spins around it.
I'll step back a moment and spell out EXACTLY what I want. Because ... I think you want it too. I want RED to kill .RSX. Thanks, we'd have some good times ... but it's over. You need to go. It's not you .. it's me ... whatever ... it's over.
I want to be able to create a LUT in any RED software app - that can be loaded INTO THE CAMERA.
I want to be able to READ a LUT from an .R3D file header - and apply that to another shot, etc.
I want a "side-car" .XML file inside the RDC folder.
The camera would write this file on FORMAT.
The camera would write meta-data values into this .XML file during POST process when camera stops record.
Now, we have am .XML file that TRAVELS with the shot. We cab EDIT, ADD, ALTER the .XML file - and never touch the .R3D files.
SCENE, SHOT, TAKE
yeah ... you know ... the MOST IMPORTANT meta-data of narrative film's post pipeline.
We still can't put it anywhere.
If RED would standardized on a "side-car" .XML file inside the .RDC - we could all ADD whatever elements we wanted - in a fully extensible, non-destructive way.
Here is where we'd write SCENE, SHOT, TAKE. Annotate.
Third parties could adapt much faster.
Doors would open to more powerful post workflows.