View Full Version : RipBot264 v1.18.3 - Simple and easy to use GUI -> IPOD . PSP . CONSOLES . BLURAY
tkwou
25th October 2017, 20:12
Hi Atak_Snajpera, just curious about 1.21.0 compared to 1.19.6 that I was using before. I notice that ffmsindex.exe indexes the video file now when it is first added, and then the video file is indexed again once encodingclient.exe opens before the distributed encoding starts.
byteshare
26th October 2017, 16:08
Hi Atak_Snajpera, just curious about 1.21.0 compared to 1.19.6 that I was using before. I notice that ffmsindex.exe indexes the video file now when it is first added, and then the video file is indexed again once encodingclient.exe opens before the distributed encoding starts.
There are several changes, but one of the most important is the switch to full 64bit AVISynth. A full change log is here:
https://www.videohelp.com/software/RipBot264/version-history#changelog
tkwou
26th October 2017, 19:25
Thanks byteshare. I was just curious about the added video indexing step. ffmsindex.exe indexes the *.mkv file when it is first added in Ripbot264 GUI to produce *.mkv.ffindex and *.mkv.ffindex_track00.kf.txt files. When encodingclient.exe opens it copies the video.mkv file to the shared folder and then ffmsindex.exe reindexes that file again to create video.mkv.ffindex and video.mkv.ffindex_track00.kf.txt. It just seems redundant.
POTI
30th October 2017, 01:34
So the auto download on the 28th said it contained a virus
VSRip.exe contained Trojan Fuerboos.A!cl
Atak_Snajpera
30th October 2017, 11:55
So the auto download on the 28th said it contained a virus
VSRip.exe contained Trojan Fuerboos.A!cl
Nope!
https://www.virustotal.com/#/file/c378767e06f9c6b1d3636f31750ba4ad205ac3cf09efc8b2e2d0f1fb8619be88/detection
byteshare
30th October 2017, 16:29
Is there anyway to get some of the log info into the media info? Such as the SSIM/PSNR data?
JASAN
30th October 2017, 20:03
I'm sorry if this has been asked before, I did a search and didn't find results here.
I'm still using version 1.19.3, I had some issues with distributed encoding and subtitles on 1.21.
Is there any way to add the ability to batch process m2ts files? Its not a recognized filetype at least in 1.19.3.
If I change the files to mts, ripbot will import successfully, but it will not use distributed encoding.
I use it to compress blu-ray tv episodes, lots of files to compress.
Thanks for all your work.
Atak_Snajpera
31st October 2017, 14:55
I had some issues with distributed encoding and subtitles on 1.21.
What issues?
byteshare
31st October 2017, 16:30
I'm sorry if this has been asked before, I did a search and didn't find results here.
I'm still using version 1.19.3, I had some issues with distributed encoding and subtitles on 1.21.
Is there any way to add the ability to batch process m2ts files? Its not a recognized filetype at least in 1.19.3.
If I change the files to mts, ripbot will import successfully, but it will not use distributed encoding.
I use it to compress blu-ray tv episodes, lots of files to compress.
Thanks for all your work.
I personally remux my m2ts files, but those should be work able in RibBot, last time I tried it at least.
As for your Distributed Encoding (DE) issues, we'd need more info as I personally am not having issues with using DE.
JASAN
31st October 2017, 18:30
Issues,
was getting random avs2yuv.exe crash errors on client machines used to run the encoding server.
Sometimes they would work for a full movie or two, sometimes not, and the incomplete chunks would still get written to the movie file, causing skips and such.
the second issue was subtitles would sometimes flash sporadically even though they were proper srt files with good timing.
Both issues went away when I reverted back to 1.19.3
JASAN
31st October 2017, 18:44
I personally remux my m2ts files, but those should be work able in RibBot, last time I tried it at least.
As for your Distributed Encoding (DE) issues, we'd need more info as I personally am not having issues with using DE.
Ripbot for sure takes single m2ts files, but not in batch mode. Also it won't keep the filenames, it changes them all to "video.xxx"
I'm just looking to see if there is a better workflow I should be using, it's right now an all manual process, since it's tv episodes, it can take a while.
Right now I rip, then take out the individual m2ts which are episodes, name them their proper names, add to ripbot individually, name them again in ripbot, queue up and distribute encode them all.
Ive tried renaming them from m2ts to .ts or .mts or .m2t, and ripbot will add them all and compress, but distributed encoding never works for me when they are added as a batch.
I'm probably doing something wrong
Atak_Snajpera
31st October 2017, 19:01
the second issue was subtitles would sometimes flash sporadically even though they were proper srt files with good timing.
Known issue. Disable "Use Multiple processing threads" option. This should also fix crashing when burning subtitles on frames.
I will see what I can do with those file names.
UPDATE:
v1.21.1
Uses original file name correctly
http://i.cubeupload.com/ykfT9c.png
JASAN
31st October 2017, 19:56
Known issue. Disable "Use Multiple processing threads" option. This should also fix crashing when burning subtitles on frames.
I will see what I can do with those file names.
UPDATE:
v1.21.1
Uses original file name correctly
http://i.cubeupload.com/ykfT9c.png
Thanks for everything, this program works like a champ.
cyperous
1st November 2017, 21:05
When I try to add a muxed mkv that contains a TrueHD+Atmos track I get an error the the items fails to be loaded into ripbot. I've tried batch and just single add both fail though only the single add throws the error. Batch just errors silently and doesn't add the item to the list of encodes.
getinfo.avs:
LoadPlugin("C:\Tools\RipBot264\Tools\AviSynth plugins\ffms\ffms_latest\x64\ffms2.dll")
video=FFVideoSource("D:\Rips\4KMovies\The Fifth Element (1997)\Moments - Zorg-featurette.mkv",cachefile = "D:\Temp\RipBot264temp\job1\Moments - Zorg-featurette.mkv.ffindex",colorspace="YV12")
LoadPlugin("C:\Tools\RipBot264\tools\AviSynth plugins\ffms\ffms_latest\x64\ffms2.dll")
audio=FFAudioSource("D:\Temp\RipBot264temp\job1\1_audio_English.thd")
AudioDub(video,audio)
WriteFile("D:\Temp\RipBot264temp\job1\info.txt","Framecount")
WriteFile("D:\Temp\RipBot264temp\job1\info.txt","Framerate")
WriteFile("D:\Temp\RipBot264temp\job1\info.txt","AudioRate")
WriteFile("D:\Temp\RipBot264temp\job1\info.txt","AudioChannels")
WriteFile("D:\Temp\RipBot264temp\job1\info.txt","AudioLength")
WriteFile("D:\Temp\RipBot264temp\job1\info.txt","Width")
WriteFile("D:\Temp\RipBot264temp\job1\info.txt","Height ")
Trim(0,-1)
filelist:
./1_audio_English.thd
./1_audio_English.thd.ffindex
./chapters.txt
./FFmsindex.cmd
./getAVSerror.cmd
./getinfo.avs
./job1.avs
./job1_a1.avs
./job1_a2.avs
./MKVExtract.cmd
./mkvinfo.txt
./Moments - Zorg-featurette.mkv.ffindex
./Moments - Zorg-featurette.mkv.ffindex_track00.kf.txt
./test.log
AMZMA
2nd November 2017, 14:46
hello, Atak
I've been using your MediaInfo GUI for more than 5 years and I really love it, in fact I already attached to it.
While expressing my gratitude, I want to ask (request) you about blurry text on 1080 display. And can you make it Exit when Escape key pressed? And please give a icon on taskbar.
Thank you so much. I really appreciate it.
byteshare
2nd November 2017, 16:10
UPDATE:
v1.21.1
Uses original file name correctly
http://i.cubeupload.com/ykfT9c.png
Is there a way to stop RipBot from converting "." to spaces?
Right now I rip, then take out the individual m2ts which are episodes, name them their proper names, add to ripbot individually, name them again in ripbot, queue up and distribute encode them all.
Try ripping the them to mkv with MakeMKV the free activation code is in their forums.
was getting random avs2yuv.exe crash errors on client machines used to run the encoding server.
Sometimes they would work for a full movie or two, sometimes not, and the incomplete chunks would still get written to the movie file, causing skips and such.
I have this issue two. I've been told the issue is with my AVISynth script. What I do to work around this is don't close the error message before you turn off that encoding client, what I mean is if Server 1 throws the error turn it off on the client (Enocding status to Off status), close the error, and then start the Server again from the encoding client (Off status to On status).
the second issue was subtitles would sometimes flash sporadically even though they were proper srt files with good timing.
As Atak_Snajpera saied: "Known issue. Disable "Use Multiple processing threads" option. This should also fix crashing when burning subtitles on frames.
I will see what I can do with those file names."
I generally handle audio and subs externally as RipBot doesn't do a good job (i.e. make it easy to copy/convert all of them) batching files with several subs and/or audio files.
Ryushin
4th November 2017, 00:09
Atak, truly you are amazing to still be supporting and adding more features all the time to RipBot264. I very much appreciate all your hard work. Just upgraded to the 1.21.x builds. Just have a couple of questions.
What does "Decoding Threads" do in the Distributed Encoding tab.
Is there anything I can do to speed up the demuxing? On my wife's new Ryzen 1800X machine it can demux an tv episode in 3 minutes to spinning rust. On a AMD server, and a Win10 virtual machine, with 48 2.1Ghz cores, it takes over 9 minutes, also to spinning rust . The demuxing process seems to mostly be single threaded from watching task manager. Any ideas on a way to speed this up?
Tazlord
4th November 2017, 07:14
I know this topic has been discussed here before but I can't seem to find the solution this this problem anywhere. Any help would be greatly appreciated.
ISSUE
When trying to enable encoding on a remote server I am receiving the following error:
https://preview.ibb.co/gSw0vw/2017_11_03_22_42_26_Windows_10_Pro_x64.png
INFORMATION
Server host is Windows 10 x64.
The system running RipBot264 main application is also Windows 10 x64.
The remote server is able to open and access files in the RipBotTemp folder. I have verified this through Windows Explorer.
AviSynth+ MT x64 has been installed on the server host (see screenshot above).
Atak_Snajpera
4th November 2017, 13:19
What does "Decoding Threads" do in the Distributed Encoding tab.
Other user asked the same question in private message...
If you set Decoding Threads to 0 then all your cpu threads will be used during decoding process. In some rare situations It will eliminate bottleneck in case when x264 can process frames faster than decoder can provide. In old days multi-threaded decoding was very buggy hence I set safe value of 1 (single thread).
Currently I do not think that this is still necessary and multi-threaded decoding should not cause any crashes.
On a AMD server, and a Win10 virtual machine, with 48 2.1Ghz cores, it takes over 9 minutes, also to spinning rust .
Maybe it is a problem with virtualization?
@Tazlord
You most likely do not have VC++ redist 2015 (x64) installed on that machine.
Tazlord
4th November 2017, 16:52
@Tazlord
You most likely do not have VC++ redist 2015 (x64) installed on that machine.
Thanks! That was it! I had 2008 and 2012 installed but I guess AviSyth+ MT needs 2015. Thanks again.
Ryushin
4th November 2017, 18:42
Maybe it is a problem with virtualization?
I was thinking that originally as well. Spent three days working on that. I was able to remove a couple of bottlenecks. Now it looks like the system has plenty of resources to spare. It's pegged one core to the max and I'm thinking that is limiting the demuxing process. Not sure if it can be threaded any further or not.
The Ryzen proc is just amazing. Thinking of going with the server version of it for my main server in the future.
Image of the processors and system load for the VM:
https://s26.postimg.org/wclagfllx/CPU_Load.png (https://postimg.org/image/wclagfllx/)
Atak_Snajpera
4th November 2017, 19:20
Thinking of going with the server version of it for my main server in the future.
You mean EPYC?
Ryushin
4th November 2017, 20:50
You mean EPYC?
Yep. Everything comes down to money though.
Atak_Snajpera
4th November 2017, 21:12
Instead of very expensive EPYC 32c/64t (2.2 GHz) I would rather choose overclocked ThreadRipper 16c/32t (~4GHz).
-Cheaper motherboard and CPU
-Similar multithreaded performance
-Better single threaded performance
klopsknoedel
4th November 2017, 22:57
Heyho,
I've found that 1.21.1 (and 1.20) looses the language information on the 2nd audio track. I can see this on all of my jobs.
!Sometime! even the first track does not have a language set. For now I can't tell if it is due to a specific codec or anything else.
This is not a big deal but sometimes this language is even missing inside the "jobXXX_MuxFiles.cmd" - files which leads into a merge-error. Unfortunatly from then I can't run this file by hand as the converted files allready got deleted by ripbot.
So this:
--compression 0:none --language 0: --sync 0:0 "D:\Temp\RipBot264temp\job86\audio_2_English.core.dts"
has to look like this:
--compression 0:none --language 0:eng --sync 0:0 "D:\Temp\RipBot264temp\job86\audio_2_English.core.dts"
http://cdn.s-hofmann.de/languagebug.png
slalom
6th November 2017, 17:26
What can you tell me about this error?
error: failed to load avisynth.dll
y4m [error]: bad sequence header magic
x264 [error]: could not open input file `-'
I have the same updated ripbot folder on all PCs
This came on one PC on both encoding servers
new to using v.1.21.1
Atak_Snajpera
6th November 2017, 18:18
You have solution literally on the same page.
slalom
6th November 2017, 20:14
You're talking about AviSynth+_FE_0.1.0.2508_X64
It fixed the problem, but why was it on only one PC? (nevermind, don't wanna know)
Is there a reason for a wider Ripbot264 program window?
It won't fit side by side with the servers window on 1680 pixels
Just wondering
MaistroX
7th November 2017, 10:25
Hi Atak_Snajpera,
Is there a reason that RipBot dno´t recognise a UHD file as ex: "00001.track_4113.hevc"?
How do I add it to RipBot so I can encode it?
Regards MaistroX
guest
8th November 2017, 07:56
Hi Atak,
So "we've" had 2 auto updates in the last week, and have no idea what has changed...:(
I know I've asked several times before, can you PLEASE add a changelog.txt with the updates !?!?!?
Also, are you going to post the "full" version of 1.12.1 on the 1st page, and update the changelog there....
Cheers :thanks:
Ryushin
8th November 2017, 14:18
Instead of very expensive EPYC 32c/64t (2.2 GHz) I would rather choose overclocked ThreadRipper 16c/32t (~4GHz).
-Cheaper motherboard and CPU
-Similar multithreaded performance
-Better single threaded performance
I'd rather use a higher clocked chip for sure. I'll have to see if they have a EPYC version at some point in time. I have a Supermicro server chassis so I use their motherboards. Hopefully Supermicro will make a ThreadRipper motherboard with ECC memory.
I have encountered a bug in 1.21.1. Sometimes when I'm editing a job when encoding is running, the job that is starting will be transposed with the job that I'm editing. I need to close RipBot264 and go and edit the jobs.list file to fix what was replaced. The bug changes the job number along with the job name. Putting the information back into jobs.list allows me to get the job back that was transposed.
BTW, absolutely phenomenal job with the new version of RipBot264 and Avisynth MT. I'm now seeing about 30fps when using mdegrain instead of 5fps with my setup.
Atak_Snajpera
8th November 2017, 17:00
Btw. How many fps do you have in my benchmark http://forum.pclab.pl/topic/1184884-x265-FHD-Benchmark/ on that AMD Opteron?
Ryushin
8th November 2017, 22:26
Btw. How many fps do you have in my benchmark http://forum.pclab.pl/topic/1184884-x265-FHD-Benchmark/ on that AMD Opteron?
Current Setup:
Server 1:
CPUs: 4 sockets, AMD Opteron 6172, 12 cores each proc, 48 cores total.
Devuan Linux
Windows 10 VM running under QEMU KVM with 44 cores
Benchmark Results:
2 x AMD Opteron 23xx (Gen 3 Class Opteron) @ 2.1GHz ( 22C / 22T )
encoded 2500 frames in 172.67s (14.48 fps), 7025.74 kbps, Avg QP:37.21
Server 2:
AMD Ryzen 7 1800X Eight-Core @ 3.6GHz ( 8C / 16T )
encoded 2500 frames in 108.78s (22.98 fps), 7025.74 kbps, Avg QP:37.21
Server 3 and 4:
Dell R610s
2 x Intel Xeon X5550 @ 2.66GHz ( 4C / 8T )
encoded 2500 frames in 197.02s (12.69 fps), 7025.74 kbps, Avg QP:37.21
Not so sure if the benchmark is a good test for that many cores or not. When using the distributed encoding, I give the Opteron server 4 instances to fully utilize the system. Before 1.21.x I had to give it 6 instances.
But I'm so impressed with Ryzen. That single CPU is pretty much doing half as much work as that quad AMD for most tasks. But with mdegrain2, the Ryzen is matching the quad AMD.
Atak_Snajpera
9th November 2017, 12:02
Benchmark uses 5 instances of x265. CPU usage should be at 100%. (prease verify)
I'm surprised that 44 cores @ 2.1 GHz gives only 14.5 fps. That's basicaly Intel Core i5-7400 @ 3.5GHz ( 4C / 4T ) level !
Ryushin
10th November 2017, 14:48
Benchmark uses 5 instances of x265. CPU usage should be at 100%. (prease verify)
I'm surprised that 44 cores @ 2.1 GHz gives only 14.5 fps. That's basicaly Intel Core i5-7400 @ 3.5GHz ( 4C / 4T ) level !
In the beginning of the test it is using all the cores and running about 16.8fps (which still is not that great), but right at the end of the test, when some of the threads have finished, it drops to 14.5fps which is what it records. The G3 Opteron may be missing some cpu extensions for x265 optimizations.
I've been thinking I may move the VM to another one of my servers and I may reload the Opteron server with Server 2013. Another project for me. :)
Toku
12th November 2017, 10:17
Hi Atak - Thanks so much for this software. Without software like Ripbot offering distributed encoding - encoding in H265 would be pretty much impossible with current consumer grade hardware.
One request - are you able to add the option to choose no audio tracks in Batch mode? I like to deal with audio tracks separately and mux them together after the encode. When using batch mode, the option to choose no audio tracks doesn't seem to be there?
lemaireus
12th November 2017, 19:24
Atak, each time I load an .mkv video with DTSHD-MA audio into Ripbot for encoding, the audio track straightaway encodes itself into a FLAC file. Is there any way I can change that behaviour?
I prefer what Ripbot does with blu ray discs, where it provides the option to decode to .wav or use the core or keep the track unchanged. In mkv files with DTSHD-MA, Ripbot doesn't offer me any option; it straightaway encodes the DTSHD-MA into a FLAC track. I wish I had the option to decode to .wav and then encode into AC3 or keep DTS core, basically use the same options which we can use in encoding blu ray discs. I know that I can encode the FLAC into an AC3 but I'd still prefer if Ripbot offered me all the options it does with blu ray discs even when I am encoding an mkv or a BDRemux with DTSHD-MA audio.
If those options are available and it's just that I haven't yet figured them out, I'd be thankful if you could point me in the right direction about configuring those options.
Atak_Snajpera
13th November 2017, 14:34
Atak, each time I load an .mkv video with DTSHD-MA audio into Ripbot for encoding, the audio track straightaway encodes itself into a FLAC file. Is there any way I can change that behaviour?
Update to 1.21.x
Ryushin
13th November 2017, 15:40
Hi Atak,
First the UI Reqeust. When using MDegrain, is it possible to add two arrow boxes like you do for HQDN3D? One for selecting what level of MDegrain, 1-3 and another one for the thSAD value and perhaps have the arrows change the value up or down by 25 or allow you to just type into the box the value you want.
Also, as a general usage for HQDN3D, I found that setting the temporal value as half of what the denoising value and rounding down give me good results. So 4422, 5522, 6633, 7733, 8844, etc.
Now about the Distributed Encoding (DE) issue. I've extracted a couple of clips that show the problem which can be downloaded from here:
https://cloud.chrisdos.com/index.php/s/gm6HakAT9J2WLr7
During the camera panning there are several skipped frames when using DE.
At first I thought the issue was relating to degraining while using DE and I tried quite a few options but the problem was still there. On a whim I turned off DE and then the skipped frames where no longer an issue. Is there anything I can do to help with the debugging? Do you need access to the original source file?
Atak_Snajpera
13th November 2017, 16:21
Do you need access to the original source file?
yes...
JASAN
20th November 2017, 22:19
Known issue. Disable "Use Multiple processing threads" option. This should also fix crashing when burning subtitles on frames.
I will see what I can do with those file names.
UPDATE:
v1.21.1
Uses original file name correctly
http://i.cubeupload.com/ykfT9c.png
Atak, where do I download the version that fixes the renaming of the files? I have some time this week to test and I just see 1.21.0 for the downloads...
Thanks again
Ryushin
21st November 2017, 04:45
Hi Atak,
Encountered something new. When clicking okay on the Avisynth window, there is a large disk load that takes about five minutes to complete before the window actually closes.
https://s26.postimg.org/wim64l0yt/Ripbot264_Disk_Load.png (https://postimg.org/image/wim64l0yt/)
Not sure what would be the cause of that issue.
Atak_Snajpera
21st November 2017, 09:51
Are you still on virtual machine?
guest
21st November 2017, 10:04
Atak, where do I download the version that fixes the renaming of the files? I have some time this week to test and I just see 1.21.0 for the downloads...
Thanks again
You'll have to download that available version, make sure auto updates are enabled, and then run the program which will download the updates, and they will be installed the next time you start the program, and it should be up to date...(you should see the update notice working, as Ripbot starts)
Ryushin
21st November 2017, 18:35
Are you still on virtual machine?
Yep. The picture is showing a large load of 100MB/s though for a long period of time.
Ran some benchmarks. It's me. The raw disk image grew and performance went south. Back to disk/vm tuning for me.
byteshare
22nd November 2017, 20:07
Hi Atak,
Encountered something new. When clicking okay on the Avisynth window, there is a large disk load that takes about five minutes to complete before the window actually closes.
https://s26.postimg.org/wim64l0yt/Ripbot264_Disk_Load.png (https://postimg.org/image/wim64l0yt/)
Not sure what would be the cause of that issue.
This is not an "issue" as it is regenerating the info.txt, and it is just slow on your machine. I'd rather it didn't if it did a check for info.txt but at least it always does which saves me when a few random jobs don't have the info.txt for some reason.
Ryushin
24th November 2017, 06:43
Ended up throwing in the towel as it really looks like I encountered some kind of KVM bug with the storage. Reloaded the whole system bare metal with Server 2012 R2. Still getting some thing set up before I start testing. Disk access seems far better now. So hopefully the slowness will be gone. Ran the x265 benchmark and it's only using about 20-30% of the system.
https://s26.postimg.org/6xbbquskl/x264_FHD_Bencmark.png (https://postimg.org/image/6xbbquskl/)
Atak_Snajpera
24th November 2017, 13:14
Testing performance on virtual machine is pointless.
Ryushin
24th November 2017, 15:32
Testing performance on virtual machine is pointless.
It's no longer a virtual machine. Bare metal 2012 R2.
forkicks
24th November 2017, 17:30
Hi. I have a problem with 1.21, all mp4 files i throw at it fail after copying the file to the shared folder (right at the start of encoding), with
Exception EFOpenError in module EncodingClient.exe at 000241AE. Cannot open file "c:\temp\ripbot264temp\job1\info.txt". The system cannot find the file specified.
This happens with all mp4s, and only with mp4s. If i throw mkvs at it, it works fine. I took a look at the mp4getinfo.cmd that gets created in the job folder, and there is an issue with it (at least with it, havent checked others). The command it runs, if i run it at the command line, outputs its result to the console, not the file. If i add "2>&1" at the end of it, then it sends its output to the file. I assume the info.txt file is then created from info taken from the mp4info.txt file, and this is the root cause of the problem.
Example:
(from mp4getinfo.cmd)
"D:\Desktop\RipBot264\Tools\mp4box\mp4box.exe" -info "E:\OldJ\conv\FILE.mp4" >> "C:\Temp\RipBot264temp\job1\mp4info.txt"
results in a 0 byte mp4info.txt (and a missing info.txt).
but running instead
"D:\Desktop\RipBot264\Tools\mp4box\mp4box.exe" -info "E:\OldJ\conv\FILE.mp4" >> "C:\Temp\RipBot264temp\job1\mp4info.txt" 2>&1
creates a proper mp4info.txt file.
Apparently mp4box is outputing to stderr instead of stdout, even if its normal output (there is no error, the file is perfectly fine).
Again, this happens on ALL mp4 files i throw at it. I'm running the program as downloaded from the first post. This did not happen with 1.20.1.
Thanks for a great piece of software.
fK
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.