[Logo] Jaikoz and SongKong Forums
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
Issue with Songkong writing comment field despite "never modify" setting.  XML
Forum Index -> SongKong Issues
Author Message
Codec



Joined: 23/12/2017 16:56:37
Messages: 4
Offline

Using Songkong 4.13 on windows 10 64bit enterprise. I have submitted support files for your reference.

I am noticing some weird behavior when it comes to writing the "comment" field. I use a software called "Mixed in Key" to analyze my tracks for key and energy level. Unfortunately Mixed in Key has limited options for which Id3 tags are used to store the energy information. I currently use the "comment" field to store this information in a numerical value (1-9). I am having problems with Songkong appending information to this comment field - even though I have excluded the comment filed in the Songkong settings. Please see the video below to witness the behavior.

https://youtu.be/nRFdwZ8Y4Ls

Can you offer any advice on how to prevent this behavior or is this a known issue/bug?
paultaylor

Pro
[Avatar]

Joined: 21/08/2006 09:21:27
Messages: 7462
Online

It may be a bug, but its not clear Im going to have to look at this in the New Year.

thanks Paul (Administrator)
Codec



Joined: 23/12/2017 16:56:37
Messages: 4
Offline

Upon further investigation using the "extended tag information" available with the Mp3tag application, it looks like SongKong is pulling this additional comment data from some other fields called "comment songs-db_custom1", "comment songs-db_custom2" and "comment songs-db_custom3" (I am still not sure where this tag data came from initially). SongKong then duplicates these into what appears to be multiple, "alternate" comment fields within the "extended tag information".

Mp3tag actually correctly displays only the initial comment tag containing the Mixed In Key numerical energy info. However, the MediaMonkey application (Which I used to demonstrate the issue initially) reads ALL of the various comment tags and displays them, separating the various entries using a "pipe" | symbol.

It is still apparent that SongKong is making changes to some "alternate" comment fields, just not the "primary" comment field. In this case, this may be the intended behavior of SongKong - although it seems strange.
paultaylor

Pro
[Avatar]

Joined: 21/08/2006 09:21:27
Messages: 7462
Online

The songs-db_custom1 corresponds to the Custom1-5 fields in Jaikoz, see http://www.jthink.net/jaudiotagger/tagmapping.html. Essentially in ID3 you can have multiple comment fields in ID3 as long as they have a different short comment description, see section 4.10 in http://id3.org/id3v2.4.0-frames

SongKong doesn't use these fields, however if you have SongKong configured so that Mp3 Metadata Tag on the Save tab is always configured to convert to V23 or V24 I wonder if that is causing the comments fields to be reorganized so that Mp3Tag is showing a different first comment ?

thanks Paul (Administrator)
Codec



Joined: 23/12/2017 16:56:37
Messages: 4
Offline

I can try toggling the tag conversion when i get home and report back.
Codec



Joined: 23/12/2017 16:56:37
Messages: 4
Offline

I cranked up Jaikoz to see if it would give me any useful information. I can get it to display the "custom 1-5" tags in a column but it will only show one comment tag column. Mp3tag seems to show "all" of the comment tags when you view "extended" information on the track.

Anyhow, it seems that Songkong is looking at the following tags:
comment musicmatch_situation
comment songs_db_occasion
comment songs_db_custom1-5
and duplicating them into several "normal" comment fields.

before screenshot: https://ibb.co/dvsppw
after screenshot: https://ibb.co/cwSB2G

I tried all 4 of the possible id3 version options in the pull-down on the save tab. They all seem to have the same behavior when it comes to these comments.
paultaylor

Pro
[Avatar]

Joined: 21/08/2006 09:21:27
Messages: 7462
Online

Okay, thankyou that does look like a bug I will raise an issue on this.

thanks Paul (Administrator)
 
Forum Index -> SongKong Issues
Go to:   
Powered by JForum 2.1.6 © JForum Team