Search the Community

Hello 2024, This is a pretty mundane question, I have been looking to use handbrake to compress 18tb of film and tv shows ¬_¬ (a life well lived) I have attached the handbrake settings I have settled on and before I go ahead and start the encode to end all encodes I wanted to make sure I'm not going to ruin the quality of my films and shows. TBH these settings have served me well and I can barley tell a difference between the source and the output but one film (Elysium) had a sweeping landscape shot in the opening scene with hills and buildings and in the source material there was no stutter but in the output file this scene had a very slight consistent micro stutter as the camera pans over the terrain and I started doubting myself. I am most concerned with keeping image quality and a decent chunk of space saving. Should I be converting to mp4 instead of mkv?, h264,h265? av1?! I don't understand any of these much in terms of the differences in quality between them. Anyway please let me know what your handbrake settings are and share some knowledge. Tagged some people I have seen mention handbrake @Crunchy Dragon @jaslion Thankings

Does anyone know how to Encode just audio to the AAC codec using HandBrake? Would appreciate a guide/how-to considering I haven't used HandBrake very often. If there's any piece of software out there that will do a better job, just let me know! As always, don't forget your questions if you have any for me or need more details. Thanks in advance to anyone who can help! :)

I have been using an old Dell workstation PC with an i7 2600 quad-core for transcoding my bluray rips for the last several years in Handrake. It's been a good machine for that purpose. I don't need the fastest encodes out there necessarily. I've always been more concerned with the output file results. I want the best quality I can get at the smallest file size. I watched a video a few minutes ago of a handbrake test a guy did with his Ryzen 3900x 12 core machine. His results blew me away in terms of speed. His PC took about an hour and a half for a single bluray movie to be encoded with the x264 encoder and the high-quality 1080p/60fps preset that comes stock in Handbrake. I didn't believe that result at first, but then I remembered that he has 3 times the number of cores I do. So I get that there is a massive speed increase available for encodes on newer hardware. So the question I have now is will these modern processors produce a more efficiently compressed (smaller file size), or a better looking video given the same Handbrake encoder settings? I encode my bluray video rips (that I make myself) with the x265 encoder at constant quality set anywhere from 20 to 24 depending on the movie or show in question. I don't often use the filter settings. I never adjust aspect or crop. I know I'm using the software encoder that theoretically doesn't use hardware acceleration. Is this a crazy question? TLDR: I don't care about encoding speed that much. Will new CPU's produce better looking or smaller video files?

Hello everyone. Today, I will tackle a topic that seems to elude common forums such that if one needs all the information in one place, there usually isn't one. So - here is the 3 codecs explained in laymen's terms, and a few HandBrake settings that might be useful. H264: Released in 2003, replaced MPEG2, H263 and MPEG4 part 10. Pros: Really easy to run, has decent enough compression for use cases up to 1080p and was (at the time of release) more than twice as efficient as the older MPEG2 standard. It is also very quick to compress. Cons: Needs quite a bit of bitrate by today's standards to produce watchable content. Gets really blocky in lower bitrates, does not do well with color banding. For a 2 hour 1080p movie, a good H264 encode needs at least 10GB to produce good results. You'll usually see sizes upwards of 15GB though. H265 (8bit): Released in 2013, also known as High Efficiency Video Codec, or HEVC for short. It is a successor to all previously mentioned codecs. Pros: Much higher compression capability than H264, upwards of 2.5x smaller file sizes for equal quality compared to H264. Because of smaller size, it is suitable for use cases like 4K media and above. Cons: Needs dedicated hardware to run (all chips that came out in the last few years support it) and is quite a bit more expensive to compress resource wise. Compared to H264, same files with same settings will take upwards of 3 times longer to compress with single pass compression, and upwards of 5 times longer with dual pass compression. It still has some of that H264 color banding issues well. H265 (10bit): A version of H265. It's also known as H265 Main10, and it's known for its higher fidelity. Pros: Even better compression than H265 8bit without loosing quality, usually 5-7%. Does away with pretty much all color banding issues and masks video artifacts better in general. It is a clear step up from H265 8bit. Cons: 20-30% longer compression times compared to H265 8bit, Needs dedicated hardware to run. Anything from Kabylake (2016) onwards will run it natively. Rule of thumb: When compressing H264 video in HandBrake, you need 50% average bitrate for your H265 10bit encode to not loose any quality when compressing with a Medium preset and 2-pass encode. Arguably, videos will look even better since there will be no color banding artifacts (if original file had any). You can go as low as 35% original bitrate, but you will need a slower encoding preset, Slow-Slower. That will significantly elongate your compression times, more than 10 times longer than an equivalent H264 encode. In my experience, it's better to allow for a bit higher average bitrate. All that said, here's my preferred method. H265 10bit needs around 3000kbps avg. bitrate for a 1080p video at medium preset and 2-pass encode. That is 3mbps. I've done 2mbps runs and gotten excellent results as well. That means - if you have an H264 1080p video with 15mbps of data rate, you can get 90% of the quality with just 3mbps and H265 10bit. That said, a 15mbps 1080p H264 video is very high quality (in consumer terms), so I'd probably run the H265 10bit encoder at least at 5-7mbps to maintain it properly. If you have any questions, I'm here to answer them. For more in-depth info, click here: VP9 vs HEVC (h265) » Quantitative Quality Analysis | Bitmovin Something to look forward to in the future: Versatile Video Coding - Wikipedia A general comparison between h264 and H265 at different bitrates: H.264 vs H.265 comparison (1080p) - YouTube

Hi I occasionally use handbrake for NVENC encoding and I noticed my GPU (1080Ti) usage was pretty low. Looking at TaskManager I can see that the GPU Video Encode is pinned to 50% and my CPU (3900X) is hovering around 30-40% usage. Is there a way to derestrict or adjust the software to allow its encoding to use 100% of the NVENC chip on my GPU? It should be able to do it it's not bottlenecked by any of the other components.

So a ~16 minute video 4k 60fps, takes ~38 minutes to encode... is this normal for my cpu? (Seems mostly being used 90-100%) And it doesn't seem to matter what bitrate the videos are, 150000kbps takes roughly the same time as 30000kbps... doesn't make sense, to me at least... I'm using the preset called "vimeo youtube HQ 2160p60 4k" (because that gives best results) Idk... i just think that takes too long? Also if I set it to average bitrate, eg, 28000 it takes even longer (???) , even though the bitrate is actually *lower* compared to this preset which will generally generate around 50000 - 60000 kbps videos (and yes, i know that's theoretically too high, but quality wise it works well, and really the problem is if I lower the bitrate manually it takes "longer" roughly 1 hour for such a "16 minutes video") Seems kinda bugged? Edit: actually 60000 seems fine (not sure about the conversion)? But, I uploaded some videos with lower bitrate (around half that) and that actually looked fine, problem is it takes even longer to encode (for whatever reason)

Hello everyone, My cpu is 11800H and under handbrake the faster the encoding mode ( medium, slow) the lower my cpu goes under load. In slow preset my cpu load hovers around 80 and in medium it won't go higher than 60. And one particular thing I noticed is that when the cpu load is low cpu frq constantly jumps between highest point and lowest. Can it be the results of a ram bottleneck? I have 32GB of 2666mhz dual channel micron E die memory. (It's r1x8) I know there isn't but my info is years old so I'll ask: Is there any test that can show if a ram is the bottleneck or not?

As the 1080p videos from my phone and camera are bloated, running them through handbrake removes the metadata, so I have to use ffmpeg with "-map_metadata 0". These are my video settings on handbrake - Nvidia NVNC HEVC h265, CQR 30, Slow preset. Not sure how much rc-lookahead is affecting the video size, and I don't know what the right command for ffmpeg is. Everything else is passthrough'd. I got the .bat script from EposVox's github which I edited a bit, full code listed at the bottom. I just want to mirror all settings in handbrake to ffmpeg. The video quality, as I tested using vmaf are slightly worse than the handbrake's encode, and are always smaller. Although I don't see the difference quite as much without pixel peeping, I only tested with smaller videos. ffmpeg -hwaccel auto -i "%%A" -map 0:v -map 0:a -map_metadata 0 -c:v hevc_nvenc -preset slow -rc constqp -qp %ffmpeg_qv% -b:v 0K -c:a aac -b:a 384k -movflags +faststart -movflags use_metadata_tags "%%A_compressed.mp4" pushd "%2" ::Default variables SET paths=paths.txt ::paths lets you put a bunch of folder paths in a text file and run this across those, instead of individually. I use this to run overnight on a LOT of footage folders at once. Thanks to Aayla for a lot of these upgrades ::Fun tip - select your folders (15 max at a time) and shift+right-click and click "copy as paths" SET /A ffmpeg_qv=30 ::change CQP value here so you only have to type it once. 22 is lossless for HEVC. ::for /R %%A in (*.mp4, *.avi, *.mov, *.wmv, *.ts, *.m2ts, *.mkv, *.mts) do ( :: echo Processing %%A :: ffmpeg -hwaccel auto -i "%%A" -pix_fmt p010le -map 0:v -map 0:a -c:v hevc_nvenc -rc constqp -qp 21 -b:v 0K -c:a libfdk_aac -vbr 5 -movflags +faststart "%%A~dnpA_CRF%ffmpeg_qv%_HEVC.mp4" :: echo Processed %%A ::) ::pause ::Test if the paths file exists and iterate through it if EXIST %paths% ( for /f "tokens=*" %%a in (%paths%) do ( echo Changing to directory %%a pushd "%%a" CALL :ffmpeg ) ) else ( ::It doesn't exist CALL :ffmpeg ) pause EXIT /B %ERRORLEVEL% ::Don't run the function when they're first defined because that's a thing Batch does for some reason??? :ffmpeg for /R %%A in (*.mp4, *.avi, *.mov, *.wmv, *.ts, *.m2ts, *.mkv, *.mts) do ( echo Processing "%%A" ffmpeg -hwaccel auto -i "%%A" -map 0:v -map 0:a -map_metadata 0 -c:v hevc_nvenc -preset slow -rc constqp -qp %ffmpeg_qv% -b:v 0K -c:a aac -b:a 384k -movflags +faststart -movflags use_metadata_tags "%%A_compressed.mp4" ::"-pix_fmt p010le" is setting it to 10-bit instead of 420 8-bit, which is what I had before (removed by me) :: "-map_metadata 0" copies all metadata from source file :: "-movflags +faststart" helps with audio streaming echo Processed %%A ) GOTO :EOF

Anyone ever seen a google doc or something that compares different handbrake encode times for different CPU's? I read handbrake benchmarks, but Anandtech and whoever else seem to set handbrake up with some random preset that just boosts FPS. They also never list what their video file is. I'd like to see a ton of CPU's encode the same video file. Like chapter 4 of an accessible bluray release of a well known movie. I currently use an i7-2600 and an i7-7700 to run my handbrake encodes, but I'd like to build a new system. Having some objective data to determine what's the best buy for my workload would be nice. Maybe if this doesn't exist yet we could start something like this. What movie and chapter would you suggest you think?

Hi everybody I'll explain my problem briefly: due to surging power bills here in Europe and the fact my current one is broken I wanna switch my Jellyfin/Emby media server to a Raspberry Pi. Unfortunately, new RBPis are sold out everywhere and so I'm stuck with an old one I have laying around (a B+ from 2014/2015). It's nice from a reduce/reuse prospective, but that board's SOC is of course old and slow, and won't support any kind of live trans-coding of video content. So i set myself up to convert my entire video library to formats which wouldn't need to be trans-coded by the server but could be played directly by the clients. The clients in question are a WebOS 5 TV (which thanks to LG's amazing OS fragmentation, will probably never get the Jellyfin app and that's why i'm also running Emby), various iOS and Android devices and several PCs (using the apps, I'm not interested in browser streaming). And here are my doubts (I'm kind of new to this all video trans-coding world). I would answer them by live testing the whole thing, but unfortunately my current media server is down for other issues and i would like to be certain of this strategy actually working before ripping out the Raspberry from its current use and setting up this new media server on it. MP4 H264 AAC 8bit seems like the safest bet, every sort of device seems to support it, but it's not as disk-space and bandwidth efficient as H265 and furthermore the latest version of Handbrake doesn't allow to take advantage of Nvidia's GPU NVENC encoder for it (i don't know why, after googling it out it seems that it used to be supported but that's no longer the case) meaning much longer trans-coding times (4 or 5 times as much, with my machine R5 3600 Quadro P4000). These factors are tempting me to go for H265, but while Jellyfin's forum has a table that would suggest that every device I use is compatible with H265, such information is nowhere to be found on Emby's blog/forum; my TV supports H265/HEVC but I came to understand (again not sure if true) that the app itself needs to be compatible with the format, it's not a given of the TV's hardware. Also, I've ended up in a Google rabbit hole of people saying that NVENC is garbage, that it destroys video quality and that shouldn't be used to re-encode stuff, others saying it's the greatest thing since sliced bread...I'm kind of confused honestly. The main question then is: can i get away with H265 given the compatibility doubts, and should NVENC be seriously considered (both for H264 and H265)? If you could help me, that would be much appreciated. Thanks everybody.

I have a 2600 OCd to 4GHz and i had never had any problems, but that was only with gaming, today i needed to use handbrake to convert a video and my cpu overheats and the system dies. I'm on a stock cooler, what should I do?

Hey guys, so I've been doing H264 encoding for a few days now. But I want to do H265 from now. My sources are usually Remux or very large sized BluRays. So I tried to do a H265 cpu encode (Remux source) using Very Slow preset, RF 22 & 2 Pass. So 1st pass went good, average 30 FPS. 2nd pass was terrible. Average 2 FPS. I guess the problem was with the Advance Option. You see when I do H264 encode I use this [trellis=0:me=umh:analyse=all:deblock=-3,-3:mbtree=0:psy-rd=1.0,0.00::aq-mode=3:aq-strength=1.0:ref=8388608/(resolution)] preset in advance option. It boosts my encode speed a lot. Without this I get only 10 FPS on Placebo H264 & with it I get around 30 FPS. So I'm looking for an advance option like that for H265, 2 Pass, Slow/Slower/Very Slow Preset. I'll be making 1080p BluRays. My RIG incase if you need: Cpu- Ryzen 7 3700X Ram- G.Skill TridentZ 16GB 3200MHz GPU- AMD RX 5700 XT SSD- Samsung NVMe 970 EVO Plus

Hello everyone. I have a weird problem with handbrake. Due the the quarantine, my university broadcasts the lessons via zoom. And I though it was a good idea to use OBS and record them for personal use, in case i want to go back and view something. But after a few weeks, the space taken by the video files started to be too much. So I though, why not transcode them to H265. Thats should help. So after a few practice runs on short videos to figure out the settings on handbrake, I was confident to get on transcoding the 50+h of uni lessons. Only one small problem. Only when selecting the H.265 (QSV) encoder, handbrake gives an error and cannot complete the transcode. Software H.265 (x265) plus hardware and software H.264 (x264 or QSV) work just fine. Also on my short practice runs, hardware H.265 worked fine. Only with the recorded uni lessons that I want to transcode it errors out. Im no expert in video formats and encoding/decoding although I study ECE so im quite familiar with how things work. I've attached one of the log files to see what kind of error it spits out. Its always the same qsv_hevc_make_header: MFXVideoENCODE_EncodeFrameAsync failed (-5) encqsvInit: qsv_hevc_make_header failed Failure to initialise thread 'Quick Sync Video encoder (Intel Media SDK)' If anyone has any idea what is causing it, I'd love to hear cause it seems to weird to work on most videos expect the one I really want to transcode. And to clarify, my PC is actually an Acer Aspire 15'' laptop (Intel Core i7-8550U / 20GB RAM / Nvidia MX150 25w). At first I though I'd use the NVENC on the MX150. And then I found out that it doesnt have the encode/decode IC... So Intel iGPU it is... Cause letting it do the software x265 transcode would be a death sentence for the laptop it self and my nerves cause I have to use it 10+h per day for uni and work. It has to be something that can be run relatively easily on the background. Thanks everyone in advance. Αριθμητική Ανάλυση Μ8 30.04.2020-1_preview.mp4 05-03-2020 22-57-58.txt

SOURCE Handbrake their official download for mac was infected with malware, verify your checksums. If you've downloaded handbrake between 2 may and 6 may you have a 50% chance of it having a trojan of the OSX.PROTON verity embedded. Updates trough integrated application update scripts are not affected since they don't install if the download doesn't pass the checksum, unless you ran a version from before v0.10.5. file: Handbrake.dmg SHA1: 0935a43ca90c6c419a49e4f8f1d75e68cd70b274 SHA256: 013623e5e50449bbdf6943549d8224a122aa6c42bd3300a1bd2b743b01ae6793 To quickly see if you're infected, check if you have a process called "Activity_agent". According to the handbrake team themselves its 100% indicative of if you're infected or not. What the malware actually tries to do is steal all your passwords, so you will have to change all passwords stored in your OSX keychain, and any other password storage if you want to be thorough. How do you remove this malware? It appears to be pretty easy, see the quote below. They also state that they will rebuild their download server completely from scratch so downloads will be slower and older versions of handbrake won't be available for download. This will cost time so there will be longer than expected downtime because of this, sounds like possibly something nasty is going on there server-side. Personally i think browser should get integrated checksum checkers already, with them being able to provide a url for where to fetch the checksum to the browser manufacturer so they can find it hassle free. Wouldn't make it 100% secure but its better than people not doing it because humans are lazy fucks. TL;DR quote:

i own a Samsung nx1 and it records in hevc h.265 but in order to edit it i need it to be standard h.264 i want to use handbrake but i dont know how to convert h.254 to h.264 please help!!

Hey all, for some reason handbrake isn't using 100% of my CPU while encoding. All 16 threads go up to 50-70% usage but never 100. Anyone know what could be the cause of this problem? Thanks!

Hey guys! I need some guidance with Handbrake if anyone feels capable... I want to use Handbrake to batch convert all my recordings from MTS to h.264 (MP4) but (open to other suggestins both on format and programs) and I need help with setting up handbrake to give me maximum quality, also is there a way to reveal the command line version of a preset, I have been looking into dropfolders to automate the process but it requires the CLI command as the standard preset it uses messes up the quality... I have looked into the CLI doc's but I guess im not smart enough to make sense of it... I use Premiere to edit my movies and for some reason it just removes the audio on the MTS files... even the adboe converter messes up this... so if anyone has an suggestion as to what to convert to, that is better than h.264 I am open to that to.. as long as premiere can handle it...

Hi, For some reason, my audio isn't been converted to other formats. E.g. AC3 passthrough from PCM or DTS. Have they change this feature or something? Cheers.

Hi, What's the better option for best quality for video. RF or Average bitrate? Also how is rf affected with h265 codecs? Cheers

hi, just wondering what would be the best formula for HVEC/H265 codecs. I've decided to do this so I can just use Direct play so I dont need to transcode every time. My smart tv only supports AC3/DD audio and i want to use the 5.1 channel audio. Also Ive encounted issues converting PCM to AAC in Handbrake. (terrible audio) cheers.

hi, Just wondering does it make a difference what file type a source file is. For example a m2ts file vs mkv An does it sometimes affect the output files video/audio? Cheers

Hi, I'm just wondering is the "Extra options" in handbrake the same like the " x264 encoder options" (In advanced tab) where you can insert code? Like the number of threads you want handbrake to use? e.g. threads=1 Cheers.

Hi, Just been doing some encoding and testing different setting etc. Just wanted to get some feedback on which codec looks better for visual quality. Both clips are from the intro of Marvels Avengers and are 48 seconds long. Same video bitrate of 12000mbps. I understand that h265 uses more cpu then h264 but from my testing it works just as well on the devices I wish to watch it on. So which one looks more appealing to the eye? H264 or H265 http://bit.ly/2wUrH6n (I didn't want to upload to youtube due to it will trans code the video) Cheers.

So I've been using my Ryzen 7 1700 system for exactly a month now (https://ca.pcpartpicker.com/list/K4hJhq) and I believe I've successfully overclocked the 1700 to 3.85gHz at 1.3v. I've run AIDA64 multiple times, anywhere from 5-30 minutes and the system is perfectly stable. I've played games at 1080p with not stutters, hangs or crashes, I've rendered video in Vegas with nothing strange to note and I've exported in DaVinci Resolve with the same results. As far as I can tell, the overclock is sound. However, for some strange reason video compression in Handbrake always leads in a system crash. The screen goes black and I have to reset the system. I'm trying to compress Vegas XAVC files to the internet 1080p 30fps setting at 20 on the quality slider on Handbrake and it never works. Any thoughts? I want to blame hardware, but literally everything other than Handbrake my hardware seems to be doing quite well so idk. Ryzen quirk? Handbrake issue? Love to hear back from everyone. Thanks a bunch ?.

So, the internet in my mind gives A LOT of conflicting and what seems like old, outdated and wrong info about the H.265 format. Everywhere I go the general consensus is to use H.264 because the former is not supported on all devices at this time however from my personal experience with my devices everything seems compatible? Also, I have read a few places that H.265 is a resource hog, using the CPU very heavily. However, aside from the encoding in Handbrake before hand to H.265 when the video is streaming over the network via Plex the CPU is at idle for the most part. Another thing to note; It seems my quality is higher and the file size is considerably lower, 8GB using H.264 and 5GB using H.265. So, my question is what is the problem with using H.265. I'm looking to get this lined out and hopefully get some factual info in this thread to help me and other people in the future, Thanks