VirtualDub2

[Gromozeka]

WNR 0.1 not worked in virtualdub filtermod

[shekh]

Originally Posted by Gromozeka

WNR 0.1 not worked in virtualdub filtermod

I tried it with official VD 1.10.5 and it had problems too. Does not crash immediately but the output is not consistent (which is enough indication that the filter is broken).
Unless you find source code there is nothing to do with it.

[Gromozeka]

Originally Posted by shekh

Unless you find source code there is nothing to do with it.

Sorry. I don't have the source code WNR 0.1
It's a pity that the wavelet technologies hasn't found the future development

[Reel.Deel]

@Gromozeka

Don't know how they compare to WNR but there's a couple of wavelet denoising plugins for AviSynth: VagueDenoiser and WaveletReducer.

[Gromozeka]

Originally Posted by Reel.Deel

@Gromozeka

Don't know how they compare to WNR but there's a couple of wavelet denoising plugins for AviSynth: VagueDenoiser and WaveletReducer.

thanks, I know about it

[jpsdr]

Discorver a big critical issue. I can't open avs file, i have always an ffmpeg error message telling me "unable to open file", when the same avs file opens perfectly with standard VDub.

[LigH]

AviSynth files should be opened using the AviSynth API, maybe VfW, but not via ffmpeg plugin, I believe ... is it possible to enforce the use of ffmpeg input even when it may not be appropriate?

[shekh]

Originally Posted by jpsdr

Discorver a big critical issue. I can't open avs file, i have always an ffmpeg error message telling me "unable to open file", when the same avs file opens perfectly with standard VDub.

Did you change priority in cch_input.ini? Eg "default = 1" or anything above -5 makes such effect.
Initial config should work (just checked).

Opening avs with ffmpeg is possible in theory, but I disabled avisynth when compiled ffmpeg so it should never work.

[jpsdr]

I didn't change anything, just updated from 14 to 15. And i don't want ffmpeg to open avisynth, i still want internal VDUb Avisynth API to open it.
I'll do more checks/tests on several PCs later, when i'll have a little time. But saying "I disabled avisynth when compiled ffmpeg so it should never work", do you mean that ffmpeg is "included" within VDubFilterMod, when not in VDub. What plugin is it ? I can check if removing it solve the issue. What's strange, it's that i've opened avs scripts before with version 14.

[LigH]

Yes, VDubFilterMod includes an ffmpeg based input filter (plugins[32|64]\cch_input.vdf). AviSynth scripts (*.avs) are not included in its file mask. They open fine in my installation of v14. They also open fine in v15 (I separated 32 bit and 64 bit files, but that may not be necessary, as their file names are all distinct).

If you have only a 32 bit version of AviSynth installed, and try to open an AviSynth script in VeeDub64.exe, it may fail, but I would be surprised if it tried to open it "desperately" in the ffmpeg input plugin.

[jpsdr]

Thanks, i'll do some tests later when back home.

[shekh]

FFMPEG base input is within avlib-1.vdplugin now, was named cch_input.vdf before.
If AviSynth is not installed, should give this error: AVI Import Filter error: (Unknown) (80040154)
If you delete cch_input.ini or put wrong priority in it: FFMPEG: Unable to open file.
Check if you have cch_input.ini in plugins32 and plugins64 folders.

internal avs/vpy has priority of -4
default for ffmpeg is set to -5 in ini to allow avs before it

[jpsdr]

I have both... : cch_input.vdf and avlib-1.vdplugin. Removing avlib-1.vdplugin solved the issue.
Keeping cch_input.vdf alone no issue, both issue, only avlib-1.vdplugin issue.
I have the .ini, and priority is -5.

Edit :
Ok...! I put the .vdf in "plugin", and the ".vdplugin" in "plugin32/64".
The cch_input.ini was, and stayed in the "plugin", so probably the avlib-1.vdplugin didn't find it in plugin32/64... I would never found out that the cch_input.ini was for avlib-1.vdplugin...

[LigH]

But that's the newer plugin. You should have removed the older cch_input.vdf instead.

[jpsdr]

And if both old an new were present it's because i've overwrited the old files with the new files, not deleted everything before copying...

[jpsdr]

BTW, isn't finaly this plugin the same as this one ?

[shekh]

Originally Posted by jpsdr

BTW, isn't finaly this plugin the same as this one ?

Are you asking about features or ...?
Apparently my plugin is developed by me and the quoted one is not. They have some common history long ago.

[jpsdr]

Yes, just about features. I have the feeling that both are doing (or are for) the same thing, meaning it would probably be useseless to have both installed, so having to choose which one i install.

[LigH]

In general, you may be right. VirtualDub originally could only handle AVI files. The demand to at least import, if not even export different formats, grew in the last years. Modifications appeared. Then Avery Lee implemented plugin interfaces and support for external encoders. shekh will surely have adapted a previous simple ffmpeg all-purpose input plugin to a central feature, supporting the extended color models and filter modes of the core application as well.

[jpsdr]

That's what i've thought just afterward. The "other" plugin may probably output allways 8bits even if the input is an mkv or a mov with a 10bits video/codec, when shekh's codec may output 10bits supporting the extended color models he added.