Big problems with M4A after updating to Windows 11 22H2

Hi Pete,

We're looking forward to today's Patch Tuesday. The question arises, will Microsoft indicate in the list of updates that this particular error has been fixed? Otherwise, you ask to send problems through the Feedback Center, but now we know that the problem is already known and has been fixed. So in the list of updates will there be information that the problem, which is already more than two years old, has finally been fixed, or will it write that “several minor problems have been fixed”? :-) When should you buy cake and champagne? :-)

"Playing mp3 on a loud soundsystem with less than 320kbps will be noticed by the audience: bad bass definition and distortions in medium/high frequencies (kind of electronic whistle). Depending on the source, even a 320kbps mp3 is not enough - we need a FLAC or a WAV."

This is nonsense. mp3 320kbps is fine, as long as you didn't get something which is a fake 320kbps and was transcoded.

"I read fully the previous post - dedicated to 22h2:

We are currently on 23h2 - and it is still not fixed that the reason why I'm launching again the discussion in the current thread."

As has been mentioned multiple times, it is currently fixed in the testing version, and the release version will come later.

Dear Pete

I read fully the previous post - dedicated to 22h2:

We are currently on 23h2 - and it is still not fixed that the reason why I'm launching again the discussion in the current thread.

The reason why i'm posting in this thread is clarifying the severe impact on iTunes files features

I would complete here my description - as this is still unclear

itunes m4a are encoded with a variable bitrate encoding - much more performant than mp3 fixed bitrate encoding

It is said that the equivaelent of a 320kbps mp3 quality is approximatively 128kbps m4a

Please note that

Playing mp3 on a loud soundsystem with less than 320kbps will be noticed by the audience: bad bass definition and distortions in medium/high frequencies (kind of electronic whistle). Depending on the source, even a 320kbps mp3 is not enough - we need a FLAC or a WAV.

But as iTune has some exclusivities on releases, it is very difficult to find some tracks elsewhere.

And m4a is a little bit better than mp3 320bps - does the job in most of situations.

Now using iTunes on Windows 11 22h2, 22h3 has a described workaround :

turning itunes m4a files into a 192 kbps fixed-rate mp3 - meaning that will result to a lesser quality sound than a 320bps mp3

Conclusion:

An mp3 320kbps 'stealed' on a pirate platform like mp3XXX has better quality than an mp3 bought §1.5-§2 on itunes and converted into a 'poor' mp3 - following Microsoft workaround.

Thats the reason why previous answers you mentioned do not resolve the problem at all.

Hope this helps clarifying the Microsoft / iTune DJ position

BR

Dear Pete,

I have encountered this problem for years now; the m4a problem is very well described here, and is still present with the latest Win11 updates. This thread is not the only one on the Internet. I think you don't understand the impact of disregarding this issue.

Users playing m4a files on Windows music software can no longer rely on their iTunes library.

Why?

Because m4a tracks cannot be broadcasted nor played in public with the problem described here.

Translating m4a into mp3 could be a work-around but will have 2 issues

1. all metadata and hotcues will be lost
2. playlists referencing any m4a must be manually updated with mp3 copies - may be very long
3. with the iTunes system, both m4a and mp3 will be stored on the disk - doubling the library space.

We are not talking about a few files bought on iTunes. Professionals do store thousands of tracks and iTunes is a good solution to get the music on different devices instantly, providing tracks with very good metadata information.

The solution - for me and I think many users - and despite the advantages of iTunes - is not buying anything ion the iTunes Store anymore- because m4a library is too complicated afterwards to maintain.

Is it the goal? Killing iTunes? I can't believe it...

The consequence is more like users running Music Software like Rekordbox Virtual DJ or Traktor can regret not having bought a Mac instead of Windows computer.

Now if Microsoft really "supports" m4a, I think that Microsoft must provide a solution - not only work-arounds.

As m4a codec is part of Windows 11 system still have issues, I think there are 3 concretes options to consider today:

a) Microsoft announces that Windows 11 no longer supports m4a - forcing software vendors like Serato providing there own codec part of their product.

b) Microsoft announces a date for a patch to be released

c) Alternative: statu quo and Microsoft supports an agreed vendor able to fix this issue delivered in a third-party driver software.

Thank you for your consideration and feedback about this annoying issue

Very Best Regards