-Brading Software Message Board
+--Forum: Mp3/Tag Studio Suggestions
+---Topic: Option to write in ID3v2.3 or v2.4 started by gathering
Posted by: gathering on Oct. 16 2002,09:38
An option to select whether to write using ID3v2.3 or ID3v2.4 would be nice.
Some suggested changes:
-the drop down list of advanced frames would need to be different for both versions
-automatically deciding to use v2.4 tag when saving files with v2.4 frames (option in settings)
-bug fix as well: when u load a file with a v2.4 tag and u modify it, it saves as a v2.3 tag
-can maximize the window using the maximise button in windows, so u can have 2 window size settings
-when synced, but v1 tag is truncated, the buttons to switch between v1 and v2 tags should still be displayed
This is the best tagging program i've found so far! That's why i bothered suggesting improvements, because i'm going to use it.
Posted by: Disposable Hero on Oct. 16 2002,13:16
Could you explain what feature is present in 2.4 that is attractive to you? I have only passing knowledge, but it seems like 2.4 is an unfinished spec, with the usual accompanying flaws.
I agree completely with the Maximize issue. I would go further and say that in the Browse tab the regular tag info should be moved to the top and the Advanced window be embedded below it, scrollable if necessary.
I'm not sure what the utility of keeping the v1 and v2 buttons active would be, but if the "synced" text indicator was still there I can't see the harm in it.
Of course Magnus will have plenty to say in this thread, I expect.
Posted by: Magnus Brading on Oct. 16 2002,18:22
I would also be interested in why you want ID3v2.4 tags? Can you name one advantage of this, in contrast to writing ID3v2.3 tags?
About the maximize button, see < this >.
And it's not a bug that it writes ID3v2.3 tags even when the file originally had a ID3v2.4 tag. The program reads all ID3v2 formats, but writes only ID3v2.3.
To get the behavior you are asking for with the v1/v2 buttons, simply deactivate the option "Intelligent tag-sync checking mode" in the "Tagging core" section of the main settings.
Posted by: Elbow on Oct. 17 2002,04:07
---------------------QUOTE BEGIN-------------------
About the maximize button, see < this >.
---------------------QUOTE-------------------
and what have you come up with?
Its a bummer at work on my Jpn OS. I have to have
no-resize cos it just jumps and flickers without it. Which means on my larger monitor settings the window is too small to really do much in depth stuff.
Not sure where the setting is to stop it in my OS as its all in Japanese.
Have you had anyone else complain about the window jumping on a NON English Font System?
Maybe its just been set up that way at my school.
If you know where it would need to be changed(large font) Id love to hear from you.
Posted by: Magnus Brading on Oct. 17 2002,23:04
The flickering problem is often triggered by peculiar character settings, and I could very much imagine that Japanese characters could be included under this description.
Anyway, what I have come up with so far is that the whole thing is cursed, not much more than that...
I can think of some tricks to make it possible to resize the window anyway, for systems where the flickering problem is the only cause for the necessity of the noresize-mode, like in your case (i.e. and not the large fonts problem). I'll try it out when I get some time.
Posted by: gathering on Oct. 18 2002,07:53
Thanks for the intelligent sync tip. I didn't really know what that did before.
->Disposable Hero
I thought v2.4 was finished with no more flaws than v2.3, but just that most ppl don't use it because of compatibility.
I'm not sure really why i like v2.4... maybe i just want the latest in everything, but it seemed tidier and efficient,
e.g.:
TDAT - Date
This frame is replaced by the TDRC frame, 'Recording time'
[F:4.2.5].
TIME - Time
This frame is replaced by the TDRC frame, 'Recording time'
[F:4.2.5].
TRDA - Recording dates
This frame is replaced by the TDRC frame, 'Recording time'
[F:4.2.5].
TYER - Year
This frame is replaced by the TDRC frame, 'Recording time'
[F:4.2.5].
< http://www.id3.org/id3v2.4.0-changes.txt >
They added new ones as well.
Maybe u could add writing v2.4 support just for compatibility, or to say "Mp3/Tag Studio can write any version ID3 tag!". That would mean u would have an option to write v1.1 and v1.0.
I don't really use the extra features though, so i think i can live with v2.3 then.
The bug is that, just say I have an "Encoding time" in my MP3s, when i save the MP3s as v2.3, the encoding time frame is still there, so technically it should be v2.4 because it uses a v2.4 frame. Now that i think about it though, u don't want to delete any info in case the user still needs it.
Posted by: Magnus Brading on Oct. 18 2002,15:41
Hmm, it should warn when the situation with the ID3v2.4 frame happens, so it might very well be a bug. Could you mail me an example file with a tag that causes this behavior (my email address is in the "contact info" section of the website)?
And about implementing ID3v2.4 writing support just to be able to say "Mp3/Tag Studio can write any version ID3 tag!" is sadly just don't worth the implementation effort, but otherwise I would have done it.
Posted by: Magnus Brading on Oct. 19 2002,14:55
Ok, it was just my memory that failed me. I just checked the ID3v2.3 specs, and when it comes to standard text frames (all frame ID:s starting with a "T", except the "TXXX" frame) all such frames are allowed within the ID3v2.3 standard. It's just that not all ID:s are predefined, but using non-predefined text frame ID:s does not make it a non-standard ID3v2.3 tag, since the text frames are specified on a higher level. So that is why I implemented it this way, and that's why it's also fully standard compliant. Thanks for the report anyway, it was apparently time for me to take a look at that spec in any case.
Posted by: gathering on Oct. 21 2002,07:54
OK, that's all resolved then!
end