Me too. Glad to see it's marked 'Fixed' here. This problem also affects
I actually reported this bug back in January 2024 on the V13.5 Bug Reporting Sheet (see row 1346 under 'ALL DATA' or row 25 under 'Sound issues'). I wonder if it went under the radar back then. It would be very understandable if it did given the sheer volume of bug reports in the immediate aftermath of V13.5's release.