Anyone else have this issue?
Every since this update. All H264 I tried transcodes to H264. Reason says because E-AC3 audio not supported. But in the past when I played the same files, only the audio would transcode and video would be direct play (say Copy).
Other formats, even higher bitrate files, work perfectly. Including HEVC.
Nvidia Shield 2019 is the device.
Thanks
Logs please. It should still be able to transcode audio only.
I can confirm this is an issue with Android device as well.
Its been reported here as well. Audio transcode causing video transcode
Any android based device I own transcodes the audio and the video for files containing EAC3 audio. That includes my Pixel, my Nvidia Shields, and my Fire-tv.
Roku does not have this issue, nore is the issue present if I cast to my Shield. Hell its not even present if I cast to my Google Home Hub display. All of these use direct play for audio and video.
Hum. Your logs show that the Android app thinks your device doesn’t support the high profile, only baseline.
Feb 04, 2020 12:33:37.343 [0x14f095dee700] DEBUG - Events By Russell - video.profile limitation applies: high != baseline [list]
Can you reproduce and provide me the log from the Android app?
@anon18523487 That is acutally my server log. Here is the client log. This line seems strange.
02-17 07:50:41.817 i: [video] The device doesn't support the 'high' profile, only: high
shield log.txt (159.5 KB)
i’m having the same issue on a firestick 4k also when i load the app it says that i require a gamepad controller, it doesn’t say “works with fire tv remote” like usual.
Yup, we found the problem. Fix will be coming out soon.
That’s actually a different issue. You can follow that at Game Controller Not Detected - #48 by spawn1980.
Maybe because it set everyone’s maximum h264 level to 1.0? If you go into settings and bump that up to something higher like 5.0 maybe that will fix it until they release an update.
I can confirm on my 4k Fire Stick. Pre-update the “recommended” H264 Max Level was 5.2 (or maybe 5.1?). Now it’s showing 1.0. Setting it back to 5.2 fixes the issue for me. There are also new options for 6.0 and 6.1 which I’ve never seen before on any Plex client. I’m guessing the addition of new options caused the issue
@PlexInTheCloud Thanks. I think you are correct about this. The previous “recommended” setting was 5.1. I think this got changed with the update, so anyone that had this set to “recommended” would now see this issue. Mine was set to 5.2 so I hadn’t noticed this issue. I’ve relayed the info to the team.
changing that will fix the issue for any h264 media but it does not fix it for anything 4K
HEVC
the level is not the issue in all cases, both my shields without a receiver are still on the correct 5.2 yet are both transcoding the video unnecessilary
Yeah, there is another issue that the devs found. That one is already being fixed.
Of course not. This thread is not about hevc.
Yes I can confirm that changing the level does not resolve it for me.
lol, my fault, i’m all over the place today trying to keep up with all these threads, my apologies, and also i’m sorry my suggested fix didn’t work anyway.
After finally getting 4k files to play without buffering issues thru the Firestick and plex app and enjoying it for two weeks, this latest update has negated everything and back to square one. No 4k playback thru the stick. The only way to get the 4k files to play now is thru DLna on the 4k Blu Ray Player. Hope the fix is soon as it was working nicely and very convenient.
kodi with the plex add-on is still playing 4K HDR very nicely for me.
alternatively you can also disable app auto updates, uninstall 7.28 and install 7.27.1 from here. Plex for Android
it looks to be fixed in 7.29.0.15665-beta
