TRACE 23:12:05.771 Request: HTTP/1.1 : SUBSCRIBE : upnp/event/content_directory TRACE 23:12:05.443 Sent to socket: Content-Type: text/xml charset="utf-8" TRACE 23:12:05.443 Sent to socket: Connection: keep-alive
TRACE 23:12:05.443 Sent to socket: Cache-Control: no-cache TRACE 23:12:05.443 Sent to socket: Accept-Ranges: bytes TRACE 23:12:05.443 Recognized media renderer: Yamaha RX-V773 TRACE 23:12:05.443 Received on socket: User-Agent: Mozilla/4.0 (compatible) TRACE 23:12:05.443 Received on socket: Connection: close
UNIVERSAL MEDIA SERVER UNKNOWN RENDERER FREE
(And by the way, feel free to add the attachment to the UMS distribution because it works just fine.) If the answer to question 1 is 'No', is it possible to add funtionality in a future release to let the user choose at installation time which renderer configs he wishes to install? Is there a way to distinguish further for the correct renderer apart from the options (UserAgentSearch, UserAgentAdditionalHeader, UserAgentAdditionalHeaderSearch) that we currently have?Ģ. So right now my workaround is to leave only the renderer config files in the renderers directory that I actually use (including my yamaha renderer config see attachment).ġ.
conf file, because the receiver seems to be detected using the same data as configured in the nf file.
UNIVERSAL MEDIA SERVER UNKNOWN RENDERER INSTALL
However at installation time I have to manualy install the. conf file for it and it streams perfectly. I own a Yamaha RX-V773 receiver, used for audio streaming. I am looking for an advice or solution to the renderer detection.
0 kommentar(er)
