InterFrame 2.8.2 - Framedoubling/60FPS/HFR conversion script

[aegisofrime]

Originally Posted by SubJunk

Cool, I'll try not to keep you waiting too long

Lol I wasn't trying to put pressure on you, if that's how it came across. I will just work on my interlaced/Needs-To-Be-QTGMC'ed stuff first.

[LexSfX]

Originally Posted by SubJunk

InterFrame has always supported multi-threading, as do most AviSynth plugins.

You just use a multithreaded version of AviSynth then make the script like:

SetMemoryMax(512)
SetMTMode(3)
DSS2('file')
SetMTMode(2)
InterFrame()

This is interesting, and I got the latest multi-threaded build from SEt ( http://www.mediafire.com/file/3gd385...q7/avisynth.7z ). Before installing it, setmtmode() returned an error saying setmtmode() didn't exist, and after installing it, it ran with setmtmode(), so I know I installed it properly. However, even after doing that, the script only used 1 thread with the interframe() call, but all 4 threads without it. I'm using ffmpegsource, if that makes a difference. It runs at full speed without the interframe() call, but interframe() seems to throttle its CPU usage to 1 of my 4 cores somehow, even though I am using setmtmode(2) before the interframe call. Do you have any ideas about why this is happening?

I'm using "avs2pipemod -benchmark interframe.avs" for testing.

My script is here: https://raw.github.com/AlexFolland/i...interframe.avs

By the way, before you say it's because there's no setmtmode(3) before the source function calls, I tried that. It didn't change anything. Also, ffmpegsource seems to be multi-threaded anyway, even without that.

I would be very happy if I could use interframe at full speed! :)

[SubJunk]

No idea why it's doing that, sorry. I've never used it with ffmpegsource

[Bernardd]

Hi SubJunk,
Thank you for this new release.
Bernard

[SubJunk]

InterFrame 2.0b1 is released

[Bloax]

"Film" tuning for 2.0b1 seems broken.

Even though the source I'm testing it on is pretty tough, it still uses pure frame blending on the easy parts.
"Smooth" Works just fine though. [/feedback]

[SubJunk]

Yeah I think the scene-change detection is too strong, that could be what's happening there. I'll look at making it weaker. Thanks for the feedback!

[Bloax]

Yeah, I'd believe that's the issue. Since in my brief testing of the new plugins, pumping the SCD way too high up resulted in the same effect.

Edit: Though it seems strange that I can't seem to find neither "Scene: x" nor "Blocks: y" definitions.

[Reel.Deel]

Hello SubJunk,

Thanks for your hard work.

In one your ealier post you said that the SVP DLLs did not work on AVIsynth 2.6. Is this still a work in progress?
I get an error for both svpflow_cpu.dll and svpflow_gpu.dll. Plugin "__" is not an AVIsynth 2.5 plugin. I'm using 2.6 MT on 32bit XP.

[noee]

Originally Posted by Reel.Deel

Hello SubJunk,

Thanks for your hard work.

In one your ealier post you said that the SVP DLLs did not work on AVIsynth 2.6. Is this still a work in progress?
I get an error for both svpflow_cpu.dll and svpflow_gpu.dll. Plugin "__" is not an AVIsynth 2.5 plugin. I'm using 2.6 MT on 32bit XP.

Don't load *cpu or *gpu. Only load the plugins SVP1 and SVP2...

[Reel.Deel]

Thanks Noee.

I had tried that but didn't realize that it only works when GPU=True.

When GPU=False I get an error.

SVSmoothFps: overlap must be even with CPU frame composition.

(__\Interframe2.avsi, line 98)

(__\Interframe2.avsi, line 51)

[kolak]

Have same error.
Also NewNum adn NewDen are String, but in help/examples they are written eg. as 48000 instead of "48000"

[aegisofrime]

Subjunk, I remember in pre 2.0 versions of InterFrame your documentation states that usage of the GPU results in softer output. Your documentation for 2.0 does not state this. Does it mean that GPU and non-GPU output are of the same quality, more or less?

[SubJunk]

Originally Posted by Reel.Deel

In one your ealier post you said that the SVP DLLs did not work on AVIsynth 2.6. Is this still a work in progress?

It works with 2.6 now

Originally Posted by Reel.Deel

When GPU=False I get an error.

SVSmoothFps: overlap must be even with CPU frame composition.

(__\Interframe2.avsi, line 98)

(__\Interframe2.avsi, line 51)

You're right. I will fix it. For now using Preset="Fast" should fix it.

Originally Posted by kolak

Also NewNum adn NewDen are String, but in help/examples they are written eg. as 48000 instead of "48000"

All strings (like Tuning and Preset) in the documentation are written without quotation marks, since they have "(String)" next to them. It has always been like that in 1.x too.

Originally Posted by aegisofrime

Subjunk, I remember in pre 2.0 versions of InterFrame your documentation states that usage of the GPU results in softer output. Your documentation for 2.0 does not state this. Does it mean that GPU and non-GPU output are of the same quality, more or less?

Yes

[kolak]

Does it use fallback method?

[SubJunk]

I'm not sure what you're asking

[kolak]

Some solutions use fallback method- so when motion adapative engine produces to many artefacts it switches to simple frame blending conversion.

[SubJunk]

There are fallbacks but in those cases we use masking on the problematic areas instead of giving up on the whole frame.

[kolak]

Does this not break frame cohesiveness?

I have some smoothness issues when watching footage on TV.
It's mainly on horizontal movements, eg when someone walks across.
Another question- it also looks like there is not enough motion blur, so footage look very sharp, but not smooth. I tried different setting for sadgamma, but still can't get enough blurring. It's ok for PC monitor, but once watched on TV than motion is not that smooth.

[Didée]

What motion blur? That's not the scope of this tool. If in frame one the ball is left, and in frame two the ball is right, it will calculate a new frame with the ball in the middle.

Creating motion blur is a quite different kettle of fish.