I've been enjoying mostly trouble free emby usage for a year or two now. I've been using the "Play To"-feature a lot because of it's convenience, but since I received a Philips 32PFS5803/12 as a gift the other day I've been struggling with it.
Hoping I can get some help here in figuring out what's wrong.
- "Play To" works fine on other devices in my home.
- I'm able to play media on the Philips TV using BubbleUPNP and MiniDLNA server, but not BubbleUPNP and emby DLNA server.
- I'm able to browse the MiniDLNA-server (used same hardware for this as the one emby is running on) and play media from it using the Philips TV UI.
- I'm not able to browse the emby DLNA-server and play media from it using the Philips TV UI (the TV froze at one attempt, and I had to yank the cable).
- I've made a "first attempt" DLNA Profile for the Philips TV, which I'm attaching, but it also does not work with the default profile.
I've attached some logs that might help. I did the following:
1) Start tcpdump of all traffic to/from 192.168.1.44 (Philips TV)
2) Restart the emby server (HAL9000 / 192.168.1.100)
3) Boot the TV up.
4) Select "Play To" Philips 32PFS5803/12 on my Laptop (192.168.1.21)
5) Hit "Play" at about "10:38:00"
6) Observe a "loading circle" on the TV for .5 secs before black screen and then nothing.
Sorry for the superfluous DLNA traffic from a emulated Windows guest machine (192.168.1.22) in the logs. It is running on the same hardware as emby, and got caught in the tcpdump I ran on the host machine since they share a common NIC. I didn't notice it until afterwards. Also it was silly of me to attempt to play a media file that had to be transcoded for this, but the same happens with files the TV can play directly.
The "dmr.xml" I've attached I pulled from the TV, I don't know if that's any help.
I can post a log of a working session with MiniDLNA to the same Philips TV if that is helpful at all.. I'm not familiar with these protocols.
Edited by jackti, 22 March 2019 - 07:21 AM.