Handbrake cpu cores reddit. I think your best bet would be to do 2 videos at once.

Handbrake cpu cores reddit Members Online Orange-Fish1980 For BD H265 typically runs around 70% CPU for a single encode - this is with an all-core overclock - 16 cores/32 threads. With UHD content, I typically see >90% CPU utilization. Members Online Thinking of building a pc dedicated to handbrake cpu encoding If you're going to encode, you really need at least a dual-core laptop. I have a server with two 6-core processors. transcoding Plex / Handbrake so your VM and unRAID GUI don't grinds to a halt. I personally use CPU x265 - on slow or slower preset, it offers great compression, and is typically faster than AV1. About 125 fps for 720p. I built a PC several months ago, and for loads (mostly games), the CPU stays at a safe temperature (around 40°C - 55°C) and idles around 30°C - 35°C. numa-pools=+,- would limit it to the first of your two CPUs. Is this perhaps a limitation of the CPU governor/scheduler This is the unofficial subreddit for the handbrake video conversion software (handbrake. The hardware encoder is a dedicated encoding core that is separate to the GPU's graphics/compute cores and just happens to reside inside the same chip. I use a ryzen 7 with 8 cores/16 threads and most encodes get the CPU (close) to 100% in 1080p and higher resolution. In Process (GUI) encoding: Windows 10: Performance cores Only, but poor CPU utilisation Windows 11: All Performance Cores. It is easier on the CPU but the problem is that the resulting MP4 video is horrible! Did you check the single thread perormance of the two processors? Also try to restrict handbrake to use only 12 cores. Handbrake) can suffer under default Windows 11 operations. Using quicksync on an intel cpu or nvenc on a nvidia gpu would get you faster FPS, probably 20-25% more, but you're also likely to get a 50-100% increase in file sizes. AMD Ryzen 5 1600 Six-Core Processor Motherboard: B450M-HDV R4. 264 has its own command. Alternatively you can assign a different priority to each docker too. Usually falling back to StaxRip to convert lots of small clips to satiate the CPU. For instance, the SIP core(the part of the silicon that actually implements the encoder) in Intel hardware is identical across the entire generation. Providing all cores aren't saturated then running multiple encodes should lower time. Hey, I have recently got a new computer and I've noticed that for some reason, when I minimize handbrake or switch to another app, the output FPS cuts in half, my CPU usage and CPU temperature drops. If you're on windows 11 with a cpu with e-cores, handbrake will automatically saturate the ecores and stay off the p cores when it's not the uppermost window. This doesn't seem normal, especially since I have a decent cooling setup. This is correct in that if focus shifts away from the Handbrake GUI window, Handbrake is shifted to the E cores leaving the P cores completely unused and idle - very irritating. I only wish that I could queue up the merging* process in similar batch tools. handbrake is using those cores wide open to run encoding on the files indicated. I am using Handbrake ver 1. As of now I've been transcoding for an hour or so and the clocks are stable at 5. If I set the affinity on HandBrake to be all the odd numbered cores (i. With fewer CPU cores in the 5800x, you might not gain anything with simultaneous encodes. The highest I see are at around 85% and only a few of them. A single detelecine thread makes it go red (~75cwith 240mm aio). When I switch back to handbrake I immediately hear my CPU cooler kicking up and the FPS goes back up again. I think it was AV1 related. The unofficial but officially recognized Reddit community discussing the latest AMD 7000 has fast CPU cores for encoding, but also supports hardware accelerated HEVC 10bit encoding, like Intel QSV, but called AMD VCE. I have an I9-11900 so 8 core and 16 threads with 32gb of ram What is the best way to encode a lot of movie with . The main benefit of hardware encoding is it doesn't tie up the CPU or GPU, so it's good for screen recording or streaming while gaming. So I just bought the fully loaded m1 iMac (8 cpu cores, 8 gpu cores, 16 GB RAM). going from 4 cores/4 threads to 8 cores/16 threads should nearly quadruple CPU-bound performance More like double, maybe 2. With HD content, I typically get 50%-60% CPU utilization. MKV and MP4 are containers, converting between the two doesn't by default reduce size. My highest temp is 87°C and CPU power draw is about 160W. This is great for gaming with minimal performance loss. I get much better performance (faster encodes) with lower temps, power and core voltage using an all-core overclock versus the default PBO settings. Depends on your budget. Using the likes of x265 (the name for the open source HEVC CPU encoder)10bit will be much slower to encode as it uses the CPU cores, but provide far superior quality at the same file size, compared to AMD VCE I have a dual CPU Xeon (8 cores per CPU with HT) setup here with 64GB RAM. Upgrading your graphics card would do nothing to affect software encoding, and would improve hardware encoding only if the card you're upgrading to has a better hardware encoder in some way - as the GPU's general Hi all, whats the current general opinion/state of play when it comes to H265 encoding, especially for 4K video. It doesn't even mention the encoder used. 5fps with 4k, about 45 for 1080p. What i've read is that one instance caps the cpu core usage and you need multiple instances of handbrake or vidcoder or whatever. 0 Reducing the number of cores available for handbrake will reduce the temperature of the removed cores, but this also means that rest of the cores will do the work that was split. It's interesting to watch how software projects decide what hardware features to support. With a 5600X and Precision Boost Overdrive enabled on all cores, Handbrake can process a Blu-Ray movie in around 40 minutes. I have tried changing its priority and affinity in the Task Manager, but to no avail. If not then you need CPU encoding at the cost of speed This is how to test it yourself. I just started encoding Blu-ray movies and find that it takes my PC a lot longer to encode them compared to DVD. Even up to now most CPU in high end user's hands were 8 core only. 9 on all cores, but with an AVX offset of -3 which means when Support for more cores over 16 threads. I have two keys on mykeyboard set to show color coded cpu and gpu Temps. Though, a much better setup is a desktop with at least six CPU cores. Currently, CPUs have more and more cores and it could be useful to use them. And x265 scales even less than x264 due to some of the changes to improve encoding efficiency (quality for size). *0 + 1 = core #1 2 and 3 are core #2 4 + 5 are core #3, etc While encoding videos (usually 4k, h. I have currently set handbrake to run 2 encodes at the same time (using 6 cores each), and to me it looks like that increases utilization. The hardware you run on can have a large effect on performance. Handbrake doesn't seem like it scales that well to the full power of these high core count CPU's. 1. Anecdotally, SVT-AV1 is able to fairly efficiently use about 16 processor cores when encoding 1080p video on a preset in the 4-6 range using the default configuration. My theory is still: Twelve cores, 24 virtual cores, two handbrake instances, ergo each handbrake as 6 physical/12 virtual cores. GPU gives you better quality than CPU for the same speed CPU gives you more flexibility, GPU is fixed to a more limited speed and quality setting If GPU gives you a quality good enough, then it's simply faster. They really need to add a utilization slider. numa-pools=-,+ would limit it to the second of your two CPUs. In saying that, in Win11 I tried encoding 3 files simultaneously and noticed my temps were hitting 100C consistently and I didn't like that. pools=8 would limit handbrake to 8 threads. This switching takes a little bit of time. After I reniced handbrake to -19 and changed the CPU governor to "performance" according to KSysGuard ghb is using maybe 23% of my processor. If you want it cooler you may need better cpu cooling, but 90c by itself isnt "dangerous" because it will self throttle if needed to prevent damage I tried lowering priority and using processlasso to limit which effective cores the programs can work with, but didn't really make a difference. Or you can just limit the total number of threads. ) 8 copies of Handbrake each limited to a core. It is doing a good job at ~125 FPs, while using the CPU would be roughly a 1/4 of that in speed. Recently, handbrake has capped itself at about 60 percent usage of my CPU when transcoding, which annoys me. If Handbrake is sensed as background (ie. focusing on running concurrent containers to overcome the 6 CPU "limit" of handbrake When using Handbrake, there's a lot of CPU work to be done. I know Handbrake sees diminishing returns on 6+ CPU cores but haven't been able to find anything on RAM speed (3600mhz, 4000mhz, etc) and IF speed. Again though, I'm a noob here. Problem is it needs to be reset each time you open handbrake to the best of my knowledge. A big place where that can factor in to CPU usage Handbrake’s use of only CPU decode, and perhaps if an audio codec is being CPU limited. . eCores are the lower wattage (economic) cores and pCores are the high power cores you want your game or video editing software to use all the time. We have compilers for different architectures of CPU, so we can, for the most part, just recompile the code from x86 to ARM and get the same output, but to move the same algorithm from CPU to GPU, it would require a complete rearchatectureing. Audio transcoding, subtitles, stream encapsulation in containers, etc. 264 to NVENC to H. Windows 10: Efficiency Cores only Windows 11: All Cores, Reasonable CPU usage. 15 Catalina, Windows 10 1909)? Feb 7, 2022 · However I am using Handbrake in a virtual machine (Ubuntu LTS in VirtualBox) with access to 24 real CPU cores and access to 32 GB of memory. Yeah and now power limit the 5800x to the same values as 5700x and measure efficiency again. This is because x265 has to wait for the audio to catch up. I think the problem is just how many cores I have. I tried converting a WEBM format video file to MP4 using Video Toolbox (yes hardware encoding). a guide for using handbrake-cli within proxmox LXC containers, with a bash script to mostly automate batch converting multiple files. The GPU happens to include a hardware encoder on the same die as its multipurpose GPU cores, because why not, transistors are cheap, and it's a feature it can market. It is not as simple as just setting flags on the compiler. I am using Handbrake snapshot to get AV1 NVENC support. I was looking on Passmark at CPU benchmarks. View community ranking In the Top 10% of largest communities on Reddit. For a giggle, I thought I'd pin handbrake to 4 E-Cores to see how much slower they are. 22 and CPU core at 4. The hardware encoder does not use the GPU for encoding. Try setting affinity manually in task manager Jan 4, 2019 · Handbrake does like a lot of physical cores & threads - but OC freq also makes a big difference. After upgrading to a Corsair H115i RGB Platinum AIO 280mm radiator, the temps dropped to about 80-85 My understanding is that 6-8 cores is a "sweet spot" for HandBrake, with more cores being useful but not necessarily scaling highly. Threads may help with thermal and responsiveness if you have a lot of cores and it's hogging them all, and scale back the cores in use by the encode. I've ran various configurations with single and concurrent encodes on 3950X, 5950X and 7950X platforms with HD and UHD content - if I'm getting 75%+ CPU utilization, I stay at a single encode. I haven't upgraded in a while because of it. Wow, didn't know that. I discovered, as is well known, that there is a limit to how many threads Handbrake can utilise for h. More CPU cores. So, it shows 4 CPU cores. The 7980xe is not a terrible choice for 450 USD, but remember x299 is expensive, and cooling to get the most out of that volcano of a CPU is expensive (best would be a custom loop, at a minimum a NH d15 or 280mm aio), the 5950x is bad value, 5900x may be the best high end choice right now, for slightly less money the 10900k or 3900x is great as well, but with the prices you listed the 3900x is . Do you happen to know of any API's or control mechanisms I can poke to prevent it from doing dodgy scheduling of our encoding? You only need to limit threads if your PC is running hot and you want to limit CPU utilization. I've modified the shortcut to HandBrake so it'll launch with only using the odd numbered cores from now on. so its not using the hyperthreading capability), the cores its using ramps up to 100%. 265. If you use handbrake, though, it will use some CPU for the decode and/or filters. As far as CPU goes, I can say as far as 1080p h264 to h265 the 5900x can transcode nearly in realtime at CQ 22 on Slow and still have a bunch of available processor power. I've had 16 core cpus since the 3950x and am now on a 7950x. It's true that for x264 and x265 using frame-based multithreading there are diminishing returns above 6 cores, but it doesn't mean that you get no benefit from the extra cores/threads at all - and the CPUs with those high core counts can intelligently if diminishing returns of higher core counts are a concern, you can run multiple encodes at a time to get the cpu running at 100%. But this absolutely sucks for trying to do anything else on your computer while maintaining maximum fps in handbrake. Hey all, Currently, I have a Ryzen 2600 paired up with a GTX 1660 Super. I typically set 2 or 3 cores for HB conversion and also set 2 or 3 cores for Firefox browser use (I have a 6 core processor), this way things run pretty smoothly. It’s a relatively new feature in handbrake, and you can set it up in the settings. So I set up a Windows 7 machine with two CPUs and 7 GHz of power. It also talks about Intel QSV as if it's a good option. If you don't have a GPU to accelerate the encoding it can tak Both Quicksync and NVENC quality has been improved. The scaling isn't 100% above 6 cores, but with reasonable resolution material it will use way more than 6 (especially if you are using filtering). In the past, when transcoding Blu Ray rips, my CPU would be at near 100 percent utilization if I checked the task manager. Encoding to HEVC as you're doing can definitely take a while depending on hardware, source video, and encode settings. OK, so I have a 4080 ADA lovelace GPU with dual 8th generation NVENC chips, coupled to an AMD 7950x 16 core CPU. it takes longer, but it can store a better looking image with a lower bitrate. I use an 8GB RX 580 Sapphire Pulse, and it can transcode an x264 1080p 10 bit movie (from any source material) in ~19 minutes for a 90-minute movie. I think your best bet would be to do 2 videos at once. x265 is a software encoder (uses standard CPU cores), with the goal of reaching the maximum efficiency of the h. Would it be better to spawn two separate instances of HandBrake, both with Process Isolation and Max Encodes at 1, or to only use one instance of HandBrake with Process Isolation and Max Encodes set at 2? The first computer has a Quad Core Xeon E5-1620 v3 3. Multi-thread tasks (ie. So in the case of high core CPUs the general consensus is to do two encodes at once, so you're more efficiently using the entire processor per unit of time, and there's no way you'd be devoting "too many" threads to a single encode. In my case, I’m using a quad-core CPU with no hyper-threading. ) Don't forget if Handbrake isn't using all your CPU cores, you can run multiple instances of Handbrake at once. Sep 27, 2024 · x265 is a specific software encoder for H. It's in that sweet spot where you are above 8 cores but not wasting it at 16. On the rig below, right now i'm at 4. More cores is definitely the answer here, but if youre going to use a 12 or 16 core, make sure that you have enough ram to keep it fed. As I recall, the clock is also separate from the main CPU core, so even in faster CPUs, the QuickSync performance ends up being identical across a generation much of the time. There can even be slowdowns from many programs trying to access the same hardware. I am converting a 4K HDR WEBM clip to MP4 4K ultra quality. Handbrake does push some of the encoding to the Apple GPU cores when you select Video Toolbox but it still heavily uses the CPU cores too. ) 1 instance of Handbrake, with a large queue and full processor usage 2. Do your own tests, maybe start with a preset 3 or 4, that should utilize more cores Preset 0 seems very overkill for 99. So a 4 Core CPU can be nearly twice as fast as a Dual Core equivalent. This should reduce CPU utilization and thus temp as well. If you’re upgrading from an older laptop with a 5th-generation Core i7 Broadwell processor, for example, you can expect to see gains in the order of 70 percent during multi-threaded workloads, and potentially up to double the performance if you’re upgrading from a Core i5. 7. 3. 265 video, it has nothing to do with NVENC. Hi I'm using VideoToolbox to encode h264 video on my M1 Pro MacBook Pro. In order to be fair, the core does a bit of work for one thread, then takes note of the state of that work, then switches to another thread. When using high core-count systems, SVT-AV1's ability to fully utilize all available threads drops off and additional cores provide less incremental encoding speed. 6k) As a heads up, on a 16/32 core system, (and 1950x) encoding to hevc (h265) with audio copy I get about 4. This is a matter of confusion for many people, because people assume that since it came with their GPU that it uses their GPU cores. 3. Until then, learn to add core limiters to your presets. Right now, when I encode UHD 4K HDR files with HEVC/H265 using CPU, I'll usually average around 0. What is your hardware(how many cores do you have, and do you have multiple CPUs)? It's still going to try and use as much processor as possible though while not pre-empted. 10, macOS 10. PBO gives poor Handbrake results. 5ghz processor, 16 gb of ram, and a nividia quadro k620 graphics card The second computer is a laptop with a dual core intel i5-5200u 2. 265 encoding. handbrake and new 64 core server cpu. it’s no secret energy efficiency goes down when you let one cpu clock higher and closer to silicon’s limits(it’s 4050mhz vs 4550mhz all core clock freq in their handbrake benchmark…. But you're not running an encoder as shaders on your regular GPU cores, the actual logic of encoding is running on the hardware encoder that the GPU has integrated in it. In Windows 10, I couldn't even get Handbrake or Vidcoder to utilize all cores properly. It will run all cores of a CPU at 100% usage at full throttle. You could go into the task manager and change the affinity so it uses less CPU cores. 0)? What operating system and version are you running (e. With more cores you get diminishing returns, going from 8 to 12 cores will not add 50% speed. 2Ghz across pretty much all cores. I have a 3900X and it easily hits 95 degrees with the stock AMD Wraith Prism air cooler. GPUs can generally be split into multiple "engines" which perform different tasks, and may use different parts of the chip. Handbrake is one of the most stressful apps for a CPU. I'm not sure what they're basing that on. 5GHz and 100% utilisation, It can still be encoded twice as fast using a $300 GPU with < 5% CPU usage. It's quite common for CPU to be a bottleneck even in hardware assisted loads. Now for lower price you're getting 16 cores Some encoders don't scale well with cores, some do and Handbrake itself is just a GUI that has these encoders built in. The newer Ryzen chips are supposed to work a lot better when the RAM speed is a 'clean' ratio of the IF speed and I was wondering if anyone had any experience with this. Even with an i9 10980XE, encoding a 2 hour 4K video takes a day at a time on CPU at the slow preset. If CPU use is not a concern you get better encoding characteristics using a software encoder and it scales with your CPU power. Time to get the vacuum out & suck the dust out of the CPU fan! Or if already clean, upgrade cooler & check airflow. In my case I want two cores to be free so I’m deselecting CPU 2 and CPU 3 cores. fr), this sub is for information exchange and helping out, not affiliated with the developers. However, when I encode with Handbrake, the temperature on the VRM and several CPU cores reach 100°C even with all fans and CPU cooler at 100% speed. The more you parallelize a single video's encoding, the per core performance will be worse. That's what I do anyway. But for the sake of apples and apples comparisons, I've been pinning the CPU affinity of the worker process. Using H265 10-bit, particularly with slower presets, to encode 4K content scales pretty well to 16 cores/32 threads. I have a 6-core 12-thread i7-8700, and with all 12 threads at 4. Handbrake will run fastest if it can use all cores/threads. The double encodemakes the cpu orange. This would be fine except I find Windows 11 still tries to offload background tasks to the efficiency cores so I get system stutters if I am doing something else while the performance cores sit idle. If Handbrake slows down your PC, there is a setting to run it at a lower priority. HandBrake can scale well up to 6 CPU cores with diminishing returns thereafter. There are times when it doesn't use it fully but mostly if the resolution is lower than full hd and in combination with some filters. Pinning cores to dockers is not exactly required (most of the time). e. I noticed that all my CPU cores are firing up to max but my GPU is sitting around idle. Also, it will cool your CPU a bit, but also slow down your encode. It's only required for dockers that run heavy e. I have found AMD’s PBO to be problematic handling heavily multi-threaded tasks. Say you have 4 cores, then for example, you can set HB to use cores #2 & #3 (because the 1st core is Core #0); then you would want to "off-load" as much off of #2 & #3 that is not Handbrake, thus leaving as much of #2 & #3 for just HB to use. My questions: If there's a CPU with a score of 20k, is it twice as good at Handbrake as a CPU with a score of 10k? (The 2700 has a score of 15. Aren't most of the encoders lose in efficiency with a lot of threads or just can't use more than a set amount of cores? I was thinking of building a cheap used dual-CPU xeon set specifically to have a lot of cores, but then read some article discussing this topic and kinda scraped the idea. I have two main problems: Number 1 - getting Handbrake to address both NVENC chips. It's quality vs speed, with both GPU and CPU. Like pools=3 will limit activity to 3 cores for 265. You can tie a HB encode to specific cores, on dual CPU machines, I usually run two parallel encodes with one on each CPU. Feb 25, 2014 · What you are experiencing is normal. Causing increased cpu usage and temperatures or delaying the output if core usage is already maxed out. What version of HandBrake are you currently running (e. While on Linux, I don't see any cores running at 100%. No, it's not about Handbrake specifically, but CPU cores are not the same as CPU threads. I think handbrake is using every bit of computing power it can ask to the cpu, but the cpu has more than handbrake can make use of. ) more copies and limit it to individual threads I am converting a 4K HDR WEBM clip to MP4 4K ultra quality - at least that's what I am trying to do. At a pinch, you can set affinity to < all cores for the HB process, but that's just a band-aid. A processor core is something that performs work, whereas a thread is something that keeps track of the state of the work. A program has at least one thread. 3 and the Nightly version give rise to these problems The 6 cores in your example is relatively modest for contemporary CPUs; with 20+ core CPUs coming to the consumer space that advice doesn't hold that well. 265), all cores in my CPU stay at 100%, but also reaches 90°C, with certain cores and the VRM reaching 100°C. Doing the same w This is the unofficial subreddit for the handbrake video conversion software (handbrake. If I have an audio track that needs encoding using a single threaded process my average encode speeds can drop to below 100fps. My understanding is in this situation if a core is nearly maxed out at the hardware level it won't have time to run another thread. I think the 8 core CPUs with hyperthreading are worth it. The story is the same using Since I encode videos a lot, I was wondering what the best price per performant CPU would be. so yes its going to generate heat while running wide open. Handbrake isn't really designed for minimising CPU usage, as some of these tasks could be better optimised or even done in hardware in some cases if that were a priority That is a shame tbh. Reply reply nmkd On some newer Intel CPUs you have to decide if you want it to run on pCores or eCores. The 7900x of course would be even better. There are special stress testing tools. On my 16-core/32-thread CPU, Handbrake will use over half of the threads doing HD encodes in H264 or H265. Happened to me a couple of times. I make a series of presets then choose the one i want based on load vs speed vs room temperature: pools=1 pools=2 pools=3 pools=4 Note: there are tasks that stress your CPU more than handbrake. Or just use ffmpeg with a script to code 1 video per core, if you have a large number of files. 4 Two weeks ago I encoded a 4K file with undervolt already applied and I didn't have any problems, now I don't understand why both version 1. I read somewhere that handbrake doesn't scale well past 6 cores Wildly incorrect. I noticed that on Windows, handbrake will run at 100% on all CPU cores (including the HT ones). If you have windows 11 it might be using only e-cores because it sees handbrake as a background program. There are a couple of workarounds: Just keeping a portion of the Handbrake GUI visible will keep the P cores active. 4 (that natively runs on and supports Apple m1 - no Rosetta). , 1. I just wondered if the new Ryzen 7000 chips would have an advantage. no application windows are visible), then the application will be moved to E cores. hello, I have an epyc 64c CPU, and i am trying to do 5. However handbrake uses all CPU's it seems but it rarely comes above 50% of total CPU usage and not more than 14% memory usage. Ryzen 5 2600. I currently use Handbrake on a laptop with a quad core i7 processor. Unlike CPUs which use their general purpose cores for damn near everything, GPUs have a lot more specialised hardware. Edit: 1 video per core, not 12 HandBrake can scale well up to 6 CPU cores with diminishing returns thereafter. The light reading seems to suggest that Handbrake doesn't scale much beyond 6 cores (and I assume that means virtual/hyperthreaded) unless you can feed it faster. I had a Ryzen 7 1800X when I built my last PC (my current one has an i7-10700). Is 86C temperature when encoding using Handbrake using 100% CPU safe? These are readings according to Core Temp. , Ubuntu 19. Basically going from NVENC H. With my A750 paired with a 3900x, which has 12 cores, my CPU usage is still quite high (I forget exactly high but it's like 60% or Exact same problem I have a system with AMD Ryzen 7 3700x with undervolt at 1. Ryzen 2600->2700->3600->2700x->3700x->3900x. Since you're encoding through a work machine for work purposes, do you have the ability to use something that has a server CPU with more cores or something that has dual CPUs? Might be a ton faster. If the PC isn't doing anything else, it leaves the P cores at idle - obviously Handbrake performance suffers greatly. 265 format. The above action will open the Affinity settings window that shows all the CPU cores (both physical and logical cores). g. Supposedly the claim was that it was about Medium when compared to CPU encodes. Here, uncheck the CPU cores you want to be free. Eg. Your point is undermined by the fact you're using x265 settings that are unfavorable to the metrics (time, VMAF) and constraints (size) you're using for comparison; all you've demonstrated so far is that if you configure x265 poorly for your goals, you can get undesirable results. 8 FPS and this can end up meaning sometimes over a full 24 hours to take a source UHD disc down to a reasonable CF17 encode. What could happen is if both encodes are competing for resources of cpu core 0 and it can't keep up to feed the other cores. 265 ? Im looking at the following methods. But the GPU encoder is working about 96% and the CPU is roughly 70% (give or take 20%) across all 8 cores /16 threads. 5ghz and 8 gb of ram The weird result is, both computers encode the video at nearly identical speeds. It won't be a handbrake issue, it'll just be that handbrake is the only thing you normally run that uses all CPU cores for an extended time. The clockrate and IPC improvements get you the rest of the way to 3x. 25x with the extra threads, but nowhere near quadruple. ohhh I must have missed that changelog. But if you aren't constrained by speed or CPU usage, the software encoders in Handbrake will get you better quality per file size. So I am running a 12900K and Windows 11 and when the Handbrake isn't in the foreground it gets relegated to the efficiency cores only. 99 use cases For reference on my 8 cores 16 threads cpu, svt_av1 uses roughly 75-70% cpu at preset 4, it will rarely go beyond that point Well that's the thing - the CPU is still superior when it comes to quality and GPUs are designed to be much faster HOWEVER my understanding is that RTX 2000 series and up (including your 3060) have improved NVENC quality. lztxoc uzmht psyela pixtcr kden bqupog odnorj gdv gkkx jmsr