05-25-2021, 03:04 PM
(This post was last modified: 05-25-2021, 03:06 PM by TheOldPresbyope.
Edit Reason: typo
)
@officialsm
The good news is---thanks to your recent post---I realized there must be a way to log BubbleUPnP events on my phone and trawled the InterWeb™ to find out how it's done and where to find the log file in the Android file system. Not exactly a well documented feature.
The bad news is my log file contains tons of informational messages but no error messages because my setup is running like clockwork as I described before.
Armed with your information I have configured the following on my test system: moOde 7.2.1 on an RPi4B/1GB with USB DAC (actually a USB-BT adapter to wireless headphones), moOde UPnP renderer enabled and set to UPnP-A/V service type, BubbleUPnP app on my Android Pixel 3A phone and using Qobuz for its library (e.g., media server), all devices communicating via a WiFi mesh network and whence to my ISP. Besides UPnP, I have the Spotify and Airplay renderers enabled in moOde.
Apart from the changes necessary to achieve the above, the moOde configuration is stock. In particular, I have no OLED display and do not have ALSA loopback enabled.
This system just finished playing contiguously all 7 tracks of the classic jazz album "Gil Evans & 10" from Qobuz without a hitch.
Typical for all the tracks, here's moOde's audio information for one (because of my BT output all audio is forced to 16 bit/48 kHz)
I notice the string "Qobuz" appears frequently in my log but I don't see it at all in yours.
Taking a typical error message from your log
I know port 49152 is the port upmpdcli listens to so 192.168.1.13 likely is the IP of your moOde player. I know what "http://192.168.1.13:49152/uuid-effba386-954d-9660-4cf6-dca6323c9a12/ctl-urn-schemas-upnp-org-service-AVTransport-1" represents. I don't know why BubbleUPnP is asking for it at this particular point (one might ask what were you doing?) and have no idea why the moOde host isn't responsive. I see no strings in my log which resemble the requests in yours.
Sorry, lacking a clear notion of what's happening in your system, I don't have the time to explore this issue further so I'm out.
Good hunting!
Regards,
Kent
PS - Not unexpectedly, I get the same null result if I point BubbleUPnP to my Linux-hosted minimserver or a DLNA server on one of my mOde players instead of to Qobuz.
The good news is---thanks to your recent post---I realized there must be a way to log BubbleUPnP events on my phone and trawled the InterWeb™ to find out how it's done and where to find the log file in the Android file system. Not exactly a well documented feature.
The bad news is my log file contains tons of informational messages but no error messages because my setup is running like clockwork as I described before.
Armed with your information I have configured the following on my test system: moOde 7.2.1 on an RPi4B/1GB with USB DAC (actually a USB-BT adapter to wireless headphones), moOde UPnP renderer enabled and set to UPnP-A/V service type, BubbleUPnP app on my Android Pixel 3A phone and using Qobuz for its library (e.g., media server), all devices communicating via a WiFi mesh network and whence to my ISP. Besides UPnP, I have the Spotify and Airplay renderers enabled in moOde.
Apart from the changes necessary to achieve the above, the moOde configuration is stock. In particular, I have no OLED display and do not have ALSA loopback enabled.
This system just finished playing contiguously all 7 tracks of the classic jazz album "Gil Evans & 10" from Qobuz without a hitch.
Typical for all the tracks, here's moOde's audio information for one (because of my BT output all audio is forced to 16 bit/48 kHz)
Code:
INPUT / OUTPUT
Source http://192.168.4.21:57645/proxy/qobuz/139B05F8F935E45276C43FDDADC2772D.flac
Encoded at Unknown
Decoded to 16 bit, 44.1 kHz, Stereo, 531 kbps
Destination Local
Output rate 16 bit, 48 kHz, Stereo, 1.536 Mbps
DSP OPERATIONS
Resample rate Off
Selective rate Off
Resample quality Off
CamillaDSP Off
Volume mixer Software (MPD)
AUDIO DEVICE
Device Creative Bluetooth Audio W2
Mixer name PCM
Interface USB
Formats S16_LE
Platform Pi-4B 1.1 1GBI notice the string "Qobuz" appears frequently in my log but I don't see it at all in yours.
Taking a typical error message from your log
Code:
[cling-90 (GetPositionInfo) (3844) ] WARNING - 0:23:30.610 - .h : Client connection was aborted: java.net.ConnectException: failed to connect to /192.168.1.13 (port 49152) from /192.168.1.9 (port 38366) after 20000ms: isConnected failed: EHOSTUNREACH (No route to host): http://192.168.1.13:49152/uuid-effba386-...ransport-1I know port 49152 is the port upmpdcli listens to so 192.168.1.13 likely is the IP of your moOde player. I know what "http://192.168.1.13:49152/uuid-effba386-954d-9660-4cf6-dca6323c9a12/ctl-urn-schemas-upnp-org-service-AVTransport-1" represents. I don't know why BubbleUPnP is asking for it at this particular point (one might ask what were you doing?) and have no idea why the moOde host isn't responsive. I see no strings in my log which resemble the requests in yours.
Sorry, lacking a clear notion of what's happening in your system, I don't have the time to explore this issue further so I'm out.
Good hunting!
Regards,
Kent
PS - Not unexpectedly, I get the same null result if I point BubbleUPnP to my Linux-hosted minimserver or a DLNA server on one of my mOde players instead of to Qobuz.
