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

[guest]

I found an issue with RipBot264 :

1. If the File name contains this symbol " – " (it's called En-dash as per
Google), then ripbot doesn't detect the Audio of the video file.
It says "No Audio" .

2. But If I remove the " – " from the file name, it starts
detecting the Audio.

Screenshots are attached as proof...Please fix this.

I bet you signed up, just to comment on this known problem.

You'll probably find that there are many other symbols/characters that will cause issues.

I doubt that it can be "fixed" within RipBot, however, you've already figured out how to work around this, so just go with that, and edit any file names with these symbols...easy peasy.

And, BTW, FYI, because you're new here, any attachments take "forever" to be approved, you would be a lot better off to use site's like "Imgur" or similar to post screenshots, etc.

[kingpin]

I bet you signed up, just to comment on this known problem.

You'll probably find that there are many other symbols/characters that will cause issues.

I doubt that it can be "fixed" within RipBot, however, you've already figured out how to work around this, so just go with that, and edit any file names with these symbols...easy peasy.

And, BTW, FYI, because you're new here, any attachments take "forever" to be approved, you would be a lot better off to use site's like "Imgur" or similar to post screenshots, etc.
Thanks for the Info. Yes, I am new here.

First, I was like, maybe it doesn't support some audio types or maybe something is wrong with these video files, so I tried to process them using other softwares then Ripbot. Then after a month of this, suddenly I figured out it was because of "File Name" ... I was like what a waste..lol.

Is there a section where I can find all the known issues ??

Also thanks for the "Imgur" tip, I will use that.

[guest]

Thanks for the Info. Yes, I am new here.

First, I was like, maybe it doesn't support some audio types or maybe something is wrong with these video files, so I tried to process them using other softwares then Ripbot. Then after a month of this, suddenly I figured out it was because of "File Name" ... I was like what a waste..lol.

Is there a section where I can find all the known issues ??

Also thanks for the "Imgur" tip, I will use that.

Hello, again,

You're welcome :)

So even though you're new to the forum, how long have you been using RipBot ??

Are you using Atak's original build's, or are you trying Pauly Dunne's ??

The latter is very update, & has many, many filtering options, I can fully recommend it.

As for a section on "known issues", sadly there really isn't one, and searching this thread looking for specific info is pretty time consuming.

Fortunately though, there aren't too many issues with RipBot, but there's ALWAY's room for improvement.

There is some info on the builds & some feedback comments here:-

https://www.videohelp.com/software/RipBot264/version-history#changelog

and here:-

https://www.videohelp.com/software/RipBot264

Good luck.

[guest]

Here we go yet again...

There has been a few new components become available in the 24 hours or so..

https://www.mediafire.com/file/c5tzrl0jkzy3mts/RipBot264_PD+Tools+(14-11-22).7z/file

So for the ppl that use my build, simply unpack, and overwrite ALL the files & folders, they will find their own "home".

And here's a twist, Atak had released an autoupdate, updating several components, BUT they are STILL not the latest available :(

So if anyone downloaded & installed the update package, for Atak's version, I posted a few days ago, you might have to repeat the process, IF you've allowed the autoupdate, if not, then it's not a problem.

Also, for those using Atak's build, there are some files in this update, that you can copy over.

eg:- MKVToolNix, MPC & x265, but that's ALL !!!!

PS:- I had a problem with the autoupdate download for Atak's version, there was/is a network problem somewhere, and I could not get it to download, even manually, and I still MANY times. (ffmpeg)

http://atak-snajpera.5v.pl/ripbot264update, doesn't reflect the latest version numbers & dates... :confused:

[gabbett1]

OK, well that is pretty much exactly the same as the first error msg you posted, so at least it's consistent !!!

Are you having problems with other demuxing ???

Maybe there is something wrong with this particular file.

Would you be able to upload a sample ??

May I suggest that you run this thru MKVToolNix, and remove all the stuff you don't want with that, THEN see what RipBot does, OR you could run only the video track thru RipBot and mux it back with ToolNix, later,

Use ToolNix to demux the video track, then import it into RB.

So it looks like it's any newer movie that it's having trouble demuxing. Not sure what to do.

[guest]

So it looks like it's any newer movie that it's having trouble demuxing. Not sure what to do.

Hi gabbett,

I recall another user was having an issue with something very similar to this, and I think he found a workaround...

Have a look here, and several posts after it...might help.

https://forum.doom9.org/showthread.php?p=1972082#post1972082

I think you will find that it's a problem with eac3to, not RipBot.

[Ryushin]

So it looks like it's any newer movie that it's having trouble demuxing. Not sure what to do.

If you are pulling in a 4K UHD ripped source then you will have to use the eac3to that comes with Atak's build. The newer versions of eac3to don't seem to work. It could be there is a new command line option that isn't being used by RB that is causing the error. Either way, rolling back to RB's eac3to version allows it to work fine.

[gabbett1]

If you are pulling in a 4K UHD ripped source then you will have to use the eac3to that comes with Atak's build. The newer versions of eac3to don't seem to work. It could be there is a new command line option that isn't being used by RB that is causing the error. Either way, rolling back to RB's eac3to version allows it to work fine.

No, I'm not doing 4K UHD disks.

[guest]

I downloaded Pauly's and I am getting this error now.

eac3to v3.34
command line: "C:\Users\Plex Server\Desktop\Dunne Ripbot\Tools\eac3to\eac3to.exe" "D:\Rip\BULLET_TRAIN" 1) 2: "C:\Temp\RipBot264temp\job1\video.mkv" -seekToIFrames 3: "C:\Temp\RipBot264temp\job1\audio_1_English.dtsma.w64" -down16 -dcadec 10: "C:\Temp\RipBot264temp\job1\10_subtitles_English_1080.sup" 11: "C:\Temp\RipBot264temp\job1\11_subtitles_English_1080.sup" 12: "C:\Temp\RipBot264temp\job1\12_subtitles_Chinese_1080.sup" 13: "C:\Temp\RipBot264temp\job1\13_subtitles_Chinese_1080.sup" 14: "C:\Temp\RipBot264temp\job1\14_subtitles_French_1080.sup" 15: "C:\Temp\RipBot264temp\job1\15_subtitles_Korean_1080.sup" 16: "C:\Temp\RipBot264temp\job1\16_subtitles_Portuguese_1080.sup" 17: "C:\Temp\RipBot264temp\job1\17_subtitles_Spanish_1080.sup" 18: "C:\Temp\RipBot264temp\job1\18_subtitles_Thai_1080.sup" 19: "C:\Temp\RipBot264temp\job1\19_subtitles_French_1080.sup" 20: "C:\Temp\RipBot264temp\job1\20_subtitles_English_1080.sup" 21: "C:\Temp\RipBot264temp\job1\21_subtitles_Chinese_1080.sup" 22: "C:\Temp\RipBot264temp\job1\22_subtitles_Korean_1080.sup" 23: "C:\Temp\RipBot264temp\job1\23_subtitles_Portuguese_1080.sup" 24: "C:\Temp\RipBot264temp\job1\24_subtitles_Spanish_1080.sup" 25: "C:\Temp\RipBot264temp\job1\25_subtitles_Thai_1080.sup" 1: "C:\Temp\RipBot264temp\job1\chapters.txt" -progressnumbers -log="C:\Temp\RipBot264temp\job1\demuxlog.txt"
------------------------------------------------------------------------------
M2TS, 1 video track, 7 audio tracks, 16 subtitle tracks, 2:06:32, 24p /1.001
1: Chapters, 17 chapters
2: h264/AVC, 1080p24 /1.001 (16:9)
3: DTS Master Audio, English, 5.1 channels, 16 bits, 48kHz
(core: DTS, 5.1 channels, 1509kbps, 48kHz)
4: AC3, English, 5.1 channels, 384kbps, 48kHz, -8ms
5: DTS Master Audio, French, 5.1 channels, 16 bits, 48kHz
(core: DTS, 5.1 channels, 1509kbps, 48kHz)

Just re-visiting this post, now I know my eyesight isn't that good anymore, but where is the actually error ??

One thing I've just noticed is the version number of eac3to, I'm pretty sure that Pauly's should be v3.36 ?? :confused:

And if you're not ripping UHD disc's, you must be getting them another way (won't say what way that is), but of course they would have been ripped to start with.

Did any of my suggestions work, meaning running it thru MKVToolNix first ??

Would you able to upload a sample of the movie you're having trouble with ??

You can do this with MKVToolNix if you want, just load the file, then go to the "Output" tab, choose the "splitting" option, and select or add the length or size you want it split to, then run it until it's completed at least one "chunk", then you can stop it.

Upload to Mediafire or similar.

Anyway, the choice is yours, if you have found a "workaround", then you're set to go, with future problems.

Cheers

[guest]

If you are pulling in a 4K UHD ripped source then you will have to use the eac3to that comes with Atak's build. The newer versions of eac3to don't seem to work. It could be there is a new command line option that isn't being used by RB that is causing the error. Either way, rolling back to RB's eac3to version allows it to work fine.

The mystery deepen's...

Problem is, he gets the same error with either Atak's or Pauly's, but I've just noticed an eac3to version discrepancy...(see my post, above)

[gabbett1]

Just re-visiting this post, now I know my eyesight isn't that good anymore, but where is the actually error ??

One thing I've just noticed is the version number of eac3to, I'm pretty sure that Pauly's should be v3.36 ?? :confused:

And if you're not ripping UHD disc's, you must be getting them another way (won't say what way that is), but of course they would have been ripped to start with.

Did any of my suggestions work, meaning running it thru MKVToolNix first ??

Would you able to upload a sample of the movie you're having trouble with ??

You can do this with MKVToolNix if you want, just load the file, then go to the "Output" tab, choose the "splitting" option, and select or add the length or size you want it split to, then run it until it's completed at least one "chunk", then you can stop it.

Upload to Mediafire or similar.

Anyway, the choice is yours, if you have found a "workaround", then you're set to go, with future problems.

Cheers

I don't know about the error. I'm not a code person. I just linked what the ripbot error displayed. I don't even know what version of eac3to I have. I'm assuming it came with the ripbot zip folder originally because I don't remember installing it. I did try to download a newer version. That did nothing. Assuming I even installed it properly.

I'm ripping Blueray's, not UHD's.

I really would prefer to fix my issue than to have some other workarounds. That's what I got this software for. It was an all in one.

[guest]

I don't know about the error. I'm not a code person. I just linked what the ripbot error displayed. I don't even know what version of eac3to I have. I'm assuming it came with the ripbot zip folder originally because I don't remember installing it. I did try to download a newer version. That did nothing. Assuming I even installed it properly.

I'm ripping Blueray's, not UHD's.

I really would prefer to fix my issue than to have some other workarounds. That's what I got this software for. It was an all in one.

OK, so there shouldn't be problem with Bluray's, then.

Yes, eac3to DOES come with RipBot, and if you want to update it yourself, you need get the download, https://www.videohelp.com/software/eac3to (unpack it, and then copy it into the "eac3to" folder inside RipBot, under the "Tools" folder, overwriting everything in there.)

What are you using to rip the disc's ??

What version of Windows are you running ??

Just trying to help :D

[darkio]

How ripbot264 correct colorimetry when upscaling dvd contents to 720p/1080p contents?

mediainfo report itu bt 601 after conversion from NTSC dvd for color matrix, transfer and colorprim.
I've forced in custom box x265 --colorprim bt709 --transfer bt709 --colormatrix bt709 but red is over satured.
No change in auto script from ripbot, no color conversion.

[guest]

How ripbot264 correct colorimetry when upscaling dvd contents to 720p/1080p contents?

mediainfo report itu bt 601 after conversion from NTSC dvd for color matrix, transfer and colorprim.
I've forced in custom box x265 --colorprim bt709 --transfer bt709 --colormatrix bt709 but red is over satured.
No change in auto script from ripbot, no color conversion.

Not 100% sure how to interpret what you want here...

You asked about LUT's 12 months or so ago, you could use a LUT, maybe.

https://forum.doom9.org/showthread.php?p=1951599#post1951599

Or under the Avisynth settings, go to the "Colours" setting, click on the and choose "ON", then a "Tweak" option will appear, where you can manually change the appropriate option, and test.

There's also an "ON (3DLUT)", where you can import a LUT.

[darkio]

yes you are right I asked for the luts about a year ago and it works very well, of that I am very happy.

What I ask now instead is how does ripbot264 correct the colorimetry after a dvd to hd conversion.

log file report:
1.26.0

Fixed: Correct colorimetry for DVD sources (ntsc->smpte170m,pal->bt470bg)
ok, sound is good, let's try!

After upscaling conversion, do not convert to itu bt 709 Rec. https://en.wikipedia.org/wiki/Rec._709, color space is the same of source.

[guest]

yes you are right I asked for the luts about a year ago and it works very well, of that I am very happy.

What I ask now instead is how does ripbot264 correct the colorimetry after a dvd to hd conversion.

log file report:
1.26.0

Fixed: Correct colorimetry for DVD sources (ntsc->smpte170m,pal->bt470bg)
ok, sound is good, let's try!

After upscaling conversion, do not convert to itu bt 709 Rec. https://en.wikipedia.org/wiki/Rec._709, color space is the same of source.

I'm pretty sure that RipBot does not this "automatically", you'd probably have to create a special custom filter, or use a suitable LUT.

Other than that, there is only the Colours setting I mentioned in the previous post.

[darkio]

HD itu 709 rec. example from mediainfo:
Color range : Limited
Colori primari : BT.709
Caratteristiche trasferimento : BT.709
Coefficienti matrici : BT.709v

SD content:
Color range : Limited
Colori primari : BT.601 NTSC
Caratteristiche trasferimento : BT.601
Coefficienti matrici : BT.601

Lut are unnecessary for colorimetry correction.
I'm asking conversion from bt 601 (smtpe170m/bt470bg) to itu 709 Rec. after upscaling. http://avisynth.nl/index.php/ColorMatrix
It seams ripbot simply "copy" source information in to converted dest. file.
When you use ripbot to convert uhd disk (hdr) to standard video (sdr), it can convert hdr signal itu bt 2020 rec to normal signal into itu bt 709 rec. When using dvd upscaling ripbot do not convert colorapace.

[guest]

When you use ripbot to convert uhd disk (hdr) to standard video (sdr), it can convert hdr signal itu bt 2020 rec to normal signal into itu bt 709 rec. When using dvd upscaling ripbot do not convert colorapace.

Yes, that is correct, and unless you can create your own special custom script that could do this conversion, you're out of luck, I'm afraid. :(

[darkio]

I'm hope atak fix this issue as soon as possible!

However, avisynth can do colormatrix conversion.
Thanks for your reply, friend. :)

edit: tmpgenc mast. work 7 can import ripbot264 avs file and transform colormatrix into itu bt 709.

https://i.postimg.cc/5QtLmRgB/Immagine.jpg (https://postimg.cc/5QtLmRgB)

[guest]

I'm hope atak fix this issue as soon as possible!

However, avisynth can do colormatrix conversion.
Thanks for your reply, friend. :)

I'm sure it can be done, I will have a look at it soon, and see what I can find.

You're welcome.

EDIT:- Good 'ole TMPGENC, I used to use that all the time, back in the day (earlier versions of cause.)

I think I may have found something that might do the job, I'll get back to you.

[darkio]

I have always considered doom9 a bible of useful encoding information and many good users available.

I think tmpgenc changes and adjusts the colorimetry automatically from the resolution of the input video.

Edit: rec 709 use full range (0-255), not limited like mpeg2 range (16-255).


Video
Formato : HEVC
Formato/Informazioni : High Efficiency Video Coding
Profilo formato : Main 10@L3.1@Main
Larghezza : 960 pixel
Altezza : 720 pixel
Rapporto aspetto visualizzazione : 4:3
Frame rate : 23,976 (24000/1001) FPS
Spazio colore : YUV
Croma subsampling : 4:2:0
Profondità bit : 10 bit
Compressore : x265 3.5+9-bf91444e0:[Windows][GCC 10.2.0][64 bit] 10bit
Impostazioni compressione : 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=960x720 / interlace=0 / total-frames=35208 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=4 / 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=6 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=25 / lookahead-slices=4 / scenecut=40 / hist-scenecut=0 / radl=0 / no-splice / no-intra-refresh / ctu=16 / min-cu-size=8 / rect / no-amp / max-tu-size=16 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=2 / 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=3 / limit-modes / me=3 / subme=3 / merange=9 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=1:1 / sao / no-sao-non-deblock / rd=4 / selective-sao=4 / no-early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=0.40 / psy-rdoq=1.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=18.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / vbv-maxrate=4096 / vbv-bufsize=4096 / vbv-init=0.9 / min-vbv-fullness=50.0 / max-vbv-fullness=80.0 / crf-max=0.0 / crf-min=0.0 / ipratio=1.40 / pbratio=1.30 / aq-mode=3 / aq-strength=0.90 / cutree / zone-count=0 / no-strict-cbr / qg-size=16 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=6 / transfer=6 / colormatrix=6 / 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 / hist-threshold=0.03 / 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
Color range : Limited
Colori primari : BT.601 NTSC
Caratteristiche trasferimento : BT.601
Coefficienti matrici : BT.601


Wrong color space conversion.

[Atak_Snajpera]

Try this for now...
1) Add --colorprim bt709 --transfer bt709 --colormatrix bt709 to your encoding profile
2) Download ColorMatrix Plugin https://www.mediafire.com/file/aj88vdobroxjbkd/ColorMatrix26.7z/file
3) extract to Tools\AviSynth plugins folder
4) Add following lines to your script under #ColorSpace

#ColorSpace
LoadPlugin("C:\RipBot264\Tools\AviSynth plugins\ColorMatrix26\ColorMatrix64.dll")
ColorMatrix(mode="Rec.601->Rec.709")

[darkio]

Hi atak,
thanks for you reply.
As mentioned before, I've already edited my profile box with --colorprim bt709 --transfer bt709 --colormatrix bt709.
The main problem after conversion are over satured colours (especially red).

I hope to see little enanchement with color matrix conversion from bt 601/bt 709 and viceversa or other color space in the next update.
I will try to use exteenal plugin too.
:thanks:

[Atak_Snajpera]

You must use colormatrix as well not only switches for an encoder.

[darkio]

Video
Formato : HEVC
Formato/Informazioni : High Efficiency Video Coding
Profilo formato : Main 10@L3.1@Main
Larghezza : 960 pixel
Altezza : 720 pixel
Rapporto aspetto visualizzazione : 4:3
Frame rate : 23,976 (24000/1001) FPS
Spazio colore : YUV
Croma subsampling : 4:2:0
Profondità bit : 10 bit
Compressore : x265 3.5+9-bf91444e0:[Windows][GCC 10.2.0][64 bit] 10bit
Impostazioni compressione : 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=960x720 / interlace=0 / total-frames=35208 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=4 / 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=6 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=25 / lookahead-slices=4 / scenecut=40 / hist-scenecut=0 / radl=0 / no-splice / no-intra-refresh / ctu=16 / min-cu-size=8 / rect / no-amp / max-tu-size=16 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=2 / 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=3 / limit-modes / me=3 / subme=3 / merange=9 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=1:1 / sao / no-sao-non-deblock / rd=4 / selective-sao=4 / no-early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=0.40 / psy-rdoq=1.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=18.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / vbv-maxrate=4096 / vbv-bufsize=4096 / vbv-init=0.9 / min-vbv-fullness=50.0 / max-vbv-fullness=80.0 / crf-max=0.0 / crf-min=0.0 / ipratio=1.40 / pbratio=1.30 / aq-mode=3 / aq-strength=0.90 / cutree / zone-count=0 / no-strict-cbr / qg-size=16 / 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 / hist-threshold=0.03 / 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
Color range : Limited
Colori primari : BT.709
Caratteristiche trasferimento : BT.709
Coefficienti matrici : BT.709

Colormatrix is ok,
testing better later

[Atak_Snajpera]

Limited is correct. HD footage always uses limited.

[darkio]

yes, of course, I'm wrong.
I have to add the setting to the script for each job queued manually and the commands from cli to do upscaling, right?

I hope it can be added later in the interface.
thanks for the help

[guest]

Try this for now...
1) Add --colorprim bt709 --transfer bt709 --colormatrix bt709 to your encoding profile
2) Download ColorMatrix Plugin https://www.mediafire.com/file/aj88vdobroxjbkd/ColorMatrix26.7z/file
3) extract to Tools\AviSynth plugins folder
4) Add following lines to your script under #ColorSpace

#ColorSpace
LoadPlugin("C:\RipBot264\Tools\AviSynth plugins\ColorMatrix26\ColorMatrix64.dll")
ColorMatrix(mode="Rec.601->Rec.709")

I have been playing around with this, and it seems to be very particular on the colorspace of the video being processed.

requirements:
YV12 & YUY2 Colorspace

And I was also having a problem with this call:-

ColorMatrix(mode="Rec.601->Rec.709")

shouldn't it be

video=ColorMatrix(video,mode="Rec.601->Rec.709")

like ALL the other RipBot scripts/calls ??

[Ryushin]

Hi Atak,

I'd like to submit a feature request for the batch processing. I use the batch a lot to pull in TV Episodes that I've used MakeMKV to rip the episodes from disks. I'd like to attach a cover to a batch import. I'd run one batch for season 1 and attach one cover to that, another batch and another cover, etc. Thanks Atak.

[gabbett1]

OK, so there shouldn't be problem with Bluray's, then.

Yes, eac3to DOES come with RipBot, and if you want to update it yourself, you need get the download, https://www.videohelp.com/software/eac3to (unpack it, and then copy it into the "eac3to" folder inside RipBot, under the "Tools" folder, overwriting everything in there.)

What are you using to rip the disc's ??

What version of Windows are you running ??

Just trying to help :D
And I greatly appreciate your help.

I'm running Windows 7. I'm using AnyDVD to rip the disks. I don't know if I copied the eac3to properly so I'm going to give that a try.

Thanks

[Atak_Snajpera]

And I greatly appreciate your help.

I'm running Windows 7. I'm using AnyDVD to rip the disks. I don't know if I copied the eac3to properly so I'm going to give that a try.

Thanks

Can you upload whole blu-ray folder somewhere? Obviously you would have to manually losslessly reduce size of each .m2ts file to something around 50-100MiB. You may try DGSplit of something similar.

[guest]

And I greatly appreciate your help.

I'm running Windows 7. I'm using AnyDVD to rip the disks. I don't know if I copied the eac3to properly so I'm going to give that a try.

Thanks

Hello again, gabbett1,

So before you do what Atak has suggested, I'd like to suggest that you use a different app to rip your disk's, just to be sure.

Also, is your Bluray optical drive in good condition, newish & "clean" inside ??

I would suggest that you try MakeMKV to rip your disc's...another user I know uses MakeMKV, and he hasn't reported any issues, and I know he's ripped 100's, if not 1,000's of Bluray's.

Maybe there's something about the newer disc's that AnyDVD is having a problem with, if as you say, the older disc's seem to be fine.

If you're interested in using MakeMKV, (latest build with registration)

https://www.mediafire.com/file/nq9e10egfb9qn76/MakeMKV.1.17.2.7z/file

Anyway, that's my 2 cents....I hated ripping Bluray's !!!!

[Ryushin]

And I greatly appreciate your help.

I'm running Windows 7. I'm using AnyDVD to rip the disks. I don't know if I copied the eac3to properly so I'm going to give that a try.

Thanks

I have used AnyDVD to rip thousands of discs and I've used MakeMKV to rip 1000's of discs. I've worn out three optical drives. :(

I do remember a few times with a few ripped discs, that they must have mastered it wrong in some manner, as RB (eac3to) could not demux it properly and RB always gave an error when it had finished ripping the disc. The way around this was to use MakeMVK to convert the main feature (or episodes) into mkv files which RB imported without issue.

You can use MakeMVK for free if you don't mind updating each 30 days with the key he provides. Though the software is so inexpensive, I would buy it as well. Both AnyDVD and MakeMKV have their places.

MakeMKV can't do DVD backups, but AnyDVD can. MakeMKV can rip the files into mkvs, but AnyDVD cannot. There are a few other differences between them that make owning both of them essential if you use optical media.

[guest]

I have used AnyDVD to rip thousands of discs and I've used MakeMKV to rip 1000's of discs. I've worn out three optical drives. :(

I do remember a few times with a few ripped discs, that they must have mastered it wrong in some manner, as RB (eac3to) could not demux it properly and RB always gave an error when it had finished ripping the disc. The way around this was to use MakeMVK to convert the main feature (or episodes) into mkv files which RB imported without issue.

You can use MakeMVK for free if you don't mind updating each 30 days with the key he provides. Though the software is so inexpensive, I would buy it as well. Both AnyDVD and MakeMKV have their places.

MakeMKV can't do DVD backups, but AnyDVD can. MakeMKV can rip the files into mkvs, but AnyDVD cannot. There are a few other differences between them that make owning both of them essential if you use optical media.

Nicely explained,
and it's always good to have a couple of different ways of doing the same process.

[jlpsvk]

any way to use ffmsindex instead lsmash???

[guest]

any way to use ffmsindex instead lsmash???

there certainly is :)

overwrite this field in RipBot264.ini if you want to use FFMS2 instead of L-Smash

Note that IF you do any changes within RipBot, and press APPLY, this will be overwritten, but all you'll need to do is copy it back :)

[DefaultVideoDecoder]
MPEG-2=FFMS2
VC-1=FFMS2
AVC=FFMS2
HEVC=FFMS2
OTHER=FFMS2

Is there any specific reason you don't want to use L-Smash ???

[JThomasG]

hi

is it possible to add a crop command line in ripbot, do i don't have to go in manually for each encode if i know they will all be the same.

lets say 10 left 10 right ?

if so how would the command line look like, and will i add it to the profile settings?

Thanks

[guest]

hi

is it possible to add a crop command line in ripbot, do i don't have to go in manually for each encode if i know they will all be the same.

lets say 10 left 10 right ?

if so how would the command line look like, and will i add it to the profile settings?

Thanks

So are you wanting to add this to the x264 and/or x265 profiles themselves ??

Not in the encoding script ??

If you want x264 or x265 to do it, go here, search & read :-

http://www.chaneru.com/Roku/HLS/X264_Settings.htm

https://x265.readthedocs.io/en/master/cli.html

eg: crop
Syntax: crop:left,top,right,bottom

in the avisynth script it looks like this :-

#Crop
video=Crop(video,10,0,-10,-0)

red is "left", green is "right"

You could create a custom script and add the above call, then you could access & change it to suit your needs, and leave the x264/x265 profiles alone.

[guest]

Hold the phone, we have a nice autoupdate :)

v1.26.3
Added: 7.1 AAC encoding via FFMPEG (new profile will show up after you manually delete Audio.txt file in Profile folder)
Added: Cover art can be also added in BATCH MODE
Added: Automatic color conversion rec.601->rec.709 when upscaling from SD to HD
Fixed: Main application RipBot264.exe was launching EncodingServer.exe without proper /avisynth-prefetch-threads switch

EDIT:- I have a couple of questions about this update.

Added: 7.1 AAC encoding via FFMPEG (new profile will show up after you manually delete Audio.txt file in Profile folder)

When I remove this, adding a new job it stalls at "Gathering Information", and any other queued Job won't open as it can't find the "audio.txt".

EDIT #2:- I started from scratch with RipBot264, deleted the "Audio.txt", it created a new "Audio.txt", but it was the same settings, do I need to create a job with 7.1 audio to start with ??

EDIT #3:- It's updated now :)

2.0 OPUS CODEC 64 kbps [abr]
2.0 OPUS CODEC 96 kbps [abr]
2.0 OPUS CODEC 128 kbps [abr]
5.1 OPUS CODEC 160 kbps [abr]
5.1 OPUS CODEC 240 kbps [abr]
5.1 OPUS CODEC 320 kbps [abr]
7.1 OPUS CODEC 224 kbps [abr]
7.1 OPUS CODEC 336 kbps [abr]
7.1 OPUS CODEC 448 kbps [abr]
2.0 FHG AAC-HE 64 kbps [abr]
2.0 FHG AAC-LC 96 kbps [abr]
2.0 FHG AAC-LC 128 kbps [abr]
5.1 FHG AAC-HE 192 kbps [abr]
5.1 FHG AAC-LC 256 kbps [abr]
5.1 FHG AAC-LC 320 kbps [abr]
7.1 FFMPEG AAC 384 kbps [abr]
7.1 FFMPEG AAC 448 kbps [abr]
7.1 FFMPEG AAC 640 kbps [abr]
2.0 FFMPEG AC3 192 kbps [cbr]
2.0 FFMPEG AC3 224 kbps [cbr]
2.0 FFMPEG AC3 256 kbps [cbr]
5.1 FFMPEG AC3 384 kbps [cbr]
5.1 FFMPEG AC3 448 kbps [cbr]
5.1 FFMPEG AC3 640 kbps [cbr]

Now all we need is 5.1 E-AC3 conversion with FFMPEG, up to 1536 kbps, and 7.1 AC3 !!!

Added: Automatic color conversion rec.601->rec.709 when upscaling from SD to HD

Where is this option ??

[guest]

For those users that want a clean install of the latest build provided by Atak, without having to start from scratch with v1.26.0, and then update it.

https://www.mediafire.com/file/c1rko1406yev7jl/RipBot264v1.26.3_%2528virgin%2529.7z/file

All you need to do is keep your RipBot264.ini & EncodingClient.ini from your working/current version.

[guest]

This will bring you up to date to v1.26.3

And an Avisynth update as well (read the changelog)

simply unpack, and overwrite the folders & files !!

https://www.mediafire.com/file/1grrvr360fgpk30/RipBot264_PD+(26-11-22).7z/file

[Ryushin]

Thank Atak for the update and the new features. I appreciate it.

If you have time would be nice to have SMDegrain replace MDegrain. The results are just staggering and I resisted doing it for so long because I thought MDegrain did such a good job it could not really improve that much with SMDegrain. SMDegrain's output is so much improved it's staggering. It's like the difference MDegrain made over HQDN3D and that I would never go back to HQDN3D after seeing the results for MDegrain. Now SMDegrain has made MDegrain obsolete.

Now I'm at the point where the output is so clean with SMDegrain I think something must be wrong as the file sizes are so much smaller and I must have lost detail. Every detailed comparison I've made shows that I was wrong and the output from SMDegrain has not only removed the grain, but since the grain is removed, details actually stand out and everything appears crisper. I've actually started re-encoding older films and watching them again such as The Terminator, The Edge, etc. just because the difference in detail is so dramatic it is like experiencing the film all over again and it is a joy to watch.

SMDegrain also does not produce the detail blur I saw with MDegrain3 in a characters face when they turned their head.

The only tweak I have started doing is blksize=8 when dealing with video that has a lot of dark scenes in it.

Please replace MDegrain with the following SMDegrain strength settings:
Light: SMDegrain(video,tr=2,thSAD=200,thSADC=100,contrasharp=true,prefilter=0,refinemotion=true)
Medium: SMDegrain(video,tr=4,thSAD=400,thSADC=200,contrasharp=true,prefilter=1,refinemotion=true)
Strong: SMDegrain(video,tr=8,thSAD=800,thSADC=400,contrasharp=true,prefilter=2,refinemotion=true)

Thanks again Atak for everything.

[JThomasG]

Hi,

just an fyi

i got unable to open input file <-> from all encodingservers

i can open shared location from remote site

i have pinpointed the error to this (that i suspect), when i render subs in avisynth tab (it's a very small sub) it doesn't seem to generate the 1080_1080_sub file i seen from other encodes.

when i removed render subs from this encode it starts to work again and error was gone.

could be that the sub is not valid or something not sure but it was demuxed from source, i think "render subs" should be automatically disabled if this occur?

thanks.

[guest]

Thank Atak for the update and the new features. I appreciate it.

If you have time would be nice to have SMDegrain replace MDegrain. The results are just staggering and I resisted doing it for so long because I thought MDegrain did such a good job it could not really improve that much with SMDegrain. SMDegrain's output is so much improved it's staggering. It's like the difference MDegrain made over HQDN3D and that I would never go back to HQDN3D after seeing the results for MDegrain. Now SMDegrain has made MDegrain obsolete.

Now I'm at the point where the output is so clean with SMDegrain I think something must be wrong as the file sizes are so much smaller and I must have lost detail. Every detailed comparison I've made shows that I was wrong and the output from SMDegrain has not only removed the grain, but since the grain is removed, details actually stand out and everything appears crisper. I've actually started re-encoding older films and watching them again such as The Terminator, The Edge, etc. just because the difference in detail is so dramatic it is like experiencing the film all over again and it is a joy to watch.

SMDegrain also does not produce the detail blur I saw with MDegrain3 in a characters face when they turned their head.

The only tweak I have started doing is blksize=8 when dealing with video that has a lot of dark scenes in it.

Please replace MDegrain with the following SMDegrain strength settings:
Light: SMDegrain(video,tr=2,thSAD=200,thSADC=100,contrasharp=true,prefilter=0,refinemotion=true)
Medium: SMDegrain(video,tr=4,thSAD=400,thSADC=200,contrasharp=true,prefilter=1,refinemotion=true)
Strong: SMDegrain(video,tr=8,thSAD=800,thSADC=400,contrasharp=true,prefilter=2,refinemotion=true)

Thanks again Atak for everything.

Ryushin,

Hmmm, there IS a lot more to "Dogways" SMDegrain than those simple scripts/calls, that's just scratching the surface.

There are a total of 9 different "pre filter" options.

And there are MANY other functions that can be used, as well, most are rather "specialized"

And your examples are NOT the whole script/call, there's all the dependancies that are required.

But anyway, the following....

prefilter=-1 standard basic SMDegrain, which would still be better than MDegrain.

prefilter=0 1st of the Minblur options

prefilter=1 2nd of the Minblur options

prefilter=2 3rd of the Minblur options

prefilter=3 which uses FluxSmooth

prefilter=4 which uses Dfttest

prefilter=5 which uses KNLMeansCL

prefilter=6 which uses BM3D, (CUDA or CPU)

prefilter=7 which uses DGDenoise (nVidia based)

So there might users out there that would appreciate CUDA or nVidia based filters...

I would also like to say a BIG :thanks: to you for "pushing" these requests, especially after it took a while for me to convince you to try it, so that in itself is quite an achievement, for me :thanks:

Even tho I don't get any feedback, I hope other users are having a similar experience. :cool:

[Ryushin]

Ryushin,

Hmmm, there IS a lot more to "Dogways" SMDegrain than those simple scripts/calls, that's just scratching the surface.

There are a total of 9 different "pre filter" options.

And there are MANY other functions that can be used, as well, most are rather "specialized"

And your examples are NOT the whole script/call, there's all the dependancies that are required.

But anyway, the following....

prefilter=-1 standard basic SMDegrain, which would still be better than MDegrain.

prefilter=0 1st of the Minblur options

prefilter=1 2nd of the Minblur options

prefilter=2 3rd of the Minblur options

prefilter=3 which uses FluxSmooth

prefilter=4 which uses Dfttest

prefilter=5 which uses KNLMeansCL

prefilter=6 which uses BM3D, (CUDA or CPU)

prefilter=7 which uses DGDenoise (nVidia based)

So there might users out there that would appreciate CUDA or nVidia based filters...

I would also like to say a BIG :thanks: to you for "pushing" these requests, especially after it took a while for me to convince you to try it, so that in itself is quite an achievement, for me :thanks:

Even tho I don't get any feedback, I hope other users are having a similar experience. :cool:

I know there are a lot more options available. But for the vast majority of users, the three options I quoted work wonderfully for almost all content. It's nice that SMDegrain has the contrasharp option to use after the Minblur (prefilter1-3) options. To blur your video without sharpening would just soften the whole video and that would not be good.

I scan my jacket disc covers in and the final step I do in GIMP is a Selective Gaussian Blur to remove the dithering/halftone in the printed image and then a unsharp (oxymoron there) to sharpen the image and the result comes out excellent. The options with SMDegrain give us similar improvement.

Since MDegrain is now obsolete, RB should adopt SMDegrain. It's not good to have new users to have to download RB, and then have to download Pauly Dunne's patch, then have to learn how to use Custom scripts to get good results, much less, learn all the options in each script. Take me for example. For me to switch to SMDegrain, I did days of learning and testing. At first SMDegrain did not impress me and it gave me worse results than MDegrain and I was ready to pack it in and keep using MDegrain. But I kept with it and once I found the right options, it quickly became far superior to MDegrain.

The advantage to RB is that it's generally easy to use and users like that. It's not as daunting as Staxrip or other programs that simple give way to many options or dumb it down so much that there are almost no options available. In addition RB gives distributed encoding. Can't beat that.

[guest]

I know there are a lot more options available. But for the vast majority of users, the three options I quoted work wonderfully for almost all content. It's nice that SMDegrain has the contrasharp option to use after the Minblur (prefilter1-3) options. To blur your video without sharpening would just soften the whole video and that would not be good.

I scan my jacket disc covers in and the final step I do in GIMP is a Selective Gaussian Blur to remove the dithering/halftone in the printed image and then a unsharp (oxymoron there) to sharpen the image and the result comes out excellent. The options with SMDegrain give us similar improvement.

Since MDegrain is now obsolete, RB should adopt SMDegrain. It's not good to have new users to have to download RB, and then have to download Pauly Dunne's patch, then have to learn how to use Custom scripts to get good results, much less, learn all the options in each script. Take me for example. For me to switch to SMDegrain, I did days of learning and testing. At first SMDegrain did not impress me and it gave me worse results than MDegrain and I was ready to pack it in and keep using MDegrain. But I kept with it and once I found the right options, it quickly became far superior to MDegrain.

The advantage to RB is that it's generally easy to use and users like that. It's not as daunting as Staxrip or other programs that simple give way to many options or dumb it down so much that there are almost no options available. In addition RB gives distributed encoding. Can't beat that.

I would suggest that anyone "new" to RipBot would have a learning curve, to figure out what option did what, same with PD's build's, just because the majority of the SMDegrain filter options can only be accessed in the Custom drop down, (and by adding different scripts into the Custom folder itself), it would still quite the learning curve.... as you stated, you ARE a very experienced RipBot user, and I guess the dramatic change to the process, really stumped you for a while, but now you're reaping the benefits.

As for patching, if the user downloads the PD complete build, it's ready to fly, you don't have to get the "vanilla" version first, and then add PD's stuff to it, the only "patching" is the way the updates are implemented...manually !!!

Ripbot needs to step up, as Staxrip & Handbrake don't seem to be getting the attention they used to, and RipBot is almost in that same boat....app's like Hybrid, are WAY over the top !!!

But you're correct in saying that the DE function is a game changer...how come no one else has figured it out, kind of rewilders me.

[Ryushin]

I would suggest that anyone "new" to RipBot would have a learning curve, to figure out what option did what, same with PD's build's, just because the majority of the SMDegrain filter options can only be accessed in the Custom drop down, (and by adding different scripts into the Custom folder itself), it would still quite the learning curve.... as you stated, you ARE a very experienced RipBot user, and I guess the dramatic change to the process, really stumped you for a while, but now you're reaping the benefits.

When Atak first implemented MDegrain2, it did not take all the long to find out which options to tweak. Really only one. SMDegrain on the other hand is like a swiss army knife. There are so many options available that it's daunting.

Those three SMDegrain lines I posted are pretty much all I use now with the exception of adding blksize=8 for video with lots of dark scenes.

So I guess ideally, RB SMDegrain options would be a pull down labeled Strength with Light, Medium Hard, and then a pull down next to it with Blocksize with a default of 16 and an option to make it 8. It little mouse over popup over a "?" would say 8 is good for darker sources but takes 4 times more work to complete.

[guest]

OK, with all the conversation of late, I decided to build a "Lite" version of my somewhat popular build's (the only way I know this is the amount of downloads on Mediafire, as I don't get ANY feedback from the 100's of users, so thanks for that) ;)

This build ONLY has a select few SMDegrain based script options, & the required dependencies & NOTHING else!

I have chosen the scripts that my friend Ryushin has recommended (the only user that gives me feedback, both good & bad).

This build (as with the full blown builds) is ready to go, as is, no patching of updates, it's just all there !!!

For more info & details, please read the changlog.txt, included.

And while I'm at it, Atak, IF you are contemplating an SMDegrain implementation, this is ALL you need as far as scripts & dependencies, you would ONLY need to "work your magic" to add it in your code, so it has its own location, within RipBot.

Good luck, and enjoy :D

[Ryushin]

Hi Atak,
Probably just a typo in the code some where, but muxing the encoded job results in an error:
Error: The file 'D:\Temp\RipBot264temp\job41\Encoded_Audio_1.ac3' could not be opened for reading: open file error.
There is an Encoded_Audio_1.aac file in the job folder. So the typo might be the ac3 instead of aac for 7.1.
Modifying the job41_MuxFiles.json and replacing ac3 with aac results in the job muxing correctly.

I also wanted to mention that I do not get that frozen floating grain with SMDegrain like I did with MDegrain. If there is any grain left over from SMDegrain it looks like natural grain from the film.


Pauly Dunne: Thank you for the lite build, I appreciate it. It will make it easier for those new users to integrate into RBs official build and leave auto update turned on. Even though Atak has not been updating x265 and other dependencies that often. I don't think I've given you bad feedback. Just feedback on possible improvements or changes and you have always been accommodating in wanting to improve your builds. Your builds have always been appreciated. I'm just sorry I waited almost a year (probably) to start try them out.

[Ryushin]

Atak, since you control your updates, do you know about how many active users of RB there are in the world? Just curious.