Anyone else been having issues with the Xbox One plex client as of late? Seems to be mostly TV episode MKVs that cause me issues - they stutter, audio and video go out of sync/get artifacts etc. The same MKV seems to play fine on other clients e.g. Fire TV stick and iPhone.
I’ve tried running Meteorite on said files but that just seems to get stuck and never completes the repair.
Any ideas? It’s driving me mad as I used to enjoy watching Plex on my Xbox One 
Cheers
Seems like it’s not direct playing them anymore. I’ve got a number of MKVs that used to play fine that won’t even start anymore on XB1 circa the 1.0 PMS upgrade and the accompanying XB1 client update…
I am having the same issues and have read here over the last few weeks numerous people experiencing it.
This is one example https://forums.plex.tv/discussion/227852/why-do-some-h-264-files-need-transcoding-for-xboxone-others-dont#latest
I did read on reddit that the issue arose with the release of PMS version 1.0 and people have had success downgrading. Unfortunately I can’t try this out at the moment as I have had a hard drive crash in my NAS and so can’t change my PMS version. I need to send the drive away and get it replaced under warranty which I will do soon, but it would be great if someone else here could confirm if this works
I have heard the rollback to pre-1.0 is helpful. Unfortunately my Synology NAS doesn’t want to let you downgrade from the package manager even after gutting the install manually. I performed a completely fresh install of a post 1.0 build recently and that wasn’t helpful either (I was thinking that maybe the initial 1.0 build had caused some kind of permanent problem with the existing install, so at least that’s ruled out).
I’m sure there is some way to trick the Synology to going back to pre PMS 1.0, but at this point I’d rather look forward and not backward and have a proper fix for the issue at the PMS level going forward.
Agree it would be nice to move forward with a solution, but as yet I am yet to see any staff acknowledge that this is an issue.
Cheers guys - to be honest i’m glad to hear it’s not just me! I’m considering buying a new Apple TV or a Fire TV as it’s annoying me so much!
I’ll try rolling back to pre-1.0 and see if that helps.
Also i’ve just seen a new version - 1.1.3.2700-6f64a8d was released recently - any ideas if that helps?
I’m having the same issues. Over half of my MKVs are not streaming now, but are on iOS and Win10 devices.
I’m not so sure about 1.1.3.2700-6f64a8d, if that’s the version that supports the beta DVR functions, I’ve heard some say that it creates additional problems for XB1.
Any confirmation yet that a rollback to pre 1.0 is still helpful? If so that would make me think that writing this off as an MS problem doesn’t make sense.
timlastoria, is that content that used to play successfully on XB1? If so, definitely in the same boat here for a couple of months now…
False alarm. Latest DVR beta and I’m good.
https://forums.plex.tv/discussion/232362/dvr-beta-two-dvr-harder#latest
@timlastoria said:
False alarm. Latest DVR beta and I’m good.https://forums.plex.tv/discussion/232362/dvr-beta-two-dvr-harder#latest
This beta seems to actually fix some (but not all) of the playback issues on XB1 that started circa PMS 1.0, thanks for the heads up. I guess we’re getting there…
@opoth said:
@timlastoria said:
False alarm. Latest DVR beta and I’m good.https://forums.plex.tv/discussion/232362/dvr-beta-two-dvr-harder#latest
This beta seems to actually fix some (but not all) of the playback issues on XB1 that started circa PMS 1.0, thanks for the heads up. I guess we’re getting there…
To elaborate a bit, it seems like the 720p content that was having trouble direct playing after the upgrade to 1.0 now direct plays successfully, but the 1080p content that used to direct play still tries to transcode. The only thing that’s changed on my end recently was installing the 2nd DVR beta of PMS, so the key seems to definitely be server side and not with the XB1 client.
@opoth said:
To elaborate a bit, it seems like the 720p content that was having trouble direct playing after the upgrade to 1.0 now direct plays successfully, but the 1080p content that used to direct play still tries to transcode.
That doesn’t really make sense because the decision to transcode comes from the Xbox and not the server. Your server logs from when you start playback on one of these files should help clarify why it is transcoding, without those it would only be guessing at why things are transcoding.
@jmckee said:
@opoth said:
To elaborate a bit, it seems like the 720p content that was having trouble direct playing after the upgrade to 1.0 now direct plays successfully, but the 1080p content that used to direct play still tries to transcode.That doesn’t really make sense because the decision to transcode comes from the Xbox and not the server. Your server logs from when you start playback on one of these files should help clarify why it is transcoding, without those it would only be guessing at why things are transcoding.
I’ll work on getting the logs shortly, but if PMS itself isn’t a factor, anecdotal stories of downgrading PMS to a pre-1.0 build as a fix shouldn’t be making a difference either. I agree that it shouldn’t make a difference, but after being shut out of most of my video content for the past few months (at least on XB1, other clients were still direct playing 720/1080p content successfully) I’m all too aware of what worked and what didn’t for that period of time, and absent an XB1 client update in the recent past, the only thing that has changed on my end recently is the PMS build.
Deleted post
This is my first shot at providing logs, so I apologize if I’m too verbose (or OTTOH, not informative enough)
I provided an example of a 1080p video that I was able to successfully watch using the XB1 client just prior to the upgrade to PMS 1.0 that still fails to direct play on XB1, and an example of a 720p video that began to fail to direct play on XB1 starting with PMS 1.0, but is now working after installing the second DVR beta (1.2.0.2765) which was released a week ago. Both of these videos have continued to direct play successfully in other clients such as Android or Amazon Fire TV after the initial update to PMS 1.0.
No hardware or software changes have been made to the server or client beyond the PMS update to 1.2.0.2765 a few days ago. I have kept PMS updated regularly in the hopes that the issue would somehow be resolved with a server side update and the 720p video that now works was failing as recently as PMS 1.1.3 (I passed on 1.1.4 after reading some reports that it created new issues on XB1)
Let me know if I can provide further information.
It appears that you have a video bit rate limit set. This automatically forces a video transcode, which your server is set to not be able to handle:
Sep 20, 2016 09:47:45.268 [0x409c4400] WARN - [Plex for Xbox One] [MDE] Invalid profile property; bitrate: 3919 > 3000
Sep 20, 2016 09:47:45.478 [0x3dcc9400] WARN - [Plex for Xbox One] [MDE] Unable to play; server unable to transcode video
As far as I can tell that is the only thing triggering the transcode is the quality limit that is currently set at 3Mbps/720p.
@jmckee said:
It appears that you have a video bit rate limit set. This automatically forces a video transcode, which your server is set to not be able to handle:Sep 20, 2016 09:47:45.268 [0x409c4400] WARN - [Plex for Xbox One] [MDE] Invalid profile property; bitrate: 3919 > 3000
Sep 20, 2016 09:47:45.478 [0x3dcc9400] WARN - [Plex for Xbox One] [MDE] Unable to play; server unable to transcode videoAs far as I can tell that is the only thing triggering the transcode is the quality limit that is currently set at 3Mbps/720p.
Thanks for helping to identify the smoking gun but I’m not sure where those limits are being enforced, and that could be my fault.
In Plex Web settings, the only non original setting was “Remote Quality” which was set to 720p. After setting that to original, disabling/reenabling the direct play option in the XB1 client, restarting PMS, restarting the XB1 client (and overall system) and signing out the XB1 client and signing back in, it still wants to enforce that limit.
Other clients on the same LAN (Android/Amazon Fire TV) aren’t recognizing that limit and can direct play that file successfully.
Plex Web restrictions will only affect the web player (IE in Chrome, Safari, Firefox, etc).
Someone else pointed out to me that 720p@3Mbps is the default for a remote stream, but you should be able to change it on the pre-play screen. The screen with the movie/episode information. There should be a button (The one with the 3 bars and sliders) and when you select you get the options to select audio and quality. You need to make sure that the quality is set to original.
@jmckee said:
Plex Web restrictions will only affect the web player (IE in Chrome, Safari, Firefox, etc).Someone else pointed out to me that 720p@3Mbps is the default for a remote stream, but you should be able to change it on the pre-play screen. The screen with the movie/episode information. There should be a button (The one with the 3 bars and sliders) and when you select you get the options to select audio and quality. You need to make sure that the quality is set to original.
That’s what I figured, but Original was already checked on the video (and was the only available option) in the XB1 client, so I hadn’t fiddled with it up until now since the client gave off the impression that it was what was being used.
That being said, manually selecting Original for a single video, even though it was already checked, has resolved the playback issue for ALL 1080p videos.
THANK YOU!!! This has cleared up months of headaches. This may be a very useful fix for anyone else who has been seeing similar behavior.
@opoth said:
That being said, manually selecting Original for a single video, even though it was already checked, has resolved the playback issue for ALL 1080p videos.
Well dang. I’m glad you got it working, but this bug is one that was thought to already be fixed. (Where a lower quality was being selected even though it was being shown as the original).
Thank you for sticking with it so I can get this passed on.
