scottsandford
Member
Hi There,
It's not really a complaint as much as a suggestion to rectify a slight annoyance with RCX.
At the moment, when one makes adjustments to the look of an R3D file in RCX, one is presented with two options: choose a master RMD folder - or save the RMD with the original footage.
I would suggest that there is another (perhaps more user-friendly) option that you might want to consider implementing, that is:
Can the Master RMD folder option be related to the project file, rather than the application?
For example, let's say that I'm responsible for adjusting the look of the RAW footage to achieve some look after it's been shot (either as DIT, DoP, Colourist, etc). At the time of my corrections, I'm referencing a file that will live in a folder structure of RAW footage that will be copied many times into many locations (or perhaps has been already), but at some point, I should be able to load all of the footage into an RCX project from the folder structure present on my system and see my updates in all the different locations IF I have the same RMDs present and the same project file and the same footage.
I believe it will be far simpler to share and replicate the adjustments to the RMDs by storing them in a single folder that is referenced by the PROJECT file location, rather than defined in the application preferences - so that for PROJECT 1, the folder is RMDFOLDER1 and for PROJECT2 the folder is RMDFOLDER2.
I could then email (or share via Dropbox, etc) a copy of the project and the folder of RMDs to the client, knowing that if they opened up the project, pointed to the RMD folder (and synced whatever files were not in the correct place on their system) that the RMDs would be applied to the RAW footage based on the copy of the RMD in the folder I sent…project by project.
I'm sure there will be ways to break the system
but at least by making the RMD folder referenced at the project level, it would be easier to manage and communicate to other users who may not be so good at sorting those things out.
At the moment - I would have to change the folder at the application level, rather than the project level, in order for that to happen, then instruct someone else to do it on their system - and there is no guarantee that that will happen consistently - and then remember to change it again when I open up a different project that has different (unrelated) footage.
Defining it at a project level will take away at least some of the hassle.
Just a thought.
Scott
PS - one other suggestion would be to have an option for RCX to open with the last project viewed as a time saving option.
It's not really a complaint as much as a suggestion to rectify a slight annoyance with RCX.
At the moment, when one makes adjustments to the look of an R3D file in RCX, one is presented with two options: choose a master RMD folder - or save the RMD with the original footage.
I would suggest that there is another (perhaps more user-friendly) option that you might want to consider implementing, that is:
Can the Master RMD folder option be related to the project file, rather than the application?
For example, let's say that I'm responsible for adjusting the look of the RAW footage to achieve some look after it's been shot (either as DIT, DoP, Colourist, etc). At the time of my corrections, I'm referencing a file that will live in a folder structure of RAW footage that will be copied many times into many locations (or perhaps has been already), but at some point, I should be able to load all of the footage into an RCX project from the folder structure present on my system and see my updates in all the different locations IF I have the same RMDs present and the same project file and the same footage.
I believe it will be far simpler to share and replicate the adjustments to the RMDs by storing them in a single folder that is referenced by the PROJECT file location, rather than defined in the application preferences - so that for PROJECT 1, the folder is RMDFOLDER1 and for PROJECT2 the folder is RMDFOLDER2.
I could then email (or share via Dropbox, etc) a copy of the project and the folder of RMDs to the client, knowing that if they opened up the project, pointed to the RMD folder (and synced whatever files were not in the correct place on their system) that the RMDs would be applied to the RAW footage based on the copy of the RMD in the folder I sent…project by project.
I'm sure there will be ways to break the system
but at least by making the RMD folder referenced at the project level, it would be easier to manage and communicate to other users who may not be so good at sorting those things out.At the moment - I would have to change the folder at the application level, rather than the project level, in order for that to happen, then instruct someone else to do it on their system - and there is no guarantee that that will happen consistently - and then remember to change it again when I open up a different project that has different (unrelated) footage.
Defining it at a project level will take away at least some of the hassle.
Just a thought.
Scott
PS - one other suggestion would be to have an option for RCX to open with the last project viewed as a time saving option.