I use MC for pretty much all my multimedia management on the PC at the moment. It's not quite there yet for me in theatre view but it's getting close. There are a few niggling things remaining in my database organisation....
1. Untaggable files -- I can't count how many times I've lost tag info because I've moved or renamed a file outside MC. For taggable files, I store all info in the file, but for video files, and unsupported audio, image and document files, I've had to settle for manually creating mpl and xml files. This presents a few problems, however...
-- It's a very manual process. If I change a field in MC, I have to remember to re-export the mpl file. I'd really rather tag the file and forget about it!
-- Moving files to a new computer, sharing files with others etc ~ the paths change and because the MPL file contains the path info... tags are lost
-- If I reimport a file, MC won't automatically look for the info in the MPL file
So I was just wondering how other users get around / deal with this?
Possible Solutions: It would be great if MC could either
- auto generate an MPL file for each folder if tags cannot be written to files
- create a *.tag file or similar for each file that cannot be tagged. This could be a hidden file similar to folder.jpg, thumbs.db etc
2. Long Filenames -- This is a longrunning issue and is essentially quicktime-related problem relating to quicktime's bizarre filename restriction of 63 characters. I have lots and lots of .mov files from my camera and
over and over again I come across files which I can no longer play because I have performed a rename from properties from within MC and the resultant filename is too long. The problem is:
-- I usually performed the rename long ago without realising
-- MC can't undo the problem because it can't read the file, so I end up having to rename it externally (which means I lose tags -- d'oh! see 1.)
Firstly, does anyone out there know of a workaround for this restriction? I haven't tried quicktime alternative. Does it have the same restriction because it used the same engine? Has apple expressed any intention to fix it?
If not, then I think MC really has to tell the user that it is renaming the file to a filename which is essentially unusable. Especially considering MC is pushing it's support for iPod, podcasts etc and these use primarily apple formats.