Transcoder errors after updating

Just had the same user report that on their network using either Chrome or Safari the Plex web app via app.plex.tv doesn’t work as well as mobile devices - yet playing on their TV via the TV’s app does work. Everything works on my network - which doesn’t make any sense to me. I’m going to suggest they clear their browser cache but I don’t think that’ll do anything.

I grabbed these logs immediately hoping the events would still be in the logs.

Plex Media Server Logs_2021-06-22_19-55-32.zip (4.9 MB)

Plex/web is a javascript app running IN the browser and subject to

  1. Limitations of the particular browser
  2. Any & all plug-ins in that browser
  3. Anti-virus scanners which might get involved when streaming (depends on platform).

Again, you’re pushing this out of the server realm further and further into application specifics which I cannot address (I am not a Java developer).

Please remember, I am the OS/platform guy on the Server side , emphasis on Linux and NAS (Linux-based) platforms.

I’m mostly just trying to update you when I upload logs and voicing my own confusion with the situation, that’s all.

I uploaded the logs you requested last night this morning and just wanted to upload another set after a similar issue happened.

Did you get a chance to review the logs I uploaded this morning?

I have a question about your scanning activity.

How do you have it configured ? Do you have “partial” enabled ?

It seems that every file contains a substantial amount of scanner activity… This is a common theme throughout everything you’ve shown me.

The other thing I wanted to ask about.

  1. Ubuntu Linux.
  2. DSM eth5

Are you running a Ubuntu VM on a Synology box?

I have the first 3 options checked off for scanning, from what I’ve read in the forums (which still seems inconclusive) you need the first option checked Scan my library automatically in order for the second option Run a partial scan when changes are detected to work, then I have selected to have my music library scanned as well.

I’m running Ubuntu Server 16.04 LTS, I have a Synology NAS as well, but it has no relation to Plex other than for backups.

SSDP: Error parsing device schema for http://10.10.10.5:5000/ssdp/desc-DSM-eth5.xml

Which I think is what you’re referring to, would be a call out from my NAS. I suspect its beaconing trying to find clients for Urbackup which I have on there (SSDP).

I don’t believe there is any issue happening server-side, feel free to correct me if you think there is an issue somewhere. I thought you just wanted the build info (transcoder set to debug) to see if the web app or something potentially had a bug.

Please allow me to demystify.

  1. Automatic detection ONLY works when the media is on the Same Host as PMS.
    (Linux kernel notification service does not work over the network

  2. There is no dependency between options however some don’t benefit as much without others.

Given you have a NAS like I do, may I recommend:

Set the Library scan interval according to how often you add media (if using automatic mechanisms)

Ok, with this being said - I’ve got no media whatsoever on my NAS, it only communicates with my Plex host for backups.
All my media is stored on a second Ubuntu server which shares content via NFS over a 10Gbe ptp link, I haven’t had any issues with automatic detection.

I will be unchecking the scan library automatically because I don’t think the entire library needs to be scanned any time new content is added. If I recall correctly new media is picked up right away with just the partial scan no problem, the full scan I found only useful if I modified a file that was already scanned in. This may help to eliminate the logs being full of scans.

As for everything else; in terms of the transcoder errors, right now it seems to be isolated to a single user with web browsers and their mobile device - so I’ll chalk that up to being a client-side issue due to browser plug-ins or something of the like. I did send them links to the SOP for obtaining logs from the mobile apps, so hopefully if they encounter another issue, they’ll have some logs to send.

I’ll leave the transcoder on debugging for now, just in case.

This is how I have my library settings now.
(screenshot taken after I typed this out)

Thank you for demystifying these settings.

Whether the media is stored on a NAS or another server, ANYTHING over a network connection precludes automatic detection working.

NFS and SMB do not support "Notification.
Windows emulates it by polling many times a minute

I long for the day that I can close this one off… I know you’re the linux guy, I’m still trying to figure out if these issues are with my server or buggy client apps. I’m still not sure.

I was told by a user that they aren’t able to stream from their iPad and getting a transcoder error. I tried to reproduce this by using my tablet on my phones hotspot and tried to stream and I’m receiving the an error as well and seeing this in the console.

[Transcode] Denying access to transcode of key /library/metadata/143742 due to terminated session

This is the log from my tablet.
plex-log-kazz3r24.zip (242.8 KB)

This is from the server hopefully it’s cleaner this time.

Plex Media Server Logs_2021-06-25_16-44-55.zip (5.9 MB)

Playback was started and then terminated before it could finish the auth & start.

Jun 25, 2021 16:25:23.509 [0x7f01b3415b38] DEBUG - [Transcode] Auth: authenticated user 1 as kazz3r24
Jun 25, 2021 16:25:23.521 [0x7f01b3415b38] DEBUG - [Transcode] We're going to try to auto-select an audio stream for account 1.
Jun 25, 2021 16:25:23.521 [0x7f01b3415b38] DEBUG - [Transcode] Selecting best audio stream for part ID 128243 (autoselect: 1 language: en)
Jun 25, 2021 16:25:23.521 [0x7f01b3415b38] DEBUG - [Transcode] We're going to try to auto-select a subtitle.
Jun 25, 2021 16:25:23.521 [0x7f01b3415b38] DEBUG - [Transcode] Audio Stream: 356282, Subtitle Stream: -1
Jun 25, 2021 16:25:23.521 [0x7f01b3415b38] WARN - [Transcode] Denying access to transcode of key /library/metadata/81785 due to terminated session
Jun 25, 2021 16:25:23.522 [0x7f01cbdfdb38] DEBUG - Completed: [72.143.209.81:39993] 400 GET /video/:/transcode/universal/start.m3u8

400 Bad Request - HTTP | MDN

](400 Bad Request - HTTP | MDN)

What are you doing ? A proxy?

No proxy involved or anything fancy on my end. My server settings are as vanilla as they get.

My tablet was on my phones hotspot, I can’t speak to what the remote user has going on - but they did mention it was working previously (I know that doesn’t do much for you).

Yes, this again.

Riddle me this:
My aunt and cousin are on the same LAN in another province, they have the mobile app on Android and one on iOS. iOS has zero issues with playing media on their device or casting - except for one file (which every other device can play) I even have a copy as h.264 and h.265. Android is unable to watch anything or cast period and gets a transcoder error.

None of this, that I can see shows in the logs - at least not the errors. I almost feel like a system wipe is in order, I know that shouldn’t fix anything - but I’m at a loss. These errors never stopped coming in, I just brushed them off as being client issues because we’ve never come to a resolution here.

I’m working on getting client logs from my aunt, but that could take some time.

  • No custom ssl cert or domain
  • No proxy

I really don’t think the issue is the server, but at this point who knows.

These are the server logs.
Plex Media Server Logs_2021-07-10_18-33-29.zip (5.5 MB)

You can’t compare two different sites unless they have the exact same hardware (modem/router, ISP, and same playback devices)

If this comes down to ONE file then what’s going on in that file?

The XML of it, compared to another which plays without issue, is a good start.

What two different sites are we talking about? They’re both on the same LAN, the only thing that is different between the two of them is the mobile device they’re using.

I shouldn’t have mentioned the file, it plays fine on all other devices (for other users) so I’m doubting there’s an issue with the file itself.

But, for the sake of argument - let me know if this isn’t the right info you need from xml.

Version 1:

<Media id="190881" duration="8026784" bitrate="7971" width="1920" height="1080" aspectRatio="1.78" audioChannels="6" audioCodec="eac3" videoCodec="h264" videoResolution="1080" container="mkv" videoFrameRate="24p" videoProfile="high">
<Part accessible="1" exists="1" id="191022" key="/library/parts/191022/1625817395/file.mkv" duration="8026784" file="/mnt/Echo/Movies/Wouldntyouliketoknow/wouldntyouliketoknow-WEBDL-1080p.mkv" size="8000691990" container="mkv" deepAnalysisVersion="4" indexes="sd" requiredBandwidths="12262,11664,10994,10452,10136,9992,9992,9992" videoProfile="high">
<Stream id="527527" streamType="1" default="1" codec="h264" index="0" bitrate="7203" bitDepth="8" chromaLocation="left" chromaSubsampling="4:2:0" codedHeight="1088" codedWidth="1920" colorPrimaries="bt709" colorRange="tv" colorSpace="bt709" colorTrc="bt709" frameRate="23.976" hasScalingMatrix="0" height="1080" level="40" profile="high" refFrames="4" requiredBandwidths="11494,10896,10226,9684,9368,9340,9340,9340" scanType="progressive" width="1920" displayTitle="1080p (H.264)" extendedDisplayTitle="1080p (H.264)"> </Stream>
<Stream id="527528" streamType="2" selected="1" codec="eac3" index="1" channels="6" bitrate="768" language="English" languageCode="eng" audioChannelLayout="5.1(side)" requiredBandwidths="768,768,768,768,768,768,768,768" samplingRate="48000" title="English" displayTitle="English (EAC3 5.1)" extendedDisplayTitle="English (EAC3 5.1)"> </Stream>

Version 2:

<Media id="191011" duration="8026784" bitrate="3347" width="1920" height="1080" aspectRatio="1.78" audioChannels="6" audioCodec="eac3" videoCodec="hevc" videoResolution="1080" container="mkv" videoFrameRate="24p" videoProfile="main 10">
<Part accessible="1" exists="1" id="191152" key="/library/parts/191152/1625867726/file.mkv" duration="8026784" file="/mnt/Echo/Movies/Wouldntyouliketoknow/h265/Wouldntyouliketoknow/Wouldntyouliketoknow-WEBDL-1080p.mkv" size="3362182916" container="mkv" deepAnalysisVersion="4" indexes="sd" requiredBandwidths="38944,32153,18824,10742,10742,10742,10742,10742" videoProfile="main 10">
<Stream id="527933" streamType="1" default="1" codec="hevc" index="0" bitrate="2578" bitDepth="10" chromaSubsampling="4:2:0" codedHeight="1088" codedWidth="1920" colorRange="tv" frameRate="23.976" height="1080" level="120" profile="main 10" refFrames="1" requiredBandwidths="38174,31383,18056,10026,10026,10026,10026,10026" width="1920" displayTitle="1080p (HEVC Main 10)" extendedDisplayTitle="1080p (HEVC Main 10)"> </Stream>
<Stream id="527934" streamType="2" selected="1" codec="eac3" index="1" channels="6" bitrate="768" language="English" languageCode="eng" audioChannelLayout="5.1(side)" requiredBandwidths="768,768,768,768,768,768,768,768" samplingRate="48000" title="English" displayTitle="English (EAC3 5.1)" extendedDisplayTitle="English (EAC3 5.1)"> </Stream>

My issue is only with the transcoder failed errors that keep plaguing my users, and the fact that my poor aunt for some reason is unable to play anything at all, but that’s potentially a whole different issue entirely.

look at the required bandwidths.

H.264 + EAC-3

-vs-

HEVC + EAC-3

Can the second system transcode HEVC HDR in hardware?

Something is off with the analysis here.

Are you talking about the bitrate for the files or actual bandwidth requirement to stream them?

8 Mbps, 1080p ( * Bitrate 7974 kbps)
3.4 Mbps, 1080p ( * Bitrate 3351 kbps)

I am assuming the smart TV doesn’t support hardware decoding, but I’m not sure.

Care to elaborate?

Here are the logs from my aunts phone, I’m seeing a lot of ‘broken pipe’ - again, same network as my cousin where this all works fine.
plex-log-mobile.zip (198.7 KB)

  1. HEVC vs H.264 is not the same, even if you have a 14,000 Passmark CPU hammering through it.

  1. Being different codecs, I now see why the bitrates are off.

This is really an apples vs oranges comparison.

FYI. Early head’s up. Ubuntu 16.04 will be EOL in April and no longer supported.
You should be making plans to upgrade to 20.04 LTS sooner than later.

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