matching up metadata field names btw Audition and Windows 10

Report · Jan 26, 2020

with a music library, I like to populate both my wav and mp3 files with meta data.

Audition file info has the following first few meta titles:
Display Title

Original Artist (for standard RIFF) or

Song Title

Artist (for MP3 ID3 tag)

These seem pretty self explanatory, But Windows 10 seems to have its own idea of field names

I can figure out that Windows' "contributing artist" equates to the "original artist" or "artist" in Audition, but I can't figure out what Windows 10 column heading matches up to "title" or "song title"

There should be a one-for-one correspondence, and I just can't find title or songtitle to display it with Windows Explorer (or whatever it is called in Windows 10)

Can someone help me?

Report · Jan 27, 2020

I think you may need to take this up with Microsoft. The metadata that Windows uses doesn't appear to be consistent; the 'media' part of a file's properties it appears to be getting from the RIFF data, but the basic data is coming from the XMP metadata. That's an ISO standard (okay, Adobe invented it, but whatever...) and the field names are internationally agreed. If Microsoft are going to show you properties, those should be consistent with that, I would have thought.

Great if it was that simple, but it doesn't appear to be. For instance, if you put an artist name in the ID3 field in Audition, it will show up also in the RIFF data as 'original artist' but nowhere is it visible in the XMP data as such - although it must be there, because that's the format that metadata is stored in for a wav file, It can't save ID3 data as such, because that isn't an allowed metadata format for wav at all. I suspect that this may just be a 'visibility' issue, but I'd have to get that confirmed. There are all sorts of other little issues as well - the whole subject is a bit of a minefield, and bugs show up in it regularly.

Report · Jan 27, 2020

I was afraid of that... But I can't be alone in wanting this. Millions of
PC owners are now putting their audio files on Windows.

Report · Jan 27, 2020

The other problem with this (not of Adobe's making at all) is that there's absolutely no control over what the MP3 encoder picks up and translates when it creates the MP3 - it's a bought-in package from Fraunhofer. Although now, I don't think it needs to be any more, as it's out of patent protection completely. Dunno what's going to happen about that...