"Play Next" causes bitrate change

[joerosenthal]

Clicking "Play next" on a 96kbps song while a 44.1khz song is playing switches the bitrate.

[drpoutine]

Observed this as well.
Sometimes the bitrate will not change until you click somewhere in the progress bar and it changes back to the correct sampling rate.

Unsure if the new beta app has a debugging log to see where it fails.

[waszqba]

The original description is a bit short and got me thinking if this is the issue I'm having, so a bit more verbose description of my case:

Context:

• M1 Max machine with Sonoma 14.0 running 1.1 build 16 (beta11)
• Bit depth switching enabled

Issues:

• Sometimes LSS misses the switch for a new song when going from 44.1/16 to 48/24 on a playlist without skipping
• even when the next song has the same rate/depth, LSS sometimes switches to the next next song's params
• skipping to the next song with different depth/rate is a hit or miss:
  • LSS can ignore the new bitrate altogether
  • LSS can switch to the correct depth/rate but then switch to the previous one

What fixes the rates and depths:

• scrolling through the song fixes the rates

Overall thoughts

The switching itself is quite efficient and works fine, but the detection mechanism seems to struggle and that's where we should investigate. If I find some spare time I'll try to tinker around with it and maybe submit a PR with a fix but I can't promise anything