lenght of id3 tags displayed

[heinrichh]

I noticed that since 3.6 the length of id3 tags displayed decreased significantly. For me this is relevant for the comment tag which may contain a synopsis of a radio novel in my cases.

Is there any way to increase the read and displayed byte count of id3 tags? Compiling a custom version is not an option for me as I don't own a Linux box and compiling is way to complicated for me. But maybe there is a conf file which I can edit with a simple text editor?
 
Thanks for any help!

[Buschel]

The amount of bytes displayed cannot be configured, it is hardcoded and you would need to recompile if you want to change it. May I ask what device/player you use and how much characters you normally would require to be displayed?
The amount of bytes per tag entry was limited to avoid dropping relevant tag data in case of very large comment fields. E.g. we had issues with missing replaygain when this tag data was following very large comments.

[heinrichh]

Thanks for your interest, Buschel!
The device I'm using actually is a Sansa Fuze V2 8GB with an 32 GB microSD. The comment tags of some of my files - esp. radio novels synopsises - vary between 500 and 1000 characters = bytes. I think it wouldn't serve anyone if the tag displayed is longet than 512 bytes but 512 bytes would be very fine.

BTW I'm wondering about the issues you mentioned because sometimes the album art is included in tags and I assume the album art to be longer than only 512 bytes!

TIA
heinrichh

[gbl08ma]

BTW I'm wondering about the issues you mentioned because sometimes the album art is included in tags and I assume the album art to be longer than only 512 bytes!

Rockbox only supports album art in tags for MP3 and AAC, and since very recently, so that has not applied for ages and still doesn't apply to lots of audio formats (like OGG), for which you need to use stand-alone images files (see the wiki for more information )

[Buschel]

We only have 900 bytes (300 bytes for low memory targets) available for the metadata. The current implementation limits the maximum length of each tag field to 120 (60 for low mem) bytes. It would of course be possible to use different maximum lengths for different tag fields (e.g. 500 for comments), but I decided to choose an implementation which uses the same limitation for all tag fields.

[heinrichh]

Any chance to convince you to increase the amount for the comment tag? Some Augustiner beer?
  

[Buschel]

If the id3 metadata code would be less weird, yes 
But it isn't...

[heinrichh]

What about only showing full tag contents in the info screen? In this case you can read the file tags as they are in the files and show them. There is no need to have the whole tags handy every time or in the database. Maybe things will be easier if reading the full tags is restricted to the most popular file types like mp3, ogg and flac?