SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Writing Tags: How does Jaikoz handle "Not Supported" & "Unknown" frames?

#1

I’ve checked the offline help file & can’t find specifics about writing out “Not Supported” and “Unknown” frames. It seems Jaikoz handles them differently.

[color=blue]Mostly, I’m wondering:

  1. Are these columns dependent on tag version? Eg, is TDRL “Unknown” in an id3v2.3 tag, but supported for an id3v2.4 tag?
  2. Are “Not Supported” and “Unknown” frames both written when saving the tag? Does this depend on tag version?[/color]

Jaikoz Help says the app should recognize all official ID3 frames. TDRL is a valid frame, although only in an id3v2.4 tag … not an v2.3 tag.

I ask because it seems that Jaikoz always writes out “Not Supported” tags, but doesn’t write out “Unknown” frames.

I’ve also noticed this problem:
If I open a track that has an id3v2.3 tag which is augmented with some v2.4 frames like “TDRL” or sort order frames like “TSOA” & “TSOT”, then Jaikoz considers these v2.4 frames “Unknown” and does not write them out if I change some other frame. (Helium Music Manager writes such mixed tags as “compatible” v2.4 tags … compatible with v2.3.)

However, if I try to update the tag version to v2.4 using Jaikoz, and then save, Jaikoz still seems to throw out these “Unknown” v2.4 frames, rather than trying to fit them into the updated v2.4 tag.

[color=darkblue]If this is all more or less accurate, then I’d suggest either

  1. always display tag info based on the tag Version (including a proposed change to Version). Then, if a user changes tag Version, Jaikoz would re-scan the track based on this new tag version, and then try to apply any other changes the user made but didn’t already save; or

  2. always display tag info based on Jaikoz’s best interpretation of all tags. In this case, Jaikoz would recognize TDRL, even in a v2.3 tag.

  3. Jaikoz should also always write out all “Not Supported” and “Unknown” tag frames. I appreciate Jaikoz’s adherence to specifications, but given the lack of conformity out there, this would help avoid loss of data from other applications.[/color]

My preference would be 1 + 3. Option 2 seems to cause too many problems.

#2

[quote=GiacomoGo]I’ve checked the offline help file & can’t find specifics about writing out “Not Supported” and “Unknown” frames. It seems Jaikoz handles them differently.

[color=blue]Mostly, I’m wondering:

  1. Are these columns dependent on tag version? Eg, is TDRL “Unknown” in an id3v2.3 tag, but supported for an id3v2.4 tag?

  2. Are “Not Supported” and “Unknown” frames both written when saving the tag? Does this depend on tag version?[/color]
    [/quote]

Yes thats right because TDRL is unknown for a v23 tag, they are dependent upon the current tag version of the file not the version it is being written to. When writing unknown and unsupported frames it should just be written as read, however if on writing the tag version has been changed to a version where the frame is known upon a subsequent open on the file the frame will no longer be listed in the unknown column its value will be in the correct column (e.g Release Time).

It should do, if you change the tag version that will affects the contents of the unknown column as explained above, otherwise maybe you have hit a specific problem - please send me a test file.

Ive looked into this, and I think there maybe a problem when a tag contains frames that are unknown for this version (e.g TDRL) rather than completely unknown (FREW), I’’ get back to you on this.

#3

There is an issue with frames that are valid in v24 but not v23 such as TDRL, Ive fixed the problem but not in a position to an officila release at them moment, I may be able to provide you with an interim release if you like.

#4

I have no need for an interim release … just wanted to verify what I noticed. Thanks, Paul.

#5

Actually a couple ofg issues came up with MusicBrainz, so your fix is included in the latest release (1.9.1) - please upgrade.