You an rename them in log and transfer, or you can upload metadata to the camera and use User Clip Names. You can also edit this material later after the shoot. In FCP6, you will have to use MXF4mac to access and send the metadata over to FCP.
If I rename them in Log & Transfer what happens if I trash my capture scratch then--at a later date--want to relink a project to the MXF files. Will the new files names relink with Panasonic's numerical names?
[Gerret Warner]"Will the new files names relink with Panasonic's numerical names?"
It's very easy. you simply load all the MXF files back in to the Log and transfer window, then in the bin select all the clips/bin you want to recapture, and then right click and choose 'Batch Capture'. The Log and Transfer window will then rewrap all the MXFs to Quicktime with the names you assigned the first time. It will be as if you never delted anything.
You can try it on a test clip to make sure you got the workflow down.
Brilliant. Can't believe I've lived with those anonymous numbers for so long. To be clear, though, it sounds as if the key is to assign a name in Log and Transfer rather than in FCP 6, so that FCP makes the connection between the two names in future relinking, no?
[Gerret Warner]"To be clear, though, it sounds as if the key is to assign a name in Log and Transfer rather than in FCP 6, so that FCP makes the connection between the two names in future relinking, no? "
Yes, name in the log and transfer window, then add clip(s) to the queue. If you decide to rename in the FCP browser, then you right click on the clip(s) and choose Rename > File to Match Clip.
1. Renaming in FCP costs you a lot of time + the conversion time. The names are saved in the FCP project file, you need FCP to recover the renamed files.
2. Setting custom P2 UserClipNames cost also a lot of time but this information can be used for ever and with all P2 compatible NLEs. You're not bounded to FCP.
3. Using native MXFs in FCP allows to save this project as XML and then the XML project information is available for other workflows, e.g. you could load it into Premiere Pro on a PC that would also read the native MXFs. Same applies with systems from Autodesk which run under Linux. With MOVs you're bounded to the Mac and FCS.