Hi Tangier,
My remark was about the file properties, not about something else, so no worries, I’m very much approachable!
It’s a strange way of thinking, but once you grasp the logic, it all makes sense. (And it sucks that a lot of terminology is used double / wrong / badly rounded, that does not help…)
Wave Agent displays the SAM somewhere in the middle of the lower part of the interface.
What it means with ‘keep start TC’, is that the TC numbers will stay the same even when you change the TC rate:
This is in general a VERY bad idea to do, as then the numbers have no relation anymore with the internal clock.
So, as I told you, renaming ‘should’ be fine, but be VERY VERY afraid if WA tells you it needs to update the metadata.
UNLESS you are very sure, do NOT press ‘save’, and in all cases, UNCHECK ‘keep start TC’, as it will keep the start TC, but might change the actual timestamp. Confusing? Not so much, read on.
Samples after midnight means EXACTLY what it says. But, it is midnight when the TC generator of your BWF recorder is reset to 00:00:00:00
(And luckily nowadays close to anyone shoot TOD, so it sorta kinda matches the wall clocks.)
Oh, I call it Samples AFTER midnight, Sound Devices calls it Samples SINCE midnight. It’s the same.)
Now, SAM is the same as TC, but not in HH:MM:SS:FF format, but as an absolute frame number.
(Hence I call it time STAMP, not time CODE.)
In your case, on renaming, the file has also a Time Stamp for being a digital file. (Actually, it has two, ‘created’ and ‘modified’.) This is confusing, and probably the ‘modified’ will update / change after WA renamed it (as it was indeed modified) but has nothing to do with the internal BWF SAM.
And, if you record @ 48K, you have 48.000 ‘audio frames’ per second.
Thus, if you start recording when your recorder displays 00:01:00:00 (one minute after midnight), the SAM as written in the file is 2.880.000 (60 seconds times 48K samples)
This in not very well human readable of course, especially when it gets later.
At 23.00 PM, the number is
23 hours * 60 minutes * 60 seconds * 48000 samples per second makes
39.744.000.000
This sucks for humans, so any device / software will calculate it back to TC, that you can read in the blink of an eye
(23:00:00:00)
Now, as you know, the number of video frames as well as the play speed differs between the video frame rates.
You like to shoot 23.976, so to divide the large number back to TC, there is a 0.1% difference, making some 83 seconds difference.
The speed as recorded (thus, how the math should be done to show you the TC numbers as intended, is most of the time baked into the BWF file. But it is up to the device / software if it will do the math based on that value, or another one. (Depending on what you want to do with the file / will solve problems.)
In theory, editing software will NOT use the calculated TC, but the samples itself. This way you can sync up / place your audio on the timeline sample accurate instead of frame accurate. (That makes a big difference.)
So, depending on the setup:
The file is the same, the actual values are the same, but the TC displays are different, making up for lots of stress sometimes ☺
(And I’m only touching the surface of more fun that can be had with these relative very simple file format…)
Hth,
Bouke
http://www.videotoolshed.com