Minim stream being throttled on QNAP NAS ?

[simoncn]

(30-11-2024 17:15)windbag Wrote:  My partner says she doesn't have a clear mental picture of which part of the steaming chain does what, and I have to concur - I'll probably start a new thread along those lines. For example, once Bubble has presented a playlist to Minim, those commands execute and steaming starts, is it Bubble that controls the streaming flow or a combo of that and Minim ? My partner asks, if the phone with Bubble on it goes out of range, does the stream stop ?

In standard UPnP, it works like this:

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 is not involved in step 3. However, the control point can choose to become involved by sending a proxy URL to the renderer in step 2 instead of sending the URL provided by the server. In this case, the renderer reads audio data from the control point and the control point reads audio data from the server and manipulates it in some way before passing it on to the renderer. For example, if you have configured BubbleUPnP to transcode the audio data, this is how it happens.

If the control point is not available for any reason (off or out of range), the current track continues to play (step 3) but track advance (step 4) won't happen. Also, URL proxying (if in use) won't work, so the track would stop playing part way through after any buffered data has been played.

As using the 2x and 3x settings has made things worse, it does sound like there is a blockage somewhere in the chain between the server and the renderer. MinimServer is definitely sending all the data requested.

You can confirm whether there is any URL proxying by checking the IP addresses of your devices. In the log you sent, the device reading the audio data from MinimServer has the IP address 192.168.0.72. If this is the IP address of your Sonos renderer, there is no URL proxying. If this is the IP address of the phone running BubbleUPnP, this means that URL proxying is happening.