Log in

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


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 [420] 421 422 423 424 425 426 427 428 429

GZZ
23rd November 2024, 17:23
Whats more interesting is the power usage. Might be a fast CPU, but if it uses 3 times the power to complete the task, only 1 hour ealier, then it might not be the best CPU. Except if you have free power or dont care. I think the 7900 (non-x) (not on the above list) to be the sweet-spot, I think it will place itself between the 7700x and 7900x and properly closer to the 7900x, but at a much lower wattage.

Emulgator
23rd November 2024, 18:29
rlev, since you seem to have the most diverse collection of servers to choose from, would you mind enhancing your list by the CPU TDP or even better: real wattage ?
This would help comparing some pJ/cycles.
(Note to self: BTW, TDP I can do myself.)

rlev11
23rd November 2024, 23:13
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

Emulgator
24th November 2024, 11:29
Thanks, rlev!
This is enlightening for everyone choosing a new encoding CPU.

Ryushin
24th November 2024, 14:33
Why ??, doesn't that hinder performance ??

I don't use that setting on any of mine.

When I got my 7950X, I ended up under clocking mine. I found that for that extra 5% encoding boost to get to 100% it required twice the power. So my encoding speed is 95% of what the CPU is capable of all the while using half the power and staying under 70 Celsius while encoding 4K. Not bad to extend the life of the processor and use less power.

I have 40 kWh of battery storage for my solar system and I can keep encoding through the night just fine this way.

rlev11
24th November 2024, 17:50
When I got my 7950X, I ended up under clocking mine. I found that for that extra 5% encoding boost to get to 100% it required twice the power. So my encoding speed is 95% of what the CPU is capable of all the while using half the power and staying under 70 Celsius while encoding 4K. Not bad to extend the life of the processor and use less power.

I have 40 kWh of battery storage for my solar system and I can keep encoding through the night just fine this way.

Back when I first got my 5950x and before I put a NH-d15 cooler on it, what I did was just in the windows power plan was change max processor from 100% to 99%. What this did was disable the cpu from going into it's boost clock speeds and just run at the base speed. Don't remember exactly how much, but this dropped the output wattage by quite a bit, and like you, only noticed a slight drop in performance. This might be a quick way to test other than changing the bios to eco mode. Back then I made a powerplan desktop shortcuts that let me switch between 100% and 99% on the fly for when I was encoding. Might be something I look into again just to see with the whole farm encoding how much performance drop I really see now.

In fact yesterday I tried setting eco mode using ryzen master as a test and ended up having to pull the cmos battery and rest the bios after ryzen master rebooted and nothing came up. Screwed it all up, so I gave up on that idea.

Wishbringer
25th November 2024, 09:15
For example:
5950X with 99% Powerplan = 3.4 Ghz for all cores (Stock clock)
5950X with 100% Powerplan = 4.25 GHz for all cores (value is different for each processor)
So you get around 20% higher clock.
If power consumtion is 20% higher too, there is no implact on IPW, else lower clocks with much lower wattage have a higher IPW.
Encoding is slower but takes lower power (cheaper) overall.

In Bios there are settings for THM, TDC, EDC and PPT to play around.
And with curve optimizer you can reduce wattage too (or increase clock at stock wattage).
My core values differ from -17 to -24 with stable encoding.

Ryushin
26th November 2024, 13:59
Back when I first got my 5950x and before I put a NH-d15 cooler on it, what I did was just in the windows power plan was change max processor from 100% to 99%. What this did was disable the cpu from going into it's boost clock speeds and just run at the base speed. Don't remember exactly how much, but this dropped the output wattage by quite a bit, and like you, only noticed a slight drop in performance. This might be a quick way to test other than changing the bios to eco mode. Back then I made a powerplan desktop shortcuts that let me switch between 100% and 99% on the fly for when I was encoding. Might be something I look into again just to see with the whole farm encoding how much performance drop I really see now.

I was using Ryzen Master to make the change manually for a few weeks when the system was rebooted. After I was sure it was stable I manually changed it in the EFI/BIOS. I did not know Windows itself had the option to drop the speed of the processor. I'll need to look into that.

For example:
5950X with 99% Powerplan = 3.4 Ghz for all cores (Stock clock)
5950X with 100% Powerplan = 4.25 GHz for all cores (value is different for each processor)
So you get around 20% higher clock.
If power consumtion is 20% higher too, there is no implact on IPW, else lower clocks with much lower wattage have a higher IPW.
Encoding is slower but takes lower power (cheaper) overall.

In Bios there are settings for THM, TDC, EDC and PPT to play around.
And with curve optimizer you can reduce wattage too (or increase clock at stock wattage).
My core values differ from -17 to -24 with stable encoding.

At least for me, that last 5% performance boost literally consumed 100% more power. So for me it was worth it to under clock the processor.

chainring
26th November 2024, 18:20
Before setting the Windows Balanced power plan to 99% for the CPU max, my girlfriend would remark that the four machines participating in DE sounded like a vortex. They also pumped out quite a bit of heat. Now, they're silent, cooler and still get plenty of FPS.

stryker412
27th November 2024, 20:34
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

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.

rlev11
27th November 2024, 21:08
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
27th November 2024, 21:22
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
29th November 2024, 16:24
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
2nd December 2024, 13:22
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
5th December 2024, 12:59
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
5th December 2024, 14:39
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
5th December 2024, 18:18
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
5th December 2024, 19:28
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
5th December 2024, 20:49
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
5th December 2024, 22:32
ah ok... sorry, I canīt help then.

bar72
7th December 2024, 08:31
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
7th December 2024, 19:58
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/d/1w2N0-Kw3Lni3Tkmud-ViwluzUf7KuSJr/edit?gid=983798900#gid=983798900

supersnakeyez
8th December 2024, 00:44
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
8th December 2024, 21:30
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
9th December 2024, 11:11
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
10th December 2024, 00:20
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
10th December 2024, 03:34
"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
10th December 2024, 19:35
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
14th December 2024, 02:40
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
14th December 2024, 02:59
tds..

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

jimbobub
14th December 2024, 19:17
Originally Posted by Atak_Snajpera View Post
Try this for now...
1) Add --colorprim bt709 --transfer bt709 --colormatrix bt709 to your encoding profile
2) Download ColorMatrix Plugin https://www.mediafire.com/file/aj88v...trix26.7z/file
3) extract to Tools\AviSynth plugins folder
4) Add following lines to your script under #ColorSpace

I am unable to find where #colorspace is located. I was able to do everything else. I'm trying to properly convert bt.601 to bt.709. Thanks.

jimbobub
14th December 2024, 19:40
I forgot to add that I am converting home videos from dvds to 1280x720 avc to play on a bluray player viewing on a tv. Do I need to change the level to tv or is the limited color range accounted for already? Thanks.

rlev11
14th December 2024, 20:44
Originally Posted by Atak_Snajpera View Post
Try this for now...
1) Add --colorprim bt709 --transfer bt709 --colormatrix bt709 to your encoding profile
2) Download ColorMatrix Plugin https://www.mediafire.com/file/aj88v...trix26.7z/file
3) extract to Tools\AviSynth plugins folder
4) Add following lines to your script under #ColorSpace

I am unable to find where #colorspace is located. I was able to do everything else. I'm trying to properly convert bt.601 to bt.709. Thanks.

After you load the video, click the AviSynth button. Then on the right side click Edit Script.
#ColorSpace is located near the bottom under the video tab

jimbobub
14th December 2024, 22:17
I get the error:
Cannot load file 'C:/Ripbot264/Tools/AviSynth plugins/ColorMatrix26/ColorMatrix64.dll' Platform returned code 126: The specified module could not be found.

From the directory listed above, ColorMatrix64.dll was in there. I even tried:
video=ColorMatrix(video,mode="Rec.601->Rec.709")

I got an error still.

chainring
14th December 2024, 23:44
I'm still here, smart arse, I just don't post on this thread anymore !!!

Oh, look, it's TDS, FTLOY, Retired@55 and Pauly Dunne. Please, take your multiple personas elsewhere. Preferably, a therapist.

jimbobub
15th December 2024, 00:45
I'm making some progress. The error was the path to colormatrix64.dll. I'm using preview to test first. The video now comes up in preview and plays but there is no audio as before using the color matrix script.

tebasuna51
15th December 2024, 10:06
BTW, what's wrong with having different usernames ??

Because the forum rules:

14) Multiple registrations are prohibited and are grounds for immediate account deletion.

If the chainring post is true please select the account you want preserve and the others will deleted.

rlev11
15th December 2024, 16:33
I'm making some progress. The error was the path to colormatrix64.dll. I'm using preview to test first. The video now comes up in preview and plays but there is no audio as before using the color matrix script.

I know it is a couple extra steps, but you could just use mkvtoolnix to extract the audio, then do your ripbot encode even if the audio has issues, and then add the audio back in again.
If you only need to do this to a couple videos, probably less time than trying to figure it out

jimbobub
15th December 2024, 16:43
Thanks for your response. I don't mind demuxing, processing and remuxing if need be. When converting from bt601 to bt709, will ripbot try to match the saturation, brightness, contrast ect? Thanks.

rlev11
15th December 2024, 17:11
Thanks for your response. I don't mind demuxing, processing and remuxing if need be. When converting from bt601 to bt709, will ripbot try to match the saturation, brightness, contrast ect? Thanks.

Can't help with that as I have never had to do that type of conversion. Hopefully someone who has or knows will chime in.
I would just create a short, say 5 minute clip that you can encode quickly, and just start doing some testing and see what happens to the video and the colors.

Ryushin
22nd December 2024, 17:53
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.



Rlev11, I like the spreadsheet. It also confirms what I've seen. I can't believe how much more energy it takes to get that last 5-10% performance out of the processor.

Ryushin
23rd December 2024, 14:07
Thanks for your response. I don't mind demuxing, processing and remuxing if need be. When converting from bt601 to bt709, will ripbot try to match the saturation, brightness, contrast ect? Thanks.

Did you ever get colormatrix working? I spent a few hours on it and could not get it to work. Though, I'm trying to go from Rec.709 to Rec.2020.

I've been doing a lot of 4K upscales from HD. My workflow right now is running the video through Handbrake at CQ8 to convert my video to BT2020 before adding it to Ripbot.

Atak, when get the bug to work in RB, can you add color space conversions for 601 to 709 and 709 to 2020.

It would also be fantastic to see SMDegrain added to RB. Possible with these settings:
Light: Video=SMDegrain(video,tr=2,thSAD=200,thSADC=100,contrasharp=true,prefilter=0,refinemotion=true)
Medium: Video=SMDegrain(video,tr=4,thSAD=400,thSADC=200,contrasharp=true,prefilter=1,refinemotion=true)
Heavy: Video=SMDegrain(video,tr=8,thSAD=800,thSADC=400,contrasharp=true,prefilter=2,refinemotion=true)

These are the three I use. I mostly use Medium and Heavy though.

I have not used MDegrain at all since switching to SMDegrain. The results of SMDegrain are so much better.

Thanks Atak.

guest
23rd December 2024, 14:28
Did you ever get colormatrix working? I spent a few hours on it and could not get it to work. Though, I'm trying to go from Rec.709 to Rec.2020.

I've been doing a lot of 4K upscales from HD. My workflow right now is running the video through Handbrake at CQ8 to convert my video to BT2020 before adding it to Ripbot.

Atak, when get the bug to work in RB, can you add color space conversions for 601 to 709 and 709 to 2020.

It would also be fantastic to see SMDegrain added to RB. Possible with these settings:
Light: Video=SMDegrain(video,tr=2,thSAD=200,thSADC=100,contrasharp=true,prefilter=0,refinemotion=true)
Medium: Video=SMDegrain(video,tr=4,thSAD=400,thSADC=200,contrasharp=true,prefilter=1,refinemotion=true)
Heavy: Video=SMDegrain(video,tr=8,thSAD=800,thSADC=400,contrasharp=true,prefilter=2,refinemotion=true)

These are the three I use. I mostly use Medium and Heavy though.

I have not used MDegrain at all since switching to SMDegrain. The results of SMDegrain are so much better.

Thanks Atak.

I cannot believe you're still asking Atak to add SMDegrain to RipBot, you need to realize that he will NEVER add it !!!!

He built RipBot exclusively for his own use, and he has no interest in what other's want, unless he sees some personal benefit, and he can be very rude, as well, not to mention stubborn.

You have Pauly Dunne to thank for SMDegrain in RipBot, and now he's been banned, along with TDS, and shortly, I will be gone too.

Good luck, you'll need it.

Ryushin
24th December 2024, 16:14
I cannot believe you're still asking Atak to add SMDegrain to RipBot, you need to realize that he will NEVER add it !!!!

He built RipBot exclusively for his own use, and he has no interest in what other's want, unless he sees some personal benefit, and he can be very rude, as well, not to mention stubborn.

You have Pauly Dunne to thank for SMDegrain in RipBot, and now he's been banned, along with TDS, and shortly, I will be gone too.

Good luck, you'll need it.

For sure you got me to go down the path of learning SMDegrain and once I found the right options, the results were so much better then what I thought was possible. So I very much appreciate your efforts to bring SMDegrain to RB.

If you decide to no longer make a SMDegrain add on pack for RB, I'll create a light version that uses uses all of RB's stock components and just add the few files needed to add SMDegrain with the settings I use with with just the CPU. SMDegrain is just too good to not use it and other should have the ability to quickly use it. Once Atak adds SMDegrain, then I will stop having to do it.

Atak still adds features to RB in addition to fixing bugs. He is still supporting it. I greatly appreciate his efforts and have been relying on it since the early days. He has a life though, so I'm patient.

guest
25th December 2024, 01:30
For sure you got me to go down the path of learning SMDegrain and once I found the right options, the results were so much better then what I thought was possible. So I very much appreciate your efforts to bring SMDegrain to RB.

If you decide to no longer make a SMDegrain add on pack for RB, I'll create a light version that uses uses all of RB's stock components and just add the few files needed to add SMDegrain with the settings I use with with just the CPU. SMDegrain is just too good to not use it and other should have the ability to quickly use it. Once Atak adds SMDegrain, then I will stop having to do it.

Atak still adds features to RB in addition to fixing bugs. He is still supporting it. I greatly appreciate his efforts and have been relying on it since the early days. He has a life though, so I'm patient.

Ooooooooooh, I can feel that knife again.
Yeah, you go right ahead and release a Lite version of all my hard work, but don't you dare call it PD anything !!!
The last time you did this, you got credited, ironically, by the same prick that just threw me under the bus.
You know, I used to have a LOT of respect for you, but now it's less than zero.
And to be so naïve to think Atak is going to add SMDegrain to his little pet project, he's had years to do something, and it's so easy,
and what's he done.....NOTHING !!!!
Sure I will still keep developing it, but for my own use.
It's not safe & secure here on the Forum anymore, if I created a new username & account, how long would it be before the same guy, or other's, throw me back under the bus.
It's not worth it, and I certainly can do without the drama.
So once I've had this account deleted, you're on your own.
Way too many ungrateful ppl here.

Ryushin
25th December 2024, 15:57
Ooooooooooh, I can feel that knife again.
Yeah, you go right ahead and release a Lite version of all my hard work, but don't you dare call it PD anything !!!
The last time you did this, you got credited, ironically, by the same prick that just threw me under the bus.
You know, I used to have a LOT of respect for you, but now it's less than zero.
And to be so naïve to think Atak is going to add SMDegrain to his little pet project, he's had years to do something, and it's so easy,
and what's he done.....NOTHING !!!!
Sure I will still keep developing it, but for my own use.
It's not safe & secure here on the Forum anymore, if I created a new username & account, how long would it be before the same guy, or other's, throw me back under the bus.
It's not worth it, and I certainly can do without the drama.
So once I've had this account deleted, you're on your own.
Way too many ungrateful ppl here.

There is no knife here. I said I very much appreciate your efforts and work and you got me to started using SMDegrain. There was only praise there. In fact, I've always been very kind to you and valued your contributions.

You have done a lot of hard work pushing the boundaries of RB. You've explored many different avenues. Your PD releases showed off all your hard work. But not everyone wants to use a version that is outside of the official RB along with updates from Atak.

Adding basic SMDegrain support is just dozen files or so slip streamed into the official build and you're done. So that is where the Lite version came from. I actually encouraged you to create a stripped down SMDegrate Lite version of your PD build.

You did bring SMDegrain main stream to RB. Others were actually using SMDegrain for years before with RB, but I never went down that road because MDegrain produced good results and when I have something that works, I tend to stick with it unless I see a problem with it. You encouraged me to try SMDegrain and when I went down that rabbit hole, I found out what it could truly do and I was astounded. I posted praise for your work and asked Atak to include it in RB since it's such an improvement.

So you see, I have no malicious towards you. Pretty much only praise.

Atak is the creator of RB. It's Atak's hard work that we are all here. It's Atak's love for the project that keeps it going. I'm only grateful to Atak for keeping RB working and improving on it when he has time.

Oh, and Merry Christmas all. Have a most wonderful day.

dipais
27th December 2024, 19:36
Hello Atak Snajpera

I get the following error: https://imgbox.com/C0BK8Yoo, right after clicking "Preview Script". I haven't changed any settings, everything is using your default settings. A sample video can be downloaded at: https://pixeldrain.com/u/8kwFgutm. The video info is below:

Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 min 4 s
Bit rate mode : Constant
Bit rate : 8755 kb/s
Nominal bit rate : 10000 kb/s
Width : 1920 pixels
Height : 1040 pixels
Display aspect ratio : 1.85:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.183

Cheers,
D

dipais
27th December 2024, 20:01
Hello, All

You have Pauly Dunne to thank for SMDegrain in RipBot, and now he's been banned, along with TDS, and shortly, I will be gone too.

If you decide to no longer make a SMDegrain add on pack for RB, I'll create a light version that uses uses all of RB's stock components and just add the few files needed to add SMDegrain with the settings I use with with just the CPU. SMDegrain is just too good to not use it and other should have the ability to quickly use it. Once Atak adds SMDegrain, then I will stop having to do it.

Would you like to share the SMDegrain script that works in RB?. I want to try it. Thank you a lot.

Cheers,
D

rlev11
27th December 2024, 21:27
Hello Atak Snajpera

I get the following error: https://imgbox.com/C0BK8Yoo, right after clicking "Preview Script". I haven't changed any settings, everything is using your default settings. A sample video can be downloaded at: https://pixeldrain.com/u/8kwFgutm. The video info is below:

Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 min 4 s
Bit rate mode : Constant
Bit rate : 8755 kb/s
Nominal bit rate : 10000 kb/s
Width : 1920 pixels
Height : 1040 pixels
Display aspect ratio : 1.85:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.183

Cheers,
D


Was able to load the clip you provided and had no issues with the preview or even encoding it.

Are you able to run the encoding job without error, or is it just an issue with the preview in MPC player?

Ryushin
27th December 2024, 22:22
Hello, All

Would you like to share the SMDegrain script that works in RB?. I want to try it. Thank you a lot.

Cheers,
D

I'll have something for you probably in a couple of days. Doing some testing right now.