Dylan Reeve
Well-known member
I was reading the thread about a unique frame ID and it reminded me of something I'd been meaning to post here.
When tracking shot (RED specifically, or anything generally) it's necessary to be able to uniquely identify them. Camera, Reel and Clip Number are usually sufficient within the scope of a single project, but on a larger scale collisions are assured.
So I've been looking to make a simple unique identifier.
I know that the REDCINE XML format has a UUID, but I don't believe that it derived from clip metadata or other identifying features, but is a one-time UUID generated and associated with the clip for the purposes of tracking in relation to that XML file.
I'm wondering if it's worth looking at a semi-standardised and informal way of generating repeatable Unique Clip IDs for RED files.
Currently for one of my purposes I am generating a MD5 hash of a concatenation of the Clip Name, Shoot Date and Shoot Time, FPS and Frame Size. I feel that's pretty likely to be unique (barring the small likelyhood of MD5 collision from unique strings, but with strings derived from a similar set of data with the same length that's incredibly low).
Any thoughts, or interest.
The SolidStore will be generating clip databases as it ingests footage, which we will document for use by any interested party. It will include a clip ID (currently derived from that MD5 hash).
When tracking shot (RED specifically, or anything generally) it's necessary to be able to uniquely identify them. Camera, Reel and Clip Number are usually sufficient within the scope of a single project, but on a larger scale collisions are assured.
So I've been looking to make a simple unique identifier.
I know that the REDCINE XML format has a UUID, but I don't believe that it derived from clip metadata or other identifying features, but is a one-time UUID generated and associated with the clip for the purposes of tracking in relation to that XML file.
I'm wondering if it's worth looking at a semi-standardised and informal way of generating repeatable Unique Clip IDs for RED files.
Currently for one of my purposes I am generating a MD5 hash of a concatenation of the Clip Name, Shoot Date and Shoot Time, FPS and Frame Size. I feel that's pretty likely to be unique (barring the small likelyhood of MD5 collision from unique strings, but with strings derived from a similar set of data with the same length that's incredibly low).
Any thoughts, or interest.
The SolidStore will be generating clip databases as it ingests footage, which we will document for use by any interested party. It will include a clip ID (currently derived from that MD5 hash).