It has been over 2 months since the “Unable to determine HEVC Profile” showed up on the android app in the latest ChromeOS (doesn’t matter if the media is HEVC encoded or not or if you force the transcoder to use H264 or not) and has been documented but Plex still hasn’t even acknowledged that the issue exists let alone issued any kind of fix for it. What gives? When can we expect atleast a partial rollback or fix to actually be able to use the software on the ChromeOS? Right now I have to run in DEV mode with an older version of Plex, which causes issues because Dev mode has some issues with certain software that requires signatures.
Last I heard, @McWanke said there are internal discussions happening around the future of the apps. Take that for what it’s worth I guess. They definitely are not being very transparent though. What I get from the few interactions we’ve had is that they are digging their heels in and pushing forward with the new apps regardless of the mountain of negative feedback.
There are a lot of suspicions going around that this new direction is being forced by some investors wanting them to ge an ad-supported streaming platform first, personal media server second. This is even more evident if you look at the current app store pages. The screenshots and descriptions all focus on streaming content (not the server) and at the very end they tack it on as an afterthought.
The issues reported here are not addressed at all. Every update they make is to fix some minor things and ignore the real problems.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
