Hardware transcoding issues with PMS 1.24.x and 1.25.x? Any details on what the HW transcoding issues are and is a fix in progress?

Any update on this? Causing a lot of grief with the kids!

1 Like

Does a DEV have an update, are they talking to Google about it?

2 Likes

njwebPlex Pass

[quote=“njweb, post:14, topic:776594”]

@BigWheel @MovieFan.Plex - We have not heard anything in a while.Can someone at Plex please share an update on the investigation / root cause of the HW transcoding being broken in PMS 1.25?
Any ETA for a fix since this has been outstanding since January?

Thanks!

3 Likes

Any advance in the hw transcoding issue in shield device?

1 Like

The silence is deafening.

Just a “yes we are still working on it” would be nice but instead we are just ignored.

1 Like

Adding another comment asking for some feedback on how the fix for this is going


1 Like

when will the issue be fixed ?

1 Like

Yes, we are still working on this. I don’t have any updates.

9 Likes

It’s been 2 weeks, are there any updates?

6 Likes

It’s been months and months without any update on this issue. Makes the shield as a plex server basically unusable. I highly doubt any fix is coming given that this has been broken for almost 6 months at this point without any update.

Hi, any news on this?, what does still working on it mean?

Thanks.

2 Likes

Hi. Any news on this issue? I, think most of us all are patient but still want transcoding feature back. Thank you

1 Like

Update: After experiencing the NEW TrueHD issue

I noticed some people saying there was a potential fix for the TrueHD issue in 9.2.Beta or something similar (not sure whether that is Shield Experience, given the numbering scheme I guess it could be), I noticed that PMS 1.26 latest beta apparently has a fix for HW transcoding.
I downloaded and installed PMS 1.26.0.5715.

QUOTE - Plex Media Server 1.26.0.5715 is now available to Plex Pass users in the Beta update channel.

NEW:

** (Metadata) Pull down country info for TV shows during metadata refreshes (#13463)*

FIXES:

** (Music) Improve artist searches when the search term is an alias (#13441)*
** (PubSub) A pubsub server with sub-optimal latency could be selected (#13480)*
** (Transcoder) Hardware transcoding could fail on Nvidia SHIELD TV systems (#13452)*
END QUOTE

I have yet to test hardware transcoding fix (not sure how to force it), but it seems it may have fixed the TrueHD 7.0 playback issue on My Roku Ultra devices (for the most part, based on limited testing).

1 Like

It’s great that the 1.26 fixes a potential issue with nVidia Shield. However, the only available version on Shield as of today is 1.25.3.xxx, which is still 7 minor versions behind the current one :slight_smile: When should we expect anything newer to land on the Shield planet?
Thanks!

You are correct if you’re referring to Non- PlexPass user. Otherwise it is already available now in the beta channel to Shield users who have a PlexPass.

How do you access the beta channel?

1 Like

Follow the instructions for PMS for Shield (scroll as needed) at the following link: Early Access & Beta Releases | Plex Support
(Today is my first time doing a PMS Beta too, so I had to google it myself).

2 Likes

I just noticed that my PMS is 1.25.9.5721
So the update today was from 1.23.x.xxxx to 1.25.9.5721
Anyway, I updated to 1.26.0.5715 Beta now (double checked that the PMS version running is 1.26.0.5715

Anyway, so far no difference for me between 1.25.9.5721 and 1.26.0.5715 Beta in my limited experience so far with these 2 versions.

Tested 3 videos with TrueHD 7.0:
The two 4K True HD clips play with both of the above PMS versions, albeit one takes a while to load now (load times were faster when I was on PMS 1.23.x, but that was before the FORCED April 5th Plex TV Client update).

The one 1080P True HD 7.0 clip does not work when DirectPlay is set to ‘Auto’. For that clip, when I change DirectPlay to ‘Force’ (instead of Auto), it loads super fast and plays fine.

Same here. No changes with version 1.26.0.5715 still no hardware transcoding from 4k sources.

Thank you for your efforts,

They havent fixed anything. Issue is still there, see my detailed post, and test:

@anon18523487 - said working on it, was the fix today supposed to be it? if so, didnt work :frowning: see above