[Tim Parsons] "Because it increases the odds of repeat file names, and that makes no sense whatsoever. "
Tim-
Yes, repeats can happen, but it is rare. The actual MXF file name are not the only thing that defines the file. Each file has a Unique ID that will help to discern separate files, even though the MXF files are the same name.
P2 is actually pretty decent and not repeating file name, and is much better than AVCHD (for example) which simply starts over with 0000.mts on every card.
The last clip.txt, in my experience, really has no bearing on anything. It is the XML files that do the lion's share of the control P2 MXF files. When using P2CMS (Panasonic's MXF manager) and you copy cards to another location, the last clip.txt file isn't even written. It is an ancillary file that is used by the camera only. NLEs and DAMs will use the XML file. This allows you to combine and mesh p2 cards into larger data sets that aren't restricted to the P2 card size.
Here's a screen grab from a shoot on one card on the XML files. These files, listed by name in the Finder seem to be out of order:
P2.png
But they are not out of order in the XML or by timecode, and each one has a Unique ID that makes tracking easier.
The next card from that series looks like this:
p2_2.png
Even those those clips are 0001-0004, they look like 16, 32, 40, and 27.
The real tracking number for the clip that is named "27" is: 060A2B340101010501010D4313000000813ECF9C375205FE0080458230D5C007
It is this number that won't get repeated, and it's the Global Clip ID number that is stored in the XML for that shot.
I have had files that have the same MXF name in the Finder (2 different cameras, same shoot), but have not caused me any trouble. The NLE is smart enough to know what to look for, but this was FCP7.
Are you having trouble with something or is something not working for you?
What exactly are you trying to do that gives you pause?
Jeremy
