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

[guest]

So I did another "big ass" 4K encode today, first one in a while due to the DE problems....

It was a 3h:48m movie, originally approx 33 Gb, @ 14mb/s bitrate, I used crf 10, no filters, it ended up being approx 77 Gb @ 42mb/s.

RB reported the job to have taken 5h:33m to complete, but in reality it took 6h:45m, as there seems to be a little bit of a discrepancy with that ETA calculation.

All in all, I had a pretty good run, a couple of servers dropped out during the encode, and strangely enough, ES didn't show that they had done so.

So it was a good test for the newest build.

But there is something that I sincerely hope can be considered in the very near future, and that is some more servers, say from 16, up to 20, as I have a few more pc's that could help the cause.

I know I'm not on your Christmas Card list, Atak, but please consider, that's all I can ask.

[guest]

Thanks, something is also broken in 2-pass in v1.25.0. The "job1_EncodeVideoPass2.cmd" is blank. The process stops after the first pass.

Have you got the latest update yet ??

Don't do any 2 pass, so I can't help there.

[tkwou]

Is there a link to download the latest version? I've only been relying on the update program and so far nothing else has updated. I reverted back to v1.24.0 everything seems to work with 2-pass again.

Latest entries in update_log.txt
2019-11-28 10:22:18 : [ERROR] C:\Program Files (x86)\Ripbot264\updates\core.zip is corrupted. CRC32 mismatch. Expected value was A8535996 but got D41A7FD1
2019-11-28 10:22:18 : File C:\Program Files (x86)\Ripbot264\updates\core.zip has been deleted.
2019-11-28 10:22:18 : [ERROR] C:\Program Files (x86)\Ripbot264\updates\ffmpeg.zip is corrupted. CRC32 mismatch. Expected value was 1026A3C but got 9ACD5420
2019-11-28 10:22:18 : File C:\Program Files (x86)\Ripbot264\updates\ffmpeg.zip has been deleted.
2019-11-28 10:22:18 : Installation complete.
2019-11-28 10:22:20 : Next check after 2019-11-29 10:20:56

[tkwou]

Ok, well I decided to try editing the update.ini file so the CRC32 values would match and this managed to force an update. Now I'm at v1.25.0, the Client is at 1.15.1.0 and the Server is at 1.16.1.0. FFMPEG also updated too. I'll try another encode and see what happens.

[guest]

Ok, well I decided to try editing the update.ini file so the CRC32 values would match and this managed to force an update. Now I'm at v1.25.0, the Client is at 1.15.1.0 and the Server is at 1.16.1.0. FFMPEG also updated too. I'll try another encode and see what happens.

Hi tkwou,

Props to you for sorting that mess out.

Obviously some conflict between times & file names, etc.

Sadly, there aren't many options to get the "latest" version, as for what ever reason, and after many requests, you can ONLY get v1.24.0 from the first page.

So what you could try, is getting v1.24.0, and doing a large auto update which should bring you right up to date.

OR

I posted a pretty recent build that was the last one that worked before the DE problems...you could grab that, and then do an auto update on that...end result will be the same, just a lot less files in the update download.

So if you want to try mine, the link is on post #17777

https://forum.doom9.org/showthread.php?p=1890571#post1890571

[tkwou]

Thank you, so everything is working fine now that I have all the core files updated. DE is also working fine now that all the other computers are also updated. The 2 pass problem I was having has also been fixed by this update.

[guest]

Thank you, so everything is working fine now that I have all the core files updated. DE is also working fine now that all the other computers are also updated. The 2 pass problem I was having has also been fixed by this update.

:thanks: & :cool:

[Atak_Snajpera]

It was a 3h:48m movie, originally approx 33 Gb, @ 14mb/s bitrate, I used crf 10, no filters, it ended up being approx 77 Gb @ 42mb/s.
I still can't figure out why you keep increasing file size instead of decreasing it like rest of 99,999% people using ripbot264.

[ReinerSchweinlin]

It was a 3h:48m movie, originally approx 33 Gb, @ 14mb/s bitrate, I used crf 10, no filters, it ended up being approx 77 Gb @ 42mb/s.
CRF10? Why?

[guest]

I still can't figure out why you keep increasing file size instead of decreasing it like rest of 99,999% people using ripbot264.

Well, I guess you really don't need to figure it out...I'm happy to be that 0.001% that does things differently.

Like I state in my sig:- "Not poorly done, just doin' it my way !!!"

However, having said that, I can't recall anyone suggesting some "good" settings for retaining quality, AND small size, without the process taking forever !!!

---------------------------------------------------------------------------

So this was actually a bit of an upscaling "test", I chose the 1st of the "Lord Of The Rings" movies, the extended edition, which of course is a LONG 1080p x264 movie, and I wanted to see how it would turn out as a 2160p, x265.

So instead of using a 1 pass, 60,000kb/s run, I opted for CRF 10.

I've read on several forums that the optimal bitrate for 2160p x265, is between 45 - 65Mb/s, hence my settings.

And that was the result (size wise), quality....meh, couldn't really tell.

But one thing that didn't take very long was the combining & muxing at the end, thanks to the NVMe's (thanks for that).

So that's that !!! I just need to figure out what the problem is with a server dropping out, randomly.

So a question about the 2 "new" buttons in Encoding Client, that's pretty much only used between jobs (in a queue), correct ??

I have implemented another app, to shutdown a remote server, when it's not doing much.

And please keep in mind, the addition of more servers, in the not too distant future :)

[guest]

CRF10? Why?

Well, BECAUSE I CAN !!!!

I've noticed too many people are quick with critism (and I'm guilty of that, too), but not forth coming with suggestions (on certain subjects).

Please read my above reply to Atak, that might help.

What would you suggest for good quality, size & time taken, 4K encoding settings ??

[Atak_Snajpera]

Like I state in my sig:- "Not poorly done, just doin' it my way !!!"
Do not forget about FU sign as avatar under your nick...

[Ronski]

Well, BECAUSE I CAN !!!!

I've noticed too many people are quick with critism (and I'm guilty of that, too), but not forth coming with suggestions (on certain subjects).

Please read my above reply to Atak, that might help.

What would you suggest for good quality, size & time taken, 4K encoding settings ??

What screen size do what the resultant video on? I use H265 CRF22 and I can't tell the difference on a 120" screen, maybe if the two were side by side I could.

[guest]

What screen size do what the resultant video on? I use H265 CRF22 and I can't tell the difference on a 120" screen, maybe if the two were side by side I could.

Hey Ronski, I know you mean't to say "What screen size do you watch the resultant video on ?

I only have a 55" UHD screen, I would doubt that a 120" screen would have a good pixel size/resolution, it's still 3840 x 2160...I would suggest that it would be "cleaner" on a smaller screen.

Even viewing a 55" along side a 75/76" screen, the 55" looks "cleaner".

I will try your "setting's", so thanks for your info.

[guest]

Do not forget about FU sign as avatar under your nick...

Yes, the "old middle finger"...not necessarily FU, could be contempt or defiance..

I've often wondered what your avatar is all about...

[Atak_Snajpera]

I've often wondered what your avatar is all about...
Never heard of tekken game?

[guest]

Never heard of tekken game?

Not a gamer, so no, I wouldn't have a clue...thanks for the explanation :(

Hwoarang....

[Atak_Snajpera]

But one thing that didn't take very long was the combining & muxing at the end, thanks to the NVMe's (thanks for that).
This beta version of EncodingClient.exe is now combining chunks on fly as soon as they are encoded (yes code checks if order of completion is correct)
https://www.mediafire.com/file/zat5jd4as3wa1jl/EncodingClient.exe/file
If tests goes well I will push another auto-update.

[GZZ]

So I did another "big ass" 4K encode today, first one in a while due to the DE problems....

It was a 3h:48m movie, originally approx 33 Gb, @ 14mb/s bitrate, I used crf 10, no filters, it ended up being approx 77 Gb @ 42mb/s.


Dont know if you missed how crf works. It stands for constant rate factor and it tries is to keep at constant image quality without looking at the bitrate. So if your source is only 14Mbit, the crf 10 might oversize your output as it tries to use a higher bitrate. Having a higher bitrate then source wont make the picture better and its just wasting bits. What can help you on a 14Mbit source is to use x265 if source is x264, that will half the size of your input at the same quality and half the bitrate.

Using crf 18-20 is normal and gives a 1:1 quality at a lower birtrate. Also use default (medium) preset. Its a allround really good quality without insane encoding times. X265 is alot slower the x264 because the codec is more advanced and the compression is more difficult. use 2 pass if your going for a specific filesize. You never know the output filesize of crf.

[Ryushin]

What would you suggest for good quality, size & time taken, 4K encoding settings ??

I encode everything to CRF18 I want to keep for storage. I make a separate 1080p HDR from the 4K source at CRF21 for streaming purposes for my family and a 720p CRF21 from 1080p sources.

I've looked long and hard at 1080p blu-ray sources against the CRF18 x264 encodes. Only time I can tell any difference if I pause a single frame and look really close. When the video is running I cannot tell any difference from CRF18 and the original. From what I read x265 CRF is about 2 steps better than x264 in quality. So x265 CRF20 would look the same as x264 CRF18. Since switching to x265 for all my encodes, I'm still doing CRF18, so I'm getting better quality than if I used x264.

Try taking a good quality 4K and HD source and making a CRF18 x265 file and compare that to a CRF10 x265 file. I'm sure you will not be able to tell the difference.

I never upscale my sources. My Sony TV upscaling engine is excellent so there is no need.

I'm not a fan of grain as I feel it distracts from the film (and it also make the file size larger) so I use MDegrain2/3 with a setting usually from 100-600. Some films come out looking so much better it is startling. The Blade Runner 4K comes to mine. A grainy soupy mess and my wife and I did not like it. Once it went through MDegrain, holy smokes, it was like looking at a different film.

I try and shoot for a 2 hour HD source to be about 5GB in size and a 4K source to be about 15GB in size. I adjust MDegrain (if needed) settings until I reach something like that. For some super grainy sources, such as Blade Runner it still comes out to much larger and closer to 30GB. All depends on the sources.

Some computer 4K generated movies shrink so small that I go to CRF16 and they are still under 10GB.

[guest]

This beta version of EncodingClient.exe is now combining chunks on fly as soon as they are encoded (yes code checks if order of completion is correct)
https://www.mediafire.com/file/zat5jd4as3wa1jl/EncodingClient.exe/file
If tests goes well I will push another auto-update.

Awesome...

You really DO love this shit, don't you !!! :)

I will give this a run, at my next opportunity. (edit:- I tried this today, and I think I might have missed something, but it was probably the combining of chunks, der..... I only noticed the muxing part), why I said I missed something was because I was doing short encodes, and the combining time would have been short, anyway.

So can I suggest something ???

With the upcoming update, can you PLEASE, PLEASE, PLEASE consider a build version number revision (as a reference point to a substantial change), say at least v1.26.0.

And again, it would be really nice if you could also post a more recent build on page 1, as it's getting horribly close to 12 months old.

[guest]

Dont know if you missed how crf works. It stands for constant rate factor and it tries is to keep at constant image quality without looking at the bitrate. So if your source is only 14Mbit, the crf 10 might oversize your output as it tries to use a higher bitrate. Having a higher bitrate then source wont make the picture better and its just wasting bits. What can help you on a 14Mbit source is to use x265 if source is x264, that will half the size of your input at the same quality and half the bitrate.

Using crf 18-20 is normal and gives a 1:1 quality at a lower birtrate. Also use default (medium) preset. Its a allround really good quality without insane encoding times. X265 is alot slower the x264 because the codec is more advanced and the compression is more difficult. use 2 pass if your going for a specific filesize. You never know the output filesize of crf.

Hey GZZ, I think I have a bit of an idea, I went here :-

https://trac.ffmpeg.org/wiki/Encode/H.264

and here :-

https://trac.ffmpeg.org/wiki/Encode/H.265

and had a bit of a read...very interesting.

And yes, using crf, you have no idea what the final "size" will be, mind you, I don't really care what the final size is.

I have only tried 1 pass, as 2 pass would have to basically double the encoding time :(

[guest]

I encode everything to CRF18 I want to keep for storage. I make a separate 1080p HDR from the 4K source at CRF21 for streaming purposes for my family and a 720p CRF21 from 1080p sources.

I've looked long and hard at 1080p blu-ray sources against the CRF18 x264 encodes. Only time I can tell any difference if I pause a single frame and look really close. When the video is running I cannot tell any difference from CRF18 and the original. From what I read x265 CRF is about 2 steps better than x264 in quality. So x265 CRF20 would look the same as x264 CRF18. Since switching to x265 for all my encodes, I'm still doing CRF18, so I'm getting better quality than if I used x264.

Try taking a good quality 4K and HD source and making a CRF18 x265 file and compare that to a CRF10 x265 file. I'm sure you will not be able to tell the difference.

I never upscale my sources. My Sony TV upscaling engine is excellent so there is no need.

I'm not a fan of grain as I feel it distracts from the film (and it also make the file size larger) so I use MDegrain2/3 with a setting usually from 100-600. Some films come out looking so much better it is startling. The Blade Runner 4K comes to mine. A grainy soupy mess and my wife and I did not like it. Once it went through MDegrain, holy smokes, it was like looking at a different film.

I try and shoot for a 2 hour HD source to be about 5GB in size and a 4K source to be about 15GB in size. I adjust MDegrain (if needed) settings until I reach something like that. For some super grainy sources, such as Blade Runner it still comes out to much larger and closer to 30GB. All depends on the sources.

Some computer 4K generated movies shrink so small that I go to CRF16 and they are still under 10GB.

Hey Ryushin, :goodpost:

I am actually a little reluctant to use MDegrain on a large 4K source....wouldn't it take forever ???

I'd suggest that your crf 18 would be a good place to be, but I am still experimenting, before I settle on what I like. But yeah, I think around the 16 - 18 mark, will be it.

OR, I could just go to my high single pass settings, like I was going to in the first place, then you know approx what size you'll end up with.

I never upscale my sources. My Sony TV upscaling engine is excellent so there is no need.

My LG TV does a pretty good job, too...nearly EVERYTHING looks good on that :)

I'm not a fan of grain as I feel it distracts from the film (and it also make the file size larger) so I use MDegrain2/3 with a setting usually from 100-600.

I think the default for MDegrain, in RB is 400 (if I'm looking in the right place)

#Denoise
Loadplugin("D:\RipBot264v1.25.0\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
fv1=MAnalyse(super,isb=false,delta=1,overlap=4)
bv1=MAnalyse(super,isb=true,delta=1,overlap=4)
fv2=MAnalyse(super,isb=false,delta=2,overlap=4)
bv2=MAnalyse(super,isb=true,delta=2,overlap=4)
video=MDegrain2(video,super,bv1,fv1,bv2,fv2,thSAD=400)


I have to say, I haven't heard the phrase, "holy smokes" for such a long time...nice :)

[GZZ]

Hey Ryushin, :goodpost:

I am actually a little reluctant to use MDegrain on a large 4K source....wouldn't it take forever ???


MDegrain2 takes time on 4k source, but it also depends on the among og noise/film grain the source have. There is also a MDegrain1 and 3. Mdegrain1 is for light denoise, MDegrain2 is default and does a good job, if its still not enough, the MDegrain3. M3 will be slowest and M1 is faster then M2.

It could be nice to have a feature to select a single block (1-2 min) from the movie and run 3 small encodings with the above to see which one to use on the entire movie.

MDegrain 1 and 3 is not default in RB, you need to add them as a custom filter

[guest]

MDegrain2 takes time on 4k source, but it also depends on the among og noise/film grain the source have. There is also a MDegrain1 and 3. Mdegrain1 is for light denoise, MDegrain2 is default and does a good job, if its still not enough, the MDegrain3. M3 will be slowest and M1 is faster then M2.

It could be nice to have a feature to select a single block (1-2 min) from the movie and run 3 small encodings with the above to see which one to use on the entire movie.

MDegrain 1 and 3 is not default in RB, you need to add them as a custom filter

On the few movies that I have used M2 on, it seems to able to determine what it needs to do to that particular source :)

There is a little "tool" called "DGSplit", that can "cut" a user determined sized chunk out of a movie, and then you could do the test encodes on them.

Yes, I know that M2 is default, but I wouldn't have a clue of even where to start to add M1 or M3 as a custom filter (hint, hint)

[Ryushin]

I am actually a little reluctant to use MDegrain on a large 4K source....wouldn't it take forever ???

I'd suggest that your crf 18 would be a good place to be, but I am still experimenting, before I settle on what I like. But yeah, I think around the 16 - 18 mark, will be it.

I think the default for MDegrain, in RB is 400 (if I'm looking in the right place)

#Denoise
Loadplugin("D:\RipBot264v1.25.0\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
fv1=MAnalyse(super,isb=false,delta=1,overlap=4)
bv1=MAnalyse(super,isb=true,delta=1,overlap=4)
fv2=MAnalyse(super,isb=false,delta=2,overlap=4)
bv2=MAnalyse(super,isb=true,delta=2,overlap=4)
video=MDegrain2(video,super,bv1,fv1,bv2,fv2,thSAD=400)


I have to say, I haven't heard the phrase, "holy smokes" for such a long time...nice :)

I like older phrases. :)

MDegrain2 adds to the encoding time for sure. It usually doubles or triples the time to encode. My end goal though is for the movie to look just as good as the source or better than the source with the grain removed. So for me, encoding time isn't as important as the final quality.

I know there are some purists that want grain and want it to look like a film and to only run at 24fps (no soap opera effect). To me, I want to be wrapped up in the film, so i want it to be clean and I like that the TV interpolate frames to make it have smooth motion.

The default for RipBot264 MDegrain2 is 400 like you mentioned. I've been after Atak to extend the MDegrain option to choose 1-3 and thSAD input box with a range between 0-800.

My MDegrain3 looks like this:
Loadplugin("C:\Program Files\RipBot264\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
bv1=MAnalyse(super,blksize=8,isb=true,delta=1,overlap=4)
bv2=MAnalyse(super,blksize=8,isb=true,delta=2,overlap=4)
bv3=MAnalyse(super,blksize=8,isb=true,delta=3,overlap=4)
fv1=MAnalyse(super,blksize=8,isb=false,delta=1,overlap=4)
fv2=MAnalyse(super,blksize=8,isb=false,delta=2,overlap=4)
fv3=MAnalyse(super,blksize=8,isb=false,delta=3,overlap=4)
video=MDegrain3(video,super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=400)

I usually edit the avisynth script in the edit window to change the thSAD value. It's very rare that I need to go with MDegrain3, but when I do, I just replace Atak's line with mines.

Those links ffmpeg links you sent look good. It looks like I was mistaken then. FFMPEG says it's a 5 value difference from x264 to x265 to have it look the same. So x265 CRF18 should look the same as x264 CRF13. So for the CRF18 with x265 would be visually indistinguishable from the source.

[Atak_Snajpera]

This should explain why I decided to not use MDegrain3
https://i.postimg.cc/NFB44R4L/1.png https://i.postimg.cc/KznfB0td/2.png

Quick summary:
MDegrain1 vs No Denoise
Encoding speed reduction = 1.72x
File size reduction = 1.49x
Size/Speed ratio = 0.87

MDegrain2 vs No Denoise
Encoding speed reduction = 2.70x
File size reduction = 1.75x
Size/Speed ratio = 0.65

MDegrain3 vs No Denoise
Encoding speed reduction = 3.57x
File size reduction = 1.92x
Size/Speed ratio = 0.54

[Ryushin]

This should explain why I decided to not use MDegrain3
https://i.postimg.cc/NFB44R4L/1.png https://i.postimg.cc/KznfB0td/2.png

Quick summary:
MDegrain1 vs No Denoise
Encoding speed reduction = 1.72x
File size reduction = 1.49x
Size/Speed ratio = 0.87

MDegrain2 vs No Denoise
Encoding speed reduction = 2.70x
File size reduction = 1.75x
Size/Speed ratio = 0.65

MDegrain3 vs No Denoise
Encoding speed reduction = 3.57x
File size reduction = 1.92x
Size/Speed ratio = 0.54

On some very grainy 4K sources, MDegrain3 has cleaned up source enough to further reduce the size by 5-10GB. That is pretty significant. MDegrain3 also did wonders with the Walking Dead series.

[guest]

This should explain why I decided to not use MDegrain3

On some very grainy 4K sources, MDegrain3 has cleaned up source enough to further reduce the size by 5-10GB. That is pretty significant. MDegrain3 also did wonders with the Walking Dead series.

I'd just like to add my 2 cents worth, here...

It would be interesting to see that info for 4K x265 filtering.

Graphs, data, % etc, are all well and good, but the final test is one's eye's !!!

As 4K is becoming the norm, it needs to work for that.

I'm probably wrong, but I'm sure it wouldn't take very long for Atak to implement more MDegrain options, he's got M2 setup, all that possibly needs doing is edit the scripts for M1 & M3, add them to the drop down list, and there you have it....no more discussion.

Now who here, uses KNLMeansCL ???, it certainly doesn't seem to be mentioned very often, and I think it being fundamentally a GPU based filter, you need a powerful GPU, if I recall, you also need particular software/drivers to be able to use it, and it's SLOW....so combining M2 & KNL, would take days to encode a feature length movie, especially 4K.

There's 1 x KNL (on it's own), and 3 with M2, and 1 x M2 (on its own) option's, in the dropdown.

Personally I miss, HQDN3D, I use to use that a lot.

[Ryushin]

Graphs, data, % etc, are all well and good, but the final test is one's eye's !!!

As 4K is becoming the norm, it needs to work for that.

Now who here, uses KNLMeansCL ???, it certainly doesn't seem to be mentioned very often, and I think it being fundamentally a GPU based filter, you need a powerful GPU, if I recall, you also need particular software/drivers to be able to use it, and it's SLOW....so combining M2 & KNL, would take days to encode a feature length movie, especially 4K.

Personally I miss, HQDN3D, I use to use that a lot.

May I suggest buying the first Blade Runner in 4K and running MDegrain2-600 against that and then Watching the original. Especially the first scene when he gives the voidcomp (sp?) test in the hazy florescent room. MDegrain is so amazing in that it took out the soupy grain but left details like the cigarette smoke clear to see and make out. Maybe I'll cut out the two scenes and upload them.

I used to use HQDN3D. It was far faster than MDegrain2 and it was for a time, the only option available. The quality results though, vastly different between the two. So different I actually went back re-encoded a few sources with the new MDegrain and this was before Atak implemented threading and I was only getting 2fps. The quality was worth the wait. Now HQDN3D was also good to me when using in conjunction with MDegrain to remove a bit more harder to remove grain. But since HQDN3D cannot to 10Bit color (if I remember right) Atak removed it. That is when I switched to using MDegrain3.

[Atak_Snajpera]

May I suggest buying the first Blade Runner in 4K and running MDegrain2-600 against that and then Watching the original. Especially the first scene when he gives the voidcomp (sp?) test in the hazy florescent room. MDegrain is so amazing in that it took out the soupy grain but left details like the cigarette smoke clear to see and make out. Maybe I'll cut out the two scenes and upload them.

I used to use HQDN3D. It was far faster than MDegrain2 and it was for a time, the only option available. The quality results though, vastly different between the two. So different I actually went back re-encoded a few sources with the new MDegrain and this was before Atak implemented threading and I was only getting 2fps. The quality was worth the wait. Now HQDN3D was also good to me when using in conjunction with MDegrain to remove a bit more harder to remove grain. But since HQDN3D cannot to 10Bit color (if I remember right) Atak removed it. That is when I switched to using MDegrain3.

Yes upload IT please.

[slalom]

That is when I switched to using MDegrain3.
I don't see that in the menu, is that only for 4K?

[Atak_Snajpera]

I don't see that in the menu, is that only for 4K?

You have to create custom script


#Denoise
Loadplugin("C:\Program Files\RipBot264\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
bv1=MAnalyse(super,blksize=8,isb=true,delta=1,overlap=4)
bv2=MAnalyse(super,blksize=8,isb=true,delta=2,overlap=4)
bv3=MAnalyse(super,blksize=8,isb=true,delta=3,overlap=4)
fv1=MAnalyse(super,blksize=8,isb=false,delta=1,overlap=4)
fv2=MAnalyse(super,blksize=8,isb=false,delta=2,overlap=4)
fv3=MAnalyse(super,blksize=8,isb=false,delta=3,overlap=4)
video=MDegrain3(video,super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=400)

[Ryushin]

I've cut 7:39 from the beginning of Blade Runner which includes the voight kampff test. The original and the Mdegrain3-800 is here. I'l leave this up for a week and then take it down.

https://cloud.chrisdos.com/index.php/s/YQJ2Y6LEdPcweEP

[stryker412]

Atak, I'm finalizing a new gaming/encoding build. With regards to Ripbot only, what do you think of this build? Any hardware not ripbot friendly? I'm looking at the 5700XT vs 2070 Super for GPU.

https://pcpartpicker.com/user/Stryker412/saved/#view=mW7zNG

[Atak_Snajpera]

Atak, I'm finalizing a new gaming/encoding build. With regards to Ripbot only, what do you think of this build? Any hardware not ripbot friendly? I'm looking at the 5700XT vs 2070 Super for GPU.

https://pcpartpicker.com/user/Stryker412/saved/FwQXvK

This part list is private.

[stryker412]

This part list is private.

Sorry, fixed the original link.

[Atak_Snajpera]

Sorry, fixed the original link.

Everything looks great except that SSD... QLC? Really? You won't be happy with 100 MiB/s real write speed...
http://thessdreviewcdn2.thessdreview1.netdna-cdn.com/wp-content/uploads/2018/07/Intel-SSD-660P-HDTune.png

[slalom]

You have to create custom script


#Denoise
Loadplugin("C:\Program Files\RipBot264\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
bv1=MAnalyse(super,blksize=8,isb=true,delta=1,overlap=4)
bv2=MAnalyse(super,blksize=8,isb=true,delta=2,overlap=4)
bv3=MAnalyse(super,blksize=8,isb=true,delta=3,overlap=4)
fv1=MAnalyse(super,blksize=8,isb=false,delta=1,overlap=4)
fv2=MAnalyse(super,blksize=8,isb=false,delta=2,overlap=4)
fv3=MAnalyse(super,blksize=8,isb=false,delta=3,overlap=4)
video=MDegrain3(video,super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=400)
Any chance of adding this to the menu for novices like me?

[stryker412]

Everything looks great except that SSD... QLC? Really? You won't be happy with 100 MiB/s real write speed...
http://thessdreviewcdn2.thessdreview1.netdna-cdn.com/wp-content/uploads/2018/07/Intel-SSD-660P-HDTune.png

I currently have a 2nd drive for ripbot encodes. What drive type do you suggest as a 2nd drive?

[Atak_Snajpera]

Any chance of adding this to the menu for novices like me?

Just save that to a file in Tools\AviSynth plugins\Scripts\Custom

Just make sure path in LoadPlugin is correct

[Atak_Snajpera]

I currently have a 2nd drive for ripbot encodes. What drive type do you suggest as a 2nd drive?

Something decent using at least TLC... Just avoid QLC like plague because write endurance is also lower than in TLC.

[stryker412]

Something decent using at least TLC... Just avoid QLC like plague because write endurance is also lower than in TLC.

How about this one?
https://www.newegg.com/crucial-mx500-1tb/p/N82E16820156178?Item=N82E16820156178

[guest]

You have to create custom script


#Denoise
Loadplugin("C:\Program Files\RipBot264\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
bv1=MAnalyse(super,blksize=8,isb=true,delta=1,overlap=4)
bv2=MAnalyse(super,blksize=8,isb=true,delta=2,overlap=4)
bv3=MAnalyse(super,blksize=8,isb=true,delta=3,overlap=4)
fv1=MAnalyse(super,blksize=8,isb=false,delta=1,overlap=4)
fv2=MAnalyse(super,blksize=8,isb=false,delta=2,overlap=4)
fv3=MAnalyse(super,blksize=8,isb=false,delta=3,overlap=4)
video=MDegrain3(video,super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=400)

This is Gold !!! :)

Any chance of a script for MDegrain1, to complete the set ? :rolleyes:

[Atak_Snajpera]

How about this one?
https://www.newegg.com/crucial-mx500-1tb/p/N82E16820156178?Item=N82E16820156178

That one is sataIII not NVMe!

[Atak_Snajpera]

This is Gold !!! :)

Any chance of a script for MDegrain1, to complete the set ? :rolleyes:

#Denoise
Loadplugin("C:\Program Files\RipBot264\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
bv1=MAnalyse(super,blksize=8,isb=true,delta=1,overlap=4)
fv1=MAnalyse(super,blksize=8,isb=false,delta=1,overlap=4)
video=MDegrain1(video,super,bv1,fv1,thSAD=400)

[stryker412]

That one is sataIII not NVMe!


Gotcha. Found this one but it's much more expensive.

https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=nvme&psr=EY17&qid=1575306879&s=cyber-monday&smid=ATVPDKIKX0DER&sr=1-1

[guest]

#Denoise
Loadplugin("C:\Program Files\RipBot264\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
bv1=MAnalyse(super,blksize=8,isb=true,delta=1,overlap=4)
fv1=MAnalyse(super,blksize=8,isb=false,delta=1,overlap=4)
video=MDegrain1(video,super,bv1,fv1,thSAD=400)

:thanks:

[stryker412]

Atak what about nvidia vs Radeon for GPU?

[guest]

Gotcha. Found this one but it's much more expensive.

https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=nvme&psr=EY17&qid=1575306879&s=cyber-monday&smid=ATVPDKIKX0DER&sr=1-1

Or

https://www.amazon.com/XPG-SX8200-Gen3x4-3000MB-ASX8200PNP-1TT-C/dp/B07K1J3C23/ref=mp_s_a_1_2?keywords=adata+nvme&qid=1575307192&sr=8-2

I have some 512Gb versions, but I think I would go for EVO Plus, next. Pro's would be nice, but too exy :(