Posted: Fri May 23, 2008 9:46 am
looks like a useful script. but it still puts files in f:\Music\Music, if I choose f:\Music, as my backup folder.
The Music Manager for Serious Collectors
Just choose f:\ and it will put them in f:\music.svenni wrote:looks like a useful script. but it still puts files in f:\Music\Music, if I choose f:\Music, as my backup folder.
See previous postsvenni wrote:hey
... and with check for missig bakcup checked it is not useable.
Technically, Yesnynaevelan wrote:MoD:
Is it posssible to add an option for the user to select a custom field to copy the Track Identifier information to? I would like to use Trixmoto's Custom Report to run some reports on the backup information.
Thank youtrixmoto wrote:I'll see about getting this into the next release of "Custom Report".
Hi MCSmarties,MCSmarties wrote:MoDementia, thanks a lot for coming up with this backup mechanism. I love your idea!
However, I am reluctant to use it for the same reason that I'm afraid to use other automated backup mechanisms:
What if something goes wrong and I end up destroying my good backup with a corrupted/bad modification?
Don't take this statement as implying that I don't trust your script, there are a lot of things that can and will go wrong when manipulating a large database:
- MM crashes, corrupting the tags of the last file
- I mistakenly apply a modification to a whole bunch of songs instead of only one
- I find/rip a "better" version of a song and delete the old version, realizing too late that the new version has a problem
- I try out a new script (specially a "batch" script) that misfires and messes up a whole bunch of songs
- etc... (all the above happened to me at one time or another)
Now just imagine I run the backup (either manually, or it happens automatically when I restart MM) before I realize there' s a problem...
oh, the sheer horror - I just replaced my supposedly safe "backup" with garbage!!!
OK, the easy solution is to keep a backup of the backup - but two full backups take a lot of space, not to mention it gets messy (which backup can I trust now?)
Cut ---------------------------------------- Cut
As you can see, this would only require user intervention in a few specific situations.
That' s just a coarse overview, details may require tweaking:
- assume some changes are always desired and silently replace the backup (such as adding a value to an empty tag field or modifying the rating)
- preferences, for example maximum size of <Backup 2>(prompt cleaning when exceeded) or which changes to accept automatically, etc...
All this of course while still using your original idea, e.g. tracking a song by a unique ID to avoid redundancy.
What do you think? It seems to me that your script already does most of the work, it only really needs a couple of additions:
- a block to discriminate what action is required and run the backup routine a second time for the concerned songs
- a dialog to highlight the differences between 2 files to the user and ask for input.