@jjrjr1 said:
2. Changed Player Settings. Edge then recognizes the Container correctly as MP4 and Direct Played both Audio and Video.
What setting did you change?
The container is chosen on a by-case basis.
It will probably be different, depending on which web browser you are using. (They are not all made the same - each browser has its individual feature support and, of course, ‘quirks’. So developers built in different rules for different browsers to steer clear of these quirks and differently supported features.)
Edge supports AC3 audio, while Chrome and IE and Firefox don’t, so the transcoding / remuxing decisions will be different.
@“MovieFan.Plex”
It was in an earlier post.
Changed
Allow AC3
And upped remote and online bitrates from 3mbps to 8mbps. (LOL Trying to be considerate of people I stream from uplink bandwidth)
@jjrjr1 said:
It was in an earlier post.
Changed
Allow AC3
Otto’s answer above about AC3 support would impact this.
And upped remote and online bitrates from 3mbps to 8mbps. (LOL Trying to be considerate of people I stream from uplink bandwidth)
That is odd. The first XML you posted shows a bitrate > 3 Mbps so this file should have transcoded and not remux, so I’m not sure what is going on there. The MDE info doesn’t mention that there was a 3 Mbps limit (it should).
@“MovieFan.Plex”
I would not expect it to show a 3mbps limit since the connection was local and I have local setting to original.
I have no clue what is happening but I am no expert. Plex Web said transcoding PlexPY said Direct Streaming. Also I know Edge supports AC3. That was the main reason I looked at that setting and enabled it in hopes of resolving this problem
Chrome and IE showed behavior I expected with regards to the Audio. Although Chrome’s behavior surprised me as thinking source was MKV…
@JonnyWong16 said PlexPy could be wrong as the API has changed. But making those changes definitely fixed the stuttering and then the media Direct Played in Edge and PlexPY correctly displayed status… LOL If you can believe what you see.
@OttoKerner
I understand that but getting the source container incorrect until the change was made does not make sense to me.
CPU showed practically no utilization but PMS reported the server was not powerful enough and was direct streaming from Mpeg Transport stream to Mpeg Transport stream in spite of the fact it was a mp4 container. (According to PlexPy)
BTW is h.265 supported in a MPEGTS, I do not know. I thought is was only mpeg-2. Could be wrong.
Regardless. Making those changes in PlexWeb on Edge resolved the problem. Chrome Reported MKV container not MPEGTS. Plex Web in IE reported exactly what I would have expected. Neither Chrome or IE Stuttered.
Dunno what to make of it myself.
If there is anything you would like me to do to help test or provide more info… Just let me know.
Just so you know unless you STOP and START a video NOW PLAYING will not show anything different.
By this I mean if you start out direct playing a file but then force it to transcode by changing client bitrate NOW PLAYING will continue to show direct play. If you stop and then start the video again Now Playing will show it correct unless you change the client again. 
NOW PLAYING is not reliable. Much better to use PlexPy.
@jjrjr1 said:
@“MovieFan.Plex”
It was in an earlier post.
Changed
Allow AC3
And upped remote and online bitrates from 3mbps to 8mbps. (LOL Trying to be considerate of people I stream from uplink bandwidth)
May not be considerate at all. 
For example if you were playing videos from my system i would much prefer you play them “all out” or direct play. From my Plex server’s perspective it has unlimited bandwidth but not unlimited CPU/GPU resources.
@cayars said:
Just so you know unless you STOP and START a video NOW PLAYING will not show anything different.By this I mean if you start out direct playing a file but then force it to transcode by changing client bitrate NOW PLAYING will continue to show direct play. If you stop and then start the video again Now Playing will show it correct unless you change the client again.
NOW PLAYING is not reliable. Much better to use PlexPy.
Unless, as stated earlier, you are running PMS 1.4.x - PlexPy is not currently reliable either.
Why do you say that about PlexPy? It just reads the log files. It’s as acurate as the logs themselves.
Maybe I’m wrong and don’t know about a bug, but from my testing and experience it’s been correct while NOW PLAYING is all over the place wrong.
Ok Everyone.
I got it…
Will make those changes and call this issue resolved.
Thanks…
BTW it is only in Plex Web where I had BW sel low for Remote and online.
All my Rokus are set to original quality.
Cell Phones and Tablets usually used off local network so my Server Threshold I assume is enforced.
@cayars - because the developer of PlexPy said so 
:
@JonnyWong16 said:
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 said:
Why do you say that about PlexPy? It just reads the log files. It’s as acurate as the logs themselves.Maybe I’m wrong and don’t know about a bug, but from my testing and experience it’s been correct while NOW PLAYING is all over the place wrong.
Also wrong. PlexPy doesn’t use the Plex log file at all.
Guess I need to read up more in that thread 
@JonnyWong16
PlexPy just updated.
Does it include the fixes you mentioned with regards to PMS 1.4.x API as you mentioned in this thread???
Thanks!!
@OttoKerner
@cayars
@JonnyWong16
@“MovieFan.Plex”
Oh BTW,
I am not the only one who is apparently having or noticing this NON-Problem LOL
Here is another example that seems related.
I know it’s on the Shield but I am guessing these type posts coming up all over are all related. IMO.
But… I’m prolly all wet on that feeling.
@jjrjr1 said:
@JonnyWong16
PlexPy just updated.Does it include the fixes you mentioned with regards to PMS 1.4.x API as you mentioned in this thread???
Thanks!!
No
Cool
Thanks for the info…
@jjrjr1, sorry for seeming to drop the ball here. If you would like to investigate the underlying cause let’s try something.
- change the settings back to what they were to cause the transcoding issue
- turn on logging for Plex web, play the file and confirm it is transcoding from now playing
- let it play for a few minutes, then get me the web and PMS logs
- roll back to an earlier version of PMS
- double check web is using the same settings and repeat playback like before and get here those logs
Thanks
Just to provide some insight on my thoughts on this, 1.4.3 did introduce web v3. I haven’t looked but it’s possible some web settings got changed, which would explain the differences in behavior. That’s why I asked above to make sure the settings are the same when recreating the issue with the older PMS.
