I have recently started to re-encode my entire library to H265/HEVC using Handbrake 1.0.0 - 1.0.2. Within Handbrake I am using the “H.265 Intel QSV” (Quick Sync) as to speed up the process.
90% of these H.265 files work great and the space and quality improvements are just what I wanted.
However, I have an issue which I have run into a few times and now it is becoming a bother. Please see the attached screenshot. This occurs during playback of the files on Plex running on the Amazon Fire 4k.
The file plays fine on the PC where I am encoding it using VLC. If I force the file to transcode on the server by lowering the bit rate on the Plex client, then playback is fine also. It seems to be a specific issue with Plex on the Fire TV 4k.
I’ve also noticed it seems to be related to a lower resolution or odd resolution of a file. Most of my proper widescreen 1080p content was unaffected. But in this case, its 4:3 1080p and in other cases it was DVD rips using H.265 which also showed the issue.
Can anyone provide me some guidance? If logs are needed, can someone tell me which logs and how to get them? Thanks!
EDIT
Also, in Handbrake, if I select x265 as the encoder, playback also works fine. So there is something specific between Intel Quick Sync H265 encoding and Plex playback on the Amazon Fire 4k.
I am not looking for my NAS or Plex server to use Quicksync. I am only using it to encode the files in H.265 as I can get ~50fps during encoding of 1080p content. Encoding with Intel Quick Sync does not require (or should not require) Intel Quick Sync to decode, just a H265 decoder (or SW). The Fire TV 4k has a H265 decoder and this works for most of my files. It is about 10% that experience this issue.
I know that direct play of these H.265 files is happening because the CPU on my NAS is near 0% during playback. So with the exception of the messed up video playback, its working.
I’ve recently started to do the same thing with my library. The only difference is I’m not using the Intel Quick Sync in Handbrake. Just a standard h.265 encode. Yes, it takes longer but I’ve read things about the Intel Quick Sync that people say there are still issues with it.
I have not experienced these issues you have with any of my h.265 files.
I know that doesn’t help much but just wanted to pass along my experience with it. I’ve only have 10% of my library converted so far.
Here are the logs. Just did a fresh playback at 10:51 EST for “Star Trek - TNG - S1E03 - The Naked Now” which showed the issue. Let me know if I can gather any other data.
And Thanks @johnny15. I have a SkyLake i7 and using the Quality preset in handbrake, the quality has been at least as good as my H264 rips, but at reduced size. Also, using the quick sync lets me encode H265 w/ 1080p @ 50fps which is at least double the SW-only route, so I am moving right through my library.
@trumpy81 said:
When you turn on QuickSync in Handbrake it encodes the video itself with the QuickSync optimisations … you cannot use those optimisations on an ARM processor, you MUST have an Intel processor with HD Graphics and QuickSync in order to decode the video correctly.
You will have the same issue decoding this video on an Intel processor that does NOT have QuickSync.
Do you have documentation that states this? This would seem to defeat the purpose of using a standard like H265… Also, its only Plex on the Amazon Fire TV 4k that has this issue. It plays fine on other platforms and in other players which also don’t have Quick Sync available. On my own computer it plays fine in VLC which isn’t using an Intel graphics card. Plays fine on my Android phone which is Snapdragon powered, no Intel QuickSync.
I really think there is an issue here either with the Plex client or the Amazon Fire TV 4k. Just looking to figure out which one.
I have the identical visual problem with my Amazon Fire (latest gen) and HVEC with random videos. Usually they are 480p but I’ve rarely seen it on 1080p as well. Invariably they play fine on Roku Ultra/PMP/web/Android with no problems. I use handbrake to encode but Intel Quicksync option is disabled so I know I ain’t using it. I haven’t worked up the fortitude to try to get logs from the Fire to post yet. I actually don’t use it very often.
@trumpy81 Those are parameters for using the Intel Quick Sync encoder, there is nothing there that states the H265 file produced would be proprietary after encoding.
I have captured both client and server logs for playback of “Star Trek - TNG - S1E03 - The Naked Now” which exhibits the issue. If someone from the Plex team could take a look at the logs I would really appreciate it. I took a look but I don’t see anything obvious, although, I have no idea what I am looking for…
@trumpy81 Thanks for looking at the logs. The FireTV bug looks promising. My FireTVs are as up-to-date as I can make them. Not sure how to track down bugs on the FireTV though.
@bigdwg71 said: @trumpy81 Thanks for looking at the logs. The FireTV bug looks promising. My FireTVs are as up-to-date as I can make them. Not sure how to track down bugs on the FireTV though.
I would suggest upgrading to Handbrake 1.0.3. The last two movies I converted on Handbrake 1.0.0 had some crazy issues with the video with 3 large bands horizontally through the picture. It would come and go ever second or two. Not sure if it matters but both were animated films.
I upgraded to 1.0.3 and it seemed to resolve issues with both movies.
Hi. I know this topic has been quiet for over two years, but this is a very similar issue to what I am experiencing on my FireTV with 480p 4:3 ratio video encoded as HEVC (if I re-encode as H264 it plays fine). If I watch using PMP on my Surface Pro (the original one) it plays fine, but on my FIreTV I get picture similar to that shown above.
Is there still a bug with decoding certain video resolutions/ratios encoded as HEVC on the FireTV?
