Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Converter - No track/total tracks/date... metadata transferred problem. (Read 577 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Converter - No track/total tracks/date... metadata transferred problem.

Hi.
I use foobar for hearing and converting. I'm familiar with it's settings (to an extent, I mean, some things I forget because I don't use them often). I say this so you can know I've tried every setting I'm able to remember. I could have missed something, nonetheless.

Since last update, when I convert a track from say, FLAC (all metadata present, checked it) to MP3 using custom LAME settings, resulting files receive just part of the metadata in the original file, and I don't understand what's going on.
Artist, Album, Comments and most of the fields are copied, including image... but Date, Track number, Total tracks, Disc number, Total discs are not.

To be sure I tested it in an VM and installed the latest version from zero, without touching a single setting. Still, the same metadata isn't transferred.

So at this point I have no more ideas to test.


Can someone confirm this behaviour? Could someone help me troubleshoot this?

Re: Converter - No track/total tracks/date... metadata transferred problem.

Reply #1
I tried to edit metadata from inside foobar (I normally use MP3Tag instead).
I can edit all fields and apply changes... except those mentioned above. If I try to apply changes, they just dissapear even if editing a file with previously populated fields.

This is weird.

EDIT 1: Tracking the problem. Everything's OK in W7, so related to Windows 10 somehow.
EDIT 2: Tracked it down to a modified Windows 10 Pro image. Working OK on a vanilla install.

So... this version has a bunch of features, files, etc, removed.
What does foobar2000 use from Windows 10 that might be missing and cause this very specific behaviour??

Re: Converter - No track/total tracks/date... metadata transferred problem.

Reply #2
Are you perhaps converting to image+cue on the system where the problem happens? Cue sheets have very limited metadata support.

Re: Converter - No track/total tracks/date... metadata transferred problem.

Reply #3
Are you perhaps converting to image+cue on the system where the problem happens? Cue sheets have very limited metadata support.

No. Converting single FLAC file to single MP3 file and instucting foobar to copy metadata after finishing.
Also happens just editing metadata of a file.

My tests seem to confirm that fobar2000 uses "something" from Windows 10 that isn't present in my modified Windows.
It affects only the metadata fields mentioned. They can't be edited (and therefore can't be copied  to a new file after conversion).

I need to find what foobar2000 needs from windows10 to edit those specific fields.

EDIT: MP3Tag can edit those fields. Apparently that program has a way to manage metadata that doesn't rely on windows components for that.

 

Re: Converter - No track/total tracks/date... metadata transferred problem.

Reply #4
A missing OS component doesn't explain the issue. For tagging purposes filesystem access and UTF-8 string conversions are probably the only features used.
Have you checked the output files to see if their specs show some differences? Like something forcing only ID3v1 tags. If foobar2000 runs into problems it might report something on its console.

Re: Converter - No track/total tracks/date... metadata transferred problem.

Reply #5
A missing OS component doesn't explain the issue. For tagging purposes filesystem access and UTF-8 string conversions are probably the only features used.
Have you checked the output files to see if their specs show some differences? Like something forcing only ID3v1 tags. If foobar2000 runs into problems it might report something on its console.

Output files are completely normal AFAIK. Console shows no error.
I've forced all combinations available, ID3v1 - ID3v1+ID3v2 - ID3v2 - ID3v2.3 - ID3v2.4. No change.

This is quite significative from my point of view: it happens not only when converting files. If I try to edit "conflictive" tags of an already existing, correctly encoded and properly tagged file... they're just reset to empty fields.

EDIT: I can edit FLAC tags just fine. Editing MP3 flags causes the problem.

Re: Converter - No track/total tracks/date... metadata transferred problem.

Reply #6
If you take a problem MP3 to your working system, can you edit the tags there or does it show the same problem?

Re: Converter - No track/total tracks/date... metadata transferred problem.

Reply #7
If you take a problem MP3 to your working system, can you edit the tags there or does it show the same problem?

Yes. foobar200 in a vanilla Windows 10 install edits those files without a problem.

I think I've tracked it down to a file, C:\Windows\System32\C_20127.NLS [US-ASCII (7-bit) code page]

That file is not present on my modded Windows 10 version. If I copy it to the \System32 folder the problem is solved. I can edit MP3 tags and metadata is properly transferred after converting.

Re: Converter - No track/total tracks/date... metadata transferred problem.

Reply #8
Why the hell are you trimming off NLS tables?

Just FYI, it uses that for Unicode to ASCII, including accented characters to their unaccented ASCII equivalents.