View Full Version : RipBot264 v1.18.3 - Simple and easy to use GUI -> IPOD . PSP . CONSOLES . BLURAY
light5out
19th January 2019, 17:52
I am trying to encode a .TS that is mpeg2. It was recorded from an OTA broadcast in the US. THe video is 29.97 but ripbot has the deinterlace option greyed out. Any idea why this would be?
https://imgur.com/a/GREKgvz
Atak_Snajpera
19th January 2019, 18:25
Upload 100-200 MB sample. I will take a look.
light5out
19th January 2019, 18:36
Upload 100-200 MB sample. I will take a look.
I don't know how to cut the file. I don't currently have a tuner to record a small sample it is coming in the mail. I sent the other one back.
Atak_Snajpera
19th January 2019, 18:53
I don't know how to cut the file. I don't currently have a tuner to record a small sample it is coming in the mail. I sent the other one back.
https://www.softpedia.com/get/System/File-Management/DGSplit.shtml
byteshare
19th January 2019, 19:46
I've brought it up before, but is it possible in the batch mode to set a custom crop?
I've been using the auto crop, but it doesn't always get it right.
Right now I have about 78 files that should all have a crop of L 240 and a R 240 but many (not all) are L238 R240 and all of those have a small black line on the left side, so I'm having to go through each job and check manually, which IMO defeats the purpose of the autocrop.
light5out
19th January 2019, 19:48
https://www.softpedia.com/get/System/File-Management/DGSplit.shtml
For some reason I can't load the download page, getting an error.
pepeq
19th January 2019, 20:11
you can download DGsplit from here:
http://rationalqm.us/mine.html
light5out
19th January 2019, 20:21
https://www.softpedia.com/get/System/File-Management/DGSplit.shtml
Thank man!
https://ufile.io/gj8t7
Here you go OP, hopefully that site works never used it before.
light5out
23rd January 2019, 17:13
Thank man!
https://ufile.io/gj8t7
Here you go OP, hopefully that site works never used it before.
I recorded the same show and have the same problem, I did a test of a random recording and it worked on that one, any idea why.
Again the options to deinterlace are greyed out.
Atak_Snajpera
23rd January 2019, 17:37
Option is greyed out because your video does not have constant frame rate. Detected FPS has to be 29.97 or 25.
BTW. I'm shocked that big broadcasters in USA still use MPEG-2 format for HD content. In EU only MPEG-4 AVC is used in HD (and probably in SD as well).
LigH
24th January 2019, 00:36
Germany still uses MPEG-2 for SD broadcasts via DVB-S.
light5out
24th January 2019, 06:19
Option is greyed out because your video does not have constant frame rate. Detected FPS has to be 29.97 or 25.
BTW. I'm shocked that big broadcasters in USA still use MPEG-2 format for HD content. In EU only MPEG-4 AVC is used in HD (and probably in SD as well).
Ok, so what do you recommend I do with it, I notice when I did an encode it came out at like 25.3 fps or something. (and it was way out of sync) Basically I just want to shrink it down.
Wishbringer
24th January 2019, 07:59
Anyone having problems with auto shut down?
Has already happeden 2 times on one PC
Received yesterday a new core update for RB 1.24.0.
Was hoping that issue with non-closing/ non-responding application would be solved.
Issue is still there: When trying to close RB (manuell or per checkbox after completing encode), window closes, but RB still shows up in taskbar, but isn't responding anymore.
So autoshutdown doesn't happen too.
New start of RB isn't possible except i kill task in taskmanager before.
Atak_Snajpera
24th January 2019, 13:03
Germany still uses MPEG-2 for SD broadcasts via DVB-S.
In Poland only MPEG-4 AVC exists even in SD.
light5out
24th January 2019, 16:28
Ok, so what do you recommend I do with it, I notice when I did an encode it came out at like 25.3 fps or something. (and it was way out of sync) Basically I just want to shrink it down.
Also can someone help me understand how to identify that it is variable framerate?
byteshare
24th January 2019, 16:41
Received yesterday a new core update for RB 1.24.0.
Was hoping that issue with non-closing/ non-responding application would be solved.
Issue is still there: When trying to close RB (manuell or per checkbox after completing encode), window closes, but RB still shows up in taskbar, but isn't responding anymore.
So autoshutdown doesn't happen too.
New start of RB isn't possible except i kill task in taskmanager before.
Which Windows Version are you on? Do you have antivirus or anything running? I haven't had this issue in Windows 7 or Windows 10.
Ok, so what do you recommend I do with it, I notice when I did an encode it came out at like 25.3 fps or something. (and it was way out of sync) Basically I just want to shrink it down.
Sometimes Media info can help see if the file is a variable FPS, or if you look at the FPS info while playing the file, if your video player shows the FPS in realtime.
As for syncing up the audio/video, have you tried TimeCodes?
https://forum.doom9.org/showthread.php?p=1849546&highlight=timecodes#post1849546
...try copying the timestamp file from source to your encoded file. This is especially helpful with variable frame rate files.
Extracting timecodes (windows batch file):
Code:
FOR %%A IN (*.mkv) DO "C:\Program Files\MKVToolNix\mkvextract.exe" timecodes_v2 "%%A" "0:%%A_timecodes.txt"
^^ The above is for running the batch file in the same folder as the video files that you want to extract the timestamp info from (source)
Batch importing with Encoded files in the same folder as the extracted timecodes .txt files(windows batch file)
Code:
FOR %%A IN (*.mkv) DO "C:\Program Files\MKVToolNix\mkvmerge.exe" -o "%%~A-fixed.mkv" --timecodes "0:%%A_timecodes.txt" "%%~A"
If you're working with something other than MKVs you'd want to change that in the scripts.
The above has the batch version but you can do this with MKVExtract and the GUI.
byteshare
24th January 2019, 16:44
HEVC 3.0 stable is out:
3.0+1-ed72af8
http://msystem.waw.pl/x265/
Release notes:
https://bitbucket.org/multicoreware/x265/commits/a6a12bc3ccf4b3138f1d62b2a81c9c40c3c88d62#chg-doc/reST/releasenotes.rst
+New features
+-------------
+1. option:: '--dolby-vision-profile <integer|float>' generates bitstreams confirming to the specified Dolby Vision profile. Currently profile 5, profile 8.1 and profile 8.2 enabled, Default 0 (disabled)
+
+2. option:: '--dolby-vision-rpu' File containing Dolby Vision RPU metadata. If given, x265's Dolby Vision metadata parser will fill the RPU field of input pictures with the metadata
+ read from the file. The library will interleave access units with RPUs in the bitstream. Default NULL (disabled).
+
+3. option:: '--zonefile <filename>' specifies a text file which contains the boundaries of the zones where each of zones are configurable.
+
+4. option:: '--qp-adaptation-range' Delta-QP range by QP adaptation based on a psycho-visual model. Default 1.0.
+
+5. option:: '--refine-ctu-distortion <0/1>' store/normalize ctu distortion in analysis-save/load. Default 0.
+
+6. Experimental feature option:: '--hevc-aq' enables adaptive quantization
+ It scales the quantization step size according to the spatial activity of one coding unit relative to frame average spatial activity. This AQ method utilizes
+ the minimum variance of sub-unit in each coding unit to represent the coding unit’s spatial complexity.
+
+Encoder enhancements
+--------------------
+1. Preset: change param defaults for veryslow and slower preset. Replace slower preset with defaults used in veryslow preset and change param defaults in veryslow preset as per experimental results.
+2. AQ: change default AQ mode to auto-variance
+3. Cutree offset reuse: restricted to analysis reuse-level 10 for analysis-save -> analysis-load
+4. Tune: introduce --tune animation option which improves encode quality for animated content
+5. Reuse CU depth for B frame and allow I, P frame to follow x265 depth decision
+
+Bug fixes
+---------
+1. RC: fix rowStat computation in const-vbv
+2. Dynamic-refine: fix memory reset size.
+3. Fix Issue #442: linking issue on non x86 platform
+4. Encoder: Do not include CLL SEI message if empty
+5. Fix issue #441 build error in VMAF lib
light5out
24th January 2019, 18:30
Which Windows Version are you on? Do you have antivirus or anything running? I haven't had this issue in Windows 7 or Windows 10.
Sometimes Media info can help see if the file is a variable FPS, or if you look at the FPS info while playing the file, if your video player shows the FPS in realtime.
As for syncing up the audio/video, have you tried TimeCodes?
https://forum.doom9.org/showthread.php?p=1849546&highlight=timecodes#post1849546
The above has the batch version but you can do this with MKVExtract and the GUI.
I have not done that and thank you. I am a noob when it comes to encoding. I am looking for an easy way to shrink DVR recordings. I have used ripbot in the past and like it, but the interlaced thing always seems to be a headache. I don't even need to deinterlace if there is a way to shrink the file but keep all that the same. Because the mpeg2's look great, they are just too big.
Wishbringer
24th January 2019, 21:39
@byteshare:
Three z270, 7700k, 64gb ram, 2tb 970 Evo, vega64 with Win10pro 17763.292 (at home)
Two x470, 2700x, 64gb, 1tb 960 Evo, RX550 with Win10pro 17134.xxx (at work)
Only ms defender as av.
Issue with each of them. One z270 has a fresh reinstall today (17763.107 iso + Cu292) + drivers.
Does not happen with an old local install of RB1.23.
LigH
24th January 2019, 21:56
@byteshare: It's not the HEVC standard, but the x265 encoder, which reached version 3.0.
Ryushin
25th January 2019, 02:18
When using using hevc, and clicking on the profile ... button, and selecting a tune, such as animation, the DE Client just keeps starting the servers over and over with no progress. Changing it back to default (removes the --tune option) allows it to work again.
The encoding server says:
x265 [error]: preset or tune unrecognized
LigH
25th January 2019, 08:13
Don't assume that x265 provides all the same tunings as x264; that's not true.
Ryushin
25th January 2019, 15:45
Don't assume that x265 provides all the same tunings as x264; that's not true.
Actually, that is an option provided by Atak in the hevc settings.
Looking at: https://x265.readthedocs.io/en/default/presets.html
Also shows the --tune animation option there.
Just bringing this to Atak's attention.
chainring
25th January 2019, 18:57
I've had the same error occur as Ryushin, and only when DE is active. Single machine processing, no problem.
Adding to this, another problem only in DE mode is, anytime I attempt to de-noise with KNLMeansCL (any mode, including adaptive), the encoding on remote servers stalls. All remote servers (two of them) have dedicated GPUs, and both show OpenCL to be active. I've installed all the Visual C++ runtimes via a repack from repacks.net. De-noising with only MDegrain2 works perfectly in DE mode, if it matters.
chainring
25th January 2019, 19:04
Separate issue from the DE enabled encoding above...
What's the proper way to add an Avisynth plugin? I'm trying to use AutoAdjust from LaTo at: https://forum.doom9.org/showthread.php?t=167573 . I've manually loaded the .dll in the script, and it shows to be shared when looking at the .avs in the chunks directory, yet encoding fails. I've tried both the 32 and 64 bit versions.
Thanks!
Atak_Snajpera
25th January 2019, 19:32
Separate issue from the DE enabled encoding above...
What's the proper way to add an Avisynth plugin? I'm trying to use AutoAdjust from LaTo at: https://forum.doom9.org/showthread.php?t=167573 . I've manually loaded the .dll in the script, and it shows to be shared when looking at the .avs in the chunks directory, yet encoding fails. I've tried both the 32 and 64 bit versions.
Thanks!
Have you copied all files to own folder in Tools\AviSynth plugins
chainring
25th January 2019, 20:47
Have you copied all files to own folder in Tools\AviSynth plugins
I did. Specifically, within \Tools\Avisynth plugins, I've created an AutoAdjust folder, then within that is the AutoAdjust.dll. I've tried both the 32 and 64 bit version.
Atak_Snajpera
25th January 2019, 20:56
Open 1.avs from server side in some media player and check an error message.
byteshare
25th January 2019, 21:25
@byteshare:
Three z270, 7700k, 64gb ram, 2tb 970 Evo, vega64 with Win10pro 17763.292 (at home)
Two x470, 2700x, 64gb, 1tb 960 Evo, RX550 with Win10pro 17134.xxx (at work)
Only ms defender as av.
Issue with each of them. One z270 has a fresh reinstall today (17763.107 iso + Cu292) + drivers.
Does not happen with an old local install of RB1.23.
Hmm, I can't think of what is common between both of your machines, and what is different about my 4 boxes that I'm not having that issue with. Maybe Atak might have an idea.
@byteshare: It's not the HEVC standard, but the x265 encoder, which reached version 3.0.
I didn't intend to make that claim, but yes, I agree with you and thank you for mentioning that if anyone was confused by that.
I can understand HEVC/x265 being confused, as I did...since they are synonymous to me at this point.
GZZ
26th January 2019, 09:21
Enlighten me on this one.
What is needed to reencode a movie including Dolby Vision, seeing the new x265 3.0 support several dolby vision profiles? A tool to extract the dolby vision data from a UHD in order to process it ?
Ryushin
27th January 2019, 16: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
So I installed XMedia Recode and I selected the DXVA decoder for VC-1 in the settings and I'm now saving it as a lossless jpeg. The preview did not show any artifacts. If it remains clean I'll use RB to encode that to x265.
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.
Spasm
27th January 2019, 20:24
with those settings one exe got assigned
NODE 0 from CPU 0 to CPU 23
second EXE got assigned
NODE 0 from CPU 0 to CPU 16
nothing on node 1
can't change BIOS settings at the moment, i'm remoting in at the moment.
Let me know once you can do this test. I have some suspicion about 32 thread limit in 32 bit process (EncodingServer.exe) using windows GetNumaProcessorNode (https://docs.microsoft.com/en-us/windows/desktop/api/winbase/nf-winbase-getnumaprocessornode)function.
Any progress? I have dual 14-core CPUs and I don't get anything on Node 1 either.
I'll try disabling cores, though not sure how.
Ryushin
28th January 2019, 13:35
The last few days I've had artifact issues with encoding a VC-1 blu-ray source.
So I installed XMedia Recode and I selected the DXVA decoder for VC-1 in the settings and I'm now saving it as a lossless jpeg. The preview did not show any artifacts. If it remains clean I'll use RB to encode that to x265.
Had to end up doing a lossless H.265 encode as input to RB as RB did not understand the lossless jpeg. The issue was very much the decoder.
Atak, let me know if you need the problem sample source.
Atak_Snajpera
28th January 2019, 13:58
Had to end up doing a lossless H.265 encode as input to RB as RB did not understand the lossless jpeg. The issue was very much the decoder.
Atak, let me know if you need the problem sample source.
Check this build
https://www.mediafire.com/file/2y243yl482bz47h/ffms2-20181016-f3c6b00-win64.7z/file
Extract files to Tools\AviSynth plugins\ffms\x64
Atak_Snajpera
28th January 2019, 13:59
Any progress? I have dual 14-core CPUs and I don't get anything on Node 1 either.
I'll try disabling cores, though not sure how.
No because I have no physical access to dual cpu machine.
Ryushin
28th January 2019, 18:31
Check this build
https://www.mediafire.com/file/2y243yl482bz47h/ffms2-20181016-f3c6b00-win64.7z/file
Extract files to Tools\AviSynth plugins\ffms\x64
This fixed the problem. Thanks so much.
Atak_Snajpera
28th January 2019, 20:02
This fixed the problem. Thanks so much.
Do not get to excited too early! Make sure that this version is frame accurate first! In other words check if chunks start from correct frame! There is good reason why I use two versions of ffms2 plugin in RipBot264.
Ryushin
28th January 2019, 21:13
Do not get to excited too early! Make sure that this version is frame accurate first! In other words check if chunks start from correct frame! There is good reason why I use two versions of ffms2 plugin in RipBot264.
Oh, I think I remember the other bug now about it being frame accurate. You fixed that last time I found an issue.
I guess I'll need to watch a large portion of it to be sure.
What about using a different decoder for vc-1 sources?
Atak_Snajpera
28th January 2019, 21:19
Oh, I think I remember the other bug now about it being frame accurate. You fixed that last time I found an issue.
I guess I'll need to watch a large portion of it to be sure.
What about using a different decoder for vc-1 sources?
Other decoders are not frame accurate. Especially those using DirectShowSource interface.
Ryushin
28th January 2019, 22:12
Other decoders are not frame accurate. Especially those using DirectShowSource interface.
Yep, 4 minutes in, corruption. So I'll revert that.
Maybe another way around this is to have an option to convert from VC-1 to h.264/5 lossless using a single machine and then encode from that. The user would have to know his source would grow much larger then the original.
byteshare
30th January 2019, 03:54
In the bottom right of the "RipBot264 Encoding Client" what does the button that looks like a yellow triangle with an exclamation mark in the middle do?
when I click it, I'm not really seeing much happen.
Update: Oh, got it...opens the EncodingClientLog.txt
NiGHTsC
30th January 2019, 04:26
Off-Topic
Jan 23,2019
Anyone ever noticed this...
So grateful you're still working on RB, Atak_Snajpera
jlpsvk
30th January 2019, 22:12
any plans to implement nvencc64?
BLKMGK
31st January 2019, 05:36
May have found a bug, I've only been able to repro it 2x although I'm nervous I may have accidentally triggered it far more often. Scenario is that I'm converting many TV shows one after another. Occasionally I will have batch added a series of shows and decide I need to add others and prioritize them higher than existing jobs. So I batch add those and slide them to the top to be processed ahead of the previously added batches. On at LEAST two occasions upon doing this I've reviewed the results and found a show with a different show's soundtrack muxxed in. Unfortunately finding these screwed up episodes is going to be nearly impossible considering the volume I'm working with :( I'm not sure this error is consistent, I sure hope not, but if I can reproduce it I will save the job files. I'm on v1.24.0 right now...
byteshare
31st January 2019, 09:09
any plans to implement nvencc64?
The dev can speak to this but unless something changed there aren't plans.
pepeq
31st January 2019, 13:14
any plans to implement nvencc64?
I asked Atak the same question,
see Ataks answer here:
https://forum.doom9.org/showthread.php?p=1862510#post1862510
forkicks
1st February 2019, 21:17
May have found a bug, I've only been able to repro it 2x although I'm nervous I may have accidentally triggered it far more often. Scenario is that I'm converting many TV shows one after another. Occasionally I will have batch added a series of shows and decide I need to add others and prioritize them higher than existing jobs. So I batch add those and slide them to the top to be processed ahead of the previously added batches. On at LEAST two occasions upon doing this I've reviewed the results and found a show with a different show's soundtrack muxxed in. Unfortunately finding these screwed up episodes is going to be nearly impossible considering the volume I'm working with :( I'm not sure this error is consistent, I sure hope not, but if I can reproduce it I will save the job files. I'm on v1.24.0 right now...
I can confirm this. In my case, i narrowed it down to a couple of files that i was trying to convert from avc to 265. The extraction phase could not get the video file from it, and would (wrongly) use the video265 file that was leftover on the Temp folder from the previous conversion, resulting in a file with the correct output name, wrong video track and correct audio track. Also, ripbot showed no error.
In my view, this could be fixed in one of two ways:
1 (and best): before every new file, clear all existing items in the temp folder. This way it would fail and detect the fail because no previous file would exist that could be reused
2: Try to detect when video track extraction fails better. No idea what was causing it to fail in the first place, the file read perfectly fine, no errors, no sync problems, nothing reported wrong at all by other programs (mkvtoolnix, for example).
This is a really big problem because i also run several dozen file batches per day, and now i can't be sure if my previous conversions are right or not. This is silent data corruption at its worst, and in my case, i caught it completely by chance. I'm running the latest version (could not find any updates just now).
Thank your for your time,
fK
GZZ
1st February 2019, 23:15
Tune --Animation isnt working. I have a Ma10 profile where tune is on default, chaning ot to animation and the encoding wont start. In DE mode it will just throggle between encoding and idle forever, chaning it to default and its all working again. Maybe its a bad command.
From the Profiles folder:
"--profile main10 --output-depth 10 --tune animation" - not working
"--profile main10 --output-depth 10" - Working fine.
activoice
2nd February 2019, 02:36
Posting this here to help anyone out who might find this useful.
RunCommandSuccess and RunCommandError were added to RipBot264.ini with version 1.24 and here is how I am using it to receive a notification on my phone whenever an encoding job completes
I have these 2 lines added to RipBot264.ini
RunCommandSuccess="C:\Scripts\RipbotSuccess.cmd" %JOB%
RunCommandError="C:\Scripts\RipbotError.cmd" %JOB%
In C:\Scripts\ I have curl.exe and the 2 batch files below
RipbotSuccess.cmd
c:\scripts\curl.exe -u {pushbullet token}: https://api.pushbullet.com/v2/pushes -d type=note -d title="Ripbot264" -d body=%1+"Job Completed Succesfully"
RipbotError.cmd
c:\scripts\curl.exe -u {pushbullet token}: https://api.pushbullet.com/v2/pushes -d type=note -d title="Ripbot264" -d body=%1+"Job Failed"
So with PushBullet installed on my phone I now get notifications whenever an encoding job completes
https://imgur.com/9utHM5s
BLKMGK
2nd February 2019, 05:58
I can confirm this. In my case, i narrowed it down to a couple of files that i was trying to convert from avc to 265. The extraction phase could not get the video file from it, and would (wrongly) use the video265 file that was leftover on the Temp folder from the previous conversion, resulting in a file with the correct output name, wrong video track and correct audio track. Also, ripbot showed no error.
In my view, this could be fixed in one of two ways:
1 (and best): before every new file, clear all existing items in the temp folder. This way it would fail and detect the fail because no previous file would exist that could be reused
2: Try to detect when video track extraction fails better. No idea what was causing it to fail in the first place, the file read perfectly fine, no errors, no sync problems, nothing reported wrong at all by other programs (mkvtoolnix, for example).
This is a really big problem because i also run several dozen file batches per day, and now i can't be sure if my previous conversions are right or not. This is silent data corruption at its worst, and in my case, i caught it completely by chance. I'm running the latest version (could not find any updates just now).
Thank your for your time,
fK
Well, at least it isn't just me! Sadly unlike when I was creating files with no soundtrack (don't check the "skip demuxing" box!) I cannot easily find the files with bad data. I am HOPING I caught it early by happenstance and got lucky as spot checking a pile of files didn't find bad ones but that would be a miracle if true!
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.