[APP][7.0+][v4.3.6] BubbleUPnP - UPnP/DLNA/Chromecast Control Point and Renderer

[bubbleguuum]

Bubbleguuum is having a time-machine. In the changelog you wrote Dec-26th

Thanks for the update!!

Well spotted. Fixed.

 

[moviecut]

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.

Thanks, my BubbleUpnp-Server ist finally running again on my Synology NAS! Wooohoooooouuu! I installed it directly via File, auto-update was not working... http://bubblesoftapps.com/bubbleupnpserver/BubbleUPnPServer.spk

 

[hifidon]

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

I rebooted the device and the error message went away.

 

[bubbleguuum]

I rebooted the device and the error message went away.

Anyway Audio Cast resampling on 64-bit will be supported in the next update. Got it working.

 

[Miracle1980]

I love the application but now I am using Daphile as music player. Would be possible to make Bubbleupnp recognize Lms libraries? Basically remote controller for Squeezebox...

 

[mkdr]

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.

 

[bubbleguuum]

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.

 

[mkdr]

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

 

[bubbleguuum]

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.

 

[mkdr]

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.

https://dl.dropboxusercontent.com/u/14937594/bubbleupnp_i9300.mp4

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.

 

[bubbleguuum]

https://dl.dropboxusercontent.com/u/14937594/bubbleupnp_i9300.mp4

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".

 

[mkdr]

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.

 

[bubbleguuum]

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.

At some point, the app had an empty placeholder screen I think displayed immediately but I disabled it because it did not match necessarily the theme of the app, so was weird. Also, of course it will be slower on older devices possibly having slower internal storage too (especially the N7 2012).
And to conclude, it might be faster to load on KitKat tan Lollipop+ because ART generates huges files that have to be read by the system somehow.
I'll see what I can do to optimize load times, maybe lazy initializing some stuff, but do not expect miracles. And there's some time taken by the framework that cannot be easily reduced like classloading.

 

[hifidon]

Audio cast toggle button widget

Is this a place for feature requests? It would be great if there was a widget for toggling audio cast on and off, and starts the app if necessaray. Just a button with indication of on/off state. Unless there's already a way to do this somehow?

 

[sordna]

... taken on my Alcatel OneTouch Idol 3, Android 5.1.1.

Do you have the 5.5" version? What ROM is this? I thought Alcatel only has 5.0.2 available.

 

[bubbleguuum]

Do you have the 5.5" version? What ROM is this? I thought Alcatel only has 5.0.2 available.

it's the 5.5, model 6045X. I'm running the Resurrection Remix ROM on it (see the XDA idol forum).
It works great. CM is also available I think.

 

[CassandraN]

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

fiquett.com/2013/07/chromecast-traffic-sniffing/

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.

Anyway, thanks again.

 

[bubbleguuum]

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

fiquett.com/2013/07/chromecast-traffic-sniffing/

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.

1. Not via OpenHome as there is no pure desktop Java SDK available for communicating directly with Chromecast.
It could be done on the Chomecast receiver itself but I have no current plan for that as it would be a full rewrite.

2. Yes a reboot Chromecast option should be easy to add (EDIT: added in next update)

 

[CassandraN]

Cool. Thanks for that. Appreciated.

Any idea on what might be causing the SD card issue and if it's fixable?

 

[bubbleguuum]

Cool. Thanks for that. Appreciated.

Any idea on what might be causing the SD card issue and if it's fixable?

Not sure I understand what you mean by "loose the sd card".
Can you describe a scenario that leads to this problem.
Also I assume you play your sd card files browsing the "External SD Card" folder of the local media server, in the
Library tab ?