[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 82640] id3 tags incorrectly displayed and saved
From:       Spiros Georgaras <sngeorgaras () otenet ! gr>
Date:       2004-06-03 10:43:44
Message-ID: 20040603104344.5442.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=82640      




------- Additional Comments From sngeorgaras otenet gr  2004-06-03 12:43 -------
Yes Scott I have seen the differences in action... :-(

I have just found out that you are the developer of TagLib :-)

So I think I should tell you about another thing I've noticed

Up until now I have been using ID3v1 for all my mp3s and ID3v2 for those with a title \
longer than 30 chars.

After this discussion, when I want to write an ID3v2 tag, (title longer than 30 \
chars) i do this

1. insert the tag with: id3v2 --TIT "What ever the title is for the file" file.mp3 \
(command line) 2. convert the tag to UTF-8 with your tag-unkreaker (I have changed it \
to change the ID3v2-->IDEv2-UTF-8 instead of the original ID3v1-->ID3v2-UTF-8 - I \
have attached the file)

In this case I noticed that the TIT2 field (maybe other fileds too, haven't checked) \
is trancated to 30 chars as in ID3v1. Can this be changed so I can insert the whole \
title?

Maybe this is relevant - from id3v2.4.0-structure.txt - section: 3.2. Extended header
====================================================
    r - Text fields size restrictions

       00   No restrictions
       01   No string is longer than 1024 characters.
       10   No string is longer than 128 characters.
       11   No string is longer than 30 characters.

       Note that nothing is said about how many bytes is used to
       represent those characters, since it is encoding dependent. If a
       text frame consists of more than one string, the sum of the
       strungs is restricted as stated.
======================================================


[prev in list] [next in list] [prev in thread] [next in thread]