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

[byteshare]

Originally Posted by Atak_Snajpera

Because all plugins are still 32bit.

I thought the plugins that came with the 64bit AVISynth+ would be 64bit. My mistake, didn't think about it being more dependent on the plugins in RipBot.
I know MVTools and a few others should support 64bit.

Originally Posted by Atak_Snajpera

You will have to reduce prefech limit significantly because it looks like you are using some very demanding filters.

My filters:

LoadPlugin("C:\RipBot264v1.20.0\Tools\AviSynth plugins\hqdn3d\hqdn3d.dll")
LoadPlugin("C:\RipBot264v1.20.0\Tools\AviSynth plugins\flash3kyuu_deband\flash3kyuu_deband.dll")
LoadPlugin("C:\RipBot264v1.20.0\Tools\AviSynth plugins\masktools\masktools2.dll")
Loadplugin("C:\RipBot264v1.20.0\Tools\AviSynth plugins\mvtools\mvtools2.dll")
LoadPlugin("C:\RipBot264v1.20.0\Tools\AviSynth plugins\Custom\Deen.dll")
Import("C:\RipBot264v1.20.0\Tools\AviSynth plugins\Custom\HQdering.avs")
super = video.MSuper(pel=2)
bv1 = MAnalyse(super, isb = true, delta = 1, overlap=4)
fv1 = MAnalyse(super, isb = false, delta = 1, overlap=4)
bv2 = MAnalyse(super, isb = true, delta = 2, overlap=4)
fv2 = MAnalyse(super, isb = false, delta = 2, overlap=4)
bv3 = MAnalyse(super, isb = true, delta = 3, overlap=4)
fv3 = MAnalyse(super, isb = false, delta = 3, overlap=4)
video=video.MDegrain3(super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=1000).HQDering(strength=255).f3kdb

I'm using prefetch 2 right now, I can try 1 but most likely will have to stick with non-MT mode which puts my memory usage around 1.3-1.5GB (avs2yuv.ext) per server.

[skylinekiller]

Currently it only works if subtitle has the same name as video file.

so if I do the exact same thing I did, but change my test file to the exact same as the movie title, it will hard code when it burns?

[Atak_Snajpera]

@byteshare
Are you working with 4k footage that you can't go above 2?

[slalom]

Originally Posted by Big Vern

Hello. Not used ripbot in a while, quite a while in fact and have ran into a problem.

I have all the necessary additional tools installed, haali, avsynth, etc. When I load a file into ripbot, it takes ages to demux, even though I have 3 HDs. Once the file is finally demuxed, ripbot just sits there with the, "please wait, gathering information" message, and nothing happens at all. I have to abort the process.

I am running:
Ryzen 8 core 1700@3.70ghz, no overclocking.
16gig DDR4 3600mhz.
Windows Pro 64bit.

Regards....

Same problem here, did you find a solution?

[MaistroX]

Hey!

My RipBot just stopped working after it updated to 1.20.1!

Every prepared Movie in que just fails direct after I push START, all with the same fault in Error Message:

"
C:\>"C:\5.8 RipBot264 v1.19.2\tools\avs2yuv\avs2yuv.exe" "C:\Temp\RipBot264temp\job1\job1.avs" -o - | "C:\5.8 RipBot264 v1.19.2\tools\x264\x264_x64.exe" --pass 1 --bitrate 10000 --stats "C:\Temp\RipBot264temp\job1\job1.stats" --fps 24000/1001 --force-cfr --min-keyint 24 --keyint 240 --frames 185749 --sar 1:1 --threads 8 --pass 2 --level 4.1 --preset slower --vbv-bufsize 62500 --vbv-maxrate 62500 --filter 0,0 --ref 7 --no-mixed-refs --bframes 10 --b-adapt 2 --b-pyramid none --subme 7 --aq-mode 1 --trellis 2 --partitions all --me tesa --stdin y4m --output NUL -
y4m [info]: 1920x800p 1:1 @ 10000000/417083 fps (cfr)
x264 [info]: using SAR=1/1
x264 [warning]: DPB size (7 frames, 42000 mbs) > level limit (5 frames, 32768 mbs)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX XOP FMA3 BMI1
x264 [error]: ratecontrol_init: can't open stats file
x264 [error]: x264_encoder_open failed

C:\Temp\RipBot264temp\job1\job1.avs: 1920x800, 10000000/417083 fps, 185749 frames
error: wrote only 2285802 of 2304000 bytes

C:\>"C:\5.8 RipBot264 v1.19.2\tools\avs2yuv\avs2yuv.exe" "C:\Temp\RipBot264temp\job1\job1.avs" -o - | "C:\5.8 RipBot264 v1.19.2\tools\x264\x264_x64.exe" --pass 2 --bitrate 10000 --stats "C:\Temp\RipBot264temp\job1\job1.stats" --fps 24000/1001 --force-cfr --min-keyint 24 --keyint 240 --frames 185749 --sar 1:1 --threads 8 --pass 2 --level 4.1 --preset slower --vbv-bufsize 62500 --vbv-maxrate 62500 --filter 0,0 --ref 7 --no-mixed-refs --bframes 10 --b-adapt 2 --b-pyramid none --subme 7 --aq-mode 1 --trellis 2 --partitions all --me tesa --stdin y4m --output "C:\Temp\RipBot264temp\video.264" -
y4m [info]: 1920x800p 1:1 @ 10000000/417083 fps (cfr)
x264 [info]: using SAR=1/1
x264 [warning]: DPB size (7 frames, 42000 mbs) > level limit (5 frames, 32768 mbs)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX XOP FMA3 BMI1
x264 [error]: ratecontrol_init: can't open stats file
x264 [error]: x264_encoder_open failed

C:\Temp\RipBot264temp\job1\job1.avs: 1920x800, 10000000/417083 fps, 185749 frames
error: wrote only 2285802 of 2304000 bytes

C:\>"C:\5.8 RipBot264 v1.19.2\tools\mkvtoolnix\mkvmerge.exe" -o "C:\TEMP\Movie_2017.mkv" --compression 0:none --title "Movie_2017" --default-duration 0:24000/1001fps "C:\Temp\RipBot264temp\video.264"
mkvmerge v14.0.0 ('Flow') 32bit
Error: The type of file 'C:\Temp\RipBot264temp\video.264' could not be recognized.
-------------------------

Elapsed Time: 00h:00m:02s"

What has happened here, can anyone please explain?

P.S I havent changed a thing in setting nor in my Profiles/Avc/[HIGH 4.1] 1080p BÄSTA SLOWER . DEFAULT.txt , that I have used for years now.

[sneaker_ger]

First pass has both "--pass 1" and "--pass 2", first one gets ignored and it fails because naturally there is no pass file yet. But I don't know why RipBot did that. Or did you manually set "--pass 2" by accident somehow?

[MaistroX]

yes I did, will remove it, but it was the same Before with out both of them, RipBot would´nt start as it did Before 1.20.1 update!

Originally Posted by sneaker_ger

First pass has both "--pass 1" and "--pass 2", first one gets ignored and it fails because naturally there is no pass file yet. But I don't know why RipBot did that. Or did you manually set "--pass 2" by accident somehow?

[Atak_Snajpera]

Originally Posted by MaistroX

yes I did, will remove it, but it was the same Before with out both of them, RipBot would´nt start as it did Before 1.20.1 update!

So show us new log then.

[klopsknoedel]

@Big Gern
@slalom

Have you tried this: http://forum.doom9.org/showthread.ph...96#post1524496

[slalom]

I've gone back to 1.20.0 with no updates and it works fine

[byteshare]

Originally Posted by Atak_Snajpera

@byteshare
Are you working with 4k footage that you can't go above 2?

Correct, I am indeed working with 4K footage.

[burt123]

Well, I have just discovered a major problem with the latest auto update.
I had a batch queue encoding using the previous update (11/09/17), and it was working well, so I then updated to (13/09/17), and the DE went berserk, only a couple of the 10 servers I had enabled, connected, and I could not re connect them.

So now I'll have to "re install" the "vanilla" 1.20.0, and update up to the second last update....unless there's a fix, beforehand

EDIT:- Well, it's all working nicely today.....the only thing that I have changed was, I disabled x264 OpenCL acceleration for my GTX 580 card.....

[byteshare]

Originally Posted by burt123

Well, I have just discovered a major problem with the latest auto update.
I had a batch queue encoding using the previous update (11/09/17), and it was working well, so I then updated to (13/09/17), and the DE went berserk, only a couple of the 10 servers I had enabled, connected, and I could not re connect them.

So now I'll have to "re install" the "vanilla" 1.20.0, and update up to the second last update....unless there's a fix, beforehand

I didn't have this issue.

[burt123]

Originally Posted by byteshare

I didn't have this issue.

It's working alright, today (see my previous post)

[burt123]

So I'm having a bit of a problem with the auto shutdown option.

I generally have a "main" pc doing the Ripbot "thing", and one server helping.

Twice now (which is as many times as I've used it), when I have selected "Shutdown Servers" option, it shutdowns both pc's...I haven't tried the "Shutdown Client" option.....

I have all 16 servers enabled, 10 on the main pc, and 6 on the "helper"....maybe that shutdown option can't tell the difference between the 2....

Also, auto update hasn't worked for the last couple of days

[Atak_Snajpera]

Shutdown Servers option basically tells Encoding client to send shutdown command to ALL specified IP's. So It will shutdown your main PC as well if you also have running encodingserver.exe in background.

Also, auto update hasn't worked for the last couple of days

It was intentionally disabled by me because newer version 1.21.0 will only work with AViSynth+ MT x64. Also due to this change old jobs created by 1.20.x won't work in newer x64 environment!
I decided to abandon x86 mainly due to annoying 2 GiB limit which can be easily reached when working with multiple processing threads.

[byteshare]

Originally Posted by Atak_Snajpera

It was intentionally disabled by me because newer version 1.21.0 will only work with AViSynth+ MT x64. Also due to this change old jobs created by 1.20.x won't work in newer x64 environment!
I decided to abandon x86 mainly due to annoying 2 GiB limit which can be easily reached when working with multiple processing threads.

This is awesome. Looking forward to my batch of encodes finishing so I can test this out.

[Atak_Snajpera]

v1.21.0

Added: Support for AviSynth+ MT x64 (installer located in \Tools\AviSynth folder) 
Finally no need to automatically limit processing threads due to 32bit memory limitation.
Warning! Jobs created by older version won't work with this version! You must start with freshly created job!   
Fixed: Various tweaks and changes under the hood. 
Updated: MKVToolnix v15.0.0, EncodingServer v1.8.1

[byteshare]

Playing with the new version now, love what you did with AVISynth installer.
For x265
I'm only seeing 1 file in the folder now: x265_x64.exe
Before there were 4 files x265_x64.exe, x265_x64_10bit.exe, x265_x86.exe, and x265_x86_10bit.exe
I wanted to update becase the x265 is on 2.5+4 and stable is 2.5+5
My question before is figuring out which files to take from: http://msystem.waw.pl/x265/ wasn't too hard before.

The x265 files (for updating) come as:

libx265_main.dll
libx265_main10.dll
libx265_main12.dll
x265.exe
x265_32.exe
x265-8b.exe
x265-8b_32.exe
x265-10b.exe
x265-10b_32.exe
x265-12b.exe
x265-12b_32.exe

My guess was to use the x265.exe but it is significantly larger than the x265_x64.exe that comes with 1.21.0
Suggestion?

[Atak_Snajpera]

Yes use the largest binary (all in one).