Big problems with M4A after updating to Windows 11 22H2

Pete, I do appreciate your responsiveness. It's nice to be able to have some actual conversation. Thank you!

I actually did post about this in the Feedback hub about 6 months ago. https://aka.ms/AAns8g9 That's recent? I know you said to add videos and reproduction elements, and recheck the post in a month, and if there's no activity to go and post it more places, but I have no way of knowing if that will get more attention. Even if it did, there no way to know if any changes would occur. I may still do it next time (I appreciate the advice) but, in all honesty, I'm not getting paid for any of that work and I am a busy person.

I'd like to reiterate, I appreciate you and how you're actually being helpful here. I just think that the policies and methods used by microsoft are clunky and inefficient. It seems that's largely due to volume... So, in light of all this, I'd like to promote a suggestion that might help us all a whole lot: "Updates" are only mandatory if they are directly related to essential security updates. No more forcing an "update" that takes away a feature (like moving the taskbar). He's the feedback hub link https://aka.ms/AAnt63c
Considering the post for moving the taskbar (https://aka.ms/AAd2jme) has 27,000+ upvotes and no action has been taken, I don't think this will do it, but it's worth a shot.

Drew

Thanks. I didn't see your feedback hub entry because it doesn't have M4A in it anywhere (that's what I searched on previously). Good to know it's there.

FWIW, we don't need videos or similar, but we do need repro recordings. If you pick the Devices & Drivers -> Audio category when reporting something through feedback hub, you are able to record, right through the tool, what happens. Nothing else needed.

In this case, it was filed under Windows Security, so the audio team would never have seen it, and any recording would not have the correct data. I do wish the FB Hub tool had more guidance for picking categories.

On the taskbar docking: not sure where the shell team sits with that one, and why it hasn't been implemented in the new version (the taskbar was completely rewritten for Windows 11, which is why some catch-up was needed). They did take the feedback for not combining icons and showing icon labels and added that to a recent Windows 11 release, however, so they do listen, even if it takes a while.

Updates: I know that goes against the direction Windows has taken, so I wouldn't expect to see anything there. However, if you are running Pro or better, and know the risks, here's the supported way to disable updates:

https://devblogs.microsoft.com/windows-music-dev/take-control-of-windows-updates-on-your-windows-11-daw-pc/

Pete

Pete, I do appreciate your responsiveness. It's nice to be able to have some actual conversation. Thank you!

I actually did post about this in the Feedback hub about 6 months ago. https://aka.ms/AAns8g9 That's recent? I know you said to add videos and reproduction elements, and recheck the post in a month, and if there's no activity to go and post it more places, but I have no way of knowing if that will get more attention. Even if it did, there no way to know if any changes would occur. I may still do it next time (I appreciate the advice) but, in all honesty, I'm not getting paid for any of that work and I am a busy person.

I'd like to reiterate, I appreciate you and how you're actually being helpful here. I just think that the policies and methods used by microsoft are clunky and inefficient. It seems that's largely due to volume... So, in light of all this, I'd like to promote a suggestion that might help us all a whole lot: "Updates" are only mandatory if they are directly related to essential security updates. No more forcing an "update" that takes away a feature (like moving the taskbar). He's the feedback hub link https://aka.ms/AAnt63c
Considering the post for moving the taskbar (https://aka.ms/AAd2jme) has 27,000+ upvotes and no action has been taken, I don't think this will do it, but it's worth a shot.

Drew

Colleague, the reviews you write about and this topic, like the second one you mentioned, were created by me :-) As well as recommendations to write a review in the built-in “Feedback Center” are mentioned everywhere, in many places where this problem is discussed, including There is also this recommendation under the video provided, as well as information that your engineers know about the problem (this has been happening for a long time). So I spent a few minutes working on this, many minutes actually :-) Thanks for helping me finally solve this problem. Millions of people will be grateful to you. Something else is strange, because Microsoft is probably conducting independent testing, including the multimedia block, just as it receives information from participants in preliminary testing. How did it happen that for almost 2 years this problem was “invisible”, provided that it existed in all builds starting with 22H2? :-)

"

471 просмотр 24 апр. 2023 г.

The first track I play is an MP3 file that is playing correctly without any issue. The second track I play is an AAC/M4A file purchased from iTunes, and you can see the volume fluctuations in the waveform (as well as hear the fluctuating).

Edit: so after a bunch of troubleshooting with Microsoft Support via DM on Twitter, they recommended that I submit the issue to them via the Feedback Hub that's apparently built into Windows: https://support.microsoft.com/en-us/w..."

Colleague, what you are saying is not entirely true. This problem has been known for a long time, even if you watch the videos in the first message, you will see in the comments that the problem was reported on the forums, on social networks and in the support center from various sources. I have signaled it myself many times. It's great that the new build has finally fixed this issue, but millions of people aren't using pre-release builds. It would be reasonable to release a separate small patch this coming Tuesday. Thank you, although of course my patience has already run out.

I'll reiterate what I said in an earlier post: posting videos and posting on forums doesn't actually let Microsoft engineering teams know about the problem. And forum posts typically contain no actionable data we can work with. Unless someone on that engineering team happens to stumble across that content, it's not getting to the teams, and even then, without the data, there's not much they can do. You may have known about the problem, as well as many others in the community. But again, no reports, and no data we could use to investigate.

Engineering teams typically aren't on these peer-to-peer forums, or manufacturer forums, etc. and aren't scouring YouTube for videos. Feedback Hub is available in all Windows 10 and Windows 11 editions on all channels (not just Insider). That's how engineering teams are made aware of bugs. When there are many upvotes or entries in a relatively short amount of time, or when a Microsoft employee promotes an entry, the entry goes into our bug system for evaluation. The more entries with recordings/repro steps, the easier it becomes to investigate and fix.

There are only two feedback hub entries on this topic and both are quite new. The first reply in this thread, back in May, links to how to post the issue to Feedback Hub, but that wasn't done. You even replied that the problem was already known. The problem on the Pioneer Dj rekordbox forum was also never reported to Microsoft by any companies or users there. Again, it wasn't actually known to Microsoft.

So, this problem was not actually *reported* to Microsoft until recently. Relying on others to report a problem that is important to you does not help get the problem fixed as you can see from this thread which is an example of everyone thinking other people had already reported the problem. Instead of linking to another forum, you could have filed a Feedback Hub report, with a repro/recording. It's quite easy to do. If the problem was important to you, it would be worth it to take a few minutes to do it -- less time than replying here :)

Then, if you feel a feedback hub report isn't getting appropriate attention, you can share a link to it in forums, videos, etc. If the Feedback Hub report is within approximately 1 month, or there is one within a month that contains the recording (the data expires for privacy and other reasons) they can take a look at it right then.

As for release: there's a defined path to get a change from internal testing to a production release in retail Windows. It will almost certainly take longer than next Tuesday. I will post here when I know when it will make it out.

Pete