SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Export in Excel Format - What are the "English:Songs-DB_..." Prefixes?

#1

Hi All,

I use regularly the Excel format export/import function of Jaikoz (as I do some additional processing of my tags outside of Jaikoz).

I noticed that some values get a prefix “English:Songs-DB_:” upon Export, e.g. “English:Songs-DB_Custom1:”, then followed by the actual value of the tag. It happens primarily for the Custom fields, but also some other.

For curiosity I am wondering what is the purpose of these prefixes, and under which conditions they are applied. And second if there is any way to avoid that those prefixes are added? (Currently I Strip them manually before import … otherwise there would be double prefixes next Export time).

Thanks a lot for any insights!
Andy.

#2

Can you see exactly which field this is in Jaikoz and what audio format does this occur for ?

#3

Hi Paul,

The effect occurs only for MP3 files, not for FLAC. (~ 1/3 of my library is in MP3 format).

The fields in Jaikoz are “Custom 1” … “Custom 5”, and “Quality” (all on the “Custom” tab). If a file is affected, then it is consistent for all of these fields (i.e., either all have the prefix, or none). So seems it depends on the file itself, not the actual content of the field.

Also I just checked again, and found the prefix is actually added during the import of the XLS file into Jaikoz, not during the export step (I always noticed it after an entire import/export cycle). The Jaikoz version doesn’t make a difference (had it in 6.x and now 8.2.3).

Hope this is helpful to get closer :slight_smile:

Thanks a lot!
Andy.

#4

Hi, actually it does happen for Export i.e its in the xls file created, basically for ID3 these fields use the COMM frame and the export is exporting the comment language as well as the the actual comment.

However, there is a workaround if you export as .CSV file then it only exports the comment so you dont have the problem when you import.

Im not quite sure why there is a difference, I’ll have to delve further into it.

#5

Raised https://jthink.atlassian.net/browse/JAIKOZ-1009

#6

Paul,

Thanks a lot for digging into this, and maybe in a future version it can be fixed. For the time being I am fine with the workaround, though I had to tweak my Windows regional settings (on a German PC, Excel expects a “;” instead of a comma as CSV field separator …) - no big deal.

Btw. Thanks a lot for creating Jaikoz, really a great tool and great support!

Andy.

#7

The issue is that these fields are only exported correctly if language field is set to Default, if set to another language or if edited in Media Monkey which has its own custom language value then the language and short description are exported as well.

We are usually only interested in the value so now always only export the value, an import will now just use the default for language field (this is visible in the ID3 Edit tab).

if people really want to preserve the language value or export/import we would have to do this by adding other fields such as Quality_Language so there would be a corresponding pair of values but Im not sure this is neccessary

#8

Fixed in forthcoming 8.3.4 release.