Posted 24 November 2019 - 08:12 PM
Recently I have moved my Emby server from local install on DietPi (Emby version was 188.8.131.52) to Docker (Emby version is 184.108.40.206 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.
Posted 24 November 2019 - 08:55 PM
I have just installed Emby version 220.127.116.11 in Docker.
And required functionality is WORKING!
So the difference is in versions.
Working: Emby 18.104.22.168. DLNA plugin 22.214.171.124
NOT working: Emby 126.96.36.199. DLNA plugin 188.8.131.52
This looks like a bug somewhere.
- Q-Droid likes this
Posted 25 November 2019 - 05:50 AM
Hi, what are you trying to pause from, the web app?
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.
Posted 27 November 2019 - 02:42 PM
Can you please attach the emby server log? Thanks.
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...rectory/control. UserAgent: DLNADOC/1.50 SEC_HHP_[TV] Samsung 48/1.0 UPnP/1.0
Edited by oleshkev, 27 November 2019 - 02:44 PM.
Posted 27 November 2019 - 05:47 PM
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...rectory/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.
Posted 29 November 2019 - 07:16 PM
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 184.108.40.206. It works.
Find attached log.
Posted 29 November 2019 - 07:35 PM
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:
220.127.116.11 (which does not allow to control video) and 18.104.22.168 (which allows to control video)
Edited by oleshkev, 29 November 2019 - 07:36 PM.
Posted 30 January 2020 - 01:53 PM Best Answer
The problem is resolved for me with one of the next versions.
Current version I use, that has the problem fixed:
Emby (22.214.171.124) and DLNA plugin (126.96.36.199).
So the topic may be marked as solved/closed.
Edited by oleshkev, 30 January 2020 - 06:03 PM.
- Luke likes this
Also tagged with one or more of these keywords: DLNA, Remote, Pause
Language-specific support →
Emby Server →
Emby Server →
Emby Server →
Emby Apps →
Web App →
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users