MIOConsole3d Session
348
The record engine doesn’t really have a concept of takes once they hit the disk, so it keeps track of the
take number, and, if you have "New folder per take” enabled, generates the directory name for the Take
folder and the Track file names based upon the templates you have set up and the current take number
(and other dynamic metadata).
It then creates the folder (if you have "New folder per take” checked) and the files for the take when the
take is started.
If any of the files or folders that it attempts to create already exist, then it appends a disambiguating
sequence number to the end of the name to ensure that nothing is overwritten.
If, for example, you have the following Takes already recorded in your Record folder:
Take 0100
Take 0101
Take 0102
and you set the next take number to 99, and then hit ‘Record’ three times you’ll get:
Take 0099 ---- (New take)
Take 0100 ---- (Old take)
Take 0100(2) - (New take with disambiguation number)
Take 0101 ---- (Old take)
Take 0101(2) - (New take with disambiguation number)
Take 0102 ---- (Old take)
If you happen to have the Take number reset to 1, and you wind up doing, say, three different recordings
into the same record folder (when the next take is 1, e.g. after relaunching the console or manually resetting
it), you’ll wind up with:
Take 0001
Take 0001(2)
Take 0001(3)
The same thing happens for the files within a Take; generally, that’s not relevant if you have "New folder
per take” checked, but if you don’t then multiple takes will go into the same folder, and if the file name
doesn’t disambiguate between the takes then this mechanism will.
Also, for the file names if you wind up somehow generating the same file name within a take (e.g. you just
use the trackname for the file name, and you don’t include the file number or track number, you can wind
up with the same file name if you happen to have multiple strips with the same name), the console uses
the same mechanism to ensure the names are unique (so that no data is lost).
This disambiguation is stateless within MIO Console, so it only is going by the name it wants to create and
what already exists on the disk; the disambiguation number starts at 2 and it increments it in a loop until
it gets to one that allows it to create a new filesystem object without overwriting one that already exists.
This means that the sequence number is determined per folder/object and if there are multiple duplicates
on a given take, they may not all have the same sequence number — but that is a pretty degenerate case;
you’d have to go out of your way to get that to happen.
This also means that the sequence numbers may be different for the same take in two different record
folders.
