#3 album names truncated to 30 characters

[Jordi Monfar]

The produced lib.jbm exhibits album names truncated on
30 characters. The real issue is that some double (or
triple) feature albums, where the strings differentiating,
lets say, disc 1 from disc 2, are past the character 30.
Then Archlibrary shows only one album, with both album
tracks merged into it (2 #1 tracks, 2 #2 tracks, etc).

Album tag is where this effect is observed. No reason to
think other tags can be also truncated, but normally no
other tags take long strings (except the comment field,
not used in jbmgen AFAIK).

I have tested using ruby from Interix environment under
windows (SFU: Services For Unix - as provided by
Microsoft). Runs otherwise very well, even since version
1.0.0

[Jordi Monfar]

Logged In: YES
user_id=1205325

I realize now that 30 characters is just the limit of ID3v1
tags. Could this be a limitation of the mp3info ruby library, or
even of Archos ArcLibrary format itself, supporting only ID3v1
tags?

[Jordi Monfar]

Logged In: YES
user_id=1205325

Think I have confirmed the issue: no support for ID3v2 tags.
Only ID3v1 are read, even if a ID3v2 is present on the same
file. Files with ID3v2 only are not considered and ignored
when building the jbm.lib.

ID3v1, with 30 chars only, are way too limited. ID3v2 support
would be a must in my opinion.

[Jordi Monfar]

Logged In: YES
user_id=1205325

Have made this little modifications on my copy:

bash-3.00$ diff FileEntry.rb*
80c80
< info.tag[tag]
---
> info.tag1[tag] || info.tag2[tag]
91,92c91,92
< track = tag_info(mp3info, 'tracknum').to_i
< year = tag_info(mp3info, 'year').to_i
---
> track = tag_info(mp3info, 'tracknum')
> year = tag_info(mp3info, 'year')

Now it reads and uses ID3v2 tags perfectly. But have not
tested what happens with ID3v1 tags, specially if there are
BOTH in a file (which takes precedence, if can read both?).

Please check it, it could be so easy as this to solve.