Minim stream being throttled on QNAP NAS ?

[windbag]

(30-11-2024 18:19)simoncn Wrote:  1) The server sends a list of track URLs to the control point (BubbleUPnP) together with other metadata
2) The control point tells the renderer (Sonos) to play one of these URLs
3) The renderer reads the audio data from the track URL (i.e., from the server) and plays it. The control point is not involved.
4) Shortly before the end of the track, the control point sends another URL to the renderer for playing when the current track finishes
5) Steps 3 and 4 are repeated until the control point's playing queue is empty
&
The control point...but track advance (step 4) won't happen.

Translating that sequence by swapping
server=>Minim, control point => Bubble, renderer => Sonos, I get :

1) Minim sends a list of track URLs to Bubble together with other metadata
2) Bubble tells Sonos to play one of these URLs
3) Sonos reads the audio data from the track URL (i.e., from Minim) and plays it. Bubble is not involved.
4) Shortly before the end of the track, Bubble sends another URL to Sonos for playing when the current track finishes
5) Steps 3 and 4 are repeated until Bubble's playing queue is empty

Step1-That can't be the first step, as Minim doesn't know anything about the playlist now required until Bubble sends it that info.
Are the server and control point assignations the wrong way round in points 1&2 ?
They seem the right way round in 3 & 4

Similarly:

Bubble is not involved in step 3. However, Bubble can choose to become involved by sending a proxy URL to Sonos in step 2 instead of sending the URL provided by Minim. In this case, Sonos reads audio data from Bubble and Bubble reads audio data from Minim and manipulates it in some way before passing it on to the renderer.

Yes, that makes sense as, for the current 'lead' Sonos in the current group, I had FFmeg audio decoding switched on in Bubble, making it 'become involved' in the proxy issue.

It does make it VERY important that all my Sonos units have the same settings in the Bubble Renderer selection. Without it, making the 'same' Sonos group with a different 'lead' unit could give totally different results !
As the Sonos all too frequently has a strop and breaks apart existing groups, I wonder if this might account for the unexpected change in behaviour about 6 weeks ago.
ie I just regrouped the Sonos after a split and chose a different lead Sonos for the same group combo, but had a different renderer setting in Bubble.