This took me a while to solve but here we go. When an
ID3v2 tag is present JavaHMO automatically defaults to
reading only ID3v2 even if the tag is nearly blank and
the ID3v1 contains valid info. I found this to be a large
problem with the year category. If the following data is
present in the MP3 no year will be recognized by the
organizer.
ID3v1 Year: 2004
ID3v2 TYER:
ID3v2 TORY:2004
Because the organizer recongizes the presence of ID3v2
but when it comes across blank data for the TYER it
assumes non exists. It should have a heirarchy of
prefered data i.e. check each of the following in order
and when data is found stop and use that:
ID3v2 TYER
ID3v1 Year
ID3v2 TORY
Now maybe we don't use TORY since that is the original
recording year and a cover of a song would have the
incorrect year.
To some up, my point is:
THE ORGANIZER SHOULD GATHER DATA FROM BOTH
ID3v2 AND ID3v1 AT THE SAME TIME. ID3v2 DATA
SHOULD BE GIVEN PRIORITY BUT IF THE FIELD IS BLANK
THE DATA FROM ID3v1 SHOULD BE USED.
Thanks again,