[Android Apps and Games] LastSilmaril:
Noticed some odd behavior when using BubbleUPnP Tether Client. For all intents and purposes, servers being made available by the tether client appear as local servers in the BubbleUPnP app. So if you're using the foobar2000 UPnP server plugin (foo_upnp), the 'Restart server' option will show up under the overflow menu in the BubbleUPnP libraries list. If you're using MinimServer, the 'Rescan library' option will show up. While I was trying these options, I was also logged into the BubbleUPnP Server machine using remote desktop software, and tried to observe if anything happened. From what I saw, the 'restart server' option was in fact successfully (ish) sent to the fb2k plugin when I tried it. It didn't cause the server to restart unfortch - it threw an error about the port being used; don't know if this is a symptom of the newer foobar2000 instance I'm using or not (v1.14 beta 21), since I've never noticed this option before while on my local network and never tried it. MinimServer did not seem to respond or rescan, however. So I'm wondering if there's a way for BubbleUPnP to detect libraries provided by the tether client, such that it should treat them as if they were remote libraries, and hide these restart/rescan options. (I would suggest making these options work properly remotely, given that at least foo_upnp seemed to get *some* message, but you've already said earlier that this isn't really doable, so I won't ask again.)

That brings me to the second thing I noticed. If you have some libraries exposed on your network via the tether client, but also connect to the same BubbleUPnP Server separately using the 'Internet access with BubbleUPnP Server' settings in BubbleUPnP itself, each server *won't* show up twice in the libraries menu, and you'll *only* be able to connect using the connection set up by BubbleUPnP. The instances of those libraries provided by the tether client will not show up in the menu at all. This is inconsistent with regular behavior - in other words, if I were on my local network at home, in the location where my media servers and BubbleUPnP server is running, my media servers would be accessible both 'directly', or via BubbleUPnP Server running on my local network. I should like to be able to have access via both the tether and the app at the same time, or else to be able to select which connection should be shown at any given time via some advanced option.

Of course, I could avoid connecting to BubbleUPnP Server using the BubbleUPnP app's connection by changing it so that it only connects on Mobile, rather than on Wifi/Eth. But this is inelegant, since generally, on Wifi/Eth other than this one location, I will want it to connect to BubbleUPnP Server directly, automatically. (Actually, I was wondering, separately, if there was a way to make that option more granular, such that automatic connections to BubbleUPnP only happen on certain WiFi networks, say by SSID, or even better, by router MAC address. Or maybe the reverse - basically a location blacklist or whitelist based on MAC. Not sure how difficult this is or not and I'm sure you have other priorities, but that would be pretty amazing.)

---------- Post added at 06:01 PM ---------- Previous post was at 05:13 PM ----------

Another issue atm: BubbleUPnP is failing to play back a 24/176.4 FLAC properly - it plays back too fast and is full of skips, sorta like a different sample rate was expected by the player/it is attempting to play it back at the wrong sample rate. This happens whether connected via tether or via a connection the BubbleUPnP app makes directly. It also happens even when the file is downloaded to the phone, so it is not a network issue. The same file plays back fine in foobar2000 for Android and GoneMAD, as well as on a PC with various players. While other files from this album also have this issue, it is not universal to 24/176.4 files, as far as I can tell. But the only thing different about these files from the ones that play back fine is that the frontend to libFLAC was XLD. It uses a newer version of libFLAC, 1.3.1, than some other 24/176.4 files I have, but I also have some 1.3.1-encoded 24/176.4 files that play back just fine, so that doesn't appear to be it. I also tried removing the album artwork from the file, but this didn't resolve the issue. I don't know what is special about this file/album, and given that everything else is able to play it back fine, I'm not prepared to call the file itself corrupt or anything. I can upload a file from the album in question somewhere if you're willing to look into this.

For what it's worth, it also decodes properly when using the FFmpeg decoder, so there's a workaround for now that doesn't involve downloading and playing back in other apps, and I'm not sure how high a priority it should be. That said, I think this definitely qualifies as a bug, since it plays back fine using anything else.