This concept is also, um, ‘inspired’ >cough< by some MediaMonkey features.
I’ve recently seen scripts to set/change Types (Music, Jingles, etc.) in mAirList, and I recently remembered that if an Artist in MediaMonkey is wrong (Micheal Jakson is their example), you drag/drop the offending item(s) on the Michael Jackson Artist folder and voilà! The item’s Artist is changed (with a suitable Warning/Exclamation MessageBox, obviously!).
And then I realised …
… if all the nodes within the mAirListDB ‘system folders’ Artist, Type, and Attributes could be made drop targets, the associated action being to set that Artist, Type, or Attribute to the value of the node the items are dropped on, this would make mass changes (and even simple Artist spelling error corrections) VERY easy to do.
So for example, you could drop items on the Jingles node to set their Types to Jingle, or on a Genre node to change them to Country (for example … it’s late here!), and this would also allow custom (user) Attributes to be quickly and efficiently applied to many tracks at the same time.
The Warning/Exclamation MessageBox text would be something like:
[b]Dropping these 14 items here will change their Type to ‘Instrumental’.
These changes cannot be undone.
Are you sure you want to make these changes?[/b]
or for a change of Artist, and taking into account the fact that mAirList allows multiple Artists per item:
[b]Dropping this item here will change its Artist to ‘Kylie Minogue’.
All other Artist names in this item will be deleted.
These changes cannot be undone.
Are you sure you want to make these changes?[/b]
What does everyone think? I’m presuming (possibly wrongly) that if this can be implemented for any of the ‘system folder’ nodes, it should be reasonably (?) easy to extend that processing to all the suggested nodes: right or wrong, Torben?
BFN
CAD