Big problems with M4A after updating to Windows 11 22H2

Anonymous
2023-05-16T09:52:13+00:00

Dear colleagues, after updating Windows 11 to 22H2, there were significant problems with playing files purchased from iTunes in .m4a (AAC, ALAC) format. This problem has been fixed by a lot of people all over the world and is especially evident on the DJ forums. Problems are observed with the quality of playback, and with the volume and with a number of other parameters. This problem is detected on software that uses the built-in Windows 11 22H2 codecs (on earlier versions, the problem is not observed), Windows Media Player, RekordBox, Serato DJ Pro, etc. On players that use their own codecs (VLC, iTunes, JetAudio HD, etc.) there is no problem. When converting m4a to mp3, there are no problems. What it looks like: https://youtu.be/WqAA12pfWjg and https://youtu.be/um3QSTuLg6s Software vendors fix this issue after the 22H2 update as well, label it as a Microsoft issue and offer a workaround, such as converting the entire m4a database to other formats, which of course is completely unacceptable advice with a database of several thousand files. https://forums.pioneerdj.com/hc/en-us/community/posts/12212808237337-RekordBox-5-8-7-m4a-problems Does Microsoft acknowledge the existence of this problem and when is it planned to release an urgent fix, since. the problem has been observed for a very long time and prevents normal operation?

Thanks in advance!

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2024-03-27T00:42:35+00:00

I installed KB5035942 and unless I'm severely mistaken, the issue seems to be resolved.

Can anyone else confirm?

Was this answer helpful?

6 people found this answer helpful.
0 comments

115 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-01-30T00:14:27+00:00

    "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.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-01-29T19:41:56+00:00

    Either I'm misunderstanding you, or you didn't see the post stating that the fix is not yet in Windows, and won't be until February. It's only currently in the Windows Insider Canary channel builds.

    Pete

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-01-29T18:28:38+00:00

    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

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-01-27T16:07:08+00:00

    Please post your feedback hub link with your repro recording. I've said many times in this thread that videos are great, but they don't get us the detail we need to actually figure out the cause. Instructions are in this thread. I'm at the NAMM show on my phone so can't post screenshots or anything so please look back in this thread.

    It's possible the klite codec reads the flags in the iTunes files the same way we do.

    Pete

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments