Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
![]() |
#182 | Link |
Registered User
Join Date: Mar 2015
Posts: 775
|
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.
__________________
VirtualDub2 |
![]() |
![]() |
![]() |
#184 | Link |
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,664
|
@Gromozeka
Don't know how they compare to WNR but there's a couple of wavelet denoising plugins for AviSynth: VagueDenoiser and WaveletReducer. |
![]() |
![]() |
![]() |
#185 | Link | |
Registered User
Join Date: Jan 2007
Posts: 151
|
Quote:
|
|
![]() |
![]() |
![]() |
#187 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
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?
|
![]() |
![]() |
![]() |
#188 | Link | |
Registered User
Join Date: Mar 2015
Posts: 775
|
Quote:
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.
__________________
VirtualDub2 |
|
![]() |
![]() |
![]() |
#189 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,309
|
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. |
![]() |
![]() |
![]() |
#190 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
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. |
![]() |
![]() |
![]() |
#192 | Link |
Registered User
Join Date: Mar 2015
Posts: 775
|
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
__________________
VirtualDub2 |
![]() |
![]() |
![]() |
#193 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,309
|
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... Last edited by jpsdr; 14th February 2017 at 20:01. |
![]() |
![]() |
![]() |
#197 | Link | |
Registered User
Join Date: Mar 2015
Posts: 775
|
Quote:
Apparently my plugin is developed by me and the quoted one is not. They have some common history long ago.
__________________
VirtualDub2 |
|
![]() |
![]() |
![]() |
#198 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,309
|
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.
|
![]() |
![]() |
![]() |
#199 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
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.
|
![]() |
![]() |
![]() |
#200 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,309
|
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.
|
![]() |
![]() |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|