Transcoder issues since 1.16.4

I only have a Roku 3. ( I would be shot if I purchased another device :rofl:)

You may be having difficulty reproducing this issue, but there are a number of threads in the forum describing what appears to be the same issue. In all cases, video playback randomly skips forward seconds to minutes.

A common theme seems to be that the issue began with the server upgrade to 1.16.4.1469. Another common theme seems to be that it occurs during DirectPlay. One user mentions that when he forced his server to transcode, the problem went away.

I’ve seen the problem on my Mint 19.1 (Ubuntu 18.04) based server playing on my Samsung TV. I set the player to feed logs back to the server, turned server debug logs on, and downloaded the logs a few seconds after a skip occurred. They’re attached.

One additional note is that, when the skip occurred, the player briefly (< 1 sec) displays the buffering icon.

I uninstalled the server version that was causing the problem, re-installed 1.16.3.1402, and the problem disappeared.

Hope you guys can figure this one out.

Plex Media Server Logs_2019-08-15_23-35-32.zip (2.1 MB)

first,
I have VM’s of Redhat, Centos 7 , Fedora, Debian 8,9,10, Ubuntu 16, 18, and a few others for testing.

As I stated, i have only one Roku (the 3). I cannot recreate this with any of the playback modes. (DirectPlay, DirectStream, or Transcode).

Given I have a supply of video, If you can help me identify media parameters which expose it, I will work with that.

I would need: Video Bitrate and Encoding, Container (extension), Audio codec and channels.

…Same Problem !
Samsung Tizen 2.4.0 and Plex for Samsung 3.109.2
1.16.4 or Beta 1.16.5 doesn’t solve the problem … back to 1.16.3 … all o.k. !!!

“I would need: Video Bitrate and Encoding, Container (extension), Audio codec and channels.”

Do the debug logs not contain this information? I admit I’ve never looked at them, but that would seem like exactly the sort of information a debug log should contain (along with information about exactly what the server and client are doing at the moment a log entry is written).

File 1:
Bitrate 900kbps
Video Codec H264
Container MKV
Audio Codec AAC
Channels 2

File 2:
Bitrate 949 kbps
Video Codec H264
Container MKV
Audio Codec AAC
Channels 2

I’ve seen the problem only during Direct Play. Let me know if you need more information.

How the hell this bug made it to public version PMS update?.. Why wasn’t it fixed before releasing?..

Because it’s not human or logistically possible to regression test against every conceivable use case. That’s basic math and economics.

I can’t reproduce it yet but am still working on it.

1 Like

@dshanks01

Would you please be able to get me the mediainfo output of the file?

I would like to look at the next layer down of the encoding parameters. Tracking a hunch.

@ChuckPa

Here you go.

I can send the files themselves if it would help, though I’d rather not post them in an open forum.

mediainfo.zip (3.1 KB)

I’ll be able to post some mediainfo output for files once I upgrade the server back to 1.16.5 and get it to happen on some assets. Probably would be later tonight since I can’t remember which ones caused it in the past, though it was pretty much anything I played.

Saw the post in the other thread (Plex randomly jumping forward during playback)…Good news! I guess I don’t need to provide any more info on this. Looking forward to the fix.

Same issue here.
Please, have anyone the 1.16.3.1402 qpkg (QNap NAS) file for me?

Same issue for me as well
Server Version#: 1.16.5.1488
Player Version#: 1.1.0.831-e1ae73b1

Updating all here.

I have been informed, there is a known, confirmed, verified problem with DirectPlay and some of the players.

Engineering is working on the correction now.

The temporary workaround is to force DirectStream (change audio format is the easiest).

Many are currently testing the 1.16.5.1554 load referenced here:

My personal tests seem to indicate is is working for my clients.

PlexMediaServer-1.16.5.1488-deeb86e7f-x86_64.spk did’t fix the issue. I have reverted back to the 1.16.3 and all working as expected.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.