Thanks: since I had an issue with auto import (I moved some directories and autoimport deleted the contents of some custom fields e.g. composition) I am look for a 'dont touch' option i.e. leaving the contents of a custom field untouched.
I remember you discussing this in another thread. I think you are missing something important, so I'm going to try to explain it:
If you move a file or a directory using Windows Explorer, or another file tool, MC does not see this as a "move". What MC sees is this:
A. The file (or directory) you moved is "gone". It was deleted. So MC deletes it from it's database, INCLUDING your custom field.
B. A new file (or folder) appears in a new place, possibly with a new name. Either way, this file/directory is "new" because MC has never seen it before. So MC imports it as normal and reads the tags out of the file. Your custom fields might be in the tags of the file. If so, MC will read them. If not... then they are gone. Also, the import date for this file (or directory or files) is brand new. Again because MC sees it as new.
There are (at least) 3 things you should know about to help control and prevent this:
1. MC can be told to delete media in files and directories that "disappear". MC calls this "missing" files. By default it deletes them. But you can tell it not to if you want. What you will be left with is MC entries that can not play because the files are gone. But the entries will be there, including all fields, custom and otherwise. This option is controlled at:
Tools > Options > Library & Folders > Configure auto import > Tasks > Fix Broken links > (set to No to prevent any automatic removal)
This will become more interesting after you read the rest of this.
2. You can tell MC to write all fields to your files, including custom fields. That way they might be preserved if you move files or even if you copy the files to new systems with MC. Note that this works well with FLACs, but is not all that well supported by other file types. It depends on how well writing custom tags is supported by each different file type. The option is at:
Tools > Options > General > Importing & Tagging > Update tags when file info changes > (check to write tags)
Note that turning this on will not write any tags immediately. It will only write when tags change,or when you force a file (or files) to be written with: <right click on file> Library Tools > Update tags (from library)
3. The Rename, Move, and Copy files tool can be used to move your files or directories. If you use this, then MC will not get confused as in A and B above. It will just work and retain all of your custom fields! Use RM&C whenever you can.
For really big moves, like moving my collection from one drive to another, I generally use an external tool to actually do the copy or move. Which breaks MC's database because all of the old files disappear, like in A above! But then I immediately use the Rename, Move, and Copy files tool to update MC's database. This let's me tell MC that (for example) I have moved all files from the E: drive to the G: drive. It would take way too long to describe this process here, but you can read up on the RM&C tool here:
https://wiki.jriver.com/index.php/Rename,_Move,_and_Copy_FilesIn particular you want to read up on the Find & Replace template if you ever plan to do what I just described.
In summary, you don't need a "don't touch" option for fields in MC. Even if it existed, it wouldn't work because MC sees your moves as deleting old files and bringing in new ones. Use RM&C to move files. Tweak the options I've described to you to control exactly how MC handles all of this.
Good luck!
Brian.
Author
Topic: Auto Import Vs. Importing a single folder. (Read 1770 times)