This particular function has me perplexed - despite following to the letter the dialogue for synching tags to library.
I have a sizeable music library (almost 10K tracks) all tagged to an anal degree with v2 tags copied to v1 tags for best compatibility with my hardware mp3 players. I have set my library management in MM to at start up, check for new tracks etc. Running synch function pops up (consistently) about 20 or so tracks, not all the same each time, with some fields yellow highlighted, other tracks with no highlights. Some tracks continue to appear in this window seemingly no matter what I do.
Others appear when I have supposedly not touched that file.
Besides deciding to just not use this particular feature when the synch function is run, what the heck does it do? and why would I get these particular set of tracks (all ripped by and tagged by me) reappearing.
thanks for any comments!
Synchronizing function
Moderator: Gurus
Read this one
You might want to read http://www.songs-db.com/forum/viewtopic.php?t=548 forum item for some explanation.
Hope it helps
Hope it helps
Re: Read this one
Except that my tags are pristine ....Lowlander wrote:You might want to read http://www.songs-db.com/forum/viewtopic.php?t=548 forum item for some explanation.
Hope it helps
but the fact it is a recognized "oddity" is good, I will let that function be until it is addressed.
thanks for the note!
pristine tags
Jake,
By 'pristine', I assume you mean that you personally ripped the tracks directly from one of your CDs and never edited it.
Am I correct and if so, what tool did you use to rip the tracks that exhibited the 'desynchronization'?
thx.
Rusty
By 'pristine', I assume you mean that you personally ripped the tracks directly from one of your CDs and never edited it.
Am I correct and if so, what tool did you use to rip the tracks that exhibited the 'desynchronization'?
thx.
Rusty
Synching function
Yes these were ripped by me - either with:
Music Match Juke Box (always the latest full version) using 85% VBR or
CDEX with Lame 3.92 alt preset standard setting.
I then use MMJB to alter the tags that download from cddb or freedb.
Then (and not that I am anal about this or anything ...
) but I use a wonderful freeware program called MP3Library to do a final check and remove comments and to synch id v 1 and v 2 tags.
MP3Library has proven to be a godsend in keeping my tags pristine which in turn has eliminated problems I had in transferring tracks to my various hardware mp3 players (Creative NJB3 and iRock 530).
What I continue to see when I run the synch function on MM, are various tracks that (AFAIK) seem to be tagged for synching for no apparent reason. These tend to be somewhat random as well, since one run will show up a set of tracks, then another pass through may have a few from the first and a few others and so on.
Maybe I just really don't understand what this synch thing is doing ?
jake
Music Match Juke Box (always the latest full version) using 85% VBR or
CDEX with Lame 3.92 alt preset standard setting.
I then use MMJB to alter the tags that download from cddb or freedb.
Then (and not that I am anal about this or anything ...
MP3Library has proven to be a godsend in keeping my tags pristine which in turn has eliminated problems I had in transferring tracks to my various hardware mp3 players (Creative NJB3 and iRock 530).
What I continue to see when I run the synch function on MM, are various tracks that (AFAIK) seem to be tagged for synching for no apparent reason. These tend to be somewhat random as well, since one run will show up a set of tracks, then another pass through may have a few from the first and a few others and so on.
Maybe I just really don't understand what this synch thing is doing ?
jake
Unsynchronized Tags node strangeness
Jake,
Upon further investigation, there are a couple of problems with the manner in which MM determined that tags were unsynchronized. Basically, for MP3 files, it looked at the aggregate of ID3v2 and v1 tags--v2 having priority over v1 tags in case of conflict, and compared this aggregate to the DB. Moreover, it used this same logic regardless of how MM is configured to write tags.
In 2.0.2 beta 4 which will be coming out soon, you'll see some changes for the unsynchronized tags node:
-if MM is configured to write ID3v1 and v2 tags, it will show: tracks for which either v1 or v2 tags do not match Library contents
-if MM is configured for write ID3v1 tags, it will show tracks for which v1 tags do not match Library contents
-if MM is configured for v2 tags, it will show tracks for which v2 tags do not match library contents
As far as the non-deterministic behaviour that you've described, I've never seen this occur with this node. If you have a track that sometimes appears in the node and other times doesn't, please e-mail it to me.
thx.
-Rusty
Upon further investigation, there are a couple of problems with the manner in which MM determined that tags were unsynchronized. Basically, for MP3 files, it looked at the aggregate of ID3v2 and v1 tags--v2 having priority over v1 tags in case of conflict, and compared this aggregate to the DB. Moreover, it used this same logic regardless of how MM is configured to write tags.
In 2.0.2 beta 4 which will be coming out soon, you'll see some changes for the unsynchronized tags node:
-if MM is configured to write ID3v1 and v2 tags, it will show: tracks for which either v1 or v2 tags do not match Library contents
-if MM is configured for write ID3v1 tags, it will show tracks for which v1 tags do not match Library contents
-if MM is configured for v2 tags, it will show tracks for which v2 tags do not match library contents
As far as the non-deterministic behaviour that you've described, I've never seen this occur with this node. If you have a track that sometimes appears in the node and other times doesn't, please e-mail it to me.
thx.
-Rusty