Resume Playback Issue in Serviio 2.4 and E series TV

Hello,

I would like to report a bug in Serviio that I have in the latest version 2.4. This issue is critical as it affects the functionality of video playback via DLNA. Similar behavior was noticed in version 2.3, but I didn't bother to look into it and immediately rolled back to an earlier version for another reason.

Issue Description:
In versions 2.4 and (possible) 2.3, Serviio does not remember the playback position of a DLNA video if it is stopped after 16:40 minutes. This issue is not related to the format or type of file, nor its overall length. I have tested multiple files, including those I had successfully resumed from in earlier versions.
Completely uninstalling Serviio from the system with settings and media library and then doing a clean install and setup does not help. On version 2.4, any video file still does not remember the last position if closed at 16:40 or later.

Steps to Reproduce:
1. Play a video via DLNA.
2. Stop playback at a time later than 16:40 minutes.
3. Running the video again - it starts from the beginning (0:00) instead of resuming from the stopped position.

Additional Observations:
- If I stop playback at 16:38 or earlier, the video resumes correctly from the stopped position (usually a few seconds before the exact stop point).
- This issue does not occur in versions earlier than 2.3, where playback always resumes correctly.
- I am using a Samsung Smart TV E series (2012) connected via a wired local network. The issue is not related to the connection or file integrity.
- I don't use transcoding. I only watch file types and codecs supported by the TV.

Log Analysis:
I have enabled extended logging as per the forum guidelines and observed the following:

First Run:

2024-06-08T15:21:27,812 DEBUG [VideoDeliveryEngine] Delivering file '02_Test 2.mkv' in native format
2024-06-08T15:21:27,813 INFO [PlaybackEventsManager] Playback of media item 52795 (02_Test 2 [02_Test 2.mkv]) has started at 0% on Identifier=192.168.0.101, Profile=Samsung TV / player (E/F-series), Name=UE46EH5300
2024-06-08T15:21:46,277 INFO [PlaybackEventsManager] Playback of media item 52795 (02_Test 2 [02_Test 2.mkv]) has stopped at 0% on Identifier=192.168.0.101, Profile=Samsung TV / player (E/F-series), Name=UE46EH5300

Playback was stopped after 16:40. Upon restarting, it begins from 00:00:

2024-06-08T15:21:59,138 DEBUG [VideoDeliveryEngine] Delivering file '02_Test 2.mkv' in native format
2024-06-08T15:21:59,139 INFO [PlaybackEventsManager] Playback of media item 52795 (02_Test 2 [02_Test 2.mkv]) has started at 0% on Identifier=192.168.0.101, Profile=Samsung TV / player (E/F-series), Name=UE46EH5300
2024-06-08T15:21:59,157 DEBUG [VideoDeliveryEngine] Delivering file '02_Test 2.mkv' in native format
2024-06-08T15:22:16,906 INFO [PlaybackEventsManager] Playback of media item 52795 (02_Test 2 [02_Test 2.mkv]) has stopped at 15% on Identifier=192.168.0.101, Profile=Samsung TV / player (E/F-series), Name=UE46EH5300

"...has stopped at 15%" - Stopping before 16:40.
Playback resumes correctly despite the log indicating 0% (in fact, playback starts at about 15 minutes, i.e. 15% of the duration):

2024-06-08T15:22:28,053 DEBUG [VideoDeliveryEngine] Delivering file '02_Test 2.mkv' in native format
2024-06-08T15:22:28,053 INFO [PlaybackEventsManager] Playback of media item 52795 (02_Test 2 [02_Test 2.mkv]) has started at 0% on Identifier=192.168.0.101, Profile=Samsung TV / player (E/F-series), Name=UE46EH5300
2024-06-08T15:22:28,075 DEBUG [VideoDeliveryEngine] Delivering file '02_Test 2.mkv' in native format

The issue seems to be specific to the interaction between Serviio and certain Samsung Smart TV models. I can provide the complete log file if needed, although there are no error entries associated with the file access times.

In summary, the critical time for the playback resumption issue appears to be either 16:40 (or ~16:30 if you count the actual resumption starting slightly earlier than the stop point). Maybe this specific timing pattern may provide valuable insights for you in identifying and fixing the underlying cause of the problem.

Thank you for your attention to this matter. I look forward to your resolution.

I have the same problem but my samsung i thing is other model, i thing d. Sorry my inglish.

The problem started with version 2.3 (there was no resume then). I'm still using 2.2.1 because of this. Your 16:40 minutes are interesting, that's 1.000 seconds.
Sounds now like an easy error to find for fixing it in the next release.

Frank4711, Yes, that's probably the case. I'm currently using version 2.1, as 2.2.* has more bugs and crashes. It probably wouldn't be difficult to fix. However, as far as I understand, the error only occurs on older Samsung models. I hope the developers will be able to address this in future updates. Although, I've seen in related threads that there's often limited time and willingness to address these kinds of localized issues with older Samsung devices.

[atc98092]

The problem with any DLNA capable player is the support provided by the manufacturer. My experience with Samsung has never been that great, not so much player functionality but just a lousy user interface. I dabbled with using the TV's built in players a bit, but I moved to external players more than a decade ago. Using a player from Roku, Fire TV, Nvidia Shield (my favorite) or simply one of the many inexpensive Android based players are a vast improvement over the TV's player.

My main player is the Shield, but I also have several Rokus as well as a Fire TV and Onn 4K Media Player (Onn is a Walmart house brand, like Insignia is a Best Buy brand). With all but the Rokus I use Kodi as the media player, but there are many options available for those Android based players. Roku is limited to the Roku Media Player, but using the correct Roku profile in Serviio should provide an acceptable experience (disclaimer: I wrote all of the Roku profiles included with Serviio).