Tags are not imported correctly

[skooldj]

First of all RadioDJ is awesome!
but I have some issues with the tags, many tracks has missed tags,  i mean the tags are not imported correctly.
thanks indeed, if anyone can help I will be happy!

[mb21uk]

First of all RadioDJ is awesome!
but I have some issues with the tags, many tracks has missed tags,  i mean the tags are not imported correctly.
thanks indeed, if anyone can help I will be happy!

Yes, I find this. The vast majority of audio files get imported correctly but by no means all. Multiple dashes seem to be a particular problem.

[RFU]

I've never had a problem with importing tags.

Are you sure the tags in the files are correct to start with?

[Kai]

MP3-Files should be imported normaly without any issues. But if you have M4A-Files not all fields will be imported.
In my case Artist, Title and Album will be imported, all other fields not.
But that is not a problem of RadioDJ. It has to do with the tags in M4A-files. Reading this tags is not fully supported by the standards of M4A. M4A is normaly the audio part of a MP4-Container (M4A=Audio, M4V=Video).
Even if the M4A-file is technicaly an AAC-file, renaming it to *.aac will not help. You have to convert the file to aac or whatever you like. Then importing the tags will work.

[HITS Radio]

Hi there.
I use mp3 files perfectly edited with all id 3 tags. I noticed that he didn't import the image from some music files. I only noticed this error with the id3 tag image. I don't understand the cause of the error, but I'm paying attention. Maybe if you don't jpg the image then skip it. If png can not import.

[skooldj]

Τhe files are .mp3  all edited with mp3tag. 
I cant find what triggers this issue.
In some files the tags are not imported correct, even some files are not shown on the search.
I have read that other users have the same issue, but there is no solution, or just to find what causes this. maybe the format of the tags, maybe the format of the name of the file, who knows......

[Kai]

Did you try already another tagging program?
I'm using "TagScanner" since years and never had any problems importing mp3's with all included tags.
It's a free program and you can download it direcly from the developer: https://www.xdlab.ru/en/
Maybe you can test it with one of the files that are making problems.

[Kai]

On https://id3.org/Home you can find all information about id3-tags

[RFU]

I use Tag & Rename and I've never had a problem with tags

[jovani]

I use AudioRanger Pro Version with automatic tagger to tag and to sort the songs.  All MP3 and FLAC are imported in Radio DJ without any problem afterwards.  It also offers a lot of possibilities to adjust tags, pics, etc, manually.
https://www.audioranger.com/
Succes!

[Yodalex]

I Have same problem! if I import FLA files everithing is OK! But when I import MP3 files, Track no, Disc no, and genre is 0! not imported! I try foobar, tag editor, audioranger,etc, In all the data are display corect, but in RadioDj are not imporded this filds!!!! 

I'm not an expert at all, but I had the same problem maybe: did You tried to edit tag with same RDJ editor? I use to edit with Mp3Tag ( https://www.mp3tag.de/en/download.html ) but I had problems with few tracks that I solved using RDJ integrated ID3 editor

[jovani]

Beatunes helped me a lot.
https://www.beatunes.com/en/index.html

[DavidEsp]

Those people that had problems and those that didn't - what versions of ID3 tag did you use?   Like was it ID3v2.3 or (less widely used but possibly "lower risk" in the context of the "unread tag values" experience) ID3v2.4?  Reason for "lower risk" is given further below.  This is one of two reasons I am now considering moving over from ID3v2.3 to ID3v2.4.  The other is a richer set of officially specified frames / fields. I see that VLC and foobar handle it ok and I don't use iTunes/Music.

BTW: ID3.org has been unavailable for some time now, the most recent archive of it in The Wayback Machine (at the time of writing) is: https://web.archive.org/web/20220903174146/https://id3.org/id3v2.3.0

Regarding the un-read/blank Tag values, could the following be relevant?

I think Mp3Tag (the Florian one, not the other one) writes some text values in a way that many other apps (or the library software they're based on) accept but certain others don't.  I encountered this when I tried importing a file previously tagged ID3v2.3 via Mp3Tag with the TLAN (language) field/frame present (with string-value "fra"), into Jaikoz (which showed that field, in its display,  as blank).  I raised this (https://community.jthink.net/t/bug-language-tlan-appears-blank-unless-written-to-by-jaikoz-then-hex-data-looks-odd/11228/14) with the Jaikoz developer and he modified his software to cope.  I think the cause was (something like) when (depending on the selected string format type (e.g. ISO/ASCII or UTF-8/16) in Preferences - Mp3Tag writes a string that is meant to be defined only by a size-number, but also terminates it with nulls (off-spec but some apps do this and most seem to accept it).  Then if the string-size number accounts for any such nulls then the string-reader, on detecting those nulls (that it doesn't expect) judges the whole string to be "ill-formed" and consequently skips it, resulting in that field showing up as blank. I understand that in ID3v2.4 nulls are "allowed" in a string as "official" delimiters for multiple values in a field, but that for ID3v2.3 any such use of them is "informal", beyond the spec, and (reflecting this), not all apps/libraries allow for such possibilities.  But I am no expert - just a wandering dabbler.

It is clear that different apps can differ in their interpretations of what the ID3.org spec says.  Here's an example: https://stackoverflow.com/questions/17263280/id3v2-specification

Like I said, Jaikoz has since been modified to tolerate what (from its perspective is) "string size number too big", and now reads Mp3Tag-written strings correctly.  The last version that didn't was 11.6.1 Doves, no longer downloadable AFAICT.  The fixed/more-tolerant (depending on your POV) Jaikoz version is 11.6.2 Pulp.  In each case, I used only their macOS variant, I don't know whether or not the Windows one gave the same experience (quite possibly if the same general algorithm/grammar-rules used in each OS-specific variant).

I hope any of that is helpful