Play/pause on remote do not work, when opening Emby on TV over DLNA

[oleshkev 2]

Hello everybody.

 

Recently I have moved my Emby server from local install on DietPi (Emby version was 4.2.0.40) to Docker (Emby version is 4.3.0.26 now).

 

After this change, I cannot pause video, fast forward, rewind or continue watching.

Before the switch to docker the functionality was present.

 

I am using Samsung TV to open Emby over DLNA.

 

Does anybody have an idea why this is happened and how to fix it?

 

I have tried to run Emby in Docker with host network and with bridged network options. Result is the same.

 

Thanks,

Aleks.

[oleshkev 2]

UPDATE:

 

I have just installed Emby version 4.2.0.40 in Docker.

And required functionality is WORKING!

 

So the difference is in versions.

Working: Emby 4.2.0.40. DLNA plugin 1.0.23.0

NOT working: Emby 4.3.0.26. DLNA plugin 1.0.31.0

 

This looks like a bug somewhere.

[Luke 38500]

Hi, what are you trying to pause from, the web app?

[oleshkev 2]

Hi, what are you trying to pause from, the web app?

 

No.

 

I select Emby from Source selection screen (see attached). As I understand, some DLNA browser starts.

When I select video, built in player starts (see attached).

And then I control video with buttons on remote (see attached).

 

But in the original problem, built-in player does not show me the controls of pausing/playing etc. As a result it does not allow continue watching, but it always start video from beginning.

 

[Luke 38500]

Can you please attach the emby server log? Thanks.

[oleshkev 2]

Can you please attach the emby server log? Thanks.

Luke hello,

Please find attached (two files. one - older version but working. another - newer version, but not working).

 

I have removed several lines with keys (not sure how sensitive they are).

You are interested in communication between 192.168.17.22 (emby server) and 192.168.17.107 (TV).

 

I see the difference. In working version there is the section (marked bold) is present:

2019-11-25 00:49:13.783 Info HttpServer: HTTP POST http://192.168.17.22:8096/dlna/23084971f76e4b6ea967561ef9cad6d7/contentdirectory/control. UserAgent: DLNADOC/1.50 SEC_HHP_[TV] Samsung 48/1.0 UPnP/1.0

 

embyserver-63710236800_not_working.txt

embyserver-63710240286_working.txt

Edited November 27, 2019 by oleshkev

[Luke 38500]

And how does the other one compare?

[oleshkev 2]

And how does the other one compare?

Working is like this:

2019-11-25 00:49:37.110 Info HttpServer: HTTP POST http://192.168.17.22:8096/dlna/23084971f76e4b6ea967561ef9cad6d7/contentdirectory/control. UserAgent: DLNADOC/1.50 SEC_HHP_[TV] Samsung 48/1.0 UPnP/1.0

 

And it looks like Not working one does not have lines with "control" at all.

[Luke 38500]

Right but those are incoming requests from tv to server, not server to tv.

[Luke 38500]

What about emby server 4.2.1?

[oleshkev 2]

Right but those are incoming requests from tv to server, not server to tv.

I understand it. But it looks like emby represent itself differently. And as a result TV do not even try to do it. Or emby detects TV incorrectly and does not offer that type of control to it.

But this is just my guessing.

 

 

 

What about emby server 4.2.1?

 

I tried 4.2.1.0. It works.

Find attached log.

embyserver-4.2.1.0_working.txt

[Luke 38500]

Is the media playing the same way in both cases? e.g. direct playing/transcoding.

[oleshkev 2]

Is the media playing the same way in both cases? e.g. direct playing/transcoding.

I expected it is direct playing.

What is the proper way to determine it? I was just checking cpu utilization.

 

Do you want me to compare all 3 versions?

[oleshkev 2]

I expected it is direct playing.

What is the proper way to determine it? I was just checking cpu utilization.

 

Do you want me to compare all 3 versions?

Based on CPU utilization, it is direct playing in both versions:

4.3.0.26 (which does not allow to control video) and 4.2.0.40 (which allows to control video)

Edited November 29, 2019 by oleshkev

[Luke 38500]

Thanks for the info.

[oleshkev 2]

Just FYI.

 

The problem is resolved for me with one of the next versions.

Current version I use, that has the problem fixed:

Emby (4.3.1.0) and DLNA plugin (1.0.33.0).

 

So the topic may be marked as solved/closed.

Edited January 30, 2020 by oleshkev

[Luke 38500]

Thanks for the feedback !