Issue with renamed R3D files

[Brad Hawkins]

I've found that there are times when it is necessary to rename R3Ds in finder (for various workflow reasons), the problem is that Storm seems to ignore this new name. Upon import the clip has the original camera generated filename (A019_C156_01165C_001.R3D for example).

I can open the same file in RedCine-x, Nuke or other programs and all use the new filename, but Storm seems to resort to a baked in, camera generated filename that must be somewhere in the metadata.

 

[Uli Plank]

Sorry, but I don't consider renaming R3D files a good idea, never ever. Could you please explain the workflow reasons?

 

[Brad Hawkins]

Sorry, but I don't consider renaming R3D files a good idea, never ever. Could you please explain the workflow reasons?

I know what you mean, and woud agree for a normal production, but we're shooting VFX elements to build and asset library. For example imagine a shot of fire, we'll let the camera roll for a couple of minutes and then later chop that up into several clips. And the only way to do that is to duplicate the clip in RedCine-X or Storm.

Then when we export those duplicated and trimmed clips we have several files with the exact same name but the folders are named like this:

A016_C021_1228AN.RDC
A016_C021_1228AN_S000.RDC
A016_C021_1228AN_S001.RDC
A016_C021_1228AN_S002.RDC

And as I said, all those folders contain a file called A016_C021_1228AN_001.R3D. Obviously it's not too smart to have a bunch of files with the same filename, even if the folders are named differently.

Since these are assets that will be re-used on lots of different projects, we'd like to be able to rename them to something useful like:

FireElement_001
FireElement_002
etc.
etc.

(Disclaimer: we have been duplicating and exporting mostly in RedCine-X, but only because we started the project before Storm had that feature turned on)