Question about control point persistence when casting minimserver to DLNA speakers

[Unrevised0087]

I have setup minimserver as my music media server, and bubbleUPNP as control point for casting my music collection, but I have a specific question about how they handle DLNA casting.

Question:

When I start a 2000-song track mix playback using and cast to one of my Sony DLNA speakers, does the bubbleUPNP app process need to remain active (unkilled) on my Android phone to keep the speaker playing?

Expectation:
I’d love for the speaker to continue playing the playlist with random order and gapless playback functioning independently, even if the bubbleUPNP app getz killed or my phone gets taken off the home network (e.g., leave the house).

Is this possible with the current setup? What more do I need?

Any insights or clarification would be greatly appreciated! If logs or more details are needed, please let me know how to provide them.

My setup is as follows:

* Minimserver on Synology: hosting ~2,000 songs
* bubbleUPNP on android
* Living Room: Sony HT-Z9F
* Bedroom: Sony SRS-X88

[stefano_mbp]

Using a upnp/openhome renderer it is possible (ie. Lumïn, Linn)
If the renderer isn’t openhome then the control app must remain active, unfortunately I don’t know your sony DLNA speakers

[Unrevised0087]

(08-08-2025 11:42)stefano_mbp Wrote:  Using a upnp/openhome renderer it is possible (ie. Lumïn, Linn)
If the renderer isn’t openhome then the control app must remain active, unfortunately I don’t know your sony DLNA speakers

You are right.
Renderer must be openhome, which sony does not support of course.
Now I'm trying minimserver + bubbleupnp server + bubbleupnp app.
bubbleupnp server is constantly running on my nas, and creates openhome proxies with all my sony speakers.