MDE Error, It Seems. Strange behavior for files that should Direct Play.

I have some recent Blu-ray rips.
They are mp4 / h.264 / ac3

Trying to play this, and all the rest from the same TV Series exhibit the same problem

Takes extremely long to start playing (So far only tested in Edge).

When it finally starts playing I get the error server not powerful enough to play, check playback setup. The Video stutters every 4-5 seconds.

PlexPY shows the video to be Direct Streaming. Curious why since it is in MP4 container.
So it should not be direct streaming in the first place and direct streaming should require practically NO system resources to direct stream, making the server not powerful error seem strange.
Also the PMS box shows only 4% CPU utilization, So why the not powerful message.

This is all very confusing as these rips are pretty standard and in the same encoding format I have used for thousands of other rips without getting these problems.

Any help would be appreciated.

Logs and XML attached, The situation will be at the end of the logs

Thanks.

File is not ‘Optimized for streaming’
Thus, it will get remuxed (which only causes minimal cpu load).

If you want it to direct play, optimize your file.
On Windows mp3tag can do this for you.

side note: your season folders have unnecessarily long names. Season 01 is enough.

Well any other media I encode just like that does not exhibit this behavior.

Why remux?? It is remuxing mp4 to mp4??

Why the server not powerful enough error???

Why the buffering or stuttering??? (PlexPy does not indicate buffering)

The MDE must be telling the server to remux for some reason.

Is the fact I keep the series name on the season folder causing this??

Been watching this a bit and PlexPy does show buffering.

Why buffering for direct stream?? The CPU shows very little utilization.

Also I have throttle buffer set up in the server for 300 seconds. It is buffering at much shorter duration than that…

@OttoKerner
Stream Details
Media
Container: mpegts
Resolution: 1080p
Video
Stream: copy
Width:
Height:
Codec: h264
Audio
Stream: copy
Codec: ac3
Channels: 6
Source Details
Media
Container: mpegts
Resolution: 1080pp
Bitrate: 6009 kbps
Video
Width: 1440
Height: 1080
Codec: h264
Aspect Ratio:
Frame Rate: 24p

Plex PY says the stream details are as above.

The File is not in mpegts container but mp4. In any event even if it is mpegts, why remuxing source and stream containers are the same. Shouldn’t that be direct play not direct stream ie. a remux??

Getting the same sort of behavior on DVR recordings now as well.

@OttoKerner

Here is an XML file for a Blu-Ray Series rip encoded with the same settings as the first one I sent.

This file does not stutter but is also direct streaming.

Does this help figure out why??

A movie rip with similar bitrate Blu-ray attached that also plays without stuttering.

Incidentally, on The Roku 4 the offending file Does Not Stutter. In Fact on the Roku it Direct Plays… Can’t figure that out either.

Look at the XLM file you posted in the first post. There is a lot wrong with this file streaming wise:

It’s not optimized for streaming optimizedForStreaming=“0”
You have AC3 audio and probably want the first audio track to be AAC
You have Reference Frames at 1

I thought you were using the scripts I provide to convert media to the correct format that agrees with Plex?

@OttoKerner

I think I fixed the issue.
I changed Plex Web Settings to allow AC3 audio and changed Remote and Online Quality from 3mbps to 8mbps. Local remained at original. (This media is playing local on a 1gb lan)

Go Figure… LOL

That video now Direct Plays and PlexPy shows correctly the container is MP4

Very Strange…
Unexpected behavior to say the least…

@cayars
No I am using DVDFab to rip and encode.
This is the only file I have had trouble with
I solved the problem it seems by changing settings for PlexWeb Player.

See above post.

Plex always direct plays my media with no issue.

Thanks for the help.

The two files whose XML you posted were not encoded with the exact same settings.
I cannot tell you why the stuttering occured.
But both files are not optimized for streaming.

The files are remuxed to MPEG Transport Stream because the unoptimized MP4 container doesn’t support the HLS (streaming) protocol.
Optimize the files and you will prbably see a different outcome (at least with some client types).

And I have to agree with @cayars that a reference frame count of 1 is at least inefficient, since it either sacrifices quality or coding efficiency.

@jjrjr1 said:
I changed Plex Web Settings to allow AC3 audio and changed Remote and Online Quality from 3mbps to 8mbps. Local remained at original.

Your server treats your local clients as if they’re remote.
This indicates, that your router needs some settings changed:
https://forums.plex.tv/discussion/comment/1172731/#Comment_1172731

Alternatively, simply switch off ‘Secure Connections’.

@OttoKerner

Ok I will check that but I do not think that is so since I have my remote streaming setting to 3mbps.

So if my local connections were being treated as remote ALL my media would be transcoding which it clearly is not.

I can run 4K streams everywhere but to Plex Web for obvious reasons.

In fact My Plex web logs in directly to the IP of the server not thru plex.tv.

Pretty strange if, under those circumstances, Plex thinks It is a remote request.

Also if that were the case would it not Transcode not simply remux as Direct Stream??

Dunno.

@jjrjr1 said:
So if my local connections were being treated as remote ALL my media would be transcoding which it clearly is not.

Maybe there are other factors in play here as well, like a fractured network (which happens when your router puts e.g. wired and wireless clients into different networks or prevents direct communication between them.)

‘Mobile’ Plex apps have a workaround for the issue already built in.

In fact My Plex web logs in directly to the IP of the server not thru plex.tv.

When you point your browser to local Server IP you are merely loading the Plex Web app into the browser.
It does not mean that the web app now communicates directly with the server.

^^ I don’t think any of those things is the issue.

I do see in your log that the speed is reported being < 1.0, which is very slow for a remux. I do see that you have a DVR recording going on at the same time. Do you have your DVR set to perform a live transcode while recording? This could be taking up your CPU.

Why PMS is trying to remux your file? I will have to agree with OttoKerner that it’s because your files are not “optimized for streaming”, which is needed for browsers. The Roku doesn’t require this so it can direct play.

The XML you provided for the file that does work is a SD video with a very low bitrate. This file probabaly isn’t giving your computer any problems even if there is something else going on in the background.

@OttoKerner
There are no WiFi users here. All connections are CAT 6

Well like I said my remote setting is for only 3mbps streams allowed

Nothing here ever transcodes to a lower bitrate than my files and almost all of them exceed 3mbps

Something here is broken it seems. Either everything should be transcoding to meet the limit I have set or that limiting function is actually broken

But like you are suggesting… Prolly my error somewhere…

Why re-muxing to MPEGTS and thinking the original source is MPEGTS.

Just rather strange behavior, I cannot really understand what I have been doing wrong all these years. But I am sure it is something.

If You do not think it needs to be looked into more, OK.

It works fine for me now anyway for what ever reason.

And BTW, I have many remote users and it does seem that the limit actually works so back to square one… All local media should be transcoding if Plex thinks it is remote.

Also the drop down for selecting servers, Plex Web correctly shows that my server is Nearby…

Go figure.

Plex web knows it’s nearby but the server does not??? Really??

@“MovieFan.Plex”
Thanks for your input.
I do not use transcode while recording as that is not quite ready for prime time yet (Has gotten better in Beta 5)

Also after changing the settings in Plex Web all is working fine on edge it direct plays now.
Stream Details
Media
Container: mp4
Resolution: 1080p
Video
Stream: direct play
Width: 1440
Height: 1080
Codec: h264
Audio
Stream: direct play
Codec: ac3
Channels: 6
Source Details
Media
Container: mp4
Resolution: 1080p
Bitrate: 6017 kbps
Video
Width: 1440
Height: 1080
Codec: h264
Aspect Ratio: 1.33
Frame Rate: 24p
Notice after those Plex web changes it now correctly identifies the source as mp4.

Just tested it in Chrome. First time using it in Chrome so they are the default settings. Here are stream details in chrome
Stream Details
Media
Container: mkv
Resolution: 1080p
Video
Stream: copy
Width:
Height:
Codec: h264
Audio
Stream: transcode
Codec: aac
Channels: 2
Source Details
Media
Container: mkv
Resolution: 1080pp
Bitrate: 5817 kbps
Video
Width: 1440
Height: 1080
Codec: h264
Aspect Ratio:
Frame Rate: 24p

These data are from PlexPy.
Also notice in Chrome PMS thinks the source and stream are MKV. Egde, when failing, thought they were both MPEGTS.
In Chrome it does not stutter as it did in Edge before changing settings

Strange behavior as I understand how things work.

Just ran a comparison In IE.
LOL
Stream Details
Media
Container: mp4
Resolution: 1080p
Video
Stream: copy
Width:
Height:
Codec: h264
Audio
Stream: transcode
Codec: aac
Channels: 2
Source Details
Media
Container: mp4
Resolution: 1080pp
Bitrate: 5817 kbps
Video
Width: 1440
Height: 1080
Codec: h264
Aspect Ratio:
Frame Rate: 24p

Different results here as well.
Notice at least in IE it knows it’s a MP4, which is correct.
In IE, it transcodes audio and copies video.
And BTW this is correct and expected behavior for IE as it does not support AC3 so must transcode Audio to AAC…
Also no stuttering…

LOL
I truly did not expect 3 different results.
I suppose if I try firefox I would see something different.

As I said, if you guys are ok with all this… so am I as everything seems to at least be working so it does not stutter in edge

@cayars
@OttoKerner
@“MovieFan.Plex”
I find all this interesting and PerPLEXing

  1. Edge thought the original file was in a MPEGTS container and was Direct Streaming stuttering badly.
  2. Changed Player Settings. Edge then recognizes the Container correctly as MP4 and Direct Played both Audio and Video.
  3. In Chrome (Default Settings) Plex thought Container for media was mkv re-muxing video to mkv transcoding audio as expected since it needed aac. No Stuttering.
  4. IE actually was the only browser that behaved exactly as expected with no stuttering and default settings.

Dunno if anyone cares or if I am completely in the dark here. LOL I usually am.

John

How/why do you think Edge thought it was an MPEGTS container?
How/why do you think Chrome thought it was an MKV container?

Are you getting this info from the Plex logs or PlexPy?

Just popping in to say, don’t trust the PlexPy info on PMS v1.4. The sessions API changed, so PlexPy is gathering incorrect info until I fix it.

@cayars
Plex PY.
Is that un reliable??
After changing Plex Web Settings PlexPY reported correctly as mp4 as expected and direct playing.

If there is some more testing anyone would like me to do…
Just let me know.

If you guys think this is expected behavior in these circumstances, cool. All is working OK for me now.

BTW I did supply logs for the initial error in edge.
I have never been able to figure those logs out… LOL
So I defer to the experts…

@JonnyWong16
Thanks for the info.
Wonder why the change after changing Plex Web Settings in Edge.
The changes definitely changed performance in Edge… Stopped the stuttering and PlexPY reported what I would have expected to see.

A note…
Plex Web in now playing would show transcoding as well until the change. After which Plex Web showed Direct Playing.
Unfortunately Plex Web Now Playing does not indicate container info.