wow you have one complicated work flow ... now I'm not saying you don't need all of this, but I bet you could trim it a bit. Like why all the fuss with coverart before getting into MC (smells like iTunes
). anyway, you probably have your reasons. I just don't know enough about each software package to make an educated guess ... but it is still a mystery why you chose Lyrics as a dump field (you needed a comment type field that works on all platforms maybe?) Anyway I get what you mean by sync now.
Right now my dilemma is,
- if I use DJ Moods with acceptable values: All the values stay inside DJ Moods tag and can't get read by Traktor
hmm so you have to determine the field name that Traktor can read and use. Reverse mapping ...
So if 'I'm understanding Tractor is your front-end. Most people ask questions about how to import tags into JRiver, and then how to remap field names that might not be the same or exists in JRiver. However, using Tractor's limitations I would probably want to make sure that Traktor can import a JRiver custom tag. Couple of things I could think of experimenting with. Tag with Traktor only to see the name of the fields.
I'd do a tag dump and see the exact name of the field(s) it can read/interpret. Create that field and populate that from within JRiver. Try importing a few new music files from JRiver to Traktor and see if they are read correctly. As Traktor can read Flac files, this should work (using JRiver fields remapped to Traktor fields instead of an external programs fields remapped to JRiver fields.)
However if you only use MP3 files (so limited with ID3v2 tags, you might stumble across tags that cannot be read necessarily. Might want to jump on their forum and ask to see their tag chart .. I read a couple of posts and they use a field called PRIV which is going to cause some headaches. But I think its worth exploring. If you can determine the exact name of the tag field, and if the file type's container can support it, you ought to be able to get JRiver to populate it for you (it might require a secondary field or a manual "=[DJ Moods]" to do, but these can be done pretty quickly.
Right now my dilemma is,
- If I use calculated data [Lyrics]&datatype=: I need to import every song I want to tag
I split this as I think this is more of a workflow decision than a problem. My workflow is either my ripper will automatically write a tag that I can filter out, then I can isolate, verify and retag new music. When satisfied I remove the tag, and another view will pick it up. Then I use JRiver to transfer the music into the main media area I use for my collection. Call it sandboxing ... In other words I have a temp directory or drive that holds new music. Both are being imported, so I can listen, retag, analyze, change cover art etc. Now for you it is slightly different as you might only be keeping 10% of this music.. However so what? As long as you have it tagged in someway as temporary or work in progress, on your main views you can exclude them.
But I know DJs are portable beasts, maybe you are talking about terabytes of data per week who knows ... So maybe my sandboxing technique is too unwieldy. Maybe the DJ pool stuff is on portable hard drives or whatever that you are swapping around. What you could do then is still immediately import into JRiver but use a separate library on a completely different path. Manual importing is fast on JRiver, much faster than any other software I've come across. When satisfied, you can just use the Rename, Move Copy tool to move the files you want to keep to your main library area and autoimport can take over from there.
Mostly I rip CD's but I also buy/obtain a lot of stuff from downloads ... you mention tagscanner ... I use this too at the start of my workflow for downloaded music. I set my "WIP" tag and it is written to the file, renames the files and directory et al. Then it gets sandboxed automatically on import. When ripping CD's same story, my external ripper will write the tag for me, on import my special tagging and admin views are populated automatically.
BTW - another benefit of doing the majority of tagging on a large collection from within JRiver is that you can use a combo of views and the magic arrows on certain fields (like artist) - under Features=>Linkable columns. You might need to clean this up a bit as in one of your screenshots you have x artist and the horrible "feat." Q-Tip or something similar. Using library tools and replacing things like featuring with the semicolon, will allow you to find/group together other titles with the same artist even if there are multiple artist per track. This is another reason why sandboxing in one library is good as you can easily choose from existing values, and have consistency amongst artists when applicable and avoif having thousands of styles or variants of the same sub-genre etc.