Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.

Message icon:

What program is this forum about?:

shortcuts: hit alt+s to submit/post or alt+p to preview

Topic Summary

Posted by: Admin
« on: May 20, 2009, 23:38:31 »

fixed, will be available in new version.
Problem was not in simple unicode, but it was Little-endian, that is why WMP can't open them.
Posted by: Admin
« on: May 19, 2009, 22:45:56 »

i think this files can't be played in WMP (and decoded by WMF decoder in Similarity) because they contain a UNICODE tags. Windows Media Player Programmers very "kind" and very professional, and of course they don't read standarts ( :)
I think I add support of ID3v2 tags to ACM decoder.
Posted by: Admin
« on: May 19, 2009, 21:41:58 »

Yes i received them, and analyze them, something interesting, Windows Media Player can't play them, and Similarity used ACM decoder, this decoder can only show ID3v1 tags.
I continue research.
Posted by: surbaniak
« on: May 19, 2009, 18:40:23 »

Let me know if the mail(s) did not make it, if not I  will get it to you in a different way.
Posted by: surbaniak
« on: May 19, 2009, 18:25:33 »

MP3 file was sent over email.

Have look at what Similarity shows for  Artist for example.

Thank you very much.

Posted by: Admin
« on: May 16, 2009, 11:10:47 »

i tested, everything seems to be ok.
i edited tags in winamp, id3v1 different from id3v2, Similarity showed correct id3v2 tags, in win2k,winxp.
can you send me this file where this bug appears ?

similarity don't analyse file for id3v2 tags, it uses Windows Media SDK for taking all information, maybe your grabber write invalid tags ?

Or you maybe didn't install Windows Media Player 9.0 or later, in this case Similarity uses ACM decoder and himself searches ID3v1 tags. In this mode it's not support ID3v2.x tags.
Posted by: Admin
« on: May 12, 2009, 18:16:03 »

I see what's wrong
Posted by: surbaniak
« on: May 11, 2009, 16:04:32 »

I noticed one more thing with MP3 tags.

One of the rippers I use, populates  ID3v2   very  nicely    but   ID2v1   it  sticks  garbage strings into (for some stupid reason) ....
and it looks like Similarity is only reading   ID2v1,  and i get the garbage tag info in Similarity GUI.
Any way around that ?

ID3v1.Title = þÿ
ID3v2.Title = Good Time (Radio Edit)
Posted by: Admin
« on: May 09, 2009, 00:07:15 »

Thanks for comment.
i think this wish would implementent in future, but not in nearest versions.
Because there some troubles with different mechanism of storing tags (ID3,Vorbis,ASF).
Posted by: surbaniak
« on: May 08, 2009, 21:23:35 »

I know this one may not make it to the top of the priority list, but here is the pattern I have noticed on a number of my duplicate resolutions:

SongA is a true duplicate of SongB  but =



So now I have to open each one a few times in Winamp to Copy-Paste the tag info from the poor quality SongA to  the one I want to keep SongB (because of its superior BitRate).   Then I erase SongA.
Very time consuming.

Is there any way  a  Copy/Move ID3 Tag  info  Left<-->Right  action can be added to Similarity  [and best to let the user pick the tags to Move].