bubbleupnp Qobuz proxy

[Michael Waldor]

I'm just curious about how Qobuz proxy is working.

I do assume that bubbleupnp downloads the current track as a whole thus avoiding Internet network issues. To validate my assumption I did watch network traffic between Qobuz server and Android device (my Fritz router does provide such a functionality). And I could really see that there is much traffic at the beginning of a track, but more or less no traffic during streaming. But to my surprise that's happening always at the BEGINNING of a track. I'd expect that for safety reasons the next track would be downloaded earlier, maybe even when the current track is started (imagine short tracks lasting only e.g. 30s).

Maybe you could improve reliability of gapless playback by considering my idea.

Thanks, Michael

PS: I wonder why that option is named "Qobus proxy title" - do you mean tile?

[Michael Pujos]

If proxying is enabled, which can be automatic depending on some renderers or manually forced with More > Settings > Renderer settings > (pick renderer) > Proxy Qobuz Tracks,

BubbleUPnP will buffer the playing track fully as fast as possible, with the renderer reading from BubbleUPnP at its own pace (which can be a tad slower). 

With proxying enabled and depending on your network connection and Qobuz servers bandwidth speeds, it is possible a whole FLAC is read within a few seconds.

With gapless enabled, BubbleUPnP instructs the renderer of the next track immediately after the current track is playing, but it is up to the renderer implementation

to start pre-buffering the next track (from BubbleUPnP if proxying is enabled). It usually may do so 15-30s before the end of next track.

Note that 'Gapless control' enabled in BubbleUPnP for a renderer only applies for playing consecutive tracks of the same album, with the result of the album playing gaplessly if it is actually gapless (which the app doesn't know) and the renderer supports gapless properly. 

'Gapless control' is not implemented as a general way to pre-buffer unrelated consecutive tracks.

As for "Qobus proxy title" I suppose you mean the setting displayed as "Proxy-Qobuz-Title" in German ? 

There is a typo (that I have fixed) and it should read "Proxy-Qobuz-Titel" which is the translation for "Proxy Qobuz tracks".

'Track' is generally translated as 'Titel' in German.

[Michael Pujos]

On Sunday, May 3, 2026 at 6:28:03 PM UTC+2 Michael Pujos wrote:

 It usually may do so 15-30s before the end of next track.

EDIT:  It usually may do so 15-30s before the end of playing track.

[Michael Waldor]

Thanks for your explanation. I feel that 15..30s before start of the next track should be sufficient.

Maybe due to the current playback issues of Qobuz (lasting since some weeks) I simply suffer under that. On almost all albums some tracks jump somewhere in between to the next track, even if bubbleupnp proxy is enabled. Probabely also bubbleupnp won't get those whole (buggy) tracks from Qobuz servers.

Wrt to Title vs track vs. German Titel. That's the correct translation of track, but the English track is also a well established wording within that context. Thus you might as well translate the English track into the "German" Track witch uppercase T.

Regards, Michael

[Michael Pujos]

I will keep Titel as translation for track, unless you really feel Track would be more appropriate (and understood by all German users).

///

Qobuz had some issues the last 2 weeks with some tracks not playing at all but it should be entirely fixed.

Playback should not interrupt mid-track with proxying enabled.

If you have such issue, you can if you wish send (to bubblesof...@gmail.com) a log file, playing a Qobuz track until it unexpectedly stops:

- launch the app
- go into More > Settings > Control
- Enable "logging to file" (at the end of the page).
- IMPORTANT: Exit the app (More > Exit)
- restart the app
- run the app until the problem appears
- exit the app (More > Exit)
- email me the files found on internal storage:

On Android 10 and below:

/Android/data/com.bubblesoft.android.bubbleupnp/log.txt
/Android/data/com.bubblesoft.android.bubbleupnp/prev_log.txt (if present)

On Android 11 and higher:

/Downloads/com.bubblesoft.android.bubbleupnp_log.txt
/Downloads/prev_com.bubblesoft.android.bubbleupnp_log.txt (if present)

You can access them with a file manager app and share them to your email app for sending them.

IMPORTANT: Make sure to not restart BubbleUPnP until you have sent or saved the log file as it is overwritten on app startup. 

[Michael Waldor]

Of course you can stay with the word "Titel" to name the Qobuz proxy option.

Regarding Qobuz track skipping: I still believe that Qobuz servers do still suffer under that problem. Nevertheless I've sent you the logfile by email.

Regards, Michael

[Michael Waldor]

I've sent the problematic track towards my Denon AVR - it fails at around 1:18 and skips to the next track. I did that test using bubbleupnp as controller AND native Qobuz app, both fail. Playing that track locally works fine, i.e. probabely no Qobuz network issue.

But since different renderers fail at the same location, I assume some spurious flac encoding error. I'll try with lower sampling rate ... Anyhow it seems not to be an error within bubbleupnp.

[Michael Pujos]

Did you enable 'Proxy Qobuz Tracks' for your Denon ? It probably needs it.

[Michael Waldor]

Yes, of course. Otherwise I encounter dropouts more often. To be more precise: after enabling Qobuz proxy I had NO dropouts any more at all. But since some weeks I regularly have such kind of skipping to the next track for different albums, sometimes reproducible. Since other users have reported similar issues at Qobuz club, I do guess that Qobuz did not fully resolve its problems - the last report is from 22th of April.

Sadly I can't reduce sample rate within Qobuz app, because my Denon is connected with ethernet (no WLAN).

--
You received this message because you are subscribed to a topic in the Google Groups "BubbleUPnP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bubbleupnp/2bxAE_sCLms/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bubbleupnp+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bubbleupnp/f79cc8f4-e92a-4d89-b3d0-97b651c28703n%40googlegroups.com.

[Michael Pujos]

In BubbleUPnP, you can change audio quality in More > Settings > Local and CLoud > Qobuz > WiFi/Eth audio quality.

You can set it to 44.1/16 and check if the problem persist.

[Michael Waldor]

Yes, I'm just playing with these settings. First result: 320kb MP3 works fine using Denon renderer. Now my surprise: selecting 44kHz flac I get no output at all EVEN for local playback. Next level we know already, local playback works, but Denon will skip during playback.

My conclusion: we are hunting for the still unresolved Qobuz server issue. I'll post it towards Qobuz, hoping to get human support:-)

To view this discussion visit https://groups.google.com/d/msgid/bubbleupnp/5046940d-68e8-48c8-92d9-3c0dbfd9ae34n%40googlegroups.com.

[Michael Pujos]

44.1/16 should absolutely work. If it doesn't (playing to the Local Renderer), please send a log file of it.