Help with better upscale on this source

[Isac.martins]

Mpeg2source can only open d2v index files created by DGIndex (which can index m2v/mpg/vob, etc.)
No surprise it didn't work

Error code 126 is a general error usually related to a dependency issue one way or another.
Try AvsMeter on your plugins library to see if it finds any errors -

Since I can't read the error in your image due to the language, I'm only guessing

The error message in Portuguese says ''Could not find the specified module''
To run ''AvsMeter'' do I need to run it in PowerShell?

[davexnet]

Mpeg2source can only open d2v index files created by DGIndex (which can index m2v/mpg/vob, etc.)
No surprise it didn't work

Error code 126 is a general error usually related to a dependency issue one way or another.
Try AvsMeter on your plugins library to see if it finds any errors -

Since I can't read the error in your image due to the language, I'm only guessing

The error message in Portuguese says ''Could not find the specified module''
To run ''AvsMeter'' do I need to run it in PowerShell?

No, use the regular command prompt

EDIT - I was able to reproduce your 126 error by having either bad path or the dll name.
Check it carefully. Here in this example, I made the path with a deliberate error:
(the dll had the right name)

[Isac.martins]

Mpeg2source can only open d2v index files created by DGIndex (which can index m2v/mpg/vob, etc.)
No surprise it didn't work

Error code 126 is a general error usually related to a dependency issue one way or another.
Try AvsMeter on your plugins library to see if it finds any errors -

Since I can't read the error in your image due to the language, I'm only guessing

The error message in Portuguese says ''Could not find the specified module''
To run ''AvsMeter'' do I need to run it in PowerShell?

No, use the regular command prompt

EDIT - I was able to reproduce your 126 error by having either bad path or the dll name.
Check it carefully. Here in this example, I made the path with a deliberate error:
(the dll had the right name)

Ok, I added the plugin path and I believe it worked, but in the ''restorefps'' phase, it showed me this error:
:

[davexnet]

Yes, it assumes "convertFPS" was at one time previously used in the past to increase the frame rate,
so for RestoreFPS, you have to provide the original frame rate (which must be less than it is now)

EDIT I just saw this post, poisondeathray used double rate deinterlace first, to go from 25 > 50 fps,
then he used this filter
https://forum.videohelp.com/threads/411715-Help-with-better-upscale-on-this-source#post2706931

[Isac.martins]

Yes, it assumes "convertFPS" was at one time previously used in the past to increase the frame rate,
so for RestoreFPS, you have to provide the original frame rate (which must be less than it is now)

EDIT I just saw this post, poisondeathray used double rate deinterlace first, to go from 25 > 50 fps,
then he used this filter
https://forum.videohelp.com/threads/411715-Help-with-better-upscale-on-this-source#post2706931

Yes, I tried to do it using the script he made, but I didn't get the result he got 😔

[davexnet]

Yes, it assumes "convertFPS" was at one time previously used in the past to increase the frame rate,
so for RestoreFPS, you have to provide the original frame rate (which must be less than it is now)

EDIT I just saw this post, poisondeathray used double rate deinterlace first, to go from 25 > 50 fps,
then he used this filter
https://forum.videohelp.com/threads/411715-Help-with-better-upscale-on-this-source#post2706931

Yes, I tried to do it using the script he made, but I didn't get the result he got 😔

Post your complete script

[poisondeathray]

Are you using the original source such as in post #8 ?

Your MP4 ("Master - Vogue Soft....MP4") if similar to the one in post # 1 isn't the same; and has already been single rate deinterlaced. It's missing fields so you won't get proper deblending with restorefps

[Isac.martins]

Are you using the original source such as in post #8 ?

Your MP4 ("Master - Vogue Soft....MP4") if similar to the one in post # 1 isn't the same; and has already been single rate deinterlaced. It's missing fields so you won't get proper deblending with restorefps

Yes, I was trying with another deinterlaced source so it wasn't working.
However, I also tried with the same source that you worked with (25 fps interlaced), I did the decoupling process and also the "RestoreFPS" phase, but I didn't get your result with smooth frames.
Is this because I didn't get to the RemapFrames stage or is it unrelated?

[poisondeathray]

Are you using the original source such as in post #8 ?

Your MP4 ("Master - Vogue Soft....MP4") if similar to the one in post # 1 isn't the same; and has already been single rate deinterlaced. It's missing fields so you won't get proper deblending with restorefps

Yes, I was trying with another deinterlaced source so it wasn't working.
However, I also tried with the same source that you worked with (25 fps interlaced), I did the decoupling process and also the "RestoreFPS" phase, but I didn't get your result with smooth frames.
Is this because I didn't get to the RemapFrames stage or is it unrelated?

The smoothness required both RemapFrames and RIFE , but also Trim to put it into phase for that sample . It's explained in the post .

Try it on the actual sample in post #8, so you can learn what the script is doing, so you can make adjustments and apply it to full video

Even if you weren't making it smoother, the deblending is the 1st critical step for everything including denoising, upscaling . If you upscale blurry blended image, it's going to look worse than upscaling a non blurry image

[Roberto.marinho]

RestoreFPS is x86 only. You can use it in mp_pipeline (combine and run x86 and x64 functions in a either x86 or x64 host. x64 host is usually faster does not have memory amount restriction. Or you can divide up into steps with lossless intermediate. If you were using very slow filters, maybe that would be a better option

The Trim(2,0) was because of the way the sample was cut , there are 2 leading garbage b-frames (open GOP) that screw up the cadence. On a full source, you probably don't need it

The RestoreFPS phase might need to be adjusted. In this example it was "0.8" ,but for some scenes a different value might be slightly better e.g. 0.85, or 0.9 - or you can mix/match scenes/settings for best results. 0.8 was sort of the average , where all scenes looked ok

I left scenechange for RIFE off , because it really isn't very accurate. ReplaceFrames was used to fix the scenechanges with duplicates. Some of the blends before the scene change I left in, because it's smoother and looked ok - you'd have to go through the entire concert to fix it properly. If I was spending the time fixing it up properly - I would probably use DMVFN to interpolate the scene changes. Because you don't have a reference frame "after" before the scene change, or reference frame "before" the beginning of the next scene, you cannot interpolate using RIFE or optical flow. DMVFN is 1 directional interpolation using 2 previous frames

You can play with other deniosing /deblocking/upscaling filters - the main point of this post was really RestoreFPS to 29.97 - it gives you the best starting point for that source - clearer frames and reduction of blends. It's arguably the most important step no matter what filters you choose

MP_Pipeline("""

### platform: win64
LWLibavVideoSource("VTS_01_1.mkv")
trim(2,0)
bwdif(field=3)

### ###

### platform: win32
LoadPlugin("PATH\RestoreFPS.dll")
restorefps(29.97, 0.8)
### ###

### platform: win64
temporaldegrain2()
deblock_qed_mt2()
z_convertformat(pixel_type="RGBPS", colorspace_op="170m:709:709:l=>rgb:709:709:f")
rife()
z_convertformat(pixel_type="YV12", colorspace_op="rgb:709:709:f=>709:709:709:l")
LoadPlugin("PATH\avssr64.dll")
SR()
spline16resize(1280,720)
finesharp(sstr=1)
nonlinusm(str=0.25, rad=5)

remapframes(last, mappings="165 164
167 168
509 508
511 512
1045 1044
1047 1048
1149 1148
1151 1152
1281 1280
#1503 1502
1505 1506
#1889 1888
1891 1892
2005 2004
2006 2007
2363 2362
2365 2366
2511 2510
2513 2514
2609 2608
#2611 2612
2777 2776
2779 2780
", sourceClip=last)


propclearall()

### ###

""")

Hi friend, surprisingly, I'm trying to restore this same file, but I can't run your script. I have
''AviSynthPlus 3.7.3'' installed, and I have ''MP_Pipeline.dll'' in the plugin folders, but I know little about the software and I can't find a way to run the 32-bit version to execute the ''restorefps'' phase.

When I open AvsPmod and try to run MP_Pipeline, I get this error in the print below.

Could you help me with what I might be doing wrong?

[davexnet]

Could you help me with what I might be doing wrong?

Post your complete script

[poisondeathray]

When I open AvsPmod and try to run MP_Pipeline, I get this error in the print below.

Could you help me with what I might be doing wrong?

The error is saying that you have open parentheses, but no closed

You have this

MP_Pipeline("""

#script

But it should be this

MP_Pipeline("""

#script

""")

ie. you're missing the closing """)

[Roberto.marinho]

When I open AvsPmod and try to run MP_Pipeline, I get this error in the print below.

Could you help me with what I might be doing wrong?

The error is saying that you have open parentheses, but no closed

You have this

MP_Pipeline("""

#script

But it should be this

MP_Pipeline("""

#script

""")

ie. you're missing the closing """)

The error still persists...

[Roberto.marinho]

Could you help me with what I might be doing wrong?

Post your complete script

Sorry, I don't understand.
I want to run the expert's script ''poisondeathray'' from post #19, but I get errors from the start of the desired script

[davexnet]

Sorry, I don't understand.
I want to run the expert's script ''poisondeathray'' from post #19, but I get errors from the start of the desired script

Did you try poisondeathray's advice?

[Roberto.marinho]

Sorry, I don't understand.
I want to run the expert's script ''poisondeathray'' from post #19, but I get errors from the start of the desired script

Did you try poisondeathray's advice?

About closing the parenthesis? I tried but the error still persists

[poisondeathray]

The error still persists...

It's the wrong syntax. You need the splitter ### ### and the """ on both ends . You need to run the script within the mp_pipeline. Inbetween both """ and """

A basic source filter only script with mp_pipeline loading the video in x64 avs would look like

MP_Pipeline("""

### platform: win64

LWLibavVideoSource("PATH\YourVideo.ext")

### ###

""")

There are examples in the documentation as well

(It would be so much easier and faster if someone would compile x64 versions of old plugins like restorefps)

[Roberto.marinho]

The error still persists...

It's the wrong syntax. You need the splitter ### ### and the """ on both ends . You need to run the script within the mp_pipeline. Inbetween both """ and """

A basic source filter only script with mp_pipeline loading the video in x64 avs would look like

MP_Pipeline("""

### platform: win64

LWLibavVideoSource("PATH\YourVideo.ext")

### ###

""")

There are examples in the documentation as well

(It would be so much easier and faster if someone would compile x64 versions of old plugins like restorefps)

You were right.
I managed to get to this stage, I added the path to the plugin ''RestoreFPS'' and I get this error

I believe it is because I am using the 64-bit version, but how do I run the 32-bit version for this phase of ''RestoreFPS''?

[poisondeathray]

I managed to get to this stage, I added the path to the plugin ''RestoreFPS'' and I get this error

I believe it is because I am using the 64-bit version, but how do I run the 32-bit version for this phase of ''RestoreFPS''?

Do not close the mp_pipeline """) until the end of the script . Right now you're loading restorefps in x64 because mp_pipeline is closed. Move """) to the end of the script


Look at the example in the original post. Just follow that syntax

[Roberto.marinho]

I managed to get to this stage, I added the path to the plugin ''RestoreFPS'' and I get this error

I believe it is because I am using the 64-bit version, but how do I run the 32-bit version for this phase of ''RestoreFPS''?

Do not close the mp_pipeline """) until the end of the script . Right now you're loading restorefps in x64 because mp_pipeline is closed. Move """) to the end of the script


Look at the example in the original post. Just follow that syntax

Ah ok,
I removed the closing to add it at the end, but it's giving me the same syntax error as at the beginning

[poisondeathray]

It tells you what the error is - you're missing the end """) . You never added it back

Move """) to the end of the script

[Roberto.marinho]

It tells you what the error is - you're missing the end """) . You never added it back

Move """) to the end of the script

I searched on Google for a solution to this error but I didn't find it

[poisondeathray]

You loaded the plugin , but you need to call the filter to use it . Such as

restorefps(29.97, 0.8)

If it's exactly the same source, the trim value should be the same, otherwise you might have to adjust it

MP_Pipeline("""

### platform: win64
LWLibavVideoSource("PATH\YourVideo.ext")
trim(2,0)
bwdif(field=3)

### ###

### platform: win32
LoadPlugin("PATH\RestoreFPS.dll")
restorefps(29.97, 0.8)
### ###

### platform: win64

#add any x64 filters here

### ###

""")

[Roberto.marinho]

You loaded the plugin , but you need to call the filter to use it . Such as

restorefps(29.97, 0.8)

If it's exactly the same source, the trim value should be the same, otherwise you might have to adjust it

MP_Pipeline("""

### platform: win64
LWLibavVideoSource("PATH\YourVideo.ext")
trim(2,0)
bwdif(field=3)

### ###

### platform: win32
LoadPlugin("PATH\RestoreFPS.dll")
restorefps(29.97, 0.8)
### ###

### platform: win64

#add any x64 filters here

### ###

""")

Unfortunately I can't proceed from the ''restorefps'' phase

[poisondeathray]

Look at post 53

You are missing ### ### to close off the win32 section

Just copy/paste it and change the paths to your video and plugin location

[Roberto.marinho]

Look at post 53

You are missing ### ### to close off the win32 section

Just copy/paste it and change the paths to your video and plugin location

I added my preferred filters in version 64, but the error in the ''restorefps'' phase always persists

[poisondeathray]

Do you get error message if you comment out or delete the 4 filters? If not, start add them back 1 by 1 to debug which filter is the problem

[Roberto.marinho]

Do you get error message if you comment out or delete the 4 filters? If not, start add them back 1 by 1 to debug which filter is the problem

I deleted the 4 filters to test, but when it asks to process, it doesn't leave the loading screen, it's been loading for 10 minutes. Is this normal?

[poisondeathray]

Do you get error message if you comment out or delete the 4 filters? If not, start add them back 1 by 1 to debug which filter is the problem

I deleted the 4 filters to test, but when it asks to process, it doesn't leave the loading screen, it's been loading for 10 minutes. Is this normal?

Not normal

What AVS versions ?

Confirm that you have both avisynth x64 and x86 installed and that you're using the most recent mp_pipeline version .
https://github.com/pinterf/MP_Pipeline/releases

Did you do this as per the mp_pipeline README? There should be 4+4=8 files

Copy files from x86 (or x86_xp) folder to the plugins directory for 32 bits plugins
Copy files from x64 (or x64_xp) folder to the plugins directory for 64 bits plugins

[Roberto.marinho]

Do you get error message if you comment out or delete the 4 filters? If not, start add them back 1 by 1 to debug which filter is the problem

I deleted the 4 filters to test, but when it asks to process, it doesn't leave the loading screen, it's been loading for 10 minutes. Is this normal?

Not normal

What AVS versions ?

Confirm that you have both avisynth x64 and x86 installed and that you're using the most recent mp_pipeline version .
https://github.com/pinterf/MP_Pipeline/releases

Did you do this as per the mp_pipeline README? There should be 4+4=8 files

Copy files from x86 (or x86_xp) folder to the plugins directory for 32 bits plugins
Copy files from x64 (or x64_xp) folder to the plugins directory for 64 bits plugins

Good morning.
The ''AviSynth+'' version has 2 versions installed ''32 and 64 bits'', right? If so, this would be the version I have installed.

About the ''mp_pipeline'' version, it is the most recent version ''MP_Pipeline v0.23'', I downloaded it again and added it to the respective folders. Here are the pictures

I tried to change the ''RestoreFPS'' plugin, I changed it to the 3 available in the folder, which are: ''RestoreFPS.dll'', ''RestoreFPS_310705.dll'', ''RestoreFPS_old.dll'', but again I face the same error, it only executes the loading but does not finish.