Dogway's Filters Packs

[Dogway]

WARN: From here on and for the next 9 pages mostly @TDS basic AVS usage questions (deleted posts make it down to 6 pages). Skip to page 102 (https://forum.doom9.org/showthread.php?t=182881&page=102).

You need to provide your SMDegrain call.

EDIT: Just updated adding some additional checks, still if your source is progressive and is flagged as interlaced you need to explicitly declare interlaced=false

[LeXXuz]

Here's the entire script:
# Set DAR in encoder to 162 : 95. The following line is for automatic signalling
global MeGUI_darx = 162
global MeGUI_dary = 95
#
SetMemoryMax(40960)
SetCacheMode(0)
#
LoadPlugin("C:\Video Editing\MeGUI (x64)\tools\lsmash\LSMASHSource.dll")
LWLibavVideoSource("G:\WORK\Test.mkv")
#
AssumeFPS(25)
CTelecine()
CPostProcessing()
crop(28, 4, -28, -4)
#
ConvertBits(16)
SMDegrain(mode="MDegrain", tr=12, thSAD=240, contrasharp=true, LFR=true, DCTFlicker=true, refinemotion=true, truemotion=true, blksize=16, search=5, pel=4, subpixel=4, chroma=false, plane=0, gpuid=0)
SMDegrain(mode="MDegrain", tr=12, thSAD=120, thSADc=120, contrasharp=false, LFR=false, DCTFlicker=false, refinemotion=true, truemotion=true, blksize=24, search=5, pel=4, subpixel=4, chroma=true, plane=4, gpuid=0)
F3KDB_3(range=20, Y=36, Cb=24, Cr=24, grainY=24, grainC=12, dither_algo=2)
Prefetch(48,48)
Return(Last)
#

The 2nd call of SMDegrain causes the error, like the one with the fields before. If I just run the first call it works with subpixel=4.
With subpixel=3 both instances run fine.

[Dogway]

Yes, so what I said above, if your source is progressive and tagged as interlaced, either change the tag with propSet("_FieldBased",0), or use interlaced=false.

Just updated SMDegrain for a typo.

[LeXXuz]

But I don't understand why the 2nd call causes the error and the 1st one doesn't. They are literally the same, no?

[madey83]

@Dogway,

in your SMDegrain script you mentioned lot of modes, but in dokumention i can't find them and what are differents between them and use cases:
string "mode"="MDegrain" ("MDegrain"/ "MedianT"/ "MedianST"/.........

Could it be possible to give a light on them?

[Dogway]

@LeXXuz: The first call isn't correct either, you are treating a progressive clip as interlaced, therefore denoising might not behave as you expected. If it doesn't raise an error it doesn't mean it's correct.

@madey83: Yes, docs are work in progress. Check mode descriptions here (https://github.com/Dogway/Avisynth-Scripts/blob/b54d3880314a3e19f345136adec33df26f56101e/ExTools.avsi#L2298).

[LeXXuz]

@LeXXuz: The first call isn't correct either, you are treating a progressive clip as interlaced, therefore denoising might not behave as you expected. If it doesn't raise an error it doesn't mean it's correct.


Sorry but I can't follow you. I clearly must've missed something in the docs. I thought quarter-pel and Nnedi (may) increase accuracy or are these for interlaced sources especially and not suitable for progressive video:confused:
I just wanted to use NNEDICL to distribute a little more work to the GPU.

EDIT: It works now with propset but don't think I will use NNEDICL in this constellation. It eats up GPU memory like crazy. Thx kedautinh12 and Dogway.

[StainlessS]

Here's the entire script:
...
SetMemoryMax(40960)
Is that intentional ? (40GB) :eek:

[LeXXuz]

Is that intentional ? (40GB) :eek:

Yes. I edited out custom prefiltering which eats a lot of memory.

[LeXXuz]

FIY: Wolfram Rhodium pushed a new update of BM3DCUDA for Avisynth+ :)
https://github.com/WolframRhodium/VapourSynth-BM3DCUDA/discussions/20

[anton_foy]

Dogway can you explain what the denoising part in this (https://forum.doom9.org/showthread.php?p=1968320#post1968320) post is doing and how please?

[Dogway]

WARN: From here on and for the next 9 pages mostly @TDS basic AVS usage questions (deleted posts make it down to 6 pages). Skip to page 102 (https://forum.doom9.org/showthread.php?t=182881&page=102).

Dogway can you explain what the denoising part in this (https://forum.doom9.org/showthread.php?p=1968320#post1968320) post is doing and how please?

I don't remember well. He said it was a bit noisy so whatever denoiser it suited. Then I run ex_median() with the "shift back by one" trick, not sure why maybe to reduce ringing a bit further I think.

[guest]

I have been able to use this on a couple of encodes, but on other's, it just refuses to start encoding :(

I checked the dependencies,

https://github.com/Dogway/Avisynth-Scripts/blob/master/ResizersPack.avsi#L75

And I have all but "vsTCanny" & "fmtconv".

I'm just using deep_resize(3840,grain=0)

will adding these, fix it ??

[kedautinh12]

What errors?? Can't fix without errors

[kedautinh12]

Do you add propSet("_FieldBased",0) before deep_resize??

[Dogway]

This works for me:
setmemorymax(2048*4)
ffvideoSource("720p_src.mkv")

ConvertBits(16)

deep_resize(3840,grain=0)

Prefetch(8)

You don't need "_FieldBased" frameprop for my scripts.

[kedautinh12]

Thanks for the info, but I'm still have a strange problem.

I am wanting to upscale a 1920 to 3840, but in this case, if I use the 3840 it won't start, but if I change it down to 1920, it's OK, and 1280 downscaling doesn't work either.

It worked on a couple of other video's. They must be different, some how :(

Strange (to me)

Are you try me suggestion??

[kedautinh12]

If your source interlaced you need add propSet("_FieldBased",0)

[kedautinh12]

Just add propSet("_FieldBased",0) above deep_resize
propSet("_FieldBased",0)
Deep_Resize(...)

[kedautinh12]

Yes, that position

[kedautinh12]

Sorry to say, it doesn't change anything.

It's OK @ 1920, but as soon as it's 3840, it doesn't start.

In AVSMeter, it starts to check the script, the little cursor is flashing, then it stops :(

I'm going to delete my previous post.

Can you share your scripts and sample??? I think Deep_Resize relate post, don't need delete. Reel.Deel won't angry for that :D

[kedautinh12]

Of course

[Dogway]

Wel 1920 for 1920 is noop right? By the way I found that TIVTC was updated recently and didn't notice, it's now v1.0.27 with preliminar frame properties support, but still won't change "_FieldBased" prop, it seems to write other non normative props like "_FieldOrder" and so on... so for any issue related to IVTCed clips not tagging properly refer to its repo, either here (https://github.com/pinterf/TIVTC/issues/36), here (https://github.com/pinterf/TIVTC/issues/32)or here (https://github.com/pinterf/TIVTC/issues/18).

Also share a small snippet of the clip to see what's going on, but more likely must be an outdated script?

[Dogway]

Basically wait until TIVTC supports frame property writing and in the meanwhile add propSet("_FieldBased",0) after IVTCing your source. QTGMC+, ex_bob() or nnedi3wrap() are fine on that regard for deinterlacing. If that's not your issue post a clip with the script so I can test if something is going wrong.

[LeXXuz]

@LeXXuz: The first call isn't correct either, you are treating a progressive clip as interlaced, therefore denoising might not behave as you expected. If it doesn't raise an error it doesn't mean it's correct.


Dogway could you please explain this to me in more detail? I'd like to understand what I may did wrong. 🤔
I paused my work for now as I'm afraid I have to do it all over again because I misunderstood some of the parameters. 😭

[simple_simon]

I'm getting an avisynth script error

NNEDI3CL: Invalid Program

and it lists lines 738, 739, 740, 355, 234, 260 in the Resizers Pack and lines 938 & 1318 in the Transforms Pack

I'm using the latest versions of everything and default settings

propSet("_FieldBased",0)
deep_resize(960)

If I change "edge" to something other than nnedi3 then it works

[Dogway]

You didn't post the most important, your source loader.

In any case the script worked for me, the clip is progressive, and quite scarce of details so you are not going to gain that much by simply deep_resize() without extra sharpening. And SMDegrain, didn't find a reason to use.

My suggestion:

video=ffvideosource("src.mkv")
video=ConvertBits(video,16)
video=Tweak(video,hue=0,sat=0.8,bright=2,cont=1)
video=deep_resize(video,3840,grain=0.4,qual=2,deconv=-1,sharpness=30)

video

Don't forget to output to 10-bit or 8-bit, depending on encoding settings.

grain is a personal choice, it adds detail hallucination as well as a more filmic look.

My guess is something must be outdated on your end. You need AVS+ v3.7.3 test3 and NNEDI3CL v1.0.6, latest versions of FFMS2 (https://forum.doom9.org/showthread.php?p=1982035#post1982035) or DGDecNV, and latest versions of ExTools, ResizersPack, SharpenersPack and TransformsPack.

Dogway could you please explain this to me in more detail? I'd like to understand what I may did wrong. ��
I paused my work for now as I'm afraid I have to do it all over again because I misunderstood some of the parameters. ��

Simply add propSet("_FieldBased",0) after TIVTC, since as I explained above (https://forum.doom9.org/showthread.php?p=1981961#post1981961) the plugin is not tagging properly the clip.

[Reel.Deel]

It would be great if there was some automatic notifier for your "stuff".


"Watch" the project on GitHub. You'll get notified for any activity if you choose to.

https://i.ibb.co/jvVNM0y/github-watch.png

[poisondeathray]

I used ripbot many years ago. I just downloaded ripbot and it works for me on that sample and script either by loading a script (ripbot will Import()) , or pushing the avisynth button in ripbot and adding the lines (I'm assuming the latter way is you're using it)

I think writing a script is the better way to do it - and it's easier to debug errors . You should learn how - because it's slower to use ripbot as a script editor. You will thank yourself later.

If you don't seem to be getting error messages or feedback... Look in the temp folder, the job1 folder for the log files and info files to see if you've missed something . Hard for anyone to help with no clues or error messages

BTW, there is nothing unique about the avisynth aspect of ripbot - it just uses the notation video=blah instead of "implied last"

eg.
video=deep_resize(video,3840,grain=0,qual=2)

is really the same thing as

deep_resize(last, 3840,grain=0,qual=2)

where the "last" is implied , so you don't have to write it

deep_resize(3840,grain=0,qual=2)

[poisondeathray]

BUT, I have to ask, if you just downloaded RB, it would have been an older build, and it doesn't support ANY of Dogway's scripts (whatever you want to call them).

RipBot264v1.26.0 from 1st post
https://forum.doom9.org/showthread.php?t=127611




How do I do this :- "You should learn how - because it's slower to use ripbot as a script editor. You will thank yourself later"


Learn basic avisynth, use avspmod or vdub2. It takes longer for ripbot to "get info" and parse. Moreover, you can get useful error message all the time, and people can actually help you

As mentioned above, ripbot will work perfectly fine with "other" scripts . It will use Import() ("underneath the hood", you can look at the temp files to see what it's actually doing)

[poisondeathray]

I'm sorry, I strongly disagree that that script will work with RB 1.26.0.

That "vanilla" build doesn't support many of the calls in that script !!! I just tried it with RB 1.26.2 vanilla, and AVSMeter threw up an error immediately.

I also "imported" that script, and it had a decoding error with mvtools2.

Yes it definitely works.

Ripbot will use the local avisynth configuration, it doesn't need to support any calls. eg. If I have avisynth installed locally, it can and will use that. If I have autoloading plugins on the local avisynth install, it can and will use them. Ripbot runs on avisynth - it's not some completely different entity . Ask atak if you don't believe me...

So all I added when pushing avisynth button , was:


video=ConvertBits(video,16)
video=Tweak(video,hue=0,sat=0.8,bright=2,cont=1)
video=propSet(video,"_FieldBased",0)
video=deep_resize(video,3840,grain=0,qual=2)
video=SMDegrain(video,tr=2,thSAD=200,thSADC=100,thSCD1=400,thSCD2=130,contrasharp=true,prefilter=2,str=1.2,refinemotion=true)


because Ripbot autogenerated the video=LWLibavVideoSource... line

I didn't use your LoadPlugin calls or Import calls, because my paths are different. Check that yours are correct. (And you don't need SMDegrain for that source, but i left it in there for fun)



When you push the aviysnth button, add the lines, push ok, does ripbot accept it ? After pushing ok on ripbot's avisynth screen, a valid script should produce an info.txt file in the job1 temp folder. If the script is invalid, info.txt will be missing. For example if I purposely sabotage the script by adding video=blah it will not generate info.txt

If you push avisynth button (check that the added lines are still there and correct), push preview script, the default media player should pop up (mine is set to mpchc), and it should give you an error message if something is wrong . What does it say? or does it hang ?

[kedautinh12]

@TDS, sr for answer lately, i'm busy all yesterday. I checked your sample and it's work with deep_resize normally

[poisondeathray]

I don't follow your "procedure"..."push the avisynth button", then where do you go to add that....



I mean back on the Encoding Settings page.

To be clear:
When I add the .mkv, the page will say "Encoding Settings" at the top right. There is an avisynth button besides the CRF box.

Pushing the avisynth button, and pushing "show video script" will display the current script. I copy/paste into that script in the location directly underneath the autogenerated video=LWLibavVideoSource... line. There is a "preview script" button, and an "ok" button on the bottom right. Is this sufficient description?



MPC-HC doesn't not display any errors, either.


But does it play the filtered video properly ? Is it 3840 width ? What does it show, exactly ? black screen ? 1920 video ? what ??

If you change the script to just the video=LWLibavVideoSource... line (ie. delete all the added stuff) , preview script, what does MPCHC show, exactly ?



Do you have avisynth+ installed , or is everything under the ripbot directory in a sort of "portable" version ?

[poisondeathray]

I do not have Avisynth installed, it's ALL in the RipBot folder, so it's installed for RB to use.


When you "upgrade" avisynth , how are you doing that ? Just drop in / replace the .dll ?


AVSMeter stalls, MPC-HC doesn't display anything, naturally.

Does MPCHC pop up with black screen? That still displays black screen. That's something. Or does MPCHC not open at all ? Describe it exactly

Answer the other question



If you change the script to just the video=LWLibavVideoSource... line (ie. delete all the added stuff) , preview script, what does MPCHC show, exactly ?

[poisondeathray]

What question.


Seriously ? The question in quotes . Look closely at the last post. I quoted myself because you didn't answer the question the first time, I thought maybe you missed it


Delete all the added lines and replace LWLibavVideoSource line with

video=version()


You might have to push ok, the avisynth button again for the changes to get accepted. Push preview script. What does it say ?



I have to add that I am using the Pauly Dunne build that are highly modded !!!
Maybe some things got broken ? Where is it ?

[Reel.Deel]

I had other ppl tell me how to use scripts with RipBot, and it doesn't work, even tho they say it does.


It did and does work, PDR and I proved it to you in another thread (https://forum.doom9.org/showthread.php?p=1965689&highlight=ripbot#post1965689). You're set on using RipBot and don't want to learn another way. That is fine and all, but it makes it harder for anyone trying to help you. A simple problem becomes a 20+ post discussion... I don't use RipBot, and this would be my second time using it and I was able to follow all that PDR said.

Anyways, I have not used or updated Dogway's script in a while and updated just now to see if I could help out.

No error:
Blankclip(width=1920, height=1080, pixel_type="YUV420P8")
deep_resize(1920)

Error:
Blankclip(width=1920, height=1080, pixel_type="YUV420P8")
deep_resize(3480)

Avisynth open failure:
ArrayGet: Array index out of range. Problematic index count: 1
(TransformsPack - Main.avsi, line 519)
(ResizersPack.avsi, line 245)
(ResizersPack.avsi, line 260)
(E:test.avs, line 9)

BTW Dogway, you have some duplicate scripts in the EX mods and MIX mods folders.

[poisondeathray]

Yeah, seriously, this is getting way off topic AFAIC, all I wanted to know is why this Dogway deep_resized script works on some clips, and not on others, but on the clips it doesn't start, simply changing the res size to the size of the clip, it works, so what is the point.

Which clips does it work on? What are the differences ? For example, do you have other same dimension sources where you upscale the same amount and it works ?

They are important questions if you want to get it working

Version verifies the avs version loaded. Dogway's scripts requires a specific version or newer. You have a portable version, are you certain it's getting called correctly ? This will verify which version is getting called within your version of ripbot

The MPCHC question with "regular script" is to debug whether or not you have issues with the MPCHC chain - how reliable of a feedback tool is it, if you cannot preview other scripts or get "regular" error messages ? You need to start at a baseline with known debugging tools.


Now you're trying to teach me how to use RipBot in way that I feel is not necessary.

Changing the default scripts just leads to errors (for me).

What I wrote works for Atak's ripbot



I had other ppl tell me how to use scripts with RipBot, and it doesn't work, even tho they say it does.

How std RipBot can use a script with multiple Dogway scripts & dependencies, is beyond me.


It definitely works here with Atak's version. Both methods work - loading an avs script directly , or through the copy/paste procedure outlined above

One difference is I have installed avs+, installed plugins - and I can verify the script works in multiple programs (ie. previews in avspmod) . The problem on your end "feels" like one of the dependencies is wrong




All I can say is that most custom scripts I "throw" at RipBot, using the "Custom" script procedure works about 99% of the time, and with the one's I can't get to work, I won't pursue them further.


ok, just trying to help

[poisondeathray]

It did and does work, PDR and I proved it to you in another thread (https://forum.doom9.org/showthread.php?p=1965689&highlight=ripbot#post1965689). You're set on using RipBot and don't want to learn another way. That is fine and all, but it makes it harder for anyone trying to help you. A simple problem becomes a 20+ post discussion... I don't use RipBot, and this would be my second time using it and I was able to follow all that PDR said.


And I verified the copy/paste ripbot method works too (loading video directly, pushing avisynth button, push show video script, copy/paste, etc...)

But I noticed for certain types of changes, you need to push ok, to go back to the 1st screen and avisynth button again for things to get accepted properly - that might be a user beware issue

[Reel.Deel]

Error:
Blankclip(width=1920, height=1080, pixel_type="YUV420P8")
deep_resize(3480)

Avisynth open failure:
ArrayGet: Array index out of range. Problematic index count: 1
(TransformsPack - Main.avsi, line 519)
(ResizersPack.avsi, line 245)
(ResizersPack.avsi, line 260)
(E:test.avs, line 9)


False alarm. I somehow missed that I still had an old "TransformsPack.avsi" script in the auto-load folder. I deleted it and now it works as it should.

And I see you found the same error in the deep resize script :)

What do you mean the same error? You have yet to tell us any error message besides it doesn't work :p

[poisondeathray]

And again, as I said it's a random fault, as I had success with it a few days ago where it resized from 1920 to 3840 without issue, and then when I tried the same script to others, then this "stalling" problem appeared :(


If you go back and repeat one of the "success" encodes, does it work today ?

Have you ruled out changes that you've made since then - e.g. maybe swapped in some bad version of a dependency ? Some windoze update ?

Have you ruled out HW issues, like overheating/cooling etc... ? Unlikely if it doesn't really even start encoding or previewing, but you have to rule out HW issues whenever you get something "random" happening



As for MPC-HC, I am using the latest build 2.0.0, if that's the difference there, so beit.

If it previews other scripts ok, posts error messages ok - you can rule that out as being the problem.

make an error script in ripbot like I posted earlier

video=blah

It should say "I don't know what 'blah' means" . If you don't get any error messages, then you have other problems you need to solve


I'm wondering if your test works as you have dependencies setup differently to me ???


I'm thinking something along those lines - it's the only likely explanation if other stuff works

installed avs+ version , autoloaded plugins - but it really shouldn't matter if you Import() avs/avsi's and LoadPlugin() for the correct .dlls.

There might be an issue if multiple .dll's with the same name are loaded or autoloaded and you have manual LoadPlugin() concurrently - which version actually gets loaded ? The usual avisynth answer is to clean out your plugins directory . You can move them, and/or change the directory name, and manually load all plugins explicitly, so you know exactly which ones are getting loaded


But if I run any scripts that have Dogways stuff, with std RB, it's does not work !!!


I don't see why it would work for a modded ripbot version, but not the original. Avisynth is avisynth. Ripbot is just a GUI

Maybe if the loaded avisynth.dll version, or some .dll was different or .dll conflict, or if some script referenced a path structure that was different - but you should get error messages for path errors

No error message is very bizzare... and makes it very difficult for anyone to help


Would you be interested in "testing" the Pauly Dunne build ??
I don't have time right now, but post the link, I might get to it eventually

[Boulder]

Try taking a look at the Details tab in Task Manager when the problem occurs. Is there some encoding related process that appears to be doing something, yet nothing visible happens?

[poisondeathray]

I could almost guarantee that if you didn't have this autoload folder (and I think most here, do have this), that using those scripts with std RipBot, would NOT work !!!

It will work - Because nothing in those scripts require autoloading. Autoloading is a convenience, not a necessity for those scripts. A handful of people still manually load everything. Your problem likely has more to do with specific versions

You perform the "cleanout plugins" procedure I mentioned above and load and import everything manually in the script. I can test it tomorrow if you're really interested



Some of your script names differ from Dogway's. Did someone (PD?) just rename them? Are you certain they are the correct updated versions ?
e.g

.
.

Import("C:\RipBot264_PD (17-01-23)\Tools\AviSynth plugins\PD_TOOLS\RESIZERS-PACK\Resizers Pack.avs")


There are spaces , where dogway's has none eg. "Resizers Pack.avs" instead of "ResizersPack.avsi" . You can Import .avsi files too. The point is when more stuff gets changed there is more chance of errors or mixups

The date in the path "C:\RipBot264_PD (17-01-23)" , suggests Jan 17,2023, yet there are updated versions by Dogway on the 18th including ResizersPack.avsi if you check the commits

[Reel.Deel]

I could almost guarantee that if you didn't have this autoload folder (and I think most here, do have this), that using those scripts with std RipBot, would NOT work !!!

I'm not petty enough to prove you wrong again :)... But hey, instead of doing things backwards, why don't you install avs+ with the installer? There's even a "Install.cmd" in the AviSynth Ripbot folder which installs the files in the same location as the official installer.

I thought you'd found an error...and the error is, no error message, it just doesn't start !!!


I did find an error, and the error was because of an old file I had. I corrected that and now it works. Maybe you have that too, who knows... It's just odd that there's no error message of any kind, and then you can't even try a simple "Version()" command like PDR asked. Oh well, hope you get it all sorted out.

[LeXXuz]

Simply add propSet("_FieldBased",0) after TIVTC, since as I explained above (https://forum.doom9.org/showthread.php?p=1981961#post1981961) the plugin is not tagging properly the clip.

Ah. Now I get you. I must have missed that somehow and thought my SMDegrain parameters may be wrong. Thanks. :)

[Dogway]

Hey TDS, calm a bit we are all helping here. Basically your issue is NNEDI3CL related I think. Three points I want to check, first, your Avisynth version is r3849 while pinterf latest version (test3) is r3835, at least for x64, unless you are in x86.
Second, never use anything other than FFMS2 or DGDecNV. To reassure this, I simply tested with LSMASH and it errored out ([Fatal] Failed to read an input file). Not sure if outdated plugin though.
Third, I presume you have nnedi3_weights.bin in your plugins path.
Fourth, test with a simple example to check whether it runs to discard deep_resize() from the equation.
video=ConvertBits(video,16)
video=nnedi3wrap(video,2)

video

[Dogway]

I don't know where you got r3849 from, test r3835 to be on the same page. (EDIT: Tested with r3849 and no issues, so you can skip this)

nnedi3_weights.bin is placed in the same folder as NNEDI3CL.

Test as I said with only the nnedi3wrap() call after doing the above, then we talk.

[kedautinh12]

He got from here:
https://gitlab.com/uvz/AviSynthPlus-Builds

[poisondeathray]

I just tried this "version()" where I believe that PDR told me to put it, and it just errors asking for the lsmash path.


What I meant by deleting the added lines is the copy/pasted lines that got from your test example:


video=ConvertBits(video,16)
video=Tweak(video,hue=0,sat=0.8,bright=2,cont=1)
video=propSet(video,"_FieldBased",0)
video=deep_resize(video,3840,grain=0,qual=2)
video=SMDegrain(video,tr=2,thSAD=200,thSADC=100,thSCD1=400,thSCD2=130,contrasharp=true,prefilter=2,str=1.2,refinemotion=true)


The last line of video=something is what counts . So now , if you had:

LoadPlugin(".../LSmashSource.dll")
video = LWLibavVideoSource...
# delete all those added lines
video = version()



The video loaded by LWLibavVideoSource would be "replaced" by version() . Remember, you have to push "ok", and hit the avisynth button again for the changes take effect



I still think it's an issue that Dogway needs to address.

Maybe, but since it works with several other people, it's more likely a configuration/setup issue on your end.

It's a no-op when nothing is resized, that's the same as not including the deep_resize, or deleting the line. You can summarize your problem as when you try to use deep_resize (and 1920 doesn't count, because the filter gets skipped), you get the no preview /no error message/ hanging problem, but only some of the time.

[poisondeathray]

Something has changed dramatically, recently, prefilter=4 used to be for dfttest, but now dfttest is #5.

https://github.com/Dogway/Avisynth-Scripts/blob/master/SMDegrain/SMDegrain.avsi#L46

However, if I remove the prefilter= from the call, it still works, but I now don't know what filter it's using.

Is this line even still relevant ??

video=SMDegrain(video,tr=2,thSAD=200,thSADC=100,thSCD1=400,thSCD2=130,contrasharp=true,prefilter=4,str=1.2,refinemotion=true)

If you omit the prefilter call, the default is "-1", which is "off"

BTW, you can enable the settings debug display by toggling show=true (probably nicer to use a script editor, it's kind of "clunky" to do in ripbot)

[Reel.Deel]

Something has changed dramatically, recently, prefilter=4 used to be for dfttest, but now dfttest is #5.

https://github.com/Dogway/Avisynth-Scripts/blob/master/SMDegrain/SMDegrain.avsi#L46

However, if I remove the prefilter= from the call, it still works, but I now don't know what filter it's using.

Read the docs: https://htmlpreview.github.io/?https://github.com/Dogway/Avisynth-Scripts/blob/master/SMDegrain/SMDegrain.html

The "prefilter" parameter description section (https://htmlpreview.github.io/?https://github.com/Dogway/Avisynth-Scripts/blob/master/SMDegrain/SMDegrain.html#prefilter) still lists dfttest as #4 but the dependecies section is correct: DFTTest (v1.9.7 or higher) (for prefilter=5)
KNLMeansCL (v1.1.1e or higher) (for prefilter=6)
DGDecNV (v246 or higher) (for prefilter=7)
BM3D (test9 or higher) (for prefilter=8)

And according to the changelog: v3.5.8d (16-01-2023)
Add IQMV as prefilter=3 and tune ex_FluxSmoothST (prefilter=4)

---

BTW Dogway, IDK if you're still on Win7 but BM3D test10 no longer works with Win7 due to it using the Cuda 12 SDK.
Edit: I reported the issue and WolframRhodium compiled a version with the older sdk, test10-cuda118 works in Win7 :).

---

Yesterday
Do not let that "date" fool you, EVERYTHING is as up to date as Dogway's releases !!!


Today

I'll have to update most of my scripts, since the changes in SMDegrain, since 3.5.7d (currently using 3.5.9d), which may have been part of the problem.

:rolleyes: