Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Red's Clip Naming Fiasco ...

Rick Darge

Banned
Joined
Dec 29, 2006
Messages
3,775
Reaction score
0
Points
0
Age
44
What do I need to do?

I shot a short film a few days ago ~ We used 8 CF cards and 1 Red-raid. 2 of the CF cards have duplicated names since the mags didn't rollover I guess. The Red-Raid has the same file names as my 1st CF card, it didn't intelligently rollover with the mag change.

We began the day using the CF cards, then switched to the Red Raid after those filled up.

What do we need to do to ensure proper file naming for shoots? I usually format all my cards right before I roll on them, not in one sitting, so maybe that has something to do with it?
 
I had the same issue a week ago. At some point the card numbering wend back to 01 (when it should have been at 05) - we caught it fairly quickly, but that still meant we had duplicate clips with A01 and A02 naming.

The weirdest part, however, was using the RED Drive have having it work fine (as B001) but later on in the day, when we went back to using it after having used cards for a while, it recorded clips as A001 (meaning more duplicate A001 clips). The strangest part of this is that the A001 clips are in the B001_080314.RMD directory...

I've emailed RED directly and ask that the clip naming convention be changed in such a way that the filenames don't conflict in this way. This would mean adding another couple of characters to the filename to ensure uniqueness. They haven't made any commitments, but at least I know they heard my request.

I have yet to find a way to relabel the clips effectively. Instead I have built my conforming tools in a way that they can support duplicate clip names,
 
I've emailed RED directly and ask that the clip naming convention be changed in such a way that the filenames don't conflict in this way. This would mean adding another couple of characters to the filename to ensure uniqueness. They haven't made any commitments, but at least I know they heard my request.
Well ... I gotta say ... SCREW THE DATE STAMP - give me a TIME STAMP in the last characters of the filename.
 
The first Build of 15 went backwards in terms of stopping duplicate file names. I will test the new 15 build this week.

That's what happens in a beta. Did we mention not to use it in production?
 
That's what happens in a beta. Did we mention not to use it in production?

Mention it all you want - won't stop me. Made two features on alpha builds.

I still think TIME STAMP would end much of this madness.

Did I mention that aside from filename bugs - I love build 15.
 
Mention it all you want - won't stop me. Made two features on alpha builds.

I still think TIME STAMP would end much of this madness.

Did I mention that aside from filename bugs - I love build 15.

Hey Mark, don't use beta builds for production.
Hey Mark, don't use beta builds for production.
Hey Mark, don't use beta builds for production.
Hey Mark, don't use beta builds for production.
Hey Mark, don't use beta builds for production.
Hey Mark, don't use beta builds for production.
Hey Mark, don't use beta builds for production.

:)
 
Hey Mark, don't use beta builds for production.
Hey Mark, don't use beta builds for production.
Hey Mark, don't use beta builds for production.
Hey Mark, don't use beta builds for production.
Hey Mark, don't use beta builds for production.
Hey Mark, don't use beta builds for production.
Hey Mark, don't use beta builds for production.

:)

production is the ultimate beta test.:devil:

Now ... about the TIME stamp ...
 
production is the ultimate beta test.:devil:

Now ... about the TIME stamp ...


LOL... I have to agree with Mark. We've done more than our fair share of Ultimate Beta Testing.

Now on to that naming convention. We've had issues with this ever since Build 14. If you start a project at one resolution (e.g. 4K), change to another resolution (e.g. 2K), and then format a new card before changing back to the old resolution, the mag # will reset itself to A001.

I think there are more than a few ways to solve the issue, but the best fix would be to allow the operator to reset the mag # instead of the camera. Much like the way we can force a mag # now, except we would force the mag back to A001 and allow it to count back up from the start. This way we don't have to worry about renaming a lot of files or using Force Reel every time we format a card.

Mark's idea works great as well, but you still get semi-duplicate names (e.g. Mag1 = A001_C001_12:31:06pm, Mag2 = A001_C001_12:35:06pm). Even though the time stamp makes the file names different, you still get the prefix A001. Which if this happens a lot, it can be very frustrating to see A001 on about 10 different mags in one day of shooting (especially if you're editing these files straight from the proxies).

-Kyle-
 
Date and Time, or sometime derived from that would be the best. So A001_C001_080324_142411 for example. Although another option would be just to stick a couple of letters on the end that are derived from the timestamp or something - they don't have to be human-readable.

At the moment if you have a reset during a single day the base filename will be the same (A001_C001_080324 for example). Depending on how you offload clips you could well end up overwriting clips from the earlier card.

I think that the camera should never reset the counter itself, that should be a user-operation. And the start point should be able to manually set (to allow counting to be continued from where it had been left off previously).
 
Reel number sequencing

Reel number sequencing

Bug fixed. i.e camera should no longer be resetting the reel number based on a resolution change. Try Build 15 2.1.7

This reel reset bug was originally fixed in Build 12 or 13, for some reason it reappeared in Build 14 Beta and 15 Beta.
 
Bug fixed. i.e camera should no longer be resetting the reel number based on a resolution change. Try Build 15 2.1.7

This reel reset bug was originally fixed in Build 12 or 13, for some reason it reappeared in Build 14 Beta and 15 Beta.

So this build absolutely won't duplicate names? How does it do it?
 
Reel Number sequencing

Reel Number sequencing

So this build absolutely won't duplicate names? How does it do it?

No, what it does it re-assert the logic that the ONLY time that the reel number should reset is a) on a Project Frame Rate change or b) on a manual Force Reel
 
Back
Top