Movies marked as watched on start/stop

[saarg 2]

I have just installed Emby and scanned my library and saw that the watched status is set to watched even if you just watch the movie for a few seconds. When starting the movie again , it starts from the beginning.

This happens on both the web app, android app and in Kodi.

I have installed the trakt, and the kodi sync queue plugins and also uninstalled them, but the same result.

I'm using the docker version on unraid. The emby server version is 3.2.60.0.

The media folders are mounted read only to the docker.

Is this the correct behavior of the watched/unwatched status? 

 

Edit:

I tested binhex's emby docker and it's working there.

There is also a difference in the web app. In the official Emby version there are no file info (Codecs) and playback doesn't have the movie lenght, just changes constantly as it is transcoded. 

With binhex's version the movie lenght is correct and file info is available. So is resume playback.

Edited January 8, 2018 by saarg

[Luke 42078]

Hi, what docker are you using?

[saarg 2]

I'm using emby/embyserver (https://hub.docker.com/r/emby/embyserver/). Latest tag.

I have found the problem though. In the above mentioned container, the pre-set path to ffmpeg in the transcoding settings are /config/ffmpeg/20170308/. First thing is that they are not set as executable and second that they have the issues I mentioned in the first post.

Setting the ffmpeg path to /usr/bin solves the issue, but I have to do a refresh metadata for the file info to appear. The resume function does not work though.

Binhex's version use ffmpeg 3.4, and the one in your container in /usr/bin is 3.3.4.

Edited January 8, 2018 by saarg

[Luke 42078]

Ok, our website instructions advise a new docker container and this wont' happen anymore:

 

https://emby.media/docker-server.html

 

In the current docker container you've installed, you are certainly free to continue using that, but you have to self manage the ffmpeg build.

[saarg 2]

That explains a lot. 

I just installed the one available from the "App Store" in unraid, which is the old one. I will get it marked as deprecated in the "App Store" then, if you are not maintaining it anymore?

[Luke 42078]

No, you don't need to do that because that one has a lot of users, we're going to migrate this new one into the old one as soon as we're comfortable with the upgrade process. thanks.

[saarg 2]

It took some time before I spotted the _netcore for the new version. Thanks for pointing me in the right directions.

You might want to update the wiki as it still have the old container in the installation section.

[Luke 42078]

Thanks for the feedback. 

[soylentcreek 4]

I'm on version 3.2.60.0 which I installed on my linux server this evening, and I'm experiencing this issue as well.  Is there something I need to manually enable or patch in order for this to work properly?

[soylentcreek 4]

Version 3.2.60.13 beta seems to have fixed the issue with resuming in Kodi. 

[Luke 42078]

Hi, best thing to do is discuss an example and attach the information requested in how to report a media playback issue. thanks !