View Full Version : RipBot264 v1.18.3 - Simple and easy to use GUI -> IPOD . PSP . CONSOLES . BLURAY
byteshare
21st February 2019, 18:53
Is there an option to only extract subtitles in a certain language? For me, it would be nice to extract subtitles that are my local languge and unknown.
Maybe a box in settings where you can add which subtitles languages to extract.
If you have all copy automatically you can setup your video player to play your preferred language first.
Ryushin
21st February 2019, 19:34
It might sound like a stupid question, how do you rip a 3D movie and get a 3D rendered MKV ?
It depends. For me, I rip the 3D using MakeMKV and using my Oppo UPD-203 to play the file back in 3D.
Only other methods I've seen need to use side by side or top and bottom frame. Essentially, you will need to encode two frames to get your 3D image. There were only a couple of software packages that I saw that could do this. Clown_BD was one and the other was DVDFab.
I may revisit this again if I can find a software package that will make x265 3D T&B files.
Edit: Looks like BD3D2MK3D will do what I need now. Time to try Top And Bottom frame encoding again.
Ryushin
21st February 2019, 19:36
If you have all copy automatically you can setup your video player to play your preferred language first.
Rather not clutter up the mkv file. I can still select manually as I'm doing now.
byteshare
21st February 2019, 22:07
Rather not clutter up the mkv file. I can still select manually as I'm doing now.
Can also select all then after encoding set a batch to strip the extras you don't want. Doing it that way saves you some manual work.
slalom
22nd February 2019, 11:16
What is this?
y4m [error]: bad sequence header magic
x264 [error]: could not open input file `-'
One server is starting and stopping
forkicks
22nd February 2019, 13:04
All my servers except the main one running side-by-side on the same machine with ripbot have started to fail with:
Encoding started...
""\\PCNAME\Ripbot264temp\Tools\ffmpeg\bin\ffmpeg.exe" -loglevel panic -i "\\PCNAME\Ripbot264temp\job1\Chunks\36.avs" -strict 1 -f yuv4mpegpipe - | "\\PCNAME\Ripbot264temp\tools\x265\x265_x64.exe" --seek 176 --colorprim bt709 --transfer bt709 --colormatrix bt709 --crf 18 --fps 24000/1001 --min-keyint 24 --keyint 240 --frames 1613 --sar 1:1 --profile main10 --output-depth 10 --tune psnr --ctu 16 --max-tu-size 16 --qg-size 16 --y4m --pools "+" --output "\\PCNAME\Ripbot264temp\job1\Chunks\36.265" -"
x265: [error]: unable to open input file <->
(this is just an example, its the same for other jobs/chunks)
Also, running this command from the command line produces the same result. (I couldn't copy paste the error, so i typed it in here, please attribute any typo to my fingers :-) )
after i updated my main ripbot with the latest update and started new batches.
This happens on all files, while encoding to 265 mkvs.
I have tried updating all the servers also to latest version, same result (initally had only the main one updated to absolute last version)
Atak_Snajpera
22nd February 2019, 13:44
open \\PCNAME\Ripbot264temp\job1\Chunks\36.avs in MPC-HC and see what error message you get.
forkicks
22nd February 2019, 15:44
open \\PCNAME\Ripbot264temp\job1\Chunks\36.avs in MPC-HC and see what error message you get.
The first error i get when doing what you say is:
"Cannot load a 64 bit DLL in 32 bit Avisynth: '//PCName/Ripbot264temp/tools/avisynth plugins/ffms/x64/ffms2.dll'. (\\PCName\Ripbot264temp\job4\Chunks\6.avs, line 6)
So i tried to "fix" it by changing the x64 to x86, then it fails with:
FFVideoSource: Failed to open 'Y:\filename.mkv' (\\PCNAME\RipBot264temp\job4\Chunks\6.avs, line 7)
(this was on a different block, but was the same problem).
"Y:" there refers to a path on the system where ripbot is running, its not valid for the DE servers.
(edit: Ignore the part about the x64/x86 difference, that is fine in the script, its the other path that is the problem.)
Ryushin
22nd February 2019, 16:01
I've normally had convert sup to sub for my settings since the beginning. But I've been see some sup that are different colors other than white, turn to a different color in sub.
For example, I have a sup that is yellow but turn red after conversion to sub. I've seen grey turn to near black.
I'm encoding only in x265 now and I've just turned off convert sup to sub so the subtitles look correct. Selecting rendering subtitles always converts to sub it seems. Can rendering subtitles not work with sup?
Question, is sub generally better supported and is that why we should use that instead? All of my players now have no problems play sup, so I'll just go with that for now on.
Atak_Snajpera
22nd February 2019, 16:35
Question, is sub generally better supported and is that why we should use that instead? All of my players now have no problems play sup, so I'll just go with that for now on.
Yes. Stick with original subtitles because support for BD subtitles is much better these days.
byteshare
22nd February 2019, 17:44
I was playing around with some filters for "fun"....boring life I suppose...
Anyways, I noticed that not all filters seem to work with the same syntax and I was wondering if anyone knew or could better describe AviSynth syntax/format in RipBot for me?
Why do some filters seem to work with video=Filter and others video=video.filter? Is it just because some are "built-in" to RipBot?
for example: video=QTGMC(Settings) works but FK3DB needs video=video.fk3db(settings)
Are the filters taken in order of the jobsxxx.avs file (top to bottom)?
for example: Deinterlace would go before Decimate? I don't think this is happening since Crop is 3rd from VideoSource, but custom would go last?
If I string them in a row with a "." they are done one at a time from left to right, yes?
for example: video=video.filter01(settings).filter02(settings) > filtero1 is processed, then filter02
or if I did them:
video=video.filter01(settings)
video=video.filter02(settings)
Would it be the same as stringing them together with "."?
egres
22nd February 2019, 18:01
Just started a job after latest update...... Nothing happens.... All encoders on all the remote pc's just do nothing...
https://ibb.co/Gv2963T
The chunk directories is like this...
https://i.ibb.co/VjMYw4L/Capturedir.png
byteshare
22nd February 2019, 18:23
Just started a job after latest update...... Nothing happens.... All encoders on all the remote pc's just do nothing...
https://ibb.co/Gv2963T
The chunk directories is like this...
https://i.ibb.co/VjMYw4L/Capturedir.png
What is are your encoding settings?
I'm seeing: --output NUL -
at the end of the Encoding Server here: https://ibb.co/Gv2963T
That doesn't seem normal to me, for me it looks like:
--output "\\compname\ripbot264temp\jobxx\chunks\xx.265" -
or try creating a new job and seeing if it does the same thing, cause right now it doesn't seem to be pointing the output correctly.
egres
22nd February 2019, 18:26
I have got 2 other jobs which worked yesterday and not working today. Did not change anything to my setup, except updating core !!
egres
22nd February 2019, 18:27
By the way, --output NUL - is normal in a 2 pass setting
byteshare
22nd February 2019, 18:29
By the way, --output NUL - is normal in a 2 pass setting
Oh, okay. Did you try making a new job to see if you got the same issue? (after closing and re-opening RipBot)
Cause on CRF it is working for me.
egres
22nd February 2019, 18:31
Yes.... I started a new job, same parameters, all encoders just sit there doing nothing. Then try one of the 2 older job, same result !!
Even the local encoder just sits there, with the command line....
byteshare
22nd February 2019, 18:33
Yes.... I started a new job, same parameters, all encoders just sit there doing nothing. Then try one of the 2 older job, same result !!
Even the local encoder just sits there, with the command line....
Not sure then, but maybe Atak_Snajpera or someone else might now why. It is working for me with CRF after update both old jobs and new jobs.
egres
22nd February 2019, 18:38
Just tried it with CRF.... same issue..
byteshare
22nd February 2019, 18:41
Just tried it with CRF.... same issue..
Something else is going on then. Have you tried a reboot just to eliminate that?
Have you checked any of the log files?
Atak_Snajpera
22nd February 2019, 18:46
I was playing around with some filters for "fun"....boring life I suppose...
Anyways, I noticed that not all filters seem to work with the same syntax and I was wondering if anyone knew or could better describe AviSynth syntax/format in RipBot for me?
Why do some filters seem to work with video=Filter and others video=video.filter? Is it just because some are "built-in" to RipBot?
for example: video=QTGMC(Settings) works but FK3DB needs video=video.fk3db(settings)
Are the filters taken in order of the jobsxxx.avs file (top to bottom)?
for example: Deinterlace would go before Decimate? I don't think this is happening since Crop is 3rd from VideoSource, but custom would go last?
If I string them in a row with a "." they are done one at a time from left to right, yes?
for example: video=video.filter01(settings).filter02(settings) > filtero1 is processed, then filter02
or if I did them:
video=video.filter01(settings)
video=video.filter02(settings)
Would it be the same as stringing them together with "."?
Syntax is like this
video=Filter(video,settings)
you can create chain of filter like this
video=Filter(video,settings).FilterB(settings).FilterC(settings)
Just remember that first filter will need clip name!
Atak_Snajpera
22nd February 2019, 18:54
I have got 2 other jobs which worked yesterday and not working today. Did not change anything to my setup, except updating core !!
Smells like your antivirus/firewall is just doing some weird stuff in background. In last update I just fixed few deadlocks (when user clicked abort client randomly hung) in code and I didn't mess with other parts of the code. I'm still investigating that auto-connecting bug...
egres
22nd February 2019, 19:02
Hum, just checked firewall rules... green light on encoder and Ripbot264. Even the local encoder just sits there with the command line.... nothing happens...
Atak_Snajpera
22nd February 2019, 19:03
Hum, just checked firewall rules... green light on encoder and Ripbot264. Even the local encoder just sits there with the command line.... nothing happens...
Check if script can be opened in MPC-HC.
egres
22nd February 2019, 19:04
I will reinstall the original RipBot264v1.24.0 and try that
byteshare
22nd February 2019, 19:05
Syntax is like this
video=Filter(video,settings)
you can create chain of filter like this
video=Filter(video,settings).FilterB(settings).FilterC(settings)
Just remember that first filter will need clip name!
Oh! I think I wasn't seeing the video in the settings:
video=Filter(video,settings) on the default ones...
So video=video.filter is working because I'm just saying to AviSynth do:
video then the filter and the filter is using the video from the first "command", which is just video.
Are the custom scripts getting the "video" from the other parts of the jobxx.avs after their AVISynth scripts (assuming there are some) or should I be putting everything like QTGMC into the custom script, except for crop?
I had in the past only been using a custom script.
egres
22nd February 2019, 19:06
Check if script can be opened in MPC-HC.
I am rather new at using your wonderful software... Could you elaborate :)
egres
22nd February 2019, 19:16
Just did a fresh reinstall of RipBot264v1.24.0.7z making sure update flag was set to 0. Works like a charm
byteshare
22nd February 2019, 19:17
I am rather new at using your wonderful software... Could you elaborate :)
Click on the Job > Edit > AviSynth > Preview Script
egres
22nd February 2019, 19:18
I left encoder v1.14.2.0 on all the remote PC's, and it works
egres
22nd February 2019, 19:20
Click on the Job > Edit > AviSynth > Preview Script
I will try that when job concludes. Thanks
Atak_Snajpera
22nd February 2019, 19:26
Oh! I think I wasn't seeing the video in the settings:
video=Filter(video,settings) on the default ones...
So video=video.filter is working because I'm just saying to AviSynth do:
video then the filter and the filter is using the video from the first "command", which is just video.
Are the custom scripts getting the "video" from the other parts of the jobxx.avs after their AVISynth scripts (assuming there are some) or should I be putting everything like QTGMC into the custom script, except for crop?
I had in the past only been using a custom script.
It does not matter where you put your code.
egres
22nd February 2019, 19:27
Just killed the job.... went in Click on the Job > Edit > AviSynth > Preview Script
https://i.ibb.co/VWSxyF9/preview.png
I never had a chance to use this before, but that dont look ok !!
Atak_Snajpera
22nd February 2019, 19:29
Basically What you see here is what you will get in encoded file.
egres
22nd February 2019, 19:31
As I said, never used this > Edit > AviSynth > Preview Script and all my jobs worked fine. The mkv was just fine
egres
22nd February 2019, 19:34
This is my Video script:
#AudioSource
LoadPlugin("C:\Users\Serveur\Desktop\Video\RipBot264\tools\AviSynth plugins\NicAudio\NicAudio.dll")
audio=NicDTSSource("D:\Temp\RipBot264temp\job32\audio_1_English.core.dts")
audio=ResampleAudio(audio,48000)
#DownMix
#Delay
audio=DelayAudio(audio,0)
#Tempo
#Normalize
#AudioDub
AudioDub(video,audio)
egres
22nd February 2019, 19:36
I meant audio... this is my video script...
#MT
#VideoSource
LoadPlugin("C:\Users\Serveur\Desktop\Video\RipBot264\Tools\AviSynth plugins\ffms\x64\ffms2.dll")
video=FFVideoSource("D:\Temp\RipBot264temp\job32\video.mkv",cachefile = "D:\Temp\RipBot264temp\job32\video.mkv.ffindex")
#Deinterlace
#Decimate
#Crop
#Resize
#Tonemap
#Levels
#Colours
#Denoise
#Custom
#Prefetch
#After_Prefetch_Denoise
#After_Prefetch_Custom
#Subtitles
#AudioSource
Import("D:\Temp\RipBot264temp\job32\job32_a1.avs")
#Triming
#AVSameLength
#ColorSpace
#Return
Atak_Snajpera
22nd February 2019, 19:41
Maybe reinstall GPU driver.
egres
22nd February 2019, 19:44
https://i.ibb.co/pw4KhkD/gpu.png
Do I need to set x264 OpenCl acceleration to my gpu ?
Atak_Snajpera
22nd February 2019, 19:46
no...
egres
22nd February 2019, 19:47
So you think it my be my GPU drivers... I will try that. Thanks for your help
forkicks
22nd February 2019, 21:11
All my servers except the main one running side-by-side on the same machine with ripbot have started to fail with:
Encoding started...
""\\PCNAME\Ripbot264temp\Tools\ffmpeg\bin\ffmpeg.exe" -loglevel panic -i "\\PCNAME\Ripbot264temp\job1\Chunks\36.avs" -strict 1 -f yuv4mpegpipe - | "\\PCNAME\Ripbot264temp\tools\x265\x265_x64.exe" --seek 176 --colorprim bt709 --transfer bt709 --colormatrix bt709 --crf 18 --fps 24000/1001 --min-keyint 24 --keyint 240 --frames 1613 --sar 1:1 --profile main10 --output-depth 10 --tune psnr --ctu 16 --max-tu-size 16 --qg-size 16 --y4m --pools "+" --output "\\PCNAME\Ripbot264temp\job1\Chunks\36.265" -"
x265: [error]: unable to open input file <->
(this is just an example, its the same for other jobs/chunks)
Also, running this command from the command line produces the same result. (I couldn't copy paste the error, so i typed it in here, please attribute any typo to my fingers :-) )
after i updated my main ripbot with the latest update and started new batches.
This happens on all files, while encoding to 265 mkvs.
I have tried updating all the servers also to latest version, same result (initally had only the main one updated to absolute last version)
I managed to get my DE servers to work again by mounting a share on each of them so that the path that is set on the avs file is the same locally for each of them.
Basically, in the avs file, on each DE server,
FFVideoSource: Failed to open 'Y:\filename.mkv' (\\PCNAME\RipBot264temp\job4\Chunks\6.avs, line 7)
the "Y:" is wrong, it should be \\PCNAME\(...)". The path that is set in the avs file is only valid in the machine running ripbot.
My fix was making that path also valid on each DE server by sharing and mapping the share so that it matches.
This only happens since the last version, this was working fine previously, but the problem is definitly that.
fK
DG74
22nd February 2019, 21:30
I still have the problem with a hanging task of RipBot, so no shutdown is possible. Any solution there?
pepeq
23rd February 2019, 00:06
I still have the problem with a hanging task of RipBot, so no shutdown is possible. Any solution there?
see post #16556 for a workaround. it helped me and some others...
DG74
23rd February 2019, 12:40
see post #16556 for a workaround. it helped me and some others...
Thank you very much! This solution helped in my case, too. It's the Logitech_discord.exe process, installed by Logitech Gaming Software, that caused hanging of RipBot.
slalom
24th February 2019, 10:59
Did we fix the start-stop problem of the servers?
Ryushin
24th February 2019, 13:36
The last few days I've had artifact issues with encoding a VC-1 blu-ray source. I must have re-encoded a dozen times with different settings trying to figure out what was wrong. Even tried handbrake to no avail. Eventually I tried a lossless h.264 encode using CRF 0 and I still had the artifacts. Googling seems to point to a decoding issue:
https://forum.videohelp.com/threads/388829-Annoying-Pixelating-Blocking-After-Encoding-in-Handbrake
Atak, I never knew of this issue with VC-1. Reading the thread says using the MS decoder solves the problem. Is it possible to implement a solution that solves the decoder problems for all VC-1 sources. Looks like ffmpeg might have just fixed this bug very recently as well.
Atak, it looks like the current version of ffmpeg that is included can handle the VC-1 encoding. I ran this:
"C:\Program Files\RipBot264\Tools\ffmpeg\bin\ffmpeg.exe" -i video.mkv -c:v libx264 -preset ultrafast -crf 0 output_x264_ultrafast_lossless.mkv
and the file did not show any artifacts. Huge file size though:
Original: 9.07GB
Lossless: 45.16GB
Would it be possible to add an option to add another step to the demuxing process to transcode VC-1 sources to x264 lossless? With any VC-1 source I have to do this extra step now. Thanks much.
sneaker_ger
24th February 2019, 13:43
ffmpeg fixed the problems in April 2018. And since 1.2.0 HandBrake is ffmpeg based so if you tested it in January and had problems you were probably still on an old version.
I'm not sure what exactly RipBot did in your case (I see no log) but I assume the problem is probably with either ffms2 or l-smash plugins still being based on the old ffmpeg version.
Ryushin
24th February 2019, 22:23
ffmpeg fixed the problems in April 2018. And since 1.2.0 HandBrake is ffmpeg based so if you tested it in January and had problems you were probably still on an old version.
I'm not sure what exactly RipBot did in your case (I see no log) but I assume the problem is probably with either ffms2 or l-smash plugins still being based on the old ffmpeg version.
On the latest version 1.24.0 with the latest updates. So most likely ffms2 is still based on the old ffmpeg version. Good to know once that is updated I won't need to do lossless transcoding any longer for VC-1 sources.
katodevin
25th February 2019, 04:39
I managed to get my DE servers to work again by mounting a share on each of them so that the path that is set on the avs file is the same locally for each of them.
Basically, in the avs file, on each DE server,
FFVideoSource: Failed to open 'Y:\filename.mkv' (\\PCNAME\RipBot264temp\job4\Chunks\6.avs, line 7)
the "Y:" is wrong, it should be \\PCNAME\(...)". The path that is set in the avs file is only valid in the machine running ripbot.
My fix was making that path also valid on each DE server by sharing and mapping the share so that it matches.
This only happens since the last version, this was working fine previously, but the problem is definitly that.
fK
I can confirm that I'm seeing the same behavior on the latest version making distributed encoding not possible. Swapped back to the version from end of 2018, and everything works fine. Hopefully this gets seen/addressed as the distributed encoding is the most enticing feature of RipBot264 for me.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.