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

[slow4mula2002]

Thanks for the great app Atak been using it for years. I was wondering if it would be possible to add support for output of BDMV m2ts or ISO for backing up UHD bluray to BD-R 25/50gb. I usually just backup UHD to mkv but I've done a few test backups using makemkv and dvdfab 11 to BD-R that play in my standalone UHD bluray player. It seems ripbot264 already has most of this capability. Is this possible?

[guest]

Thanks for the great app Atak been using it for years. I was wondering if it would be possible to add support for output of BDMV m2ts or ISO for backing up UHD bluray to BD-R 25/50gb. I usually just backup UHD to mkv but I've done a few test backups using makemkv and dvdfab 11 to BD-R that play in my standalone UHD bluray player. It seems ripbot264 already has most of this capability. Is this possible?

Hi slow4mula2002,

You can choose AVCHD when creating a new job, that will create your .mt2s's in a Bluray compatible folders.

Or you could run the end result thru tsmuxer to create an .iso.

[GazzaCOP]

Hi,

Been using RB for a handful of months and it's become my go-to encoding software with killer features for me being Tonemapping and DE, although I've encoded with Handbrake for years. So, I'm moving on now to encoding in a slightly advanced manner - namely using the following script to MDegrain3 certain of my encodes, principally older movies with plenty of grain.

LoadPlugin("C:\RipBot264\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
bv1=MAnalyse(super,isb=true,delta=1,overlap=4)
fv1=MAnalyse(super,isb=false,delta=1,overlap=4)
bv2=MAnalyse(super,isb=true,delta=2,overlap=4)
fv2=MAnalyse(super,isb=false,delta=2,overlap=4)
bv3=MAnalyse(super,isb=true,delta=3,overlap=4)
fv3=MAnalyse(super,isb=false,delta=3,overlap=4)
video=MDegrain3(video,super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=800)

It all works beautifully but I'm having to copy and paste the script every time into the AVISynth '#denoise' section in the AVISynth video window which is a pain, especially if I forget. Is there a way to get my 'MDegrain3 custom script' into the DENOISE dropdown box next to the window so I can just select it rather than copy/paste each time? Or is there another method I could use? (I've set up a specific X265 profile to introduce --aq-mode 3 although naturally the X265 script doesn't influence the script passed to AVISynth).

Incidentally I find KNLmeansCL hopeless...either one or both my servers regularly stalls when I engage KNLmeansCL....no biggy, MDegrain is good for me.

[Atak_Snajpera]

1) in notepad paste

#denoise
LoadPlugin("C:\RipBot264\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
bv1=MAnalyse(super,isb=true,delta=1,overlap=4)
fv1=MAnalyse(super,isb=false,delta=1,overlap=4)
bv2=MAnalyse(super,isb=true,delta=2,overlap=4)
fv2=MAnalyse(super,isb=false,delta=2,overlap=4)
bv3=MAnalyse(super,isb=true,delta=3,overlap=4)
fv3=MAnalyse(super,isb=false,delta=3,overlap=4)
video=MDegrain3(video,super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=800)

2) save as mdegrain3.avs in /avisynth plugins/scripts/custom folder (im writing from my head)

3) select your custom script from combobox on last page.

[GazzaCOP]

Of course, custom scripts, it works perfectly and so logical. Many thanks and a donation is on its way

[slow4mula2002]

Hi slow4mula2002,

You can choose AVCHD when creating a new job, that will create your .mt2s's in a Bluray compatible folders.

Or you could run the end result thru tsmuxer to create an .iso.

AVCHD output is only an option when you encode to x264. When encoding to hevc the only output available is mkv.

[guest]

AVCHD output is only an option when you encode to x264. When encoding to hevc the only output available is mkv.

OK, fair point, but you didn't mention x265/HEVC !!!

You can still run the end result thru tsmuxer to generate either .m2ts or an .iso !!!

Yeah, I got that wrong, tsmuxer does NOT output to .iso...

[slow4mula2002]

OK, fair point, but you didn't mention x265/HEVC !!!

You can still run the end result thru tsmuxer to generate either .m2ts or an .iso !!!

Yeah, I got that wrong, tsmuxer does NOT output to .iso...

Yeah I said UHD bluray idk why anyone would encode hevc from a UHD bluray to h264...makes no sense. There might be a way to re-encode UHD with HD audio to m2ts using free tools but I haven't been able to locate a method that would consistently work. DVDfab does the job I'm describing well but it's a bit pricey. I might just have to purchase if I decide this is something I'd like to do.

I understand AVCHD is a "standard" so atak was kind enough to include this in his app but there is no "standard" for backing up a UHD bluray to BD-R 25/50.

If I open a mkv with tsmuxer with a truehd audio track then it isn't recognized so that also does not work. All of my mkvs have the original HD audio.

[guest]

Yeah I said UHD bluray idk why anyone would encode hevc from a UHD bluray to h264...makes no sense. There might be a way to re-encode UHD with HD audio to m2ts using free tools but I haven't been able to locate a method that would consistently work. DVDfab does the job I'm describing well but it's a bit pricey. I might just have to purchase if I decide this is something I'd like to do.

I understand AVCHD is a "standard" so atak was kind enough to include this in his app but there is no "standard" for backing up a UHD bluray to BD-R 25/50.

If I open a mkv with tsmuxer with a truehd audio track then it isn't recognized so that also does not work. All of my mkvs have the original HD audio.

Yeah, sorry 'bout that, you DID mention UHD several times, I guess I generally refer to them as 4K disks.

I haven't got any equipment that can play TrueHD, so I rip out the THD track, and convert it to DTS-HD 7.1, then you can remux it back in with either RB, or tsmuxer (for m2ts), or MKVToolNix (for mkv). All with "free" tools. !!!

I think you'll find that some of the very latest tsmuxer builds (nightly) will support TrueHD under certain conditions.

I have done many "conversion's" like this, works very well, just a little time consuming.

Not too sure why you'd then want to "burn" back onto an optical disk.

Each to their own, I guess.

[slow4mula2002]

Yeah, sorry 'bout that, you DID mention UHD several times, I guess I generally refer to them as 4K disks.

I haven't got any equipment that can play TrueHD, so I rip out the THD track, and convert it to DTS-HD 7.1, then you can remux it back in with either RB, or tsmuxer (for m2ts), or MKVToolNix (for mkv). All with "free" tools. !!!

I think you'll find that some of the very latest tsmuxer builds (nightly) will support TrueHD under certain conditions.

I have done many "conversion's" like this, works very well, just a little time consuming.

Not too sure why you'd then want to "burn" back onto an optical disk.

Each to their own, I guess.

I don't want to convert the main HD audio track. I've tried every tsmuxer build I can find and none seem to recognize the dolby true hd/atmos audio tracks. It seems like it would possible to add this capability to this GUI but if there isn't a big enough audience then it is what it is. The capability to encode back to HEVC/retain original audio track and output m2ts in bluray structure.

Why burn back to optical disk..well like I said I usually just output to mkv but possibly higher quality on a single layer bd-r (22.5gb) for what I would typically create a mkv or retain intact hevc/audio with a dual layer bd-r (45gb). Why did people ever backup bluray to AVCHD? Same reason here. It's nice to be able to take a UHD bluray backup and play it at a friends house in their UHD player. No usb drives or hard drives hoping their device supports the mkv.

[FurbyTime]

Is there anyway to have the batch function process multiple audio tracks at once? I deal with a lot of multi-audio video and would love to be able to avoid having to manually enter the second track if possible.

[fits79]

I download the latest version and when i add one mkv file it bring me this error with the ffprobe.exe file:

https://i.postimg.cc/3rZytJyv/image.jpg

Why?

[LigH]

That sounds Greek to me. Literally... Can you summarize the meaning of this error in English?

PS: Apparently it's just the simple "application stopped working" message. Not much to learn from that one. May simply be a corrupt file.

[guest]

Hi Atak,

It's been about 5 weeks since the last update, and I have been sniffing around, and I think there are some newer builds available.

L-smash, ffmpeg, mkvtoolnix, avisynth 3.60 and even the very important eac3to, it's latest (although old) is 3.34, and RB has 3.33.

And there might even be a few more, eg:- x264 or x265, etc.

Cheers

[Ripmann]

Another minor feature request for consideration: Right-click on a job -> Duplicate Job.

Rationale: I often need to do several encodes of the same source using different settings. I do it to compare quality, but others do HEVC and non-HEVC versions or size-limited (4gb DVD)and CQ (12gb HDD backup) versions for example. Adding a duplicate job for the same source can take a while (demuxing, subs, etc.) It would be much easier to be able to duplicate the first job with all the subtitles, names and other settings, and just tweak the one or two values you want to change.

If you're ever going to take a look at that jobs UI, here's another non-essential one to consider:

The ability to delete multiple jobs at once, instead of removing them one by one. For example:

Select multiple jobs -> and

A) Press DEL key (currently does nothing)
B) Click Remove (currently only removes the last job in selection and auto-selects next (makes total sense when removing one job but may cause confusion with multiple jobs selected))
C) Right click->Remove Job (currently doesn't exist; redundant anyway)

Rationale: not an issue with a few jobs, but for those who deal with many small files it should be a welcome addition. I just had an unusually large number of jobs in the queue (67 mini conversions), and the ability to remove all 58 selected jobs at once would certainly be helpful, compared to clicking Remove 58 times. Thankfully my usual job count is nowhere near as large, but I assume that people who do full series batches with dozens of episodes would love it.

[Ripmann]

Hi,

Been using RB for a handful of months and it's become my go-to encoding software with killer features for me being Tonemapping and DE, although I've encoded with Handbrake for years. So, I'm moving on now to encoding in a slightly advanced manner - namely using the following script to MDegrain3 certain of my encodes, principally older movies with plenty of grain.

LoadPlugin("C:\RipBot264\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
bv1=MAnalyse(super,isb=true,delta=1,overlap=4)
fv1=MAnalyse(super,isb=false,delta=1,overlap=4)
bv2=MAnalyse(super,isb=true,delta=2,overlap=4)
fv2=MAnalyse(super,isb=false,delta=2,overlap=4)
bv3=MAnalyse(super,isb=true,delta=3,overlap=4)
fv3=MAnalyse(super,isb=false,delta=3,overlap=4)
video=MDegrain3(video,super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=800)

It all works beautifully but I'm having to copy and paste the script every time into the AVISynth '#denoise' section in the AVISynth video window which is a pain, especially if I forget. Is there a way to get my 'MDegrain3 custom script' into the DENOISE dropdown box next to the window so I can just select it rather than copy/paste each time? Or is there another method I could use? (I've set up a specific X265 profile to introduce --aq-mode 3 although naturally the X265 script doesn't influence the script passed to AVISynth).

Incidentally I find KNLmeansCL hopeless...either one or both my servers regularly stalls when I engage KNLmeansCL....no biggy, MDegrain is good for me.

Thanks for your MDegrain3 settings. Old movies are too grainy for the unmodded MDegrain2 preset, so I've been tweaking it instead. With your preset as a guide, I finally decided to do a few trial MDegrain3 runs to compare the results.

By the way, did you try Atak's suggestion of saving the code as a custom script? I'm curious how it'll work if I run it together with "KNLmeansCL" in the Denoise menu. Will it be processed similarly to "Mdegrain2+KNLmeansCL" or not? I assume it's not as simple (at the very least the processing order will probably be messed up), but I don't know AviSynth nearly well enough to guess.

[guest]

If you're ever going to take a look at that jobs UI, here's another non-essential one to consider:

The ability to delete multiple jobs at once, instead of removing them one by one. For example:

Select multiple jobs -> and

A) Press DEL key (currently does nothing)
B) Click Remove (currently only removes the last job in selection and auto-selects next (makes total sense when removing one job but may cause confusion with multiple jobs selected))
C) Right click->Remove Job (currently doesn't exist; redundant anyway)

Rationale: not an issue with a few jobs, but for those who deal with many small files it should be a welcome addition. I just had an unusually large number of jobs in the queue (67 mini conversions), and the ability to remove all 58 selected jobs at once would certainly be helpful, compared to clicking Remove 58 times. Thankfully my usual job count is nowhere near as large, but I assume that people who do full series batches with dozens of episodes would love it.

Hey, that is a good suggestion, however, if you go to the Main "tab" (under Settings) in RB, there is an option to "Keep jobs after successful conversion", I think it's checked by default, if you unchecked that, then it will "clean" the job queue, as it goes. ;)

[guest]

Thanks for your MDegrain3 settings. Old movies are too grainy for the unmodded MDegrain2 preset, so I've been tweaking it instead. With your preset as a guide, I finally decided to do a few trial MDegrain3 runs to compare the results.

By the way, did you try Atak's suggestion of saving the code as a custom script? I'm curious how it'll work if I run it together with "KNLmeansCL" in the Denoise menu. Will it be processed similarly to "Mdegrain2+KNLmeansCL" or not? I assume it's not as simple (at the very least the processing order will probably be messed up), but I don't know AviSynth nearly well enough to guess.

If you have saved MDG3 as a custom filter, you should be able to choose that from the custom dropdown, and choose knlmeans from the "denoise" dropdown...OR you might be able to make another custom for both..

For KNLMeansCL (mono setting of 2):-

#After_Prefetch_Denoise
LoadPlugin("C:\RipBot264\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll")
video=KNLMeansCL(video,d=1, a=2, s=4, h=2, device_type="GPU", device_id=0)

OR

For KNLMeansCL (adaptive) (mono setting of 2):-

#After_Prefetch_Denoise
LoadPlugin("C:\RipBot264\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll")
denoisemask=ConvertToY(video)
denoisedvideo=KNLMeansCL(video,d=1, a=2, s=4, h=2, device_type="GPU", device_id=0)
video=Overlay(video,denoisedvideo,mask=denoisemask,opacity=1.0)

Might look a bit like this :-

#Custom
LoadPlugin("C:\RipBot264\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll")
video=KNLMeansCL(video,d=1, a=2, s=4, h=2, device_type="GPU", device_id=0)

LoadPlugin("C:\RipBot264\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
bv1=MAnalyse(super,isb=true,delta=1,overlap=4)
fv1=MAnalyse(super,isb=false,delta=1,overlap=4)
bv2=MAnalyse(super,isb=true,delta=2,overlap=4)
fv2=MAnalyse(super,isb=false,delta=2,overlap=4)
bv3=MAnalyse(super,isb=true,delta=3,overlap=4)
fv3=MAnalyse(super,isb=false,delta=3,overlap=4)
video=MDegrain3(video,super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=800)

or you could tidy that up a bit, as long as all the "command's" are there.

[Ripmann]

If you have saved MDG3 as a custom filter, you should be able...

Thanks for taking the time to write down all your suggestions. Appreciate it.

Edit: By the way, is it possible to edit the list of the Lock Size values somewhere? I constantly have tweak them to adjust to my personal needs. As one example, for the dual-layer media I have, 8150 often produces oversized files. I use 8135 to get consistent results to fit it. The single-layer media I have is the opposite: 4480 is usally too low to hit the max capacity, so I use 4488 all the time.

[guest]

Thanks for taking the time to write down all your suggestions. Appreciate it.

Edit: By the way, is it possible to edit the list of the Lock Size values somewhere? I constantly have tweak them to adjust to my personal needs. As one example, for the dual-layer media I have, 8150 often produces oversized files. I use 8135 to get consistent results to fit it. The single-layer media I have is the opposite: 4480 is usually too low to hit the max capacity, so I use 4488 all the time.

OK, I'm no expert when it comes to this program, and I don't use the Lock Size option very often, as I just let it create the size output file that the settings process.

As for a "hidden" setting for the Lock Size numbers, there doesn't seem to be one. But I'm sure someone could prove me wrong.

HOWEVER, in "Batch" you can edit all the settings and then save them as default, so you could use Batch for your re sizing, either one at a time, or as many as you like :)
You will find reference to these settings in the RipBot264.ini file.

It would actually be a really nice addition to the main job settings, wouldn't it....:rolleyes:

[LucasSimba]

Hey everyone,

I recently discovered RipBot264 and found it really useful, especially because I want to use specific encode settings. Everything works fine, except for one setting: chroma-qp-offset

I set --chroma-qp-offset -3, but for some reason the video file created has --chroma-qp-offset -6. Every other settings entered in the command line section of RipBot264 is respected.

Any idea why this happens? And is it possible to have -3?

Thank you!

Encode settings:

cabac=1 / ref=4 / deblock=1:-1:-1 / analyse=0x3:0x113 / me=umh / subme=9 / psy=1 / psy_rd=1.00:0.15 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-3 / threads=32 / lookahead_threads=4 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=50 / rc=2pass / mbtree=1 / bitrate=3000 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=31250 / vbv_bufsize=31250 / nal_hrd=none / filler=0 / ip_ratio=1.40 / aq=3:1.00

CLI command:

--cabac --ref 4 --deblock -1:-1 --partitions i4x4,i8x8,p8x8,b8x8 --me umh --subme 9 --psy-rd 1.00:0.15 --merange 24 --trellis 2 --8x8dct --cqm flat --deadzone-inter 21 --deadzone-intra 11 --chroma-qp-offset -3 --threads 32 --lookahead-threads 4 --bframes 3 --b-pyramid normal --b-adapt 2 --b-bias 0 --direct auto --weightp 2 --keyint 250 --min-keyint 25 --scenecut 40 --rc-lookahead 50 --bitrate 3000 --ratetol 1.0 --qcomp 0.60 --qpmin 0 --qpmax 69 --qpstep 4 --cplxblur 20.0 --qblur 0.5 --vbv-maxrate 31250 --vbv-bufsize 31250 --nal-hrd none --ipratio 1.40 --aq-mode 3 --aq-strength 1.00

[Atak_Snajpera]

I see this
/ fast_pskip=1 / chroma_qp_offset=-3 / threads=32 /
Where do you see -6 ???

[LucasSimba]

I see this

Where do you see -6 ???

The encode settings are the ones that I want and that I enter in RipBot264. I see -6 when I select the video file created with RipBot264 in MediaInfo.

[Atak_Snajpera]

x264 encoder most likely automatically changes that value because in my case after adding --chroma-qp-offset -3 to default profile I got chroma_qp_offset=-5
I suspect that value (-3) is incorrect with other settings and thus has to be automatically corrected by x264.

[LucasSimba]

x264 encoder most likely automatically changes that value because in my case after adding --chroma-qp-offset -3 to default profile I got chroma_qp_offset=-5
I suspect that value (-3) is incorrect with other settings and thus has to be automatically corrected by x264.

That’s weird because I can get -3 when I encode with Hybrid. But with Hybrid, analyse=0x3:0x113 becomes analyse=0x3:0x133 for some reason.

[SKPN]

Is there any way to encode to WEBM using VP8/VP9?

[guest]

Is there any way to encode to WEBM using VP8/VP9?

You've asked about this before.....

I'm pretty sure that RB can not do this...(but I could be proven wrong)

I would suggest that you give Handbrake a go...

https://handbrake.fr/docs/en/latest/technical/containers.html

or there's this :- (command line stuff, :scared:)

https://www.webmproject.org/

[SKPN]

You've asked about this before.....

I'm pretty sure that RB can not do this...(but I could be proven wrong)

I would suggest that you give Handbrake a go...

https://handbrake.fr/docs/en/latest/technical/containers.html

or there's this :- (command line stuff, :scared:)

https://www.webmproject.org/

I did ask once before, but I never got an answer. I've been using Handbrake for those encodes, but I was hoping to be able to use RB for the distributed encoding.

[guest]

I did ask once before, but I never got an answer. I've been using Handbrake for those encodes, but I was hoping to be able to use RB for the distributed encoding.

Yes, it is a little frustrating when you don't get a reply that you really want...

It's also a shame that the creators of Handbrake don't seem to be interested in adding a distributing encoding function :(

I guess to get the best out of HB is to have a powerful cpu, and fast storage (NVMe)

I guess you have a legit reason for wanting this format.

Cheers

[Tlen]

Hi,

i found this thread and this program searching for distributed x264 encoding.

So i'm going to try this (finger crossed)!

I've seen there is only a 2 pass mode.

Could you add a 3 pass mode?

I know most people think that even 2 pass its just useless,

but comparing thoroughly entirely many films in my collection

I've found that a third pass gives that little improvement (seen as better line, geometry, grain preservation)

that in a "Archival" scenario is wanted, no matter what.

So a 3 pass mode could be added?

Thank you very much

[guest]

Hi,

i found this thread and this program searching for distributed x264 encoding.

So i'm going to try this (finger crossed)!

I've seen there is only a 2 pass mode.

Could you add a 3 pass mode?

I know most people think that even 2 pass its just useless,

but comparing thoroughly entirely many films in my collection

I've found that a third pass gives that little improvement (seen as better line, geometry, grain preservation)

that in a "Archival" scenario is wanted, no matter what.

So a 3 pass mode could be added?

Thank you very much

Welcome to the forum..

So if you've just "found" RipBot264, what were you using before that could do 3 pass encodes ???

Surely certain filtering would do the job just as well, and probably faster than a 3 pass.

[Tlen]

Hi,

yes i just "found" it, because up till now i've done the job manually with a cmd script and calculating the bitrate with pen and paper.

With ripbot i could do calculations faster AND at the same time do parallel encoding.

And no, obiously no filtering can do a job of better preserving the original source.

[Atak_Snajpera]

Hi,

yes i just "found" it, because up till now i've done the job manually with a cmd script and calculating the bitrate with pen and paper.

With ripbot i could do calculations faster AND at the same time do parallel encoding.

And no, obiously no filtering can do a job of better preserving the original source.

May I ask you why you aim for certain bitrate/size? Are you going to put your videos on CD/DVD?

[Tlen]

Yes, i like to have a standard size for my collection, even if i put them on hard disk.

About DVD9 for every film (fhd) and some more for 3 hour films.

With 3 pass, and settings to max slowness (not placebo) and some tweaking, i find that size gives almost perfect reproduction of the source.

Moreover, in the past i did test with "quality" encoding and automatic bitrate.

I wasn't impressed by the results. I obtained a bigger file and lesser quality.

[Atak_Snajpera]

Why not use constant quality mode instead? x264 will automatically decide how mamy bits is required for particular movie. Using n-pass mode is only useful If you have fixed space. Every movie is different (duration and complexity) so using the same size limit is quite illogical for me.

[Tlen]

I understand that can seem counter-intuitive.

But with the multipass and fixed size the encoder can take out the best out of each (different) source.

Multipass gives the encoder the opportunity to analyse more times the same frames to take the best decisions.

Quality encoding can't be multipass so the analysis of the encoder is limited.

Indeed initially i was confident that quality encoding could do a good job (as you say),

but different tests proved me the opposite (compared to a tweaked multipass).

In a way, seems that leaving every decision to the encoder gives a sub par result comparing to manually tweaking (and mpass).

And this fact makes sense.

It's like comparing a stock car with factory settings, with the same tuned-nos-modded-stock car.

Obviously there's no match.

[Atak_Snajpera]

Btw. Have you tried x265 instead of x264. According to my tests you can expect better quality at default medium preset than x264 using veryslow. If you also add MDegrain2 filter then you can get even extra up to 1.8x size reduction in constant quality mode.

[Tlen]

Yes, i tried x265 too.

x265 (at last at the current stage), suffer from a loss of details, comparing to the (almost same presets) of x264 and same final size.

And this can appear counter-intuitive too ("What? a more modern encoder gives worst results at the same bitrate of an older one?")

This because x265 has been created to go where x264 can't.

That is, lower bitrate with acceptable quality. You will never be able to encode a UHD on a BD with x264 with the same quality as x265.

The downsize of it (up till now) is that you can't obtain the same quality of x264 at lower resolutions (and higher bitrates).

The aim of x265 is "good quality" on lower bitrates.

So if you want "Archival Quality" on higher bitrates x264 is a better choice.

Regarding the MDegrain2 (and filters in general), if you want to remain faithful to the original (as i want), filters are just a no-go.

If you want to obtain a smaller file at the cost of fidelity, yes you can use every filter you want.

But in this case there's no sense to make a multipass. A quality encoding (as you say) is sufficient.

Archival quality (my aim) is to obtain the most faithful reproduction of the original at an acceptable encoded final size.

[guest]

Yes, i tried x265 too.

x265 (at last at the current stage), suffer from a loss of details, comparing to the (almost same presets) of x264 and same final size.

And this can appear counter-intuitive too ("What? a more modern encoder gives worst results at the same bitrate of an older one?")

This because x265 has been created to go where x264 can't.

That is, lower bitrate with acceptable quality. You will never be able to encode a UHD on a BD with x264 with the same quality as x265.

The downsize of it (up till now) is that you can't obtain the same quality of x264 at lower resolutions (and higher bitrates).

The aim of x265 is "good quality" on lower bitrates.

So if you want "Archival Quality" on higher bitrates x264 is a better choice.

Regarding the MDegrain2 (and filters in general), if you want to remain faithful to the original (as i want), filters are just a no-go.

If you want to obtain a smaller file at the cost of fidelity, yes you can use every filter you want.

But in this case there's no sense to make a multipass. A quality encoding (as you say) is sufficient.

Archival quality (my aim) is to obtain the most faithful reproduction of the original at an acceptable encoded final size.

You have some very unusual expectations & requirements for your encoding, and I doubt that RB (or anything for that matter) will do what you want it to do.

Most of us like to clean up movies with an acceptable file size, and with old grainy, noisey movies, once they are filtered & cleaned they look SO much better than original.

Others like to increase bitrate (me) as they don't care what the file size is.

If you want to keep the original "quality" why don't you just copy them, as is.

What is your preferred file type ? (mkv, mp4, etc), or do you need them to be the correct size & format to burn to disc ??

I would suggest loading the files into MKVToolNix, remove the irrelevant tracks, and just produce an "original" quality mkv.

It just seems that you are spending a LOT of time, for no real result.

[Tlen]

You have some very unusual expectations & requirements for your encoding

I think instead i have a clear and legitimate goal (and actually reached if i can say it).

I doubt that RB (or anything for that matter) will do what you want it to do.

I'm already obtaining what i want.

I just asked to add to the program the option to make the 3rd pass (the second is already present). Simple as that.

and with old grainy, noisey movies, once they are filtered & cleaned they look SO much better than original.

That is your opinion.

In my opinion, you are destroying both atmosphere and details removing grain. Grain IS detail if you didn't think about that.

If you want to keep the original "quality" why don't you just copy them, as is.
That was my initial idea, but with an average of 30 gig per film, i would not have sufficient space.

9 Gig for film with almost perfect quality it's a good compromise for Archival Quality.

But here we are derailing on phylosophical and personal taste.

It just seems that you are spending a LOT of time, for no real result.
I'm spending my time with the result i want.

BTW. I repeat, just asked to add the option for third pass.

Could @Atak_Snajpera please add that? :)

That's all.

Thank you.

[Atak_Snajpera]

Grain IS detail if you didn't think about that.

Grain/noise is just an artefact covering details in picture. I prefer to stabilize those random dancing pixels with MDegrain2 than forcing an encoder to preserve them at any cost.

[guest]

I think instead i have a clear and legitimate goal (and actually reached if i can say it).



I'm already obtaining what i want.

I just asked to add to the program the option to make the 3rd pass (the second is already present). Simple as that.



That is your opinion.

In my opinion, you are destroying both atmosphere and details removing grain. Grain IS detail if you didn't think about that.


That was my initial idea, but with an average of 30 gig per film, i would not have sufficient space.

9 Gig for film with almost perfect quality it's a good compromise for Archival Quality.

But here we are derailing on phylosophical and personal taste.


I'm spending my time with the result i want.

BTW. I repeat, just asked to add the option for third pass.

Could @Atak_Snajpera please add that? :)

That's all.

Thank you.

Of course we are all entitled to our own opinions, and ways of doing things to our individual likings.

May I ask what the main formats & resolutions of your collection ??

'Cause if you think 9 gig is plenty, then you clearly not working with 4K, or even 1080p resolutions.

3 pass's on a 4K movie would take a considerable amount of time.

And unfortunately for you, I have no control whatsoever, with what gets added or changed in RipBot 264.

And from what I've read, Atak has his views on your situation, as well.

So I guess we'll just have to see if something is added.

[Tlen]

@Atak_Snajpera
On old films, grain / noise is integral part of the picture because a strip film is made of... circle grains wich can deteriorate becoming themselves "just grain".

So removing grain and noise you are removing part of the picture too.

Moreover, It's taken for granted that every denoiser by default remove valid part of the picture (altough small when well tuned) as part of standard false positive.

But this argument is part of the neverending debate "to denoise or not denoise".

I want just to point you at the fact that in case of too pushed denoising you end up in (unfortunately) common situations of plastic-look and devastated source like Predator Hunter Edition or Terminator 2.

In those case, they said "Wow look at how beutiful it is with all this ugly grain gone".

What a pity that all users with a minimum of experience badly complain with that, asking for disk replacement or refund.

There are plenty of forums with complaints about DNR (Bluray forum to say one)

@Pauly Dunne
Sorry, i had to be more precise.
All my collection is 1080p. And 9 gig for a 1080p (with accurately tuned multi pass) it's just... right. Not too big, not too small.

[Atak_Snajpera]

On old films, grain / noise is integral part of the picture because a strip film is made of... circle grains wich can deteriorate becoming themselves "just grain".
But grain != details still... By adding noise/grain you are not increasing details in frame. If you have old movie with grain then details are already destroyed (covered).

I want just point you at the fact that in case of too pushed denoising you end up in (unfortunately) common situations of plastic-look and devastated source like Predator Hunter Edition or Terminator 2.

In those case, they said "Wow look at how beutiful it is with all this ugly grain gone".
That's why I only use Mdegrain filter instead of KNLMeansCL. It is slow but instead of bluring whole frame it stabilizes noise (lower randomness in frames = better compressibility). Unfortunately I do not have access to my main PC right now but I will try later to post some examples how good results you can obtain without getting that "photoshopped" look on skin.

[Tlen]

You can have a point on stabilizing temporal noise, that hypotetically could cause not much damage,
but i prefer watching a film quite "imperfect" as seen on theater.
Removing temporal noise, gives the film a "static" appearance which i find a little strange.
But again it's a matter of taste.

Speaking about damage, i want to post one of big damage, Predator.

https://thumbs2.imagebam.com/9d/07/45/0b4bf01347598277.jpg (http://www.imagebam.com/image/0b4bf01347598277)https://thumbs2.imagebam.com/54/21/c1/bd22d01347598279.jpg (http://www.imagebam.com/image/bd22d01347598279)

Look at the water in the Hunter edition.
It's just made of... ceramic or gel... or alien something.

And that's a perfect example of how grain / noise, DEFINES a content.

[Atak_Snajpera]

You can have a point on stabilizing temporal noise, that hypotetically could cause not much damage,
but i prefer watching a film quite "imperfect" as seen on theater.
Removing temporal noise, gives the film a "static" appearance which i find a little strange.
But again it's a matter of taste.

Speaking about damage, i want to post one of big damage, Predator.

https://thumbs2.imagebam.com/9d/07/45/0b4bf01347598277.jpg (http://www.imagebam.com/image/0b4bf01347598277)https://thumbs2.imagebam.com/54/21/c1/bd22d01347598279.jpg (http://www.imagebam.com/image/bd22d01347598279)

Look at the water in the Hunter edition.
It's just made of... ceramic or gel... or alien something.

yeah that looks ugly indeed. This is typical when you use simple spatial denoiser.
https://www.youtube.com/watch?v=IgLtIzrnedc

MDegrain (Temporal Denoiser) won't give you that blurry mess.

[Tlen]

MDegrain (Temporal Denoiser) won't give you that blurry mess.

Yes, i know temporal denoisers, and as i've said they can do much less harm.

But it's a matter of preference :) (top respect for other opinions).

For me, over the time, unfiltered films seem to me more "natural".

That is to say that in the past i did my good amount of testing with filters :)

[Atak_Snajpera]

Yes, i know temporal denoisers, and as i've said they can do much less harm.

But it's a matter of preference :) (top respect for other opinions).

BTW. Those predator frames look like lazy upscale from SD resolution instead of proper transfer from film.

[Tlen]

Mmm, to me seems not.

Other screenshots seem to show details

https://caps-a-holic.com/c_list.php?c=4788

Not a perfect transfer (the original one), but i've seen worse.

[Atak_Snajpera]

Mmm, to me seems not.

Other screenshots seem to show details

https://caps-a-holic.com/c_list.php?c=4788

Not a perfect transfer (the original one), but i've seen worse.

Very thick grain looks suspicious... I do not see high resolution at all in all those screenshots. Everything seems too blurry in comparison to other movies from that time period.

Aliens looks much better
https://caps-a-holic.com/c.php?go=1&a=0&d1=5207&d2=5208&s1=48586&s2=48602&i=4&l=0