Wed May 16, 2018 1:05 am by atc98092
That is dependent on two things. The DLNA server itself must support it, and the TVs themselves must support it. The videos must not be transcoded, or there's no way for Serviio to know when playback stops. And some players just ignore the database field that shows where playback was stopped. I have Samsung TVs, but have never noticed if that was available. It's also possible that one of your TVs supports it and the other doesn't, so it might work from TV A to TV B, but not in reverse.
It sounds like it was working before an update. I don't believe Serviio made any changes to that, but Zip might not give up details of changes to the database. But it's certainly possible that Samsung pushed out an update that changed its behavior. It wouldn't be the first time that something used to work with my Samsung and an update broke it. In fact, I've given up on using the Samsung DLNA player and use either Roku players or my Sony Blu Ray player. In fact, I almost never use the Samsung Smart TV features any longer. For Amazon, Netflix, Vudu or YouTube (my main sources outside of my Serviio server) my Roku Ultra is much better and easier to use than the TV's apps, and the Roku supports 4K HDR well. The Sony is only 1080, and doesn't have a very fancy interface for DLNA playback. But it always works, and that's the most important thing, since my wife uses it the most!
Dan
LG NANO85 4K TV, Samsung JU7100 4K TV, Sony BDP-S3500, Sharp 4K Roku TV, Insignia Roku TV, Roku Ultra, Premiere and Stick, Nvidia Shield, Yamaha RX-V583 AVR.
Primary server: Intel i5-6400, 16 gig ram, Windows 10 Pro, 22 TB hard drive space | Test server Windows 10 Pro, AMD Phenom II X4 965, 8 gig ram
HOWTO: Enable debug logging HOWTO: Identify media file contents