Help with better upscale on this source

[poisondeathray]

Post the preview screenshot for this

MP_Pipeline("""

### platform: win64
BlankClip()
### ###

### platform: win32
version()
### ###

### platform: win64
### ###

""")

and this

MP_Pipeline("""

### platform: win64
version()
### ###

### platform: win32
### ###

### platform: win64
### ###

""")

[davexnet]

edit

[Roberto.marinho]

Post the preview screenshot for this

MP_Pipeline("""

### platform: win64
BlankClip()
### ###

### platform: win32
version()
### ###

### platform: win64
### ###

""")

and this

MP_Pipeline("""

### platform: win64
version()
### ###

### platform: win32
### ###

### platform: win64
### ###

""")

Like this?

[poisondeathray]

mp_pipeline is not working at all for you

Are you running as administrator or have elevated privileges ? mp_pipeline has a slave executable (.exe) that windows might not like, especially if it's run from a C:\ drive



What about a simple avs script , without mp_pipeline, to verify that avs x86 and x64 are working


you would check with avspmod x64 to initialize avs x64

version()

And a simple x86 avs script - you would check with avspmod x86 to initialize avs x86

version()

[Roberto.marinho]

mp_pipeline is not working at all for you

Are you running as administrator or have elevated privileges ? mp_pipeline has a slave executable (.exe) that windows might not like, especially if it's run from a C:\ drive



What about a simple avs script , without mp_pipeline, to verify that avs x86 and x64 are working


you would check with avspmod x64 to initialize avs x64

version()

And a simple x86 avs script - you would check with avspmod x86 to initialize avs x86

version()

Sorry, but I don't understand, my friend. Is there another filter besides ''restorefps'' that can do this job in the 64-bit version?

I really liked the smoothness you left in the file, but I can't process the video at all.

If I sent you the files, could you do just this ''restorefps'' phase for me and I could reprocess it later with my filters in the 64-bit version?

[poisondeathray]

Is there another filter besides ''restorefps'' that can do this job in the 64-bit version?

Not that I know of

If you can't get mp_pipeline working, a workaround is you can run restorefps in 32bit avisynth (e.g. vdub x86) , export a lossless intermediate . Import that lossless intermediate into 64bit avisynth for farther processing

The benefit of the mp_pipeline workflow is fewer steps, less HDD space, and faster overall

[Roberto.marinho]

Is there another filter besides ''restorefps'' that can do this job in the 64-bit version?

Not that I know of

If you can't get mp_pipeline working, a workaround is you can run restorefps in 32bit avisynth (e.g. vdub x86) , export a lossless intermediate . Import that lossless intermediate into 64bit avisynth for farther processing

The benefit of the mp_pipeline workflow is fewer steps, less HDD space, and faster overall

Ok,
But how can I run avisynth version 32?

Do I need to open ''AvsPmod_32''?

Because I tried to do the ''restorefps'' processing in AvsPmod_32 and I got this error.
I apologize for my lack of experience.

[poisondeathray]

But how can I run avisynth version 32?

Do I need to open ''AvsPmod_32''?

Use a 32bit bit application, like 32bit avspmod or 32bit vdub2 . If you use avspmod, you will eventually have to encode it with avspmod, and it's not easy setting up the encoders for x86 . You can use 32bit avspmod to preview, but I would use vdub2 32bit to encode to a lossless intermediate like lagarith or ut video

Because I tried to do the ''restorefps'' processing in AvsPmod_32 and I got this error.

It means you have KNLMeansCL.dll in the wrong directory. That is a 64bit plugin, but you placed it in the 32bit plugins directory . Move it somewhere else , and all the 64bit plugins to the correct place, or somewhere else .


In your script you will need a source filter as well, before restorefps. You have to load the video

[jagabo]

If you open an AviSynth scropt with a 64 application you will get 64 AviSynth. If you open an AviSynth script with a 32 bit application you will get 32 bit AviSynth.

The error message is telling you that you are running 32 bit AviSynth and tried to load a 64 bit AviSynth filter (knlmeanscl). 32 bit AviSynth can only use 32 bit filters, 64 bit AviSynth can only use 64 bit filters. So you need to replace that 64 bit filter with a 32 bit version.

Finally, even if you successfully loaded the filter your script wouldn't run because you never opened a video file in the script.

[Roberto.marinho]

If you open an AviSynth scropt with a 64 application you will get 64 AviSynth. If you open an AviSynth script with a 32 bit application you will get 32 bit AviSynth.

The error message is telling you that you are running 32 bit AviSynth and tried to load a 64 bit AviSynth filter (knlmeanscl). 32 bit AviSynth can only use 32 bit filters, 64 bit AviSynth can only use 64 bit filters. So you need to replace that 64 bit filter with a 32 bit version.

Finally, even if you successfully loaded the filter your script wouldn't run because you never opened a video file in the script.

Oh yes, thanks, I was lost about that error.

[Roberto.marinho]

But how can I run avisynth version 32?

Do I need to open ''AvsPmod_32''?

Use a 32bit bit application, like 32bit avspmod or 32bit vdub2 . If you use avspmod, you will eventually have to encode it with avspmod, and it's not easy setting up the encoders for x86 . You can use 32bit avspmod to preview, but I would use vdub2 32bit to encode to a lossless intermediate like lagarith or ut video

Because I tried to do the ''restorefps'' processing in AvsPmod_32 and I got this error.

It means you have KNLMeansCL.dll in the wrong directory. That is a 64bit plugin, but you placed it in the 32bit plugins directory . Move it somewhere else , and all the 64bit plugins to the correct place, or somewhere else .


In your script you will need a source filter as well, before restorefps. You have to load the video

Good afternoon, friend,
I managed to advance to this stage of rife(), but it gives me this GPU error. Could it be because the processing needs to be done only by the GPU or can I do it through the processor?

Taking advantage of the question, where can I download the DLL for the ''avssr64'' filter? I couldn't find it on any website.

[poisondeathray]

I managed to advance to this stage of rife(), but it gives me this GPU error. Could it be because the processing needs to be done only by the GPU or can I do it through the processor?

avs version of RIFE is based on the vulkan/NCNN version and is GPU only , but many GPU's are supported, even integrated GPU's

Make sure you fulfill the requirements listed in the requirements section
https://github.com/Asd-g/AviSynthPlus-RIFE

Requirements:

Vulkan device

AviSynth+ r3688 or later (1 / 2 / 3)

Microsoft VisualC++ Redistributable Package 2022 (can be downloaded from here)

You might need to update GPU drivers . If you download gpu-z, there will be a checkbox for vulkan. If it's checked, it means your GPU supports vulkan and should work .


There are other framerate interpolators you can use instead of rife - such as mvtools2, svpflow, interframe (uses mvtools2) but generally they are not as good, but much faster

Taking advantage of the question, where can I download the DLL for the ''avssr64'' filter? I couldn't find it on any website.

https://www.infognition.com/super_resolution_avisynth/

[Roberto.marinho]

I managed to advance to this stage of rife(), but it gives me this GPU error. Could it be because the processing needs to be done only by the GPU or can I do it through the processor?

avs version of RIFE is based on the vulkan/NCNN version and is GPU only , but many GPU's are supported, even integrated GPU's

Make sure you fulfill the requirements listed in the requirements section
https://github.com/Asd-g/AviSynthPlus-RIFE

Requirements:

Vulkan device

AviSynth+ r3688 or later (1 / 2 / 3)

Microsoft VisualC++ Redistributable Package 2022 (can be downloaded from here)

You might need to update GPU drivers . If you download gpu-z, there will be a checkbox for vulkan. If it's checked, it means your GPU supports vulkan and should work .


There are other framerate interpolators you can use instead of rife - such as mvtools2, svpflow, interframe (uses mvtools2) but generally they are not as good, but much faster

Taking advantage of the question, where can I download the DLL for the ''avssr64'' filter? I couldn't find it on any website.

https://www.infognition.com/super_resolution_avisynth/

I updated the GPU drivers, downloaded the RIFE models but I face this model error

[poisondeathray]

I updated the GPU drivers, downloaded the RIFE models but I face this model error

Extract the models into a "models" folder in the same folder level as rife.dll . ie. in the folder that contains rife.dll, create a folder called "models"

[Roberto.marinho]

I updated the GPU drivers, downloaded the RIFE models but I face this model error

Extract the models into a "models" folder in the same folder level as rife.dll . ie. in the folder that contains rife.dll, create a folder called "models"

I came to thank you for all the effort and patience you had with me, thanks to you I was finally able to perform the restoration. You are a 10 =)