Unable to update "Comment" field in FLAC files (Win 11)

Hi,
I have noticed a bug in that mp3tag does not display my updated (and saved) Comment field in FLAC files (or my djay Pro software ignores that datafield change in files edited with mp3tag). All other fields properly display when updated.

It only happens with FLAC files. In each case, there is only one file by each name on my local drive. (No externals are connected).

This has happened with every FLAC file I have tested.

My OS is Windows 11 Pro (clean install).

Any suggestions?

Thanks!

If you reopen these FLAC files in mp3tag do the comment fields exist?

If the first test above shows that the comments remain in mp3tag, then the next test needs to confirm of you DJ software is using the same field. Add a comment in your DJ software and save it. Then open that in mp3tag and check all fields to see where that comment is stored. Use the Extended Tags window Alt+T you to see all stored tags easily.

If the comment that was saved in your DJ doesn't show up in mp3tag it is likely they are using a custom tag that is not supported.

Hi,

Thanks for responding. My replies are below:

If you reopen these FLAC files in mp3tag do the comment fields exist?

Yes. The “comment” field exists, but the contents of that field are inconsistent. I’ll explain below.

If the first test above shows that the comments remain in mp3tag, then the next test needs to confirm of you DJ software is using the same field. Add a comment in your DJ software and save it. Then open that in mp3tag and check all fields to see where that comment is stored. Use the Extended Tags window Alt+T you to see all stored tags easily.

If the comment that was saved in your DJ doesn't show up in mp3tag it is likely they are using a custom tag that is not supported.

Let me state that djay Pro 5.2 (Win) software does not provide a means to edit metatags. It requires the use of the third-party tag editor, which is how I came upon using Mp3Tag software.

Again, this is only impacting FLAC files and that I have repeated this issue on several FLAC files. Also, gentle reminder that this is on the Windows 11 Pro OS.

Continued experimentation has revealed the following:

Djay Pro 5.2 calls the field “Comments” while Mp3Tag calls it “Comment” - and - Windows File Explorer calls it “Comments”. The contents of File Explorer’s “Comments” field correctly ports to the “Comments” field on djay Pro 5.2 (Win).

Another field, for example, “Genre” translates properly among all three platforms, I’m guessing this is due to the consistency of the identical field name.

Based on the above, it would seem that - at least among the platforms of Windows File Explorer, djay Pro, and Mp3Tag, it is Mp3Tag that uses the less popular “Comment” field title as opposed to “Comments” (with an s at the end).

Is this something I can change on my end? Or would making that modification to Mp3Tag require someone’s else’s effort?

Thanks very much for your time.

The label in the Windows explorer does not say a lot - e.g. as I use the the German version of Win11 the comment has "Kommentar" as label.
So, please

and preferably show us as screenshot of that dialogue.

Note that the friendly name that you see on the face of mp3tag likely maps to a far less descriptive field name internally and even depends on what audio format it applies to. Whether it shows as Comment in mp3tag or Comments in Explorer or other software is less relevant.

This will make it more challenging to help identify the field frame they are actually using. Do they provide any resources that help point you in the right direction for this? The FLAC format is easily the most universal lossless format, so supported fields are not usually an issue.

From the documentation.

image

Hello,

If I understand you correctly, the actual field name that File Explorer, Mp3tag and djay Pro likely have "background" field names - not just 'friendly' field names as you termed them.

If that is the case, I understand. However, it would seem that Explorer and djay Pro 5.2 are using the same internal descriptive internal field name (and so the same field contents are exchanged between them), while Mp3tag does not. At least on FLAC files and on Windows 11.

While I check with tech support at Algoriddim (djay Pro's manufacturer), might you be able to verify if, indeed, Mp3tag and Explorer are using the same internal descriptive internal field name in their respective Mp3tag's "Comment" and Explorer's "Comments" friendly fields?

Also, I am including screen shots below, as requested.

Again, many thanks for your help.

The MP3tag screenshot shows the main window but not the extended tags dialogue as requested.
Press Alt-T to open it.

Use the field DESCRIPTION in MP3tag

Sorry, please see this screenshot including the window dialogue displayed when I press Alt-T in Mp3tag.

As you can see in the screenshot I just pasted, Mp3tag does not show a field called DESCRIPTION available to edit. (See the left panel of the window.)

Also, djay Pro 5.2 does not display a field called Description. Nor does djay Pro 5.2 offer any options to display anything other than its default tag fields.

Further, the contents that you see in Mp3tag's extended tags dialogue window in the field called DESCRIPTION was content I added in the "Comment" field of Explorer.

Fun!

Yes, the default configuration does not show that field.
But you can customize MP3tag.
Either you add a field in the tag panel to show the contents of DESCRIPTION
(see the documentation:

Or add a mapping in the Ctrl-O Options>Tags>Mapping
grafik
see the bottom line in the screenshot

Thanks for that suggestion, but as I mentioned earlier (in this admittedly long thread!), djay Pro software does not offer the DESCRIPTION tag as one of the displayed tags in that software. Seemingly, djay Pro does not offer options in the library tags it displays - just the default fields.

Pardon my ignorance, but does Mp3tag offer me the option of renaming a field?

This goes back to what I posted earlier about tag field mapping. The fields in mp3tag map directly to the common "standards".

Your Djay Pro software is using this field for what they are calling comments. Regardless of the name, the container is what matters. Knowing that this is where your FLAC comments are being driven from, that is where they need to go.

See the above suggestion from @ohrenkino to have mp3tag automatically do the translation for you. Using that method you can enter the data consistently in the current COMMENT field and when saved for FLAC files they will be saved in DESCRIPTION. When viewed in Explorer and your software, you should now see what you are expecting.

Yes, true. This may be due to some unanswered requests that had to be issued more than once and also a lack of descriptions which of the already mentioned suggestions you tried and what the result was.

You can see in your own screenshot that MP3tag shows there a field with the name DESCRIPTION for the data that you entered in the Windows Explorer.
So, what happens, if you take a new flac file, create a new field of the type DESCRIPTION enter some data and check that file in the Windows Explorer and then in your player?

Your problem has already been answered here:

I must be misunderstanding something. It seems that the advice I was given (above) does not apply to FLAC files. Is that correct?

The suggestions are all correct.
But which of these have you applied so far?

Again, apologizing for the long thread, but this all started with the issue of mp3tag's porting of data specifically for FLAC files.

I'm trying not to waste anyone's time. Could you please clarify which solution would port the field contents into my djay Pro 5.2 sofware (as MS File Explorer does)? Also, I should point out that I don't want to create a 'solution' for FLAC files that would hinder the proper field contents from mp3tag to djay Pro (such as the Comments field) into other file formats, such as mp3, wav, aiff, etc. That would just be trading one problem for another.

Thanks very much for your help.

If you doubt even the developer's suggestion as linked in this post:

then there will be no way around it but that you have to test it yourself.

  • Set up the mapping,
  • enter something in the field for comment in a FLAC file and also for an mp3 file.
  • save the modification,
  • check in your player
  • check in the windows explorer
  • whether you see the expected data.