11-04-2019, 07:04 AM
Hi Kent,
thank you for looking into this. It is indeed a pretty cool feature, aus I think it entails using cast to send to bubble, and then using bubble recoding to dlna to send to moode.
The thing is: the error I posted is happening on moode. So that means that I actually am sending to moode, and moode is receiving something, but then "stalls" on localhost (127.0.0.1) on a port with a connection refused error. The error is generated as a curl error, and the only place to find it, is the mpd logs.
The error is a connection refused error on a port, which looks as a proxy port error. Even worse: when I use one of the solutions proposed for curl with a proxy error, I actually do get the album/song image displayed! (Solution used is: "unset http_proxy" / "unset https_proxy"), but the song never plays.
So this error seems to be more mpd related than anything else, unfortunately the logs are scant on this. Any way to get them more clear?
thanks,
Hendrik-Jan
thank you for looking into this. It is indeed a pretty cool feature, aus I think it entails using cast to send to bubble, and then using bubble recoding to dlna to send to moode.
The thing is: the error I posted is happening on moode. So that means that I actually am sending to moode, and moode is receiving something, but then "stalls" on localhost (127.0.0.1) on a port with a connection refused error. The error is generated as a curl error, and the only place to find it, is the mpd logs.
The error is a connection refused error on a port, which looks as a proxy port error. Even worse: when I use one of the solutions proposed for curl with a proxy error, I actually do get the album/song image displayed! (Solution used is: "unset http_proxy" / "unset https_proxy"), but the song never plays.
So this error seems to be more mpd related than anything else, unfortunately the logs are scant on this. Any way to get them more clear?
thanks,
Hendrik-Jan
