I am getting a weird error message every time I start audio cast. It still seems to work correctly though, so don't know if anything is actually wrong. Here's the message:
Audio Cast: System UI: cannot play: cannot resample (unsupported on 64-bit CPU)
edit: forgot to mention I'm using a Nexus 6P.
It was down and is up again now.
The package needs to be updated but update11 is not the reason. It needs to be updated so it installs on DSM 6 beta.
All the installers always install the latest version (update11 at this time) and are not updated themselves when there
is a new updatexx version.
To update your current update10 version, simply start the web config, go to Settings/Update and tap 'Check for update'.
It is possible your install is already up-to-date, if you did not disable autoupdate.
This message is shown each time an app or process (System UI here) attempts to play audio that is not 44.1 kHz / 16 bits (the output combo of Audio Cast).
In that case, Audio Cast resample to 44.1/16, but it is not supported on 64 bit devices (only on 32 bit), for technical reasons.
Maybe it will be supported in the future but it's a bit complicated.
Here it is probable that you have a system sound played by System UI that is not 44.1/16
Bug: Since some weeks, or ~2-3 months, cant really say when it started, the app takes much longer to start than it used to. If you tap the app the phone/tablet does nothing for about 3-6 seconds and then BubbleUPnP appears. This is really bad behavior. You should look into start the gui, and then do background stuff or do the init stuff via threads, not blocking the gui to load.
Well, this does not happen on most devices. Only the very first launch after install takes several seconds, as a long one-time operation is performed.
Can you tell me what is your device, android version, ROM (if any), whether you are rooted and have Xposed installed.
It happens on all my devices, rooted or not rooted, custom rom or original rom, no xposed running on any of them though.
Samsung Galaxy SIII i9300, custom rom, rooted, Android 5.1.1
Nexus 7 2012, original rom, rooted, Android 5.1.1
Telekom Puls, original rom, no mods, Android 5.0.1
I recorded a small video (the launch really starts when the icon becomes highlighted) taken on my Alcatel OneTouch Idol 3, Android 5.1.1. Can you tell me how it compares with your devices.
It would be helpful if you could record a video, for example on the SGS3, so I can have a better idea.
This app can be used or if you can adb to your device, screenrecord.
Your video seems same as broken. It was way better before in some older version. The main gui should be loaded really after 0.5-1 second and not after 3-x seconds. Even if the guis is grayed out, and then becomes usable after some preload time, it feels much better this way then to have no responses after a click for a while.
Given your initial post I was expecting something much worse. It takes 3s at most. Other apps also do not load instantly but will show a splash screen.
Maybe I can optimize it more a bit and gain 1s at most by lazy loading some stuff, but it will be difficult. And it is not a matter of "do background stuff or do the init stuff via threads, not blocking the gui to load".
The loading time is about 3 seconds on the s3 (now, it was much better like mostly instant in older versions of your app), 3+ on my other devices. Most other apps load instantly on my s3, like I said, yes, "loading screen" or grayed out gui is the way to go.
BubbleUPNP still rocking my world. Thanks for the recent chromecast discovery fixes, they improved things a lot.
Of course, this is the kind of terrible relationship where we only talk when I have a problem. So....
When playing from the local media server (on an SD card on a Moto X Style, but also a problem with my previous Moto G), BubbleUPNP occasionally just seems to lose the SD card, as in all the file handles go stale or something. I fix by restarting and recreating the playlist (as the old one no longer appears to be valid) but it makes for using bubbleupnp for playback on the move tricky.
Also a couple of feature requests:
1) Would it be possible to for bubbleupnp-server to support gatewaying Chromecasts via an OpenHome renderer? This would enable both me and my partner to be able to control the music when it's playing multiroom.
2) Chromecast multiroom is a bit buggy at the moment. So we end up rebooting the Chromecasts more than we'd like to. Could a "reboot device" option be added to the context menu for a chromecast. Internet search suggests that it's a matter of sending a relatively simple POST request to the Chromecast. Details at
If there could be a "reboot all Chromecasts in group" option too, that would be even more handy, although that's probably a lot more work.
with version 220.127.116.11 i have the error below streming from Qobuz. This error appers only with this album. With oiginal Qobuz app works correctly.
Could you help me to investigate/fix?
Since 2 days I have the problem that I can`t login into my Tidal account with Bubbleupnp. All other devices with Tidal and other apps with Tidal login are working, only the Tidal login in Bubbleupnp doesn`t work.
Error message: Authentication failed : Client not found
Bubbleupnp server want`s always to start the playlist from Tidal, but the app shows me error 600...
Has Tidal something changed, like in January this year???
I tried searching, but didn't find anything;
My question is regarding "casting" Tidal to a UPnP renderer.
Using Bubble on a Android 11 tablet, there is no "notification bar" now playing item. Is this the expected behavior?
When using, for example, MConnect to do the same thing, there is a notification item that shows what's playing and has simple playback controls.
When using Bubble, there is no such item, so if I want to quickly see what's playing I have to open up the full Bubble application.
I`m using BubbleUPnP Server on my Synology NAS and from time to time BubbleUPnP Server crashs.
Server log says:
[main ] SEVERE - 01:00:16.953 - Main : java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Caused by: java.lang.OutOfMemoryError: Java heap space
NAS, Java or BubbleUPnP Server problem?