- #Best handbrake settings for blu ray 1080p 480p#
- #Best handbrake settings for blu ray 1080p 1080p#
- #Best handbrake settings for blu ray 1080p pro#
On very bad sources I do have audio sync issues but I fix it by forcing DirectStream for Plex (this audio anomaly might be fixed by removing VBR but I don't have enough files like this to focus on fixing and I am getting too old to care).įile sizes are approximately 1Gb for an average runtime film at 480p settings & 3Gb at 1080p. I am able to DirectPlay to nearly every device including Roku, Xbox, Android, iOS, Amazon, TV's, tablets, and smartphones. I feel I have come across a configuration that meets all my needs.
I have several thousand encodes and I spent years tweaking settings.
#Best handbrake settings for blu ray 1080p 1080p#
I also have chosen not to store any compressed files above 1080p settings as I feel the visual differences are not worth what it takes to support 4k with Plex. I choose to run handbrake 0.9 as I prefer the settings GUI over 1.x but I use 1.x if I have a 4k source where I want to preserve HDR. I can explain why I chose each item and how I configured it to run at 8watts average but your question was related to handbrake settings so let me give you those. I run RAMDiskVE 12Gb virtual drive to host my Plex transcoding to spare writes on the SSD/HDD and extend my server life.
#Best handbrake settings for blu ray 1080p pro#
My current plex server is an ASUS H110I-PLUS D3 w/Intel i5 6500 & 16GB G.Skill DDR3 W7圆4 Pro on a Samsung 860 EVO 550GB and content on WD100EFAX-68LHPN0. My use case is to have a 24/7 server using >60watts running Plex 24/7 capable of 12 streams, 3 of them as transcodes. I have been encoding for many years and thought I would provide my settings that I chose to settle on. I agree with bobbster574, the settings are highly subjective. (I may have rambled a bit much about subtitles lol) Regarding other settings in general (quality/speed/etc.) That's dependent on how much space you have/want to use, and the video quality you want to have. Of course if you're never going to use a surround sound track, you can save some space due to a lower bitrate, especially if you're dealing with a lossless audio source. I ran a jellyfin server off a raspberry pi for a while and it could handle downmixing 7.1 and 5.1 audio tracks to 2.0 with ease (for reference, it could not transcode even SD video in real time). Regarding audio downmixing, it's not an intensive process. Of course you could go in and try and fix the errors and use another text based format like SSA/ASS which allows you to define fonts and positioning, but that requires a lot of time and effort to do. You could potentially use OCR to get SRT subtitles (which are more commonly supported) from the image based DVD/Blu-ray subs but it's not perfect, so you end up with errors, and you lose things like the font and positioning of the original subs, which at best loses some information and at worst you end up with the subs covering important onscreen info. If you're working with DVD/Blu-ray rips, they'll have image based subtitles, that won't be supported on most clients, so you'll either need to burn them in beforehand (which means you can't turn them off or have more than 1 subtitle option), or you'll need to transcode to burn them in as you play the file. But you can also run into limitations regarding subtitles. Obviously newer formats like h.265, VP9, and AV1 are more efficient, so you can have smaller files while maintaining a similar level of video quality (technically, you can direct stream these formats, but support may vary from client to client, and is less universal than h.264). However, limiting yourself to direct streaming can also be quite limiting. As these days it's compatible with damn near everything, so you can get away with direct streaming everything, meaning that you don't need to worry about server specs or usage as the CPU/GPU isn't really used. H.264 is often considered to be pretty good for Plex/emby/jellyfin/etc. The "best" settings for whatever situation are dependent on your use case and preferences.
0 kommentar(er)
