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

[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.

[Retired@55]

Originally Posted by 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.

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 ??

[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

[Retired@55]

Originally Posted by dipais

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

FYI, x265 commands can be changed infinitum, I'd suggest that the x265 & RB defaults are just a "nice" starting point.

There are modded builds that allow even more commands than with std or RB variants.

see here :- https://x265.readthedocs.io/en/master/cli.html

[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.

[Retired@55]

Originally Posted by supersnakeyez

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.

"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.

[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.

[Retired@55]

Originally Posted by Boulder

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.

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%.

[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.

[TDS]

Originally Posted by chainring

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

I'm still here, smart arse, I just don't post on this thread anymore !!!

[jimbobub]

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]

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]

Originally Posted by jimbobub

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