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

[rlev11]

I've always set chunk size to 2 which seems to strike a good balance between not having each server spend time initializing each chunk too many times, and not having that last extra large chunk take forever by itself especially doing 4k.

[Atak_Snajpera]

I've always set chunk size to 2 which seems to strike a good balance between not having each server spend time initializing each chunk too many times, and not having that last extra large chunk take forever by itself especially doing 4k.

Have you done some benchmarks 1 vs 2 with the same video?
Yes you save some seconds at each chunk but at the same time you may waste some time at the end with last longer chunk.
It is hard to tell straight away if 2 is a good balance...

[cypher007]

IT is not a bug, IT is a feature.

https://i.postimg.cc/GhXFdPdX/Untitled-1.png

Make sure that unused IPs are set to 0.0.0.0 in settings

ill try that fix. i use 0 as i find if i encode two large chunks on two machines it gets a lot closer to the locked size i set on 2 pass.

[rlev11]

Have you done some benchmarks 1 vs 2 with the same video?
Yes you save some seconds at each chunk but at the same time you may waste some time at the end with last longer chunk.
It is hard to tell straight away if 2 is a good balance...

Even bench marking 2 different 1080p movies "It is hard to tell straight away if 2 is a good balance..."

Forbidden Planet chunk size 1- 8:32 with a 3900x doing the last chunk, and chunk size 2- 8:36 with a 7900x doing the last chunk.
So this made me think chunk size 1 should be a clear winner. Faster with a slower machine doing the last chunk.

Then I did North by Northwest. chunk size 1 - 12:23 with a 5900x doing last chunk and then chunk size 2 was 11:48 with the 7900x doing the last chunk.

Seems to me too many different variables to be able to say 1 is better than the other globally. I did my test with only 1 encoder thread per server, I usually run my 5950x machine with 2 threads. That could make a difference in how things line up. In the end they probably even out so it really doesn't make much of a difference. Although I need to try out a couple 4k as that will make the biggest difference time wise if that last chunk gets done by the slowest machine in the farm and how much bigger that chunk is. I run everything between a 7950x and a i9-10850k.

Kind of makes me think in the end its probably best to leave chunk size at the default 1 and just not worry about it.

[cypher007]

what do i need to change to get distributed encoding to max my cpu's?

one machine with an i5 10400f is only using 50% and 6 threads according to the encoder window. the other encoder is an i5 13500 that says its using 20 threads but still seems a little under utilized.

[rlev11]

what do i need to change to get distributed encoding to max my cpu's?

one machine with an i5 10400f is only using 50% and 6 threads according to the encoder window. the other encoder is an i5 13500 that says its using 20 threads but still seems a little under utilized.

the 10400f should be 6 cores 12 threads. regardless of what the encoder window is saying, load a utility like cpuid hwmonitor and see exactly what the processor utilization is on each thread.

easiest way to see if loading a second encoding thread helps is to just on the ripbot encoding server window, click add additional server , make sure the amount of total threads each cpu has is checked and then click activate. it should load up a second encoding server window with a port of :2000. then in the distributed encoding window just add the ip address with port:2000 and start that server.

I think you will find that adding a second server on lower level machines will not make that much of a difference. I have found that only when I get to the ryzen 9's with 16cores/32 threads that they have the additional head room to make an additional server worth the while.

For an i5, the 13500 is actually a pretty powerfull cpu, I have one and find that it is equivalent to a 16 core Ryzen 3950x and is just under a Ryzen 5900x

Of course your mileage may vary

[guest]

what do i need to change to get distributed encoding to max my cpu's?

one machine with an i5 10400f is only using 50% and 6 threads according to the encoder window. the other encoder is an i5 13500 that says its using 20 threads but still seems a little under utilized.

Good to see that you're using DE :)

Yes, just follow rlev11's suggestions, that's a good way to load up the CPU.

However, I'm surprised he didn't go on to mention that you can tweak it by using the encoders command line:-

Server1CommandLine=/port 1000 /priority normal /restart-if-no-progress /avisynth-prefetch-threads 16 /x264-threads 32 /x265-threads 32
Server2CommandLine=/port 2000 /priority normal /restart-if-no-progress /avisynth-prefetch-threads 16 /x264-threads 32 /x265-threads 32


And testing the values in red, to suit your specific CPU..it CAN make a lot of difference, especially with 4K encodes.

Also, if by chance you're using a PD build, and using SMDegrain filters, you also need to change this setting, (the small red circle) it also makes a HUGE difference, but if you're not, then it needs to be checked !!!

https://i.imgur.com/jsNxCJ0.jpg

The bigger red circle relates to this:-

/avisynth-prefetch-threads 16

[cypher007]

i cant seem to edit a mpls using the edit button. it opens the stream selection window shows one of the m2ts files says please wait analysing and just sits there.

[avinewbie]

Hi,

Does anyone have a copy of Pauly Dunnes Mod version 5 of Ripbot ?
(His media fire links are gone from previous posts)

[m5g]

Hi everyone, after use auto-update to latest version, Ripbot wont startup, just stays invisible in process manager... whats happened. downloaded 1.26.0 version from here loads ok, but after update - stops working...

Win 10 Pro x64, 32 Gb RAM, Intel Core i7-10700KF, Nvidia RTX 3060 12 Gb

[forkicks]

Hi everyone, after use auto-update to latest version, Ripbot wont startup, just stays invisible in process manager... whats happened. downloaded 1.26.0 version from here loads ok, but after update - stops working...

Win 10 Pro x64, 32 Gb RAM, Intel Core i7-10700KF, Nvidia RTX 3060 12 Gb

Same here. Downgrading to 1.26 brings it back, but as soon as it auto updates, it's gone again. Process launches, never starts the encoding servers, and never shows the gui.
Win11 x64, 64GB, Ryzen 5900x

[guest]

Hi everyone, after use auto-update to latest version, Ripbot wont startup, just stays invisible in process manager... whats happened. downloaded 1.26.0 version from here loads ok, but after update - stops working...

Win 10 Pro x64, 32 Gb RAM, Intel Core i7-10700KF, Nvidia RTX 3060 12 Gb

@m5g & forkicks

Firstly, there hasn't been any updates since mid June '23.

And clearly neither of you read the previous posts, closely !

In my post, directly above yours, (and at the bottom of this post) there's a link to v1.27.0, why don't you give that a shot, and turn off Auto Update, just to see what happens.

But having said that, I haven't had this problem....

[m5g]

In my post, directly above yours, (and at the bottom of this post) there's a link to v1.27.0

Same issue... Unpacked 1.27.0 and it wont start - just stays in process manger and wont show UI

[m5g]

@m5g & forkicks
Firstly, there hasn't been any updates since mid June '23.


Seems since that update it stops working

[forkicks]

In my post, directly above yours, (and at the bottom of this post) there's a link to v1.27.0, why don't you give that a shot, and turn off Auto Update, just to see what happens.

Happens exactly as described. Does not show any GUI while showing up in the process list. 1.26 starts normally. This is both on clean installs and with existing configurations already in place.

Please don't assume posts haven't been read.

[Atak_Snajpera]

Just uninstall GeForce experience or other junk siting in background (ASUS soft) and ripbot should appear on desktop.

[forkicks]

Thank you for your replies.

I'm not running nvidia's geforce experience, nor am I using ASUS software (for what its worth, I'm running gigabyte hardware, but I'm not using any of their tools either in this system).

Do you happen to know, or suspect, of what the change may be between 1.26 and 1.27 that causes this? That way I could look and try other software to see what is causing it in the first place. Again, 1.26 runs just fine, and I'm sticking with it for the time being, but it's starting to become a very interesting puzzle to solve.

[m5g]

I'm not running nvidia's geforce experience, nor am I using ASUS software (for what its worth, I'm running gigabyte hardware, but I'm not using any of their tools either in this system)

So am i. Installing as always only latest vdieo driver, creating custom setup without nvidia shit. GIGABYTE motherboard too/.

And why 1.26 works well and 1.27 didnt? So the problem is on the program side for sure. Just author dont want to dig it (

[m5g]

How to get latest 1.26.3 version before 1.27.0 to test it

[Atak_Snajpera]

Run windows in safe mode and then check if ripbot appears on desktop.

[guest]

How to get latest 1.26.3 version before 1.27.0 to test it

@m5g & forkicks

Because I have kept nearly every individual update, I have a surprise for you both.

I had a working v1.26.3 build, and I have included EVERY update since that build from (20-11-22), so you can incrementally update that build until you get to the stage where it has your current issue with v1.27.0.

Simply download this :-

https://www.mediafire.com/file/sz6jmb560orv65k/RipBot264v1.26.3.7z/file

unpack it, and copy the files from "UPDATES (progressive)" folder, into the Updates folder in RB, ensure that you enable Auto Updates, so they are used,

IMPORTANT...disconnect from the "Net" while you do all this !!! otherwise it's just a wasted exercise.

After updating to the level you want, DISABLE Auto Updates before reconnecting to the "Net".

GOOD LUCK.

[pinco1117]

Hello, first I wanted to thank once again Atak_Snajpera for this program and for the news of version 1.27 (finally I updated the program), second also thanks to TDS for the direct link to version 1.27, third if it helps I have took version 1.27 directly and put it on two different PCs on one it started quietly on the other it didn't start, through task manager I checked the wait chain through the details and in my case it was a function of logitech more precisely the EXE "logitechg_discord.exe" renamed it (since I don't use it) in "logitechg_discord.exe.old" terminated it in task manager and the program started without problems. I did this following the advice of Atak_Snajpera in an old post and I have always found this way the program that blocked it.

[m5g]

Thanks for all advices! Finally, i found what prevents 1.27.0 to launch by shutting down background processes one by one and try to run Ripbot ) Its called Saby Plugin launcner ) Thanks everyone!

[guest]

Thanks for all advices! Finally, i found what prevents 1.27.0 to launch by shutting down background processes one by one and try to run Ripbot ) Its called Saby Plugin launcner ) Thanks everyone!

Good to know :)

Still weird that v1.26.0 was OK, though :confused:

[guest]

*edited out*

You might as well go ahead and delete these posts...

Simply choose "Edit", then choose "Delete" (bottom right corner), then over in the left bottom corner, choose "Delete Message",
then go back over to the right bottom corner, and choose "Delete this Message"...done :)

[forkicks]

I initially had (double) posted inacurate information.

So I found out what was interfering with ripbot 1.27 start, and it's the "widgets.exe" from windows 11 widget thingy. This is a windows 11 executable, not something you install manually. Killing it while ripbot 1.27 is stuck on loading immediately makes the gui show up. It also only blocks ripbot 1.27 loading after a few minutes of being active. If you try to run 1.27 immediately after boot, it runs (I only caught this while trying to identify the problem. I usually leave my system on for long periods). As another interesting effect, if I have ripbot 1.27 already running when widgets.exe does its thing (whatever that is), ripbot continues to run, but will hang when I try to close it (ripbot's gui becomes unresponsive when you try to exit it). Trying to start ripbot after widgets.exe has been running for a few minutes still gives no gui.

So, this isn't exactly something that you can uninstall (there are probably ways to, but it's an OS component. I have never used it, but it still runs).

Also, version 1.26 has no problem with it.

(thanks for the tip about deleting the posts. I tried to before, but couldn't track the "delete" option on edit)

[john33]

If you wish to uninstall 'widgets.exe'(disable permanently), Google "Disable Widgets in Windows 11" and there's a PowerShell script available.

[m5g]

Found another app that prevents Ripbot 1.27.0 to luanch!!! Its Discord desktop app!!!!!!!!!!!

So strange behaviour. that 1.26.0 works and 1.27.0 not. Definately Ripbot problem....

[rlev11]

Have you tried just turning off widgets in the taskbar settings and see if that makes a difference. I have always had that turned off and have never had an issue with any version of RipBot starting up. I do still see a Widgets.exe process (with 8 sub processes) in task manager.

[forkicks]

Have you tried just turning off widgets in the taskbar settings and see if that makes a difference. I have always had that turned off and have never had an issue with any version of RipBot starting up. I do still see a Widgets.exe process (with 8 sub processes) in task manager.

I have it turned off. In fact, I have never even seen it. I'm running Win 11 Enterprise, and it won't show at all. But the process runs, and causes this.

About removing it, I imagined there would, ofc, be ways to achieve that, but is it reasonable to continue removing other applications when the common factor is ripbot itself? Maybe understanding what's causing it in the first place would be a better alternative in the long run.

[guest]

I think you will find that one reason RipBot is having more & more problems is that it's built to originally work under Windows 7 (AFAIK), and with more & more apps, widgets, etc, etc being part of the Windows 10/11 "way of life", it interferes with RipBot's operation.

As the dev seems to be deadset against anything other than Windows 7, and if he doesn't want to do anything, or see benefits in modernising or updating, then "we" can't do anything about it.

So I think it WILL be up to the individual user to remedy these situations as best they can, even if that means not being able to use more common & up to date app's, driver's, etc, etc, or not using RipBot...

I guess one remedy would be to have at least 2 PC's, one with all the "do dad's", and one to run RipBot....

There's only been 1 person that has attempted to update & modernise (to a point) RipBot recently, and the Pauly Dunne build's were, a bit of a game changer, but he's all but disappeared, due to lack of support from the majority.

[Atak_Snajpera]

I have it turned off. In fact, I have never even seen it. I'm running Win 11 Enterprise, and it won't show at all. But the process runs, and causes this.

About removing it, I imagined there would, ofc, be ways to achieve that, but is it reasonable to continue removing other applications when the common factor is ripbot itself? Maybe understanding what's causing it in the first place would be a better alternative in the long run.

1) open ripbot264.ini
2) change line
UseAutoUpdate=1
to
UseAutoUpdate=0
3) save

I hope this helps...

[guest]

1) open ripbot264.ini
2) change line
UseAutoUpdate=1
to
UseAutoUpdate=0
3) save

I hope this helps...

OR here:-

https://i.imgur.com/CyFTpcI.jpg

Isn't that sort of defeating the purpose ???

Are you suggesting that the users use a lesser RB build, as not to interfere with other app's they want/need to use !!!

[cypher007]

ripbot keeps detecting m2ts 50fps files as 25fps.

is there a switch i can add to the script to force 50fps?

i tried fpsnum=50 with fpsden=1 and i ended up with it wanting to encode 1 frame.

[LigH]

Please check details of your source with MediaInfo. M2TS is only the container, but it may contain e.g. MPEG-2 or MPEG-4 video ... and different AviSynth source filters (FFMS2, L-SMASH Source, DGDecNV ...) may be more or less successful in handling each possible variant.

[cypher007]

Please check details of your source with MediaInfo. M2TS is only the container, but it may contain e.g. MPEG-2 or MPEG-4 video ... and different AviSynth source filters (FFMS2, L-SMASH Source, DGDecNV ...) may be more or less successful in handling each possible variant.

already done that and its HEVC at 50fps. Vidcoder (handbrake) seems to recognise it fine but when i use that to encode other vids at 20 RF it seems to make a larger file than ripbot would at CQ 20. i assume theyre supposed to equal the same qulaity/file size? also ripbot is quicker than vidcoder.

[Atak_Snajpera]

Can you upload that file somewhere?

[cypher007]

Can you upload that file somewhere?

its about 3gb.

ive also noticed another file which is part of the same disc shows 25fps and double the runtime when in ripbot.

ive had this issue before with some videos. i dont know why handbrake sees it as 50fps but ripbot 25fps.

[Atak_Snajpera]

Just use some cutting program. Type "Binary File Splitter" in google.
I need small sample 100-200MB.

[guest]

its about 3gb.

ive also noticed another file which is part of the same disc shows 25fps and double the runtime when in ripbot.

ive had this issue before with some videos. i dont know why handbrake sees it as 50fps but ripbot 25fps.

You could use MKVToolNix to create a small sample, but it will be an .mkv :(

Tsmuxer might work.

[cypher007]

why does rf 24 in Vidcoder (handbrake) give me a 1.46gb file but the same video done with ripbot on 24 give me a 1.05gb file?

[guest]

why does rf 24 in Vidcoder (handbrake) give me a 1.46gb file but the same video done with ripbot on 24 give me a 1.05gb file?

There could well be some settings, sort of in the background/hidden, that could affect the outcome between the two apps.

How different are the bit rates between the two videos ??

Is there any visible difference to the quality of the files ??

[cypher007]

There could well be some settings, sort of in the background/hidden, that could affect the outcome between the two apps.

How different are the bit rates between the two videos ??

Is there any visible difference to the quality of the files ??

thats the odd thing the Vidcoder file doesnt show the bit rate in media info. heres the two files media info's. first one is Vidcoder:

General

Complete name : C:\Users\Administrator\Videos\Title 4.mkv
Format : Matroska
Format version : Version 4
File size : 1.48 GiB
Duration : 16 min 24 s
Overall bit rate mode : Variable
Overall bit rate : 12.9 Mb/s
Frame rate : 24.000 FPS
Encoded date : 2023-08-19 11:26:03 UTC
Writing application : HandBrake 1.6.1 2023012300
Writing library : Lavf59.27.100
ErrorDetectionType : Per level 1

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 16 min 24 s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Writing library : x265 3.5+1-f0c1022b6:[Windows][GCC 10.2.0][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=3 / numa-pools=12 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=3840x2160 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-eob / no-eos / no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=24 / keyint=240 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=20 / lookahead-slices=8 / scenecut=40 / no-hist-scenecut / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=1 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / no-strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=4 / selective-sao=4 / early-skip / rskip / rskip-edge-threshold=0.050000 / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=0.75 / psy-rdoq=4.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=24.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / ipratio=1.40 / pbratio=1.30 / aq-mode=1 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=1 / transfer=1 / colormatrix=1 / chromaloc=1 / chromaloc-top=2 / chromaloc-bottom=2 / display-window=0 / cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-sbrc / no-hdr10 / no-hdr10-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=0 / analysis-save-reuse-level=0 / analysis-load-reuse-level=0 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00 / scenecut-aware-qp=0conformance-window-offsets / right=0 / bottom=0 / decoder-max-rate=0 / no-vbv-live-multi-pass / no-mcstf
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 2
Format : FLAC
Format/Info : Free Lossless Audio Codec
Codec ID : A_FLAC
Duration : 16 min 24 s
Bit rate mode : Variable
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Bit depth : 16 bits
Compression mode : Lossless
Title : Stereo
Language : English
Default : Yes
Forced : No
MD5 of the unencoded content : 00000000000000000000000000000000

Menu
00:00:00.000 : Chapter 1
00:06:57.000 : Chapter 2

now the ripbot one:

General

Complete name : D:\Extras\t.mkv
Format : Matroska
Format version : Version 4
File size : 1.06 GiB
Duration : 16 min 24 s
Overall bit rate mode : Variable
Overall bit rate : 9 221 kb/s
Frame rate : 24.000 FPS
Encoded date : 2023-08-17 15:16:09 UTC
Writing application : mkvmerge v74.0.0 ('You Oughta Know') 64-bit
Writing library : libebml v1.4.4 + libmatroska v1.7.1

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 16 min 24 s
Bit rate : 8 797 kb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.044
Stream size : 1.01 GiB (95%)
Writing library : x265 3.5+100-3dae0c3cc:[Windows][GCC 12.2.0][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=3 / numa-pools=12 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=3840x2160 / interlace=0 / total-frames=23631 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-eob / no-eos / no-hrd / info / hash=0 / temporal-layers=0 / open-gop / min-keyint=24 / keyint=240 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=20 / lookahead-slices=8 / scenecut=40 / no-hist-scenecut / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=3 / selective-sao=4 / early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=24.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=1 / transfer=1 / colormatrix=1 / chromaloc=0 / display-window=0 / cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-hdr10 / no-hdr10-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=0 / analysis-save-reuse-level=0 / analysis-load-reuse-level=0 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00 / scenecut-aware-qp=0conformance-window-offsets / right=0 / bottom=0 / decoder-max-rate=0 / no-vbv-live-multi-pass / no-mcstf / no-sbrc
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 2
Format : FLAC
Format/Info : Free Lossless Audio Codec
Codec ID : A_FLAC
Duration : 16 min 24 s
Bit rate mode : Variable
Bit rate : 422 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 11.719 FPS (4096 SPF)
Bit depth : 16 bits
Compression mode : Lossless
Stream size : 49.5 MiB (5%)
Writing library : libFLAC 1.2.1 (2007-09-17)
Language : English
Default : Yes
Forced : No
MD5 of the unencoded content : 088CDBF0DF89CFDD105B10D4B022EE09

Menu
00:00:00.000 : en:Chapter 01
00:06:57.000 : en:Chapter 02

[cypher007]

actually the bitrate is there but listed differently. so if its higher why doesnt cq in ripbot equal rf in vidcoder?

[guest]

actually the bitrate is there but listed differently. so if its higher why doesnt cq in ripbot equal rf in vidcoder?

I still reckon it's the difference between the apps.

The writing applications and writing libraries are different.

And even x265 versions are different.

[cypher007]

I still reckon it's the difference between the apps.

The writing applications and writing libraries are different.

And even x265 versions are different.

ok it seems rf 25.5 in vidcoder equals near enough the same as rf 24 in ripbot.

so i will use vidcoder to encode the troublesome 50fps files and ripbot for main 24fps videos.

[Boulder]

The settings in the two encodes are totally different. For example, aq-mode 1 vs 2 can make a huge difference in the final bitrate.

[cypher007]

The settings in the two encodes are totally different. For example, aq-mode 1 vs 2 can make a huge difference in the final bitrate.

ah that probably explains the difference. wonder why these sort of options are not visible in the interface of both programs?

[guest]

ah that probably explains the difference. wonder why these sort of options are not visible in the interface of both programs?

So kinda like I said, it's the differences between the apps, if you stick with one, then that's it, but when you start "comparing" them, inevitably there will be some significant differences.

When you learn a bit more about RipBot, you will soon realise that you can change a LOT of settings, either using custom scripts, and custom x265 commands.

When using Distributed Encoding, you will be able to view all the settings that the app is using to do the encode, in the Encoder Server "window". That can also be beneficial in knowing what x265 commands can be added, changed, etc, etc.

Chances are, if you studied & compared the MediaInfo data, (as Boulder mentioned) and matched RB with Vidcoder (at least as far as x265 commands are concerned) you may get a LOT closer results.

Also, maybe you give this a shot with the FPS issues you're having :-

http://avisynth.nl/index.php/FPS#ChangeFPS

ChangeFPS(25000, 1000)

[Yopen71]

Hello. Are there any limitations in the ripbot264 on the use of the cpu? To be specific I can't use the full power of my cpu and gpu .The cpu used during encoding is no more than 22%

https://iili.io/JJ3JxIa.md.png (https://freeimage.host/i/JJ3JxIa)
https://iili.io/JJ3JzhJ.md.png (https://freeimage.host/i/JJ3JzhJ)

Edit: Second pass is no more than 46%
https://iili.io/JJ3ohml.md.png (https://freeimage.host/i/JJ3ohml)