Playback issue after exiting video – requires full app restart (UMS 14.12.1 on Windows 7)

[kennytime]

Hey everyone,

I’m currently using Universal Media Server (v14.12.1) on a Windows 7 SP1 (64-bit) machine with 8 GB RAM. My main use case is streaming video content from this PC to my Samsung S90C via DLNA/UPnP – mostly through the TV’s native media player, rarely on my phone via the BubbleUPnP app + MX Player Pro on Android.

Everything starts out fine: playback works perfectly, whether transcoding is activated or not. However, the problem begins after I exit the video – for example, if I go back to the video list and then try to play the same or file again. (Different files still work well.)

Instead of resuming playback, the video just loads endlessly, and eventually my TV shows a generic network error like “no network” (which clearly isn’t true – everything else works fine) and starts some troubleshoot bs. The only workaround I’ve found is to fully restart the UMS application. A normal server restart within the UI doesn’t help – I need to actually close the program and relaunch it, which takes quite a while on my older PC.

This issue happens consistently, whether I use the Samsung TV player or BubbleUPnP on Android, and it only started happening after I updated UMS. Unfortunately, I don’t remember the exact version I had before, but I was like 12.x or something. Also worth noting: I didn’t update over the old version – I performed a completely fresh install and reconfigured everything from scratch.

This behavior is super frustrating, especially since it used to work perfectly before. Exiting a video shouldn’t break the videos playback functionality until a full relaunch.

Any help or suggestions would be highly appreciated! By the way, I'm not a total noob, but I'm also not an expert with UMS, especially when it comes to fine-tuning and stuff. It would be helpful if you could provide relatively simple instructions.

Thanks a lot in advance


EDIT: How strange; I tried to create a debug log file and replicate the error as mentioned in the thread above, but now it suddenly works perfectly fine. It was still an issue yesterday. I'll try again later, and if the bug occurs again, I'll submit the log file.

[mik_s]

This is probably caused by the resume feature in UMS being turned on.

This feature is for renderers that can't resume so UMS will remember and make a virtual video by starting to transcode from the last played position.

Most devices these days remember the last position so best to turn off resume and let them handle it themselves.

Another thing you can do is add "DisableUmsResume = true" to its conf file and this will disable it only for this renderer.

There may also be a problem with this unless its behaviour has changed and this has been mentioned a lot recently.
The virtual file it makes should be separate and have a different ID than the original file and you should have to select that one for it to play, but I think the same ID is given to both so even when playing the original it picks the resume file.
As the TV is expecting the video in one format it will be confused when being sent the transcoded video in another so causes an error.

If it happens again could you post your logs (see the red section above) and I'll see if I can confirm this theory.