RipBot264 v1.18.3 - Simple and easy to use GUI -> IPOD . PSP . CONSOLES . BLURAY

[rlev11]

Originally Posted by stryker412

How do you think the 5700X or 5700X3D might do? I've had a few people suggest I just upgrade my 3700X to the 5700X and call it a day without having to do a full build.

Seeing how there is very little difference between the 3900x and 5900x, I doubt there would be much of a difference between the 3700x and 5700x in encoding performance. Remember encoding is based a lot on core and thread count, maybe a 5900x or a 5950x from the 3700x to get more cores. You will have to account for additional cooling though, either an aoi or a noctua d15, but that also brings into play the case on if it can handle an aio or the 165mm cooler height of the Noctua.

[rlev11]

Since we have been talking power usage lately, i found this that is interesting. Instead of changing the max cpu state in the power plan to 99%, leave that at 100%. then regedit here:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 and change "Attributes" (DWORD) and set to "2"

Now, there is a new setting on advanced power settings: (in the legacy control panel power options) "Processor performance boost mode". Set it to "Disabled" and cpu power drops considerably.
This works for both AMD and Intel CPU's and forces everything to run at the base clock speed (setting to 99% didn't do anything for me on my Intel systems)

Have found on my AMD boxes, there is little performance difference with a considerable power decrease. On the Intel systems, since they have a much lower base clock (larger spread from base to boost speed) it does hamper performance a bit more. On my i7-14700, disabling boost, dropped p-cores to 2gz and E-cores to 1500 mhz. but cpu power dropped from 175 watts to 35 watts. lost about 30-40% performance

Just something else to consider if looking at lowering power usage quickly without messing with BIOS settings.

If I get some time this weekend, I'll run some numbers comparing the same video/chunk for each machine both boost enabled/disabled and come up with a fps versus watts used and see where things shake out.

[Ryushin]

Originally Posted by Retired@55

Why do ppl buy multi core CPU's, then hobble them just to save some energy / money ??

Why not buy a lesser CPU, and run it at 100%, what's the point in having a 16C CPU, that is hobbled down to be equivalent to a 12C ??

The upgraded processor is able to process more FPS. Lowering the max speed by 5% results in processor that is more efficient for each clock cycle and more importantly, it will extend the life of the processor by not pushing it to thermal limits for days/weeks on end.

And as someone else said, their machines won't sound like a jet turbine just to gain another 5% performance at double the power usage and most likely killing the processor sooner then later.

[ReinerSchweinlin]

Originally Posted by rlev11

This is the total Package Power as reported by CPUID HWMonitor when each server is in the middle of a chunk of a 4k encode. Only thing i do on the Ryzens is set a Thermal Limit in the PBO section of the bios. I set the 9000 and 7000 series to 85c, and the 5000 and 3000 to 75c

First wattage is total package and second is core/ia core watts

9950x 20.02 200w, 146w
7950x 18.3 190w, 144w
7900x 17.37 170w 125w
7700x 11.26 128w, 95w
5950x 11.15 147w, 104w
5900x 9.07 148w, 95w
3950x 9.43 112w, 85w
3900x 9.78 130w, 101w
i7-14700 13.98 175w, 170w
i5-14500 12.44 133w, 130w
i5-13500 12.64 119w, 117w
i5-12600k 9.59 115w, 112w

Thanx, this is really helpfull. Without doing the math, at first glance the 7900x seems like a performance/watt winner.

[hardkhora]

Is there a way to force files shorter than 60 seconds to still be encoded distributively?
The problem I'm having is that my main RipBot controlling computer, which I don't usually encode with but like using as the central server, uses a iGPU (UHD 770).
Any video with KNLMeansCL used gets extra blurry/halos around the edges of things when encoding with the UHD 770, but with KNLMeansCL off or when I use any of my other computers with discrete GPUs I don't have that issue.
Example of the issue:
https://imgur.com/a/X09dQrh

[ReinerSchweinlin]

Originally Posted by hardkhora

Is there a way to force files shorter than 60 seconds to still be encoded distributively?
The problem I'm having is that my main RipBot controlling computer, which I don't usually encode with but like using as the central server, uses a iGPU (UHD 770).
Any video with KNLMeansCL used gets extra blurry/halos around the edges of things when encoding with the UHD 770, but with KNLMeansCL off or when I use any of my other computers with discrete GPUs I don't have that issue.
Example of the issue:
https://imgur.com/a/X09dQrh

do you really need nlmeans noise reduction on this footage? Looks fine to me.... I usually use CPU degrain on anime, rarely nlmeans does a better job.

[hardkhora]

Originally Posted by ReinerSchweinlin

do you really need nlmeans noise reduction on this footage? Looks fine to me.... I usually use CPU degrain on anime, rarely nlmeans does a better job.

I agree, I don't need it for that footage, that was to illustrate the problem.
I was trying to understand if there a way to force files shorter than 60 seconds to still be encoded distributively?

I also tried updating the iGPU driver and that didn't make a difference.

[ReinerSchweinlin]

Originally Posted by hardkhora

I agree, I don't need it for that footage, that was to illustrate the problem.
I was trying to understand if there a way to force files shorter than 60 seconds to still be encoded distributively?

I also tried updating the iGPU driver and that didn't make a difference.

hm, I just looked up the chunk size - guess you tried that too - and found 1 minute as the smallest chunk...
if you don´t run a encoding server on the master PC - shouldn´t it pass one chunk onto one of the network encoders? Have you tried that ?

[hardkhora]

Originally Posted by ReinerSchweinlin

hm, I just looked up the chunk size - guess you tried that too - and found 1 minute as the smallest chunk...
if you don´t run a encoding server on the master PC - shouldn´t it pass one chunk onto one of the network encoders? Have you tried that ?

When the file can't be chunked (is below 60 seconds), then the process bypasses the distributed encoding and encodes it locally via the main RipBot window (same as if you turned off distributed encoding all together). So, even if there is no encoding server it still acts locally.
I tried setting the chunk size to 0 but it still won't pass it to encoding servers as I'd expect.

[ReinerSchweinlin]

ah ok... sorry, I can´t help then.

[bar72]

Originally Posted by Retired@55

Why do ppl buy multi core CPU's, then hobble them just to save some energy / money ??

Why not buy a lesser CPU, and run it at 100%, what's the point in having a 16C CPU, that is hobbled down to be equivalent to a 12C ??

It's a bit like having a 2.0 litre over a 1.6 litre diesel engine in my car.

Doesn't have to work as hard to achieve sitting at the speed limit which puts less strain on engine overall.

[rlev11]

So I got a chance to do a full test for FPS and wattage on my entire encoding farm with cpu boost enabled and disabled. I did a separate run with a 4k source (3840x1600 light degraining) and a 1920x1080 source with heavy degraining just to see how they compare. The below link is for the spreadsheet with the results. Ran each run and got the fps from the distributed encoding window and for each cpu it was the same chunk number so that matches up. I also timed each run and saw about a 10-12% increase in total encoding time without boost, which is close to what the fps difference is. Saw about a 48% total drop in combined power usage.
So my math may be fuzzy on the end result, but it looks like it is much more cost efficient to run at least AMD processors with boost disabled since their spread is minimal. Just using my raw numbers, If an encode runs for 1 hour at full power, I would use appx 106380 total watts. If running with boost off and it takes 15% longer (69 minutes) I get 63135 total watts used for the same encode.

I am not advocating anything with this, just was curious of the difference and how it all fits together. And plus, as others have mentioned, your computers don't sound like a turboprop taking off.

https://docs.google.com/spreadsheets...#gid=983798900

[supersnakeyez]

I'm running RB 1.27.4 and for some reason every time I try to encode a movie from Netflix it encodes like normal but when played back on computer or portable hard drive the movie keeps skipping and looping which makes watching impossible. Only happens with Rb for some strange reason. Same file I encode with other software works fine.

[chainring]

Originally Posted by rlev11

I also timed each run and saw about a 10-12% increase in total encoding time without boost, which is close to what the fps difference is. Saw about a 48% total drop in combined power usage.

Almost half the power and only increasing encoding time up to 12%. That's an insane difference. Those of us who live where electricity isn't cheap, it's a seriously welcomed difference.

[dipais]

Originally Posted by Atak_Snajpera

check log. (right click on job and then SHOW LOG)

Hello Atak Snajpera

I see from the logs shown in mediainfo that RipBot has different default settings than the x265.

x265 default   : --ctu 64 --max-tu-size 32 --qg-size 32 --merange 57 --aq-mode 3
RipBot default : --ctu 16 --max-tu-size 16 --qg-size 16 --merange 9 --aq-mode 2

I really hope you can explain why you chose a different setting than the default x265. What is the impact?. What are the effects or what are the advantages and benefits that RipBot users can get with these settings?.

Cheers,
D

[supersnakeyez]

Originally Posted by Retired@55

Might need to upload a sample...

Are you using std RB or an old PD build, and what app did you use to have the encode work OK ??

I'm using latest stable version of ripbot and the program that works flawlessly is Handbrake. I've had to resort to handbrake ever since rb kept crapping out on my encodes.

[supersnakeyez]

Originally Posted by Retired@55

"Stable" version ???

I haven't been doing any encoding of late, and there has been a couple of updates to RB that I haven't tried yet,
but there were some problems with the build I was using, months ago, and I had to swap a few things around for it to work like it should (or should I say, "to my liking")....sadly.

Support of RipBot is sadly not what it used to be

I'll get back into it again, soon, no doubt.

So, the latest build of HB, 1.9.0 ??....never doubt good old Handbrake

Good luck.

yea HB has been working like a charm and gets updates regularly.

[Boulder]

I did a little power consumption test on a 5950X just for fun, using my chunked encoder to run an analysis step.

With PBO enabled and Curve Optimizer tweaked cores, the process took 1h 45min 47sec.
With stock multiplier and PBO disabled (i.e. all cores constantly at 3600 MHz), the process took 1h 50min 22sec.

The average power consumption of the whole PC with PBO enabled was 416,7 Watts and with stock clocks 361,8 Watts. These were measured using a Shelly smart plug with 5-second resolution stored to an SQL database.
So with about 5% loss in performance, a gain of close to 15% in energy efficiency which is quite nice if you for example don't have any excessive solar power to utilize here.

[chainring]

Originally Posted by Retired@55

Fortunately for some of us here, have "excessive solar power", and also some of us have batteries, as well, so it is of little interest or consequence.

Let them run @ 100%.

Neat. So don't comment, TDS.

[chainring]

Originally Posted by Retired@55

tds..

Yeah, your previous user name. What was the one before that? We all know.