[SOLVED] mpd streaming error on 7.2.1

[officialsm]

Hi,
I'am exeperiencing various kind of errors. Using BubbleUPNP, music streaming stops after 2 or 3 songs. Restarting it i can have errors or sometimes it starts streaming music but with no audio. In this scenario if i power off the power on amplifier it plays correctly. But not ever: somethimes i have same errors as previous point. With radio configured on Moode same issue.
The only thing i have changed is that i have reinstalled oled scripts.
On logs verbose i dont have errors.

Could you help me to investigate?

Error radio 1:
https://drive.google.com/file/d/1xicTg5A...sp=sharing

Error radio 2:
https://drive.google.com/file/d/1UJjUPuA...sp=sharing

Error BubbleUPNP:
https://drive.google.com/file/d/1qdhtzJA...sp=sharing

[TheOldPresbyope]

@officialsm

I can't comment on the OLED scripts.

As for 4ZZZ FM in Brisbane AU, I seem to recall this community station has used a succession of streaming servers. Just now I see that "https://iheart.4zzz.org.au/4zzz" is a working URL.

Regarding BubbleUPnP usage, you haven't given any technical details. Notably, you didn't tell us the UPnP service type selected for the UPnP renderer. See the recent thread Tracks won't advance w/bubbleUPnP.

For the record, just now I'm listening to tracks served from minimserver running on a Linux host with BubbleUPnP as control point and moOde UPnP renderer set to UPnP-A/V. Tracks are advancing just fine.

Regards,
Kent

[the_bertrum]

As @TheOldPresbyope says your details are a little light, but I'll throw this in. I've noticed that the UPnP playback can get a little picky when CamillaDSP is on. I've not done much more research into the phenomenon since the chap who had the problem I was looking into has stopped taking part in the thread, but if you have Camilla on, try turning it off as an experiment.

[officialsm]

Hi,
thank you for helping me.
I have Camilla DSP turned off. I have Alsa Loopback tuenrd ON. TRied to change form Openhome to UPnP-AV but i t stops after 4-5 songs. BubbuleUPNP appa have no battery limitations and no auto kill.

One strange thing is that i BubbleUPNP app i have published two different mpd service with same name. If i switch from them i can see different songs list. Is it normal?

In BubbleUPNP app logs i have this kind of errors:

[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-1
[cling-90 (GetPositionInfo) (3844) ] WARNING - 0:23:30.610 - .d : GetPositionInfo: Error: Current state of service prevents invoking that action. Connection error or no response received.
[TimeTask: SIMOODE (3879) ] WARNING - 0:23:30.611 - .e0 : TimeTask: SIMOODE: n.c.a.i.q.c: Current state of service prevents invoking that action. Connection error or no response received.
[cling-90 (GetPositionInfo) (3844) ] WARNING - 0:23:32.110 - .h : Client connection was aborted: java.net.ConnectException: failed to connect to /192.168.1.13 (port 49152) from /192.168.1.9 (port 38368) after 20000ms: isConnected failed: EHOSTUNREACH (No route to host): http://192.168.1.13:49152/uuid-effba386-...ransport-1
[cling-90 (GetPositionInfo) (3844) ] WARNING - 0:23:32.111 - .d : GetPositionInfo: Error: Current state of service prevents invoking that action. Connection error or no response received.
[TimeTask: SIMOODE (3879) ] WARNING - 0:23:32.111 - .e0 : TimeTask: SIMOODE: n.c.a.i.q.c: Current state of service prevents invoking that action. Connection error or no response received.
[main (2) ] INFO - 0:23:32.183 - onPause()@7462977:5932
[main (2) ] INFO - 0:23:32.183 - removed listener: 3 listeners
[main (2) ] INFO - 0:23:32.183 - .e0 : stopping task ViewBlinkTask
[main (2) ] INFO - 0:23:32.185 - removed listener: 2 listeners
[main (2) ] INFO - 0:23:32.185 - removed listener: 1 listeners
[main (2) ] INFO - 0:23:32.185 - removeListener (context: com.bubblesoft.android.bubbleupnp.MainTabActivity@7462977)
[main (2) ] INFO - 0:23:32.185 - removed listener: 0 listeners
[main (2) ] INFO - 0:23:32.237 - onResume
[main (2) ] INFO - 0:23:32.806 - onStop()@7462977:5932
[main (2) ] INFO - 0:23:34.431 - onPause
[main (2) ] INFO - 0:23:34.477 - onResume
[cling-90 (GetPositionInfo) (3844) ] WARNING - 0:23:34.519 - .h : Client connection was aborted: java.net.ConnectException: failed to connect to /192.168.1.13 (port 49152) from /192.168.1.9 (port 38370) after 20000ms: isConnected failed: EHOSTUNREACH (No route to host): http://192.168.1.13:49152/uuid-effba386-...ransport-1
[cling-90 (GetPositionInfo) (3844) ] WARNING - 0:23:34.520 - .d : GetPositionInfo: Error: Current state of service prevents invoking that action. Connection error or no response received.
[TimeTask: SIMOODE (3879) ] WARNING - 0:23:34.520 - .e0 : TimeTask: SIMOODE: n.c.a.i.q.c: Current state of service prevents invoking that action. Connection error or no response received.
[TimeTask: SIMOODE (3879) ] INFO - 0:23:34.520 - .e0 : TimeTask: SIMOODE: max failure count reached (5), stopping task
[main (2) ] INFO - 0:24:05.432 - onPause
[main (2) ] INFO - 0:24:06.475 - ACTION_SCREEN_OFF

[the_bertrum]

If there are two renderer entries in your BubbleUPnP app, that suggests that you have an old cached connection. Reboot your phone, moOde and the UPnP server. You should only have the one moOde renderer then and things may work more reliably.

[officialsm]

If there are two renderer entries in your BubbleUPnP app, that suggests that you have an old cached connection.  Reboot your phone, moOde and the UPnP server.  You should only have the one moOde renderer then and things may work more reliably.

Already done without success. Reinstalling app is ok

[officialsm]

UPDATE: 
How i stream:

BUBBLEUPNP as streaming app connected throught wi-fi to Raspberry 4 with Moode 7.2.1. Qobuz as service.
Raspberry is connected throught USB cable to a CXA81 amplifier with integrated DAC

the behavior is this:

BUBBLEUPNP stream a playlist. after 2-3 songs it stops. On the app the current song is pause. If i press play button it continue to play but without sound. On Raspberry -i have an oled display with eq bars- seems to be all ok and the songs is playing. But no sound.
If i power off and then power on amplifier (BUBBULEUPNP pause the song, i think because the connection to dac goes down) it come back to have sound correctly (after press play).
No errors in moode log.

@TheOldPresbyope any idea to investigate and fix issue?

[the_bertrum]

If i power off and then power on amplifier (BUBBULEUPNP pause the song) it come back to have sound correctly (after press play).

This line confuses me. Which amplifier? How does turning off the amplifier send a signal to BubbleUPnP to pause?

Let's back up a bit to first principles: can you tell us what version of moOde, what your full equipment chain is (files server, UPnP Server, UPnP controller, Pi version, type of DAC, amplifiers and so on).

[officialsm]

If i power off and then power on amplifier (BUBBULEUPNP pause the song) it come back to have sound correctly (after press play).

This line confuses me.  Which amplifier?  How does turning off the amplifier send a signal to BubbleUPnP to pause?

Let's back up a bit to first principles:  can you tell us what version of moOde, what your full equipment chain is (files server, UPnP Server, UPnP controller, Pi version, type of DAC, amplifiers and so on).

Thank you. I updated my previous post

[TheOldPresbyope]

@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)

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 1GB

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

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-1

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.