Mark L. Pederson
REDuser Sponsor
I've been thinking about the possibilities of a side-car XML file for R3Ds for long time - so I'm totally excited about the possibilities for RMD.
One thing I think could be interesting is if the RMD file actually contained all the parameters for every occurrence in a PROJECT(s) - including correlation to a specific EDL or XML timeline(s) w/event #'s and TC location of the shot in the timeline.
Here's an example:
Imagine that parts of the same shot exist three times in the timeline of a project.
While editing - these shots would change - in-points, out-points, geometry, and where in the timeline the shots exist (event # + TC).
Color could be adjusted in an RCX, NLE, VFX or DI application.
Now imagine if third party apps added a "update RMD" action - you make some changes to an edit (or color) - then press "update RMD" and that action writes the updated parameters to all the RMD files inside the RDCs in the timeline/project.
Now - this RDC folder, all by itself, (because of the RMD side-car file) knows exactly where the shot is used in a specific project and specific edit - what the geometry and color changes are - and even the name of the application, date and time and username that created those parameters.
Now the actual CLIP becomes super-intelligent with respect to a project - and even multiple projects.
What would be interesting - would be to also have a MASTER PROJECT R3D META-DATA DATABASE - a single XML file for a PROJECT - that contains all the meta-data in the CLIPS (RMDs) used in the project.
Now ... if two people work individually on the same R3D (using copies of the RDC) - their separate data would get collected into the MASTER PROJECT R3D META-DATA DATABASE - and one could "SYNC" back to the RMDs in any set of RDCs.
Anyway ... there are some very cool possibilities here.
One thing I think could be interesting is if the RMD file actually contained all the parameters for every occurrence in a PROJECT(s) - including correlation to a specific EDL or XML timeline(s) w/event #'s and TC location of the shot in the timeline.
Here's an example:
Imagine that parts of the same shot exist three times in the timeline of a project.
While editing - these shots would change - in-points, out-points, geometry, and where in the timeline the shots exist (event # + TC).
Color could be adjusted in an RCX, NLE, VFX or DI application.
Now imagine if third party apps added a "update RMD" action - you make some changes to an edit (or color) - then press "update RMD" and that action writes the updated parameters to all the RMD files inside the RDCs in the timeline/project.
Now - this RDC folder, all by itself, (because of the RMD side-car file) knows exactly where the shot is used in a specific project and specific edit - what the geometry and color changes are - and even the name of the application, date and time and username that created those parameters.
Now the actual CLIP becomes super-intelligent with respect to a project - and even multiple projects.
What would be interesting - would be to also have a MASTER PROJECT R3D META-DATA DATABASE - a single XML file for a PROJECT - that contains all the meta-data in the CLIPS (RMDs) used in the project.
Now ... if two people work individually on the same R3D (using copies of the RDC) - their separate data would get collected into the MASTER PROJECT R3D META-DATA DATABASE - and one could "SYNC" back to the RMDs in any set of RDCs.
Anyway ... there are some very cool possibilities here.
Last edited:
