![]() ![]() Other codecs hardware performance loose out to software performance but AV1 hardware encoding outperformed software encoding by a substantial amount. It appears that hardware decoder in the Arc A380 is extremely well tuned for AV1, more so than for other codecs given its performance compared to software encoding of the same codec. AV1 is just the opposite with hardware encoding files being smaller than software AV1 encoding files. HandBrake, an advanced open-source transcoder, supports both software- and hardware- based encoding and decoding, accelerated by 12thGen IntelCore processors and Intel Arc Graphics solutions. Smallest hardware transcode to HEVC has larger files than software encoding of HEVC. Note that while software encoding HEVC is slightly faster than AV1 harware encoding power requirements drop drastically for very little difference in actual speed. One note is that you must have at least one filter active or AV1 transcode will stop almost immediately. You do have to go to preferences to activate hardware encoding. 4K to 4K AV1 transcode still faster than real-time at 39 FPS. Shrinking from 4K to 1080P is almost double real-time speed, about 44 FPS. Quality is still good even on fastest setting & files about same size as fastest software encoding HEVC & smaller than smallest software encoding AV1 all recorded at fastest speed. ![]() Takes a huge load off CPU & is quite fast on the fastest setting. Arc 380 AV1 hardware encoding does work on it as well. Worst case, I'll clear the CMOS/BIOS and start from scratch, but if anyone knows what's going on, I could use some enlightenment.I have latest nightly version & AV1 is present & accounted for. Have I screwed things up, or is this behavior normal? For one thing I thought the non-k version of the i5-2500 wasn't overclockable, so how come I can take it from 16 to 33? And why do I have to overclock it to 33 just to get it to run like it should?Īny help would be greatly appreciated. I've checked in the UEFI/BIOS and the OC section is set to "Auto", overclocking not "Enabled" in UEFI/BIOS. And I seem to have lost all TurboBoost, as the CPU sits at whatever the ASRock OC'ing utility has the CPU ratio set to. The blue bar is there at 3.3 GHz.īut I shouldn't have to overclock the utility to get back to 3.3 GHz, the i5-2500 is supposed to run at that by default, especially when Handbrake is pegging all four cores to 99.9%. So I eventually discovered that if I used the ASRock utility to bump up the CPU ratio to 33, the Intel monitoring utility looks normal again while encoding with Handbrake. Developed with the interests of developers that require a precise estimation of CPU power in mind, Intel Power Gadget is the official power usage monitoring utility for all Intel Core. Then I ran the 64-bit version of TMonitor, and it showed me a flat 1600 MHz across all four cores. Instead of the blue bar sitting at 3.3, it was gone. Except the Intel monitor utility showed nothing, no bar. So I bumped it up to 17 and everything seemed fine. Even though I'm not supposed to be able to overclock a non-k CPU.Īs I recall when I first ran the ASRock utility, my default CPU ratio was set to 16. So for some reason I decided to be stupid, and I ran the ASRock Extreme Tuning Utility, since I was encoding with Handbrake and thought I'd see if I could give it a little boost. Typically it shows 3.3 GHz (base) and every few seconds bumps up to 3.4 or 3.5 then back down again (the higher numbers are in a lighter shade of blue than the base 3.3 GHz). I had been running a utility I copied from one of my laptops, "Intel (R) Turbo Boost Technology Monitor 2.5", a little gadget that displays the instantaneous processor speed. I've got an ASRock H67M mobo with an i5-2500 CPU. On Intel Macs, if you wanted to know the stats about your CPU like clock, load, power usage and temps, there was a very handy tool called Intel Power Gadget, which listed all of this. ![]()
0 Comments
Leave a Reply. |