That all your 4K efforts are absolutely wasted on.
No need buying live rabbits for animals that can no longer chase them down for the kill - canned rabbits are good enough and way easier to digest.
![]()
That all your 4K efforts are absolutely wasted on.
No need buying live rabbits for animals that can no longer chase them down for the kill - canned rabbits are good enough and way easier to digest.
![]()
lol, my 4K efforts are for me, and the rest of the crowd thatâs under 40⊠the 2x65 year olds donât even have access to those libraries⊠Mainly cause neither of them has a 4K TV⊠But streaming 30Mbit 4K HDR files remotely is fun⊠Iâve gotten it up to 14 remote streams (only cause we ran out of people with 4K TVâs/Devices) hehe
Thanks Jason, JuiceâŠ
So, trying to figure out x265 or x264⊠does it depend on WHAT devices would be playing it? Like some old DVD players may fail, but I donât have any. The devices that have to play it for me are:
So, in ANY of the above situations, would x265 offer a challenge? I think only my older Panasonic TV may have an issue, however, a Roku with Plex solves that problem, unless you think Roku stick also has difficulty with x265?!
I think the Roku Stick+ should be ok for 265. Your best bet is to encode a single test file with your normal playback experience and test it out ahead of time.
The rest of your devices definitely support 265 (although the iOS devices donât like .mkv containers, and will âtranscodeâ the container (de-multiplex and re-multiplex into mp4), so if you donât need 3-4 audio streams, and 3-4 subtitle streams, Iâd recommend just making the container .mp4
Thanks, I am making all mp4, apart from downloads. Now, for iOS playing natively there maybe issues, what about playing it via Plex on iOS?
I have 4 users that play on iOS via the Plex app all the time, no issuesâŠ
The best test file is a Preview from right in Handbrake. 240 seconds is plenty long enough to find all (the many) failure points associated with 265. Throw it into an âOther Videosâ library for quick access without a lot of matching drama.
Youâll be happy youâre making a 4 minute preview when you notice HB moving âGlaciallyâ through material that once marched along briskly. Also in combination with that - when, not if, Plex is required to transcode 265 for any reason (an unbelievably long list) the transcoder will devour your CPU creating 264 from 265.
Youâll notice this right away with the orange spinnerâs almost constant presence. <âanother reason to hate 265? <âfor me - I donât need any more reasonsâŠlol
I encode 1080p 265 at 250fps. Thatâs a little over 10x as fast as the movie plays⊠You just need to enable hardware acceleration for Handbrake, provided you have a video card capable of it.
I just did some tests, and a few questions about your suggestions
Generally, WHAT Kbps is recommended in x265 for the following resolutions?
I found the same thing. Itâs worse on video sources than film sources.
Yep. If your devices support h265, and/or you have Plex Pass and your server supports acceleration of h264, itâs fairly unnecessary to use h264 except for extreme compatibility.
This is a rabbit hole. For DVDâs, you should probably just use default interlace detection in Handbrake, with Decomb-default, and frames-per-second as âsame as sourceâ.
The main problem is that if itâs a film source, you also want to detelecine. Otherwise youâll have a repeated frame every fifth frame (you can see this going frame-by-frame in a player that supports it). There are exceptions, like old Star Trek TV show DVDâs, that require 30fps even though parts of it is film. Like I said, itâs a big rabbit hole.
Someone else may have a good link for how to know to determine this stuff, I unfortunately donât have time at the moment.
I believe Auto should keep things at the maximum resolution, and will take care of the anamorphic setting.
There is large disagreement here, but I prefer x265 quality-based, RF 18 or 19 for DVDâs.
Thanks, last question, I have an Nvidia card and could use x265 (Nvidia Nvenc), which is A LOT FASTER! But, at the same quality rating, it results in a much larger file, but if I could do a fixed bitrate (letâs say 1500 kbps), can change the file size to be the same as x265 CPU one⊠DOES it change the quality of Encoding using the Nvidia card?
you donât need LapSharp on HD material. You would ONLY use it for DVD material and never more than itâs default setting. I canât see that it actually does anything, except that the encode looks better than the source - and thatâs what you want in a sharpening filter. If you guys are adjusting the filter so that you see it doing something - ur on your own (and you donât know what youâre doing).
If you use Decomb with the default detection it doesnât do anything to material thatâs not interlaced. On material that is interlaced it ONLY decombs the artifacts - meaning that you can see it turning on and off, the resolution bouncing clear and fuzzy (even, I, âMagooâ, can see that - thereâs a reference lost on youth). If you use Yadif with no detection the entire video is deinterlaced and when combined with LapSharp you end up with a nice deinterlaced item - with no bouncing resolutions.
if anyone on the planet thinks HEVC improves video quality - youâll need a LOT more experience with encoding/watching your work. There are some âmythsâ about encoding that you may believe - that simply are not true/have no basis in fact or reality. Also - if you plan on using HEVC - you better outfit everyone in your Plexiverse with a Shield, or have one HELL of a machine when it has to transcode most of what it delivers. You are opening up the door to a whole lot of unnecessary pain and suffering if youâre using DVD or lower level HD. If you use 4K - you better prepare for pain and suffering at epic proportions, but also learn - a LOT more than you do now about HEVC, 'cause youâll be using the HELL out of itâŠlol
When I first started encoding there were no helpful people that knew anything about it other than a few sites that offered basic or bogus information I had to build on with literally YEARS of trial and error.
Eventually, if your encoding career continues, you will learn these important lessons - and also be re-encoding a LOT of earlier stuff when you find out how wrong you were about a lot of things. Iâve always got something in Handbrake - a lot of it re-encodes⊠nobodyâs perfectâŠlol
People think Hardware is the answer to the worldâs problems. Hardware encoding is inferior to good old fashioned CPU horsepower in every conceivable way and is ONLY meant to be used when your graphic card has more horsepower than your Fischer Price Server Machine (The Cow Says; Moo).
Really, though - a lot of this stuff you just have to find out for yourself and in the end you have to watch what you encode. Make your eyeballs happy. As your eyeballs get older they may be happy with something totally different than theyâre happy with now, but hereâs hoping you get to experience that horror show - it beats the crap out of the alternative.

What video card (and CPU) do you have?
Ryzen 2700x and a GTX 1070Ti
Heh, this is hotly debated as said before. For me, this is what I have set currently
DVD/480 - 1024 kbps (I change all 29.976 FPS content to 23.976 when DVD Source)
720p - 2560 kbps
1080p - 4096 kbps (if itâs got a lot of action in it or loads of panning shots (think LOTR) I sometimes put this up to 5120 but this is rare)
4K Non HDR - 12,288 kbps @ x265 8bit
4K HDR - 25,600 VBR with the MAXIMUM bitrate set to 76,800 kbps @x265 10bit, but I do not use Handbrake for HDR content as itâs still an 8bit pipe (even the nightly builds) So I use StaxRip with VapourSynth to do all of my HDR encodes
That ranks as the #1 piece of bad advice ever uttered by mankind.
Same As Source - always.
Variable Framerate - always.
If youâve never experienced the pure joy of changing framerates - like live action and CGI in any Star Trek Show - you just havenât lived (long enough).
Framerates always need to be Same As Source - or ur askinâ for it.
Umm Juice, thatâs incorrect⊠Any source that came from Film is shot at 23.976 fps, not 29.976, all DVDâs are Telecined to be 29.976, which means they have 6 additional frames every second of film, when you âDe-Telecineâ something (using a proper 3-2 pull down) youâre restoring it to its original state. The only place this doesnât work or make sense is when itâs Made for TV stuff or shot on vhs stuff, because some of that was shot at 29.976, but for the most part, 95+% of media is SUPPOSED to be 23.976 fps. Setting it at 23.976 in Handbrake performs a 3-2 Pull down from a 29.976 DVD source ;-). Handbrake is actually supposed to do this on its own, however, sometimes it has issues detecting that it was an original film source and leaves it at 29.976 with the extra frames that are garbage. This is why I have chosen to just set it manually, and anything that I know for sure wasnât film (some older TV shows and some low budget tv shows) I put it back to original, but that is rare⊠I think I have maybe 100 or so DVD Source titles, maybe lessâŠ
Also, no source ever should be âVariable Framerateâ Thatâs a sign of some pirated content
it is definitely an issue with some older shows on dvd like star trek, x-files, etc.
the source dvd has mixed framerates.
a specific example I remember is my old x-files dvds, the intro is at one frame rate, the rest of the show is mostly in the other framerate.
Pretty sure even X-Files is 23.976, Star Trek is likely a 29.976 source, but all of my X-Files BluRays are definitely 23.976⊠I donât have the DVDs to check against though, soâŠ
yes, it is generally a dvd specific problem.
most bluray releases tend to be cropped and framerate corrected