I installed KB5035942 and unless I'm severely mistaken, the issue seems to be resolved.
Can anyone else confirm?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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!
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.
I installed KB5035942 and unless I'm severely mistaken, the issue seems to be resolved.
Can anyone else confirm?
Hi All
Thanks to @Feelisreal and the Mixxx team reaching out directly and providing a bunch of repro information, we're looking into this.
I hate seeing folks frustrated here. These forums can be great for solving typical consumer problems, but they are not an effective way to get bug reports to Microsoft. I wish we had a better loop here on the forums, but it's just how these intentionally operate. As a result, posting here is not actually reporting a problem to Microsoft. That's why we have Feedback hub and official support.
Feedback hub entries, with recorded audio traces (which require picking the correct category when reporting) and as many details as possible, are the more effective approach. The more entries or upvotes we see on a specific topic, the more it bubbles up. Feedback hub reports with sufficient upvotes and activity make it into our internal bug tracking systems if they have actionable information. It's not perfect by any stretch, but it does work.
There are only two feedback hub entries on this topic right now, the oldest is from a month ago and is under audio and sound (correct category). The other is 3 weeks ago and is under "install and update" so the audio team wouldn't see that one and it wouldn't include the correct traces. Neither report has yet hit the threshold to make it to engineering but I've made folks aware.
We're looking into it, now, thanks.
Pete
Any update to this? I have the same issue!
So we are talking two years! It took me countless hours to even figure out, that the issue was Windows 11 and not something else. Seeing this and sweatting through various DJ Sets that it wont be too noticable I am contemplating of abandoning Window alltogether I might move over to Mac since it will also run all my producer tools. Beeing a "Hobby DJ" I can only wonder what it must be like for people who make a living out of DJaying and with Rekordbox beeing affected probably a few thousand Dollars worth of equipment, that cant be used with their Windows 11 Computer for several years now.
It´s still not fixed! Update 23h2 08.11. F. Microsoft for that! You had over 2 years time! Whats going on! Money is running from us with that realy BIG PROBLEM!