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

[guest]

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.

Interesting find with the bug :)

I had to say "good & the bad" feedback, and yes, I don't think you actually have given any bad, as you say....

If you download the "Lite" build, the changelog.txt, will explain the changes a lot more than I mentioned here, on the Forum.

It should be the same to use as "standard" RB, just with the SMDegrain scripts available to use, without any "fiddling", and I also mention that Autoupdates could probably be enabled, without any effect on what I've added.

And yes, it would be interesting to know how many RB downloads have been accessed from Mediafire...it would have to be substantial.

Just in the time I've been posting stuff, there would be a total of many, many hundreds of downloads...

[cypher007]

ok tried again to use the working hours function, this time with a fresh install of win 10. it shutsdown but still doesnt wake up. i can wake it using wol but ripbot sits there saying its waiting till the time set to start encoding, which has already passed.

[cypher007]

the machine will wake if i press a key on the keyboard. how does ripbot schedule the shutdown and startup?

[guest]

the machine will wake if i press a key on the keyboard. how does ripbot schedule the shutdown and startup?

You must have a short memory, approx 4 months ago, you asked the same question(s).

https://forum.doom9.org/showthread.php?p=1972932#post1972932

Atak actually tried to help, a lot, with all sorts of suggestions, and even a "special" fix.

And now, here "we" are again...

Clearly there is something about your setup, motherboard BIOS settings, Windows power settings, etc.

Atak provides these services that I'm sure he tests thoroughly, BUT just because it works on his setup, doesn't mean it will on someone else's !!!

https://forum.doom9.org/showthread.php?p=1973545#post1973545

AGAIN, if you can't get it to work, then you'll just have to find some other way to do what you're expecting this to do.

[Atak_Snajpera]

ok tried again to use the working hours function, this time with a fresh install of win 10. it shutsdown but still doesnt wake up. i can wake it using wol but ripbot sits there saying its waiting till the time set to start encoding, which has already passed.

try this
1) Change system date format to YYYY/MM/DD
2) open ripbot264 (do not click on settings!)
3) open WorkHours.csv in notepad
4) add start and end time. for example.

"2022-11-29 12:00";"2022-11-29 12:01"
"2022-11-29 12:02";"2022-11-29 12:03"

5) Save file.
6) Run some encoding
if everything goes well encoding will start automatically at 12:00 and pc will go to sleep mode at 12:01. Then at 12:02 PC will weak up automatically. At 12:03 PC will shut down again.

[guest]

try this
1) Change system date format to YYYY/MM/DD
2) open ripbot264 (do not click on settings!)
3) open WorkHours.csv in notepad
4) add start and end time. for example.

"2022-11-29 12:00";"2022-11-29 12:01"
"2022-11-29 12:02";"2022-11-29 12:03"

5) Save file.
6) Run some encoding
if everything goes well encoding will start automatically at 12:00 and pc will go to sleep mode at 12:01. Then at 12:02 PC will weak up automatically. At 12:03 PC will shut down again.

So what I would like to know is, when using this feature, what happens to the progress of the encode, when it turns itself off ??

If you were using DE, then whatever chunk(s) is being processed, would be lost, when the pc shuts down, and hopefully, when it starts again, it would start on the next chunk (the one that was not completed, when it shutdown), but if you weren't using DE, then the whole encode would be lost.

I really can't understand why this is a good idea.....

[darkio]

thanks a lot for automatic colormatrix conversion!

I hope to see in nesr future dehalo (some stupid avsi svript), dering, deband and derainbow filter with good settings.
Some old anime can benefit it.
Manual import of these script or load plugin works well edit ripbot script.

[cypher007]

You must have a short memory, approx 4 months ago, you asked the same question(s).

https://forum.doom9.org/showthread.php?p=1972932#post1972932

Atak actually tried to help, a lot, with all sorts of suggestions, and even a "special" fix.

And now, here "we" are again...

Clearly there is something about your setup, motherboard BIOS settings, Windows power settings, etc.

Atak provides these services that I'm sure he tests thoroughly, BUT just because it works on his setup, doesn't mean it will on someone else's !!!

https://forum.doom9.org/showthread.php?p=1973545#post1973545

AGAIN, if you can't get it to work, then you'll just have to find some other way to do what you're expecting this to do.

its not quite the same as this time im using windows 10 rather than windows server 2022. i thought i would eliminate the OS doing odd stuff.

[rlev11]

Trying out the new PD-Lite version as I would like to start doing some smdegrain comparisons, but having issues with the scripts.

when ever I choose a smdegrain custom script, when it goes to start decoding I immediately get a :

temp\ripbot264temp\job1\info.txt does not exist

and the encode immediately aborts. Not sure what is going on, I first thought the plugins variable wasn't set correctly so i changed all the call outs to the hardcoded path to the avisynth plugins folder. That changed nothing.

Any thoughts?? choosing mdegrain like normal works fine, just the custom smdegrain scripts

I checked and something in the smdegrain script is keeping the info.txt from being generated. It is there if I don;t choose a smdegrain script, but as soon as I do it dissapears in the job folder.

it is definately something with the last line:
video=SMDegrain(video,tr=2,thSAD=200,thSADC=100,contrasharp=true,prefilter=0,refinemotion=true,blksize=8)


if I remove this from the script leaving all the loadPlugin and Import lines the encode does at least runs although it doesn't really do anything.

[cypher007]

try this
1) Change system date format to YYYY/MM/DD
2) open ripbot264 (do not click on settings!)
3) open WorkHours.csv in notepad
4) add start and end time. for example.

"2022-11-29 12:00";"2022-11-29 12:01"
"2022-11-29 12:02";"2022-11-29 12:03"

5) Save file.
6) Run some encoding
if everything goes well encoding will start automatically at 12:00 and pc will go to sleep mode at 12:01. Then at 12:02 PC will weak up automatically. At 12:03 PC will shut down again.

Ok tried it. Clicked start on the encode then ticked work hours and it shutdown straightaway then didn’t wake up.

[guest]

Trying out the new PD-Lite version as I would like to start doing some smdegrain comparisons, but having issues with the scripts.

when ever I choose a smdegrain custom script, when it goes to start decoding I immediately get a :

temp\ripbot264temp\job1\info.txt does not exist

and the encode immediately aborts. Not sure what is going on, I first thought the plugins variable wasn't set correctly so i changed all the call outs to the hardcoded path to the avisynth plugins folder. That changed nothing.

Any thoughts?? choosing mdegrain like normal works fine, just the custom smdegrain scripts

I checked and something in the smdegrain script is keeping the info.txt from being generated. It is there if I don;t choose a smdegrain script, but as soon as I do it dissapears in the job folder.

it is definately something with the last line:
video=SMDegrain(video,tr=2,thSAD=200,thSADC=100,contrasharp=true,prefilter=0,refinemotion=true,blksize=8)


if I remove this from the script leaving all the loadPlugin and Import lines the encode does at least runs although it doesn't really do anything.

Have sent a couple of PM's...

Will be posting a revised, updated build, shortly.

[guest]

Have made a few changes (hopefully for the better).

Please read the changelog, as there are some prerequisites that need to be installed !!!

https://www.mediafire.com/file/vszi5sgort8vx53/RipBot264_PD_Lite_%252801-12-22%2529.7z/file

[guest]

Trying out the new PD-Lite version as I would like to start doing some smdegrain comparisons, but having issues with the scripts.

when ever I choose a smdegrain custom script, when it goes to start decoding I immediately get a :

temp\ripbot264temp\job1\info.txt does not exist

and the encode immediately aborts. Not sure what is going on, I first thought the plugins variable wasn't set correctly so i changed all the call outs to the hardcoded path to the avisynth plugins folder. That changed nothing.

Any thoughts?? choosing mdegrain like normal works fine, just the custom smdegrain scripts

I checked and something in the smdegrain script is keeping the info.txt from being generated. It is there if I don;t choose a smdegrain script, but as soon as I do it dissapears in the job folder.

it is definately something with the last line:
video=SMDegrain(video,tr=2,thSAD=200,thSADC=100,contrasharp=true,prefilter=0,refinemotion=true,blksize=8)


if I remove this from the script leaving all the loadPlugin and Import lines the encode does at least runs although it doesn't really do anything.

Can you post your full script ??

[rlev11]

#MT



#VideoSource
LoadPlugin("C:\Users\rleva\Desktop\RipBot-Lite\Tools\AviSynth plugins\lsmash\LSMASHSource.dll")
video=LWLibavVideoSource("D:\MKV\From Here to Eternity (1953) 4k\From Here to Eternity (1953) (1).mkv",cachefile="D:\Temp\RipBot264temp\job1\From Here to Eternity (1953) (1).mkv.lwi")

#Deinterlace

#Decimate

#Crop

#Downscale

#Tonemap

#Levels

#Colours

#Denoise

#Custom
LoadPlugin("C:\Users\rleva\Desktop\RipBot-Lite\Tools\AviSynth plugins\masktools\masktools2.dll")
LoadPlugin("C:\Users\rleva\Desktop\RipBot-Lite\Tools\AviSynth plugins\mvtools\mvtools2.dll")
LoadPlugin("C:\Users\rleva\Desktop\RipBot-Lite\Tools\AviSynth plugins\RgTools\RgTools.dll")
LoadPlugin("C:\Users\rleva\Desktop\RipBot-Lite\Tools\AviSynth plugins\PD_TOOLS\MedianBlur2\MedianBlur2.dll")
Import("C:\Users\rleva\Desktop\RipBot-Lite\Tools\AviSynth plugins\PD_TOOLS\EXTOOLS\ExTools.avs")
Import("C:\Users\rleva\Desktop\RipBot-Lite\Tools\AviSynth plugins\PD_TOOLS\LSF-PLUS\LSFplus.avs")
Import("C:\Users\rleva\Desktop\RipBot-Lite\Tools\AviSynth plugins\PD_TOOLS\SHARPENERS-PACK\Sharpeners Pack.avs")
Import("C:\Users\rleva\Desktop\RipBot-Lite\Tools\AviSynth plugins\PD_TOOLS\SMDEGRAIN\SMDegrain cpu.avs")
Import("C:\Users\rleva\Desktop\RipBot-Lite\Tools\AviSynth plugins\PD_TOOLS\Zs_RF_Shared\Zs_RF_Shared.avs")
video=SMDegrain(video,tr=2,thSAD=200,thSADC=100,contrasharp=true,prefilter=0,refinemotion=true)



#Prefetch

#After_Prefetch_Denoise

#After_Prefetch_Custom

#Sharpen

#Upscale

#Borders

#Subtitles

#AudioSource
Import("D:\Temp\RipBot264temp\job1\job1_a1.avs")

#Triming

#AVSameLength

#ColorSpace

#Return

[guest]

Originally Posted by rlev11
Thanks

Umm, can you please try something...

I have my RipBot folder directly on my C:\ drive, could you unpack the latest build, then copy it to the root of C:\.

I'm not sure if a longer path is what the problem is....I'm grasping at straws now, as I am NOT having any problems !!!

[rlev11]

No change, paths in the script changed to the corrected ones automatically with the variable and are correct. Even tried re-running the 4 installs again from the new c:\Ripbot264 folder and no difference.

[guest]

No change, paths in the script changed to the corrected ones automatically with the variable and are correct. Even tried re-running the 4 installs again from the new c:\Ripbot264 folder and no difference.

Yeah, like I said, I'm clutching at straws..

I even copied my RipBot folder to the desktop, and it still worked.

So unfortunately, I have no more suggestions...I know that it works perfectly for me, both the "full" & "lite" builds, and because of that I can't reproduce your problem.

Have you got any unique permissions or anything setup ??

I'm pretty sure you're going to keep at it, and I'm sorry I can't help.

One last idea, this is the script in the build:-

#Custom
LoadPlugin("%AVISYNTHPLUGINS%\masktools\masktools2.dll")
LoadPlugin("%AVISYNTHPLUGINS%\mvtools\mvtools2.dll")
LoadPlugin("%AVISYNTHPLUGINS%\RgTools\RgTools.dll")
LoadPlugin("%AVISYNTHPLUGINS%\PD_TOOLS\MedianBlur2\MedianBlur2.dll")
Import("%AVISYNTHPLUGINS%\PD_TOOLS\EXTOOLS\ExTools.avs")
Import("%AVISYNTHPLUGINS%\PD_TOOLS\LSF-PLUS\LSFplus.avs")
Import("%AVISYNTHPLUGINS%\PD_TOOLS\RESIZERS-PACK\Resizers Pack.avs")
Import("%AVISYNTHPLUGINS%\PD_TOOLS\SHARPENERS-PACK\Sharpeners Pack.avs")
Import("%AVISYNTHPLUGINS%\PD_TOOLS\SMDEGRAIN\SMDegrain cpu.avs")
Import("%AVISYNTHPLUGINS%\PD_TOOLS\Zs_RF_Shared\Zs_RF_Shared.avs")
video=SMDegrain(video,tr=2,thSAD=200,thSADC=100,thSCD1=400,thSCD2=130,contrasharp=true,prefilter=0,str=1.2,refinemotion=true)

What if you edited the script's "%AVISYNTHPLUGINS% with your whole path...

LoadPlugin("%AVISYNTHPLUGINS%\masktools\masktools2.dll") changed to LoadPlugin("C:\Users\rleva\Desktop\RipBot-Lite\Tools\AviSynth plugins\masktools\masktools2.dll")

[rlev11]

will try again tomorrow, but that is one of the first things I tried earlier today

[guest]

will try again tomorrow, but that is one of the first things I tried earlier today

I'm really sorry about this, but there is clearly something unique going on with your systems.

But it might be something really simple.

I have sent a PM to another user that uses my build's, without issue...so I'm hoping that he might have a "lightbulb moment".

But it would be really great if someone else is having similar issues, would leave a comment.

[Ryushin]

OK, with all the conversation of late, I decided to build a "Lite" version of my somewhat popular build's
https://www.mediafire.com/file/orr7krjsn5buqtu/RipBot264_PD_Lite+(28-11-22).7z/file

Good luck, and enjoy :D

I tried to download the lite version but the link does not seem to be working. I was going to see if there was something wrong so I could help rlev11.

rlev11: Have you tried just setting a custom script using the default mdegrain options, just to make sure custom scripts are working:
#Custom
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)
fv1=MAnalyse(super,blksize=8,isb=false,delta=1,overlap=4)
fv2=MAnalyse(super,blksize=8,isb=false,delta=2,overlap=4)
video=MDegrain2(video,super,bv1,fv1,bv2,fv2,thSAD=200)

If that works, then try:
#Custom
LoadPlugin("%AVISYNTHPLUGINS%\masktools\masktools2.dll")
LoadPlugin("%AVISYNTHPLUGINS%\mvtools\mvtools2.dll")
LoadPlugin("%AVISYNTHPLUGINS%\RgTools\RgTools.dll")
LoadPlugin("%AVISYNTHPLUGINS%\PD_TOOLS\MedianBlur2\MedianBlur2.dll")
Import("%AVISYNTHPLUGINS%\PD_TOOLS\EXTOOLS\ExTools.avs")
Import("%AVISYNTHPLUGINS%\PD_TOOLS\LSF-PLUS\LSFplus.avs")
Import("%AVISYNTHPLUGINS%\PD_TOOLS\RESIZERS-PACK\Resizers Pack.avs")
Import("%AVISYNTHPLUGINS%\PD_TOOLS\SHARPENERS-PACK\Sharpeners Pack.avs")
Import("%AVISYNTHPLUGINS%\PD_TOOLS\SMDEGRAIN\SMDegrain cpu.avs")
Import("%AVISYNTHPLUGINS%\PD_TOOLS\Zs_RF_Shared\Zs_RF_Shared.avs")
Video=SMDegrain(video,tr=4,thSAD=400,thSADC=200,contrasharp=true,prefilter=1,refinemotion=true)

I'm using the full tools folder currently as I could not download the light and test that. Also try changing my last line and remove all options so SMDegrain uses the default:
Video=SMDegrain(video)

If there are any errors in the script or plugins being called, missing or in the wrong order, then you get the error you were seeing. It would be nice if there was some kind of debug output in RB so you could see what is happening.

Atak, that would be a nice feature to add. avisynth debugging/logging.

[Ryushin]

Trying out the new PD-Lite version as I would like to start doing some smdegrain comparisons, but having issues with the scripts.

when ever I choose a smdegrain custom script, when it goes to start decoding I immediately get a :

temp\ripbot264temp\job1\info.txt does not exist


I'm digging into this now. I can confirm it also does not work.

Though I went a different route. First I downloaded Atak's 1.26.0 build and moved the Tools folder into my RB folder. This way I have a stock RB Tools folder. I turned on auto update and let it run two rounds of updates until the Tools folder was updated as Atak intended.

When Pauly Dunne made his light version it still had the entire tools folder in it. So I stripped it down to just the files that should be needed, PD_Tools and the Custom scripts.

So I made a feather weight version that weighs in at 272KB and you can just copy that into the RB folder and it won't overwrite a single file:

Though it does not work. I'm going to do the same thing with PDs full build, though I suspect there is a newer component that has overwritten a RB file.

[Ryushin]

The problem with the PD Lite version was that it was missing the Resizers Pack.
I've added the RESIZERS-PACK folder to PD_Tools and modified the scripts to add this line:
Import("%AVISYNTHPLUGINS%\PD_TOOLS\RESIZERS-PACK\Resizers Pack.avs")

I stripped down the Lite version so you can just paste the Tools folder into the RB folder it it will merge into the Tools folder without overwriting any RB files. So you can leave RB's auto update turned on.
https://cloud.chrisdos.com/s/5B8sYfgSL8oTwQR (Zip file is only 287KB in size)

I also did the same for the full tools that Pauly released on November 8th and stripped it down so it only contains PD_Tools files and scripts. I applied the two PD updates released in November to the that folder as well:
https://cloud.chrisdos.com/s/MQBEqcEENLZffAr (7z file is only 32.6MB in size)

Pauly, I personally prefer your versions like this. So they don't overwrite any of Atak's files. Though it would be nice if Atak updates x265 and perhaps a few other tools more often. But he has to support his build, so I understand if he is hesitant to upgrade the packages every release. Through quarterly or twice yearly would be nice.

I'm switching to the Full build that is stripped. I do like the possibilities of using your other tools and scripts such as the debanding and such.

[rlev11]

So I was using a 4k source file for my testing. I guess I should have tried another file. I tried some 1080 and 720p stuff an I did get it working now using the smdegrain scripts. I have tried a couple different 4k mkv's and they still fail. Have only tried a couple of files so far so not 100% sure I have this completely figured out yet, but i am making some headway.

I did have to copy the PD-Lite version to my servers and start the encoding server from that PDLite folder for the encoding servers to work. I guess that makes sense that the encoding servers would need some of the dependencies

[rlev11]

Ryushin,

so what you are saying is that if I already have a fully updated 1.26.3 Atak release, all I should have to do is download the lite zip file, copy it into the correct folder and I should be good to go??

any benefit to merging the larger zip from the nov 8 and just copying the scripts from the latest lite version?

Update: So this is what I did, just merge the full tools folder from the zip download and then added the scripts from the lite download.

It's working now (allbeit slower than expected), even for 4k stuff. Only thing I have to figure out is 1 of the 2 current encoding servers is not working. I did just merge the tools folder on the encoding server but I have to figure this out before I add in the other 7 encoding servers

[Ryushin]

Ryushin,

so what you are saying is that if I already have a fully updated 1.26.3 Atak release, all I should have to do is download the lite zip file, copy it into the correct folder and I should be good to go??

any benefit to merging the larger zip from the nov 8 and just copying the scripts from the latest lite version?

Yes, download either version, extract the Tools folder, then just drag and drop the Tools folder into the RB folder (which also has a Tools folder) and it will merge and not overwrite any of the original Atak provided RB files.

The larger 7z file is if you want access to all of Pauly Dunne's many different scripts and plugins. If you just want SMDegrain, then the lite version is all you need.

I'm running the larger stripped version now with RB's auto updates turned on.

[rlev11]

Found for the encoding servers, just merging the tools folder does NOT allow the encoding server to work, (these are copies of the latest Atak version as well) I had to copy the "important to install" folder from the PD-Lite version download and I did the Vcdist,avisynth, and Libfftw3f-3 installs from that folder. This allowed the encoding servers to actually work and not throw an error that it could not open the chunk. Avisynth was installed from the windows installer that pops the first time you open the excodingserver.exe

The "important to install" folder from the PD-Lite version download was done on my client yesterday during troubleshooting so I am not sure if that would also need to be done to an Atak version as well in addition to just merging the Tools folder, my best guess would be YES it would.

[guest]

The problem with the PD Lite version was that it was missing the Resizers Pack.
I've added the RESIZERS-PACK folder to PD_Tools and modified the scripts to add this line:
Import("%AVISYNTHPLUGINS%\PD_TOOLS\RESIZERS-PACK\Resizers Pack.avs")

Hi, yeah, the reasoning behind leaving out that, was the file I was testing with, didn't "call" for it, unfortunately, it wasn't a 4K test file :(

[guest]

Yes, download either version, extract the Tools folder, then just drag and drop the Tools folder into the RB folder (which also has a Tools folder) and it will merge and not overwrite any of the original Atak provided RB files.

The larger 7z file is if you want access to all of Pauly Dunne's many different scripts and plugins. If you just want SMDegrain, then the lite version is all you need.

I'm running the larger stripped version now with RB's auto updates turned on.

Well, you 2 guys have been busy, while I've been asleep (time difference), and now there's a whole new build, so now I will have to re-evaluate this project, as any future builds, I can't call my own, anymore :(

I will "study" what you've done with the stripped down builds, and go from there.

But at this stage, it seems like both the "Lite" & full builds are "fixed".

EDIT:- I've just noticed a glaring oversight with this..this very important folder "SMDEGRAIN Scripts (& others)" is missing from the stripped down "full" build.

This folder contains ALL the scripts that can be copied to the Custom folder, so they can be used in RB.

The "Lite" build does not require that folder, as the dependencies aren't included, hence "Lite"

[guest]

Found for the encoding servers, just merging the tools folder does NOT allow the encoding server to work, (these are copies of the latest Atak version as well) I had to copy the "important to install" folder from the PD-Lite version download and I did the Vcdist,avisynth, and Libfftw3f-3 installs from that folder. This allowed the encoding servers to actually work and not throw an error that it could not open the chunk. Avisynth was installed from the windows installer that pops the first time you open the excodingserver.exe

The "important to install" folder from the PD-Lite version download was done on my client yesterday during troubleshooting so I am not sure if that would also need to be done to an Atak version as well in addition to just merging the Tools folder, my best guess would be YES it would.

You 2 guys have been busy, and it sounds like between the 2 of you, you have sorted it out, and had some success :)

I was pretty confident that Ryushin would get to the bottom of this.

Sorry I couldn't chime in, as I was asleep (time difference).

Well done to you both :)

[guest]

Hey guys,

Due to recent findings & problems with my builds, for some users (at least the users that inform me of problems, thanks mainly to rlev11), I will be pulling ALL my current builds, until further notice.

Thanks for your support :o

But don't forget this one, v1.26.3 (virgin) build :-

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

[cypher007]

got a question. when i do a 2 pass hvec 265 encode ive noticed the bit rate on the second pass steadily increases and the frame rate drops steadily also. surely the bit rate would vary depending on the action or not in the movie?

[guest]

got a question. when i do a 2 pass hvec 265 encode ive noticed the bit rate on the second pass steadily increases and the frame rate drops steadily also. surely the bit rate would vary depending on the action or not in the movie?

Not sure why you're doing a 2 pass..

Are you referring to the encoding "speed" shown at the bottom of the encoder window.

It will vary depending on what it has to encode at that time...

[cypher007]

the fps and kbps at the bottom. doing a 2 pass as want it to fir a bdr size in case later on i start freeing up space.

18266

[guest]

the fps and kbps at the bottom. doing a 2 pass as want it to fir a bdr size in case later on i start freeing up space.

18266

It's best if you do not attach files like this, they take a long time to be approved, you're better off using a site like Imgur or something, and posting the link.

[rlev11]

Ryushin and Pauly,

Looks like to get the encoding servers on an bare updated install to work with the SMdegrain scripts, all that needs to be done is the libfftw3f-3 dll install from the "Important to Install" folder. I didn't have to do anything else install wise or merge in the Tools folder. AVIsynth was already installed from the windows installer the first time the encoding server started up.

Currently testing a full frame 4k grainy source to do a speed comparison. Doing just an Mdegrain3-300 I was getting about 28fps will my whole farm active. Doing it with the SMDegrain medium script it is running around 42fps. That's like a 50% increase in speed, WOW!.

I still have to affinity mask the 16 core Ryzens down to 12 with SMdegrain, but even with all 16 cores active, the performance does not drop off the cliff like it does with just MDegrain. CPU usage on the 16 core Ryzens also is much less with SMDegrain, so I think with them firing up a second server instance will be really beneficial. Will probably play with the affinity mask and activate the 4 unused cores from server1 and use them on server 2 to balance things out a bit.

[Ryushin]

Hey guys,

Due to recent findings & problems with my builds, for some users (at least the users that inform me of problems, thanks mainly to rlev11), I will be pulling ALL my current builds, until further notice.

Thanks for your support :o

But don't forget this one, v1.26.3 (virgin) build :-

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

Please don't take down your builds. Without your builds we would not have SMDegrain and other tools. These are still your builds. I did not create them, you did. I just stripped down the files to the core of what you created. My links are purposely only valid until the end of January. If I've offended you by posting them I'll take then down now if you like. These are based on your work of course.

Might I suggest three builds.

SMDegrain Only: Stripped down so it does not overwrite any RB files and is a tiny download.
PD Tools and Scripts: Stripped down so it does not overwrite any RB files.
Full PD Tools and Updated Tools: Your full build that replaces the RB Tools folder.

It would also be interesting for you to see what build users pick. I think the SMDegrain only will be fairly static and not have to be updated often. The other two builds will require more of your meticulous attention.

I would use your "PD Tools and Scripts" version as I focus more on "It just works" kind of thing. Not overwriting any RB files will minimize problems. But I also don't get the improvements either. It would be nice if Atak keeps x265 and other important tools updated more often.

Please don't be discouraged. You've added a lot to RB and it is greatly appreciated.

[Ryushin]

Ryushin and Pauly,

Looks like to get the encoding servers on an bare updated install to work with the SMdegrain scripts, all that needs to be done is the libfftw3f-3 dll install from the "Important to Install" folder. I didn't have to do anything else install wise or merge in the Tools folder. AVIsynth was already installed from the windows installer the first time the encoding server started up.

Currently testing a full frame 4k grainy source to do a speed comparison. Doing just an Mdegrain3-300 I was getting about 28fps will my whole farm active. Doing it with the SMDegrain medium script it is running around 42fps. That's like a 50% increase in speed, WOW!.

I still have to affinity mask the 16 core Ryzens down to 12 with SMdegrain, but even with all 16 cores active, the performance does not drop off the cliff like it does with just MDegrain. CPU usage on the 16 core Ryzens also is much less with SMDegrain, so I think with them firing up a second server instance will be really beneficial. Will probably play with the affinity mask and activate the 4 unused cores from server1 and use them on server 2 to balance things out a bit.

Very good to know. We bought new parts for our Desktop computer with the cyber monday sales. The desktop is currently running a first gen Ryzen 7 1800x and we have bought the Ryzen 9 7950x, which should come today, but the other parts won't get here until next week. I'll have to look at the affinity mask and see how I'm going to set it up.

[rlev11]

On this grainy 4k source I'm running now(most cpu intensive), a single encoding server was around 6fps, 2 combined is around 9fps. This is on my 7950x.

OMG, going from an 1800x to a 7950x, you are in for quite a ride performance wise....

[guest]

Please don't take down your builds. Without your builds we would not have SMDegrain and other tools. These are still your builds. I did not create them, you did. I just stripped down the files to the core of what you created. My links are purposely only valid until the end of January. If I've offended you by posting them I'll take then down now if you like. These are based on your work of course.

Might I suggest three builds.

SMDegrain Only: Stripped down so it does not overwrite any RB files and is a tiny download.
PD Tools and Scripts: Stripped down so it does not overwrite any RB files.
Full PD Tools and Updated Tools: Your full build that replaces the RB Tools folder.

It would also be interesting for you to see what build users pick. I think the SMDegrain only will be fairly static and not have to be updated often. The other two builds will require more of your meticulous attention.

I would use your "PD Tools and Scripts" version as I focus more on "It just works" kind of thing. Not overwriting any RB files will minimize problems. But I also don't get the improvements either. It would be nice if Atak keeps x265 and other important tools updated more often.

Please don't be discouraged. You've added a lot to RB and it is greatly appreciated.

Hey Ryushin, don't worry too much that I have temporarily taken them down, it doesn't mean yours will suddenly stop working :rolleyes:

Having said that, I did decide to do that before I downloaded and unpacked your stripped down options, upon opening, I realised I was kind of wrong for thinking that, as I really couldn't see any changes, but one major omission in the "full" build.

See, this is why feedback is SO important, out of the 100's of downloads, hardly anybody leaves feedback..... are they having problems or not, who knows, so if rlev11 hadn't commented on the setup problems he was having, I would never have known,
as I haven't had these problems, and tbh, I can't figure out why he had problems with the "full" build a couple of weeks ago.

I know why he had certain problems with the "lite" build, but that was my fault for not testing with a 4K clip.

What needs to be done is a very thorough set of install instructions for first timers (and experienced users), so that will take a little time to get right. rlev11 has even offered to help with that, if needed.

As for 3 variants, I think that is a little bit of overkill, I think that a revised "Lite" build is good for ppl that only want the basic SMDegrain experience, and then the "full" build is for the user that wants to try & use MANY, MANY filter options, with no real limits.

As for overwriting the original RipBot folders & files, this IS necessary for the "full" build to be able to use all the resources that SMDegrain requires, and up to date as possible.

So many components within RipBot are very old, and some are probably even redundant.

As I've said many times before, my builds do NOT require the original RipBot to be downloaded or "installed", they are standalone builds !!!

I don't know what more I can say.

But one thing I will say, is, I am working on more "special" filters, I added 3 yesterday, and probably a couple more today, so I haven't given up, I just need to rehash the current process.

[guest]

Very good to know. We bought new parts for our Desktop computer with the cyber monday sales. The desktop is currently running a first gen Ryzen 7 1800x and we have bought the Ryzen 9 7950x, which should come today, but the other parts won't get here until next week. I'll have to look at the affinity mask and see how I'm going to set it up.

Wow, I'm impressed to know that you've lashed out and got a 7950X :cool:

We'll have to compare notes..

There's is a folder in my builds that has the Affinity options all written up, so it won't be hard to implement (thanks again to rlev11 for that)

[guest]

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
Fixed: PC didn't automatically wake up at scheduled time if system date format was different than YYYY-MM-DD

Thanks Atak

FYI:- This is only significant IF the user uses the "Work Hours" function.

Fixed :)

[cypher007]

ok ive tried today with my laptop to use work hours and it still doesnt work. its obviously an issue with windows 10 and this feature.

it will always shutdown at the correct time but then never wakes.

i would like to get this working as i have a 4kwp solar array and electric is now £0.40 per kwh in the UK or $0.48 in US equivalent. so not small beans.

[Atak_Snajpera]

I do not have access to physical Windows 10 machine. Only Win7 and virtual win11. It works 100% on my win7 even with non-standard date format like MM-DD-YYYY. Maybe other users could test if this is a problem indeed related with win10/11.

[rlev11]

ok ive tried today with my laptop to use work hours and it still doesnt work. its obviously an issue with windows 10 and this feature.

it will always shutdown at the correct time but then never wakes.

i would like to get this working as i have a 4kwp solar array and electric is now £0.40 per kwh in the UK or $0.48 in US equivalent. so not small beans.

Couple things to maybe try. First in the advanced settings of the power plan, make sure that allow wake timers is enabled.

If that doesn't work, Google how to wake your computer using windows task scheduler. You could then make the task scheduler wake the computer a couple minutes before you have set whatever you have in ripbot and see if that makes things work.

[guest]

I do not have access to physical Windows 10 machine. Only Win7 and virtual win11. It works 100% on my win7 even with non-standard date format like MM-DD-YYYY. Maybe other users could test if this is a problem indeed related with win10/11.

Atak, PLEASE explain how this works, so "we" all know...

So what I would like to know is, when using this feature, what happens to the progress of the encode, when it turns itself off ??

If you were using DE, then whatever chunk(s) is being processed, would be lost, when the pc shuts down, and hopefully, when it starts again, it would start on the next chunk (the one that was not completed, when it shutdown), but if you weren't using DE, then the whole encode would be lost.

[guest]

ok ive tried today with my laptop to use work hours and it still doesnt work. its obviously an issue with windows 10 and this feature.

it will always shutdown at the correct time but then never wakes.

i would like to get this working as i have a 4kwp solar array and electric is now £0.40 per kwh in the UK or $0.48 in US equivalent. so not small beans.

Come on cypher, I think it's time you gave up on this...

I have a 5.2kW solar array, and my power is approx $0.38 per kwh, but my "rule", if the solar isn't generating enough power so I can encode for "free", I don't do any, and with the weather in my area being really crappy for months & months, I don't get much done :(, and time's running out.

I would think that if there were other users that use this function, you would have had some replies, but in my way of thinking, as you haven't, no body uses it !!!!

If Atak would explain what it does to encodes in progress, then it's probably not a really economical process, as you would be losing encodes, everytime it shuts down !!!

As rlev11 suggested, maybe you should set up a Windows Task to shut down & wake up the laptop, but then that wouldn't restart the interrupted encode, would it :(

[slalom]

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.
What about the speed?
What's the difference in speed between SMDegrain & MDegrain at those 3 settings you suggest?

[guest]

What about the speed?
What's the difference in speed between SMDegrain & MDegrain at those 3 settings you suggest?

Hi slalom,

https://forum.doom9.org/showthread.php?p=1979320#post1979320

[cypher007]

Come on cypher, I think it's time you gave up on this...

I have a 5.2kW solar array, and my power is approx $0.38 per kwh, but my "rule", if the solar isn't generating enough power so I can encode for "free", I don't do any, and with the weather in my area being really crappy for months & months, I don't get much done :(, and time's running out.

I would think that if there were other users that use this function, you would have had some replies, but in my way of thinking, as you haven't, no body uses it !!!!

If Atak would explain what it does to encodes in progress, then it's probably not a really economical process, as you would be losing encodes, everytime it shuts down !!!

As rlev11 suggested, maybe you should set up a Windows Task to shut down & wake up the laptop, but then that wouldn't restart the interrupted encode, would it :(

if i wasnt on such crap money i would just let it run, but im now looking at using works pc to do the encodes. the problem i have is a typical 2hr movie takes about 24hrs on my i5 10th gen.

[Ryushin]

What about the speed?
What's the difference in speed between SMDegrain & MDegrain at those 3 settings you suggest?

Well, thing is, SMDegrain and MDegrain are so different from one another the speed should not be comparable. SMDegrain calls a lot more functions and I would think it would be vastly slower, but it's not. SMDegrain is comparable in speed to MDegrain. All depends on functions used.

Generally, and I don't know why, SMDegrain Light and Medium is faster than equivalent MDegrain. While SMDegrain Hard is about 20-30% slower than MDegrain. SMDegrain gives vastly improved visuals over MDegrain. Just as MDegrain gave huge improved visuals over HQDN3D.

Edit: blksize=8 drops the speed down by half, which is okay as it's processing four times as many blocks. I use this to prevent "blotchy" in content that the background is almost dark, or having two similar colors, such as in Untouchables, where Sean Connery is wearing a navy blue uniform at night on the bridge. Though I have to zoom up on the image to notice it.