Skip to main content
Topic: UPnP MediaRenderer output | discussion (Read 143833 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: UPnP MediaRenderer output | discussion

Reply #425
Dear Peter and HA folks ,
I used foorbar2000 upnp output plugin to cast to my hardware Yamaha streamer and software neutron player inside my hi-fi android DAP & audiophile smartphone LG G7 ThinQ. When I cast from my laptop in flac format to Yamaha it works good, but when to software renderer neutron player it plays first 20-30 secs only, then it gets stack then. Playing with settings I found WAV format works but FLAC don't work normally. I tried to investigate the issue and found content-length http header is absent in the response of the stream url when format is FLAC but present when format is WAV. Is this a bug?
My config
Code: [Select]
manufacturer=Neutron Code Limited
model=Neutron Music Player
forced-format=WAV
supports-pause=true

manufacturer=Yamaha Corporation
model=NP-S303
forced-format=WAV
supports-pause=true


Re: UPnP MediaRenderer output | discussion

Reply #426
Hi,

I have met the same problem for Neutron audio player. Checking the blog I found below info. The component has been optimized for a number of real world devices.
Peter: Reply #287
Case:  Reply #378

Re: UPnP MediaRenderer output | discussion

Reply #427
Hi,

I have met the same problem for Neutron audio player. Checking the blog I found below info. The component has been optimized for a number of real world devices.
Peter: Reply #287
Case:  Reply #378

sacduser, thank you! However  I haven't got your message. I understand that some tweaks were applied, but is this a valid reason to deny option having content length header with FLAC format as we have for WAV?

Re: UPnP MediaRenderer output | discussion

Reply #428
Hi
The current specification has been discussed in the blog and seems to suit a number of users. You can use foo_upnp if you want a more standard upnp component.

Re: UPnP MediaRenderer output | discussion

Reply #429
Hello,
I have a "reactivity" problem : I am using a Raspberry with the MoOde distribution. The MoOde UPnP renderer is immediately found by BubbleUPnP on my portable phone (which shows it is working correctly), but in using Foobar I must wait several minutes to let UPnP Mediarenderer Output find the renderer.
Once found it stays active without problem, but if I quit Foobar and start it again I have to wait several minutes until the MoOde renderer is found again.

The device properties are :
Friendly name : Moode UPNP
IP address : 192.168.1.12
Presentation URL : http://192.168.1.12:49152/upmpd/presentation.html
Manufacturer : JF Light Industries
Manufacturer URL : https://opensourceprojects.eu/u/medoc/profile/
Model : UpMPD
Model number : 1.0
Model description : UPnP front-end to MPD
Model URL : https://opensourceprojects.eu/p/upmpdcli/code/
Serial number : 42

Any way to improve ?
Thanks,
John


I use Moode also but haven't experienced these issues.  For its UPnP renderering capabilities it uses a version of upmpdcli and libupnpp which are now a bit dated.  I can't promise that updating these components will resolve things for you, but its probably worth trying. This is a relatively straighforward process that's set out here: https://www.lesbonscomptes.com/upmpdcli/downloads.html  (If you're using a recent version of Moode the 'upmpdcli.list' file will need to be edited for 'Buster - Raspbian AND other armhf Debian' systems).  Good luck

 
SimplePortal 1.0.0 RC1 © 2008-2020