Vapoursynth

[feisty2]

eedi3 16bits: guess I'm getting there, now the upper half of the image is good and the lower half is gone... like blank and all black..
damn, never thought programming would be painful like this..

[chainik_svp]

Myrsloik
I'm feeling very stupid to ask such a dumb question - but do you have a Windows build of mpv, compiled with VapourSynth support?
In other words - where can I find .lib/.dll files suitable for linking with gcc?

[jackoneill]

In other words - where can I find .lib/.dll files suitable for linking with gcc?

They're in the installer. Nothing keeps you from compiling your program with GCC. I didn't need the .lib file, even.

x86_64-w64-mingw32-g++ -o app.exe app.o -L/path/to/vsscriptdll -lvsscript

[chainik_svp]

C:/msys32/mingw32/lib/vapoursynth.lib: error adding symbols: File in wrong format


const VSAPI *vs = getVapourSynthAPI(VAPOURSYNTH_API_VERSION);
qDebug()<<"VS: "<<(vs!=0);
return 0;

g++ .... -L"C:\Program Files (x86)\VapourSynth\core32" -lvapoursynth

undefined reference to `_imp__getVapourSynthAPI@4'

What am I doing wrong?

[jackoneill]

C:/msys32/mingw32/lib/vapoursynth.lib: error adding symbols: File in wrong format


const VSAPI *vs = getVapourSynthAPI(VAPOURSYNTH_API_VERSION);
qDebug()<<"VS: "<<(vs!=0);
return 0;

g++ .... -L"C:\Program Files (x86)\VapourSynth\core32" -lvapoursynth

undefined reference to `_imp__getVapourSynthAPI@4'

What am I doing wrong?

Ugh. I'm revising my answer above: Nothing keeps you from compiling your program with GCC, if you're compiling a 64 bit program. If you're compiling a 32 bit program, apparently you need to create your own .lib files. (if someone knows why it's not the same for both, I would love to hear about it.)

For vsscript.dll this worked:

LIBRARY vsscript
EXPORTS
vsscript_clearEnvironment@4
vsscript_clearOutput@8
vsscript_clearVariable@8
vsscript_createScript@4
vsscript_evaluateFile@12
vsscript_evaluateScript@16
vsscript_finalize@0
vsscript_freeScript@4
vsscript_getCore@4
vsscript_getError@4
vsscript_getOutput@8
vsscript_getVSApi@0
vsscript_getVariable@12
vsscript_init@0
vsscript_setVariable@8

Save as vsscript.def and run

dlltool -d vsscript.def -l vsscript.lib

Link the resulting vsscript.lib into your application. You don't need to point ld to vsscript.dll.

For vapoursynth.dll, this .def file should work:

LIBRARY vapoursynth
EXPORTS
getVapourSynthAPI@4


This is annoying stuff. Have you considered creating only 64 bit applications?

[chainik_svp]

jackoneill

Have you actually tried to execute compiled binary?
Yeah, it links w/o errors, but gives "procedure entry point "getVapourSynthAPI@4" couldn't be located" at runtime

depends.exe shows that .exe asks for "getVapourSynthAPI@4" while the library contains "_getVapourSynthAPI@4"

You may think that adding "_" to the .def file could help? no :D it that case linking fails again

===============

The correct answer is:
dlltool --add-stdcall-underscore -d vsscript.def -l vsscript.lib

Now it works! :)

I wonder why it isn't included into "SDK"?

[jackoneill]

I tried to run it in Wine, but VapourSynth isn't installed there, so it only got as far as reporting that Python34.dll was missing. I'm glad you got it to work.

[Pat357]

jackoneill

The correct answer is:
dlltool --add-stdcall-underscore -d vsscript.def -l vsscript.lib

Now it works! :)

I wonder why it isn't included into "SDK"?

Thank you ! I was looking for this too ;-)

Do you need to link in both the vapoursynth.lib and the vsscript.lib ?
Can you show me how you do this linking ?

Thanks again, man !

[jackoneill]

Thank you ! I was looking for this too ;-)

Do you need to link in both the vapoursynth.lib and the vsscript.lib ?
Can you show me how you do this linking ?

Thanks again, man !

If you use VSScript, only vsscript.lib needs to be linked.

I think a command similar to this works:

g++ -o asdf.exe asdf.cpp -L. -lvsscript

Give -L the folder where vsscript.lib is.

[Q3CPMA]

Hello,
I tried to search in the thread, but I didn't find anything related. How are we supposed to process variable framerate videos?

[jackoneill]

Hello,
I tried to search in the thread, but I didn't find anything related. How are we supposed to process variable framerate videos?

That's a fairly vague question. Can you elaborate?

[Q3CPMA]

That's a fairly vague question. Can you elaborate?

Well, when using ffsm2 to open clips with variable framerate, it gives me a constant framerate in the end (only in the metadata, since the doc says that there's the same number of frame), so, how would I do to get the same framerate in the output file?

[sneaker_ger]

Raw video, Y4M etc. don't know about variable framerate. You have to save timecodes into external file using vspipe and load into encoder/muxer.

vspipe script.vpy - --y4m --timecodes timecodes.txt | x264 - --demuxer y4m --tcfile-in timecodes.txt -o output.mkv
(btw.: vspipe help is missing "--tcfile-in" part of x264)

I have not tested this:
1.) I don't know if ffms2 creates frame duration metadata
2.) I don't know if timecodes.txt is created immediately for use

At least in AviSynth ffms2 also has a parameter to create timecode file directly. I don't know if that parameter is available in the VapourSynth version. (And of course it would be useless in case you actually want to work with the frame duration metadata within VapourSynth)

[Q3CPMA]

Raw video, Y4M etc. don't know about variable framerate. You have to save timecodes into external file using vspipe and load into encoder/muxer.

vspipe script.vpy - --y4m --timecodes timecodes.txt | x264 - --demuxer y4m --tcfile-in timecodes.txt -o output.mkv
(btw.: vspipe help is missing "--tcfile-in" part of x264)

I have not tested this:
1.) I don't know if ffms2 creates frame duration metadata
2.) I don't know if timecodes.txt is created immediately for use

At least in AviSynth ffms2 also has a parameter to create timecode file directly. I don't know if that parameter is available in the VapourSynth version. (And of course it would be useless in case you actually want to work with the frame duration metadata within VapourSynth)

Thanks, I'll try. It would be cool to have a wrapper that transfer all metadata automatically into a matrovska container.

[jackoneill]

1) ffms2 does attach the frame duration to each frame.
2) The timecodes file is only complete after vspipe writes all the frames.

If sneaker_ger's command doesn't work, you'll have to pass the timecodes file to the muxer after x264 is done.

[Q3CPMA]

1) ffms2 does attach the frame duration to each frame.
2) The timecodes file is only complete after vspipe writes all the frames.

If sneaker_ger's command doesn't work, you'll have to pass the timecodes file to the muxer after x264 is done.

It worked perfectly, except the fact that I couldn't use a pipe.

vspipe script.vpy --y4m --timecodes tc.dat out.y4m
x264 out.y4m --demuxer y4m --tcfile-in tc.dat -o out.mkv

did the trick.

[sneaker_ger]

Yes, like jackoneill said timecode file is not ready at start of conversion (when x264 needs it), so my example does not work.

You could do like he suggested without having to save huge y4m file:
vspipe script.vpy --y4m --timecodes tc.dat - | x264 - --demuxer y4m -o es.264
mkvmerge -o out.mkv --timecodes "0:tc.dat" es.264
(but since x264 does not have timecodes it cannot do things like framerate aware CRF if you care about that)

[Q3CPMA]

Actually, this doesn't work well. I have two problems:
- The output video is offset by -0.217s
- I have random passages where I get garbled frame order and/or frame repetition. Original segment (http://104.233.78.12/share/original.mp4), garbled segment (http://104.233.78.12/share/vapoursynth.mp4). (I hope it's okay with the rules; it's only a less than 2s segment :scared:). I insist on the fact that this problem appears randomly.

I also tried with the mkvmerge method, still fucked.

[sneaker_ger]

Can you test latest RC?
http://forum.doom9.org/showpost.php?p=1724748&postcount=2088

[Q3CPMA]

Can you test latest RC?
http://forum.doom9.org/showpost.php?p=1724748&postcount=2088

I can't since I'm not on Windows. Tried with the latest git, and the second problem is still here. Well, only the second one, at least.

[Q3CPMA]

Maybe it's time to hit the ffms2 bug tracker.

[ZMachine95]

Hi guys, I have the exact same problem of Q3CPMA.

Randomly on certain film it happens the same thing... I use always Blu-Ray Source and I noticed that happens randomly.

I used Lsmash and ffm2 and both have random problem but NOT IN THE SAME VIDEOS.

The strange thing is that if I extract the passage when it start to get offset and repeat frames (with AVC it simply repeat frames, when with HEVC it completely ruin the video from the beginning getting an effect of slowmo with frames repeated quickly with a "disco effect") and encode from my pc (same source, plugins, version, script and encoding params) the output is PERFECT.

Now I will try to encode the same file from the beginning in my pc and see if the problem show up. If it doesn't I cannot find a real cause for the problem.

I use latest versions of alll plugins and Vapoursynth R27 (64bit). Latest cli build of x264 and x265.

[jackoneill]

Hi guys, I have the exact same problem of Q3CPMA.

Randomly on certain film it happens the same thing... I use always Blu-Ray Source and I noticed that happens randomly.

I used Lsmash and ffm2 and both have random problem but NOT IN THE SAME VIDEOS.

The strange thing is that if I extract the passage when it start to get offset and repeat frames (with AVC it simply repeat frames, when with HEVC it completely ruin the video from the beginning getting an effect of slowmo with frames repeated quickly with a "disco effect") and encode from my pc (same source, plugins, version, script and encoding params) the output is PERFECT.

Now I will try to encode the same file from the beginning in my pc and see if the problem show up. If it doesn't I cannot find a real cause for the problem.

I use latest versions of alll plugins and Vapoursynth R27 (64bit). Latest cli build of x264 and x265.

Do you get the same broken output if you run the same commands with the same input a second time?

Also for Q3CPMA: put core.text.FrameNum right after the source filter and see what frame numbers come out at the end.

[Q3CPMA]

Do you get the same broken output if you run the same commands with the same input a second time?

Also for Q3CPMA: put core.text.FrameNum right after the source filter and see what frame numbers come out at the end.
The frame count isn't disrupted during the fuckup. What does it mean? That the timecode file is wrong?

[jackoneill]

The frame count isn't disrupted during the fuckup. What does it mean? That the timecode file is wrong?

It means that whatever goes wrong happens in the source filter, not in VapourSynth and not in x264.

[Q3CPMA]

It means that whatever goes wrong happens in the source filter, not in VapourSynth and not in x264.

Wait, it seem that using both ffms2-git and the mkvmerge method solve it.

Now, does anyone know when the imagemagick plugin will support the HDRI version? Most distro distribute this version :( .

Nevermind, managed to reproduce it.

[jose1711]

hi, i am getting the following issue with a particular dv video (for others it works fine):

Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0xb1001b40 (LWP 11289)]
[New Thread 0xb1802b40 (LWP 11288)]
[New Thread 0xb29b3b40 (LWP 11287)]
[New Thread 0xb2003b40 (LWP 11286)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb1001b40 (LWP 11289)]
0xb7d65740 in __memcpy_ssse3 () from /usr/lib/libc.so.6
(gdb) bt
#0 0xb7d65740 in __memcpy_ssse3 () from /usr/lib/libc.so.6
#1 0xb70deeb9 in vs_bitblt(void*, int, void const*, int, int, int) () from /usr/lib/libffms2.so.4.0.0
#2 0xb70e08e6 in VSVideoSource::OutputFrame(FFMS_Frame const*, VSFrameRef*, VSAPI const*) ()
from /usr/lib/libffms2.so.4.0.0
#3 0xb70dfa14 in VSVideoSource::GetFrame(int, int, void**, void**, VSFrameContext*, VSCore*, VSAPI const*) ()
from /usr/lib/libffms2.so.4.0.0
#4 0xb7540d78 in VSNode::getFrameInternal(int, int, VSFrameContext&) () from /usr/lib/libvapoursynth.so
#5 0xb754f72a in VSThreadPool::runTasks(VSThreadPool*, std::atomic<bool>&) () from /usr/lib/libvapoursynth.so
#6 0xb75506d0 in std::thread::_Impl<std::_Bind_simple<void (*(VSThreadPool*, std::reference_wrapper<std::atomic<bool> >))(VSThreadPool*, std::atomic<bool>&)> >::_M_run() () from /usr/lib/libvapoursynth.so
#7 0xb7eadaee in std::(anonymous namespace)::execute_native_thread_routine (__p=0xb2d00544)
at /build/gcc/src/gcc-5.2.0/libstdc++-v3/src/c++11/thread.cc:84
#8 0xb793f1c3 in start_thread () from /usr/lib/libpthread.so.0
#9 0xb7d24e8e in clone () from /usr/lib/libc.so.6


test.vpy:

import vapoursynth as vs
import havsfunc as haf

core = vs.get_core()

ret = core.ffms2.Source(source=sourcefile)
ret = haf.QTGMC( ret, Preset='Placebo', TFF=True)
ret.set_output()


vapoursynth-git r27.38.gf2e10bb
ffms2-git 2.21.32.gd7dd577

thank you for any hints,

jose

[Myrsloik]

hi, i am getting the following issue with a particular dv video (for others it works fine):
...

1. Does it still crash if you don't use QTGMC?
2. I need a sample that makes it crash

[jose1711]

1. yes, it crashes even when qtgmc line is removed
2. sample will be provided via dropbox (link in pm)

[jose1711]

@Myrsloik: just curious, have you been able to retrieve the sample video?

[Windy Core]

Hi
I come across a strange problem

When I tried to load a native vapoursynth plugin like this
import vapoursynth as vs
core = vs.get_core()

core.std.LoadPlugin('C:/f3kdb.dll')
It always get error:
Failed to evaluate the script:
Python exception: Failed to load C:/f3kdb.dll
Traceback (most recent call last):
File "vapoursynth.pyx", line 1467, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:24719)
File "", line 4, in <module>
File "vapoursynth.pyx", line 1366, in vapoursynth.Function.__call__ (src\cython\vapoursynth.c:23214)
vapoursynth.Error: Failed to load C:/f3kdb.dll

I tried a lot of plugins and found that none of native vapoursynth plugin can be load.
The version of vapoursynth is R27,and the version of python is 3.4.3
Though it can't load native plugins,it still can load avisynth plugins by "core.avs.LoadPlugin" and work well with them.
I search a lot but found nothing about such problem.So I can only ask for help here.Can somebody tell me what's going on and how to solved it?

[~ VEGETA ~]

I get this:

Failed to initialize VapourSynth

I have Windows 7 x64 (on a dedi server). I tried this with the editor and the shell but still no use.

my script is just the one that prints the core version. I use the R27 official binary.

[~ VEGETA ~]

Now I put this:

import sys
import vapoursynth as vs
core = vs.get_core()
core.std.LoadPlugin(r'C:\Program Files (x86)\VapourSynth\plugins32\ffms2.dll')


it outputs:

Failed to evaluate the script:
Python exception: Failed to load C:\Program Files (x86)\VapourSynth\plugins32\ffms2.dll
Traceback (most recent call last):
File "vapoursynth.pyx", line 1467, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:24719)
File "C:/Users/VEGETA/Desktop/Untitled.vpy", line 4, in <module>
core.std.LoadPlugin(r'C:\Program Files (x86)\VapourSynth\plugins32\ffms2.dll')
File "vapoursynth.pyx", line 1366, in vapoursynth.Function.__call__ (src\cython\vapoursynth.c:23214)
vapoursynth.Error: Failed to load C:\Program Files (x86)\VapourSynth\plugins32\ffms2.dll


I know I haven't set an output, but I did and no use. It doesn't load the native plugins.

[Are_]

What about...
import sys
import vapoursynth as vs
core = vs.get_core()
core.std.LoadPlugin(r'C:\Program Files (x86)\VapourSynth\plugins32\ffms2.dll')


... or the actuall name of the dll?

[~ VEGETA ~]

Are_

I put it as you did, I just didn't copy it here properly.

I have loaded it as avs and it worked greatly... However, when loaded as vs (std) it doesn't.

[Windy Core]

It seems that ~ VEGETA ~ faced the same problem as mine

I tried the Vapoursynth R20 with Python 3.3.5

To my suprise, it work.The problem occured on R27 didn't appear on R20.
But maybe R20 is too old for some plugins
When I tried to load BM3D and flash3kyuu_deband, it always say
Failed to evaluate the script:
Python exception: 'Core only supports API R3 but the loaded plugin uses API R196610'
Traceback (most recent call last):
File "vapoursynth.pyx", line 1060, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:16489)
File "", line 4, in <module>
File "vapoursynth.pyx", line 983, in vapoursynth.Function.__call__ (src\cython\vapoursynth.c:15542)
vapoursynth.Error: 'Core only supports API R3 but the loaded plugin uses API R196610'


I also tried the version above R24,but same problem come again,all native vapoursynth plugins can't be loaded while avs plugins can be load normally.
Failed to evaluate the script:
Python exception: Failed to load C:/f3kdb.dll
Traceback (most recent call last):
File "vapoursynth.pyx", line 1467, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:24719)
File "", line 4, in <module>
File "vapoursynth.pyx", line 1366, in vapoursynth.Function.__call__ (src\cython\vapoursynth.c:23214)
vapoursynth.Error: Failed to load C:/f3kdb.dll

I also tried on my friend's computer.The same python, same vapoursynth, same script,same plugins, but there is no problem at all.Everything seems good on his PC.

This confuse me a lot.

[foxyshadis]

vapoursynth.Error: 'Core only supports API R3 but the loaded plugin uses API R196610'This means either "You have to update VapourSynth to run this plugin" or "You have to fix your plugin." It looks like the memory is corrupted, so I'd try loading only f3kdb, no BM3D and no video, nothing but the core= and LoadPlugin lines, and see if that changes the error.

Actually, what download are you using? There are several floating around, from the official release (https://github.com/SAPikachu/flash3kyuu_deband/releases) to a build from a few months ago (https://forum.doom9.org/showthread.php?p=1712577#post1712577). That might help narrow down the problem.

[jackoneill]

Windy Core and VEGETA: here is a vapoursynth.dll (win32 (http://ulozto.net/xqCDFLhn/vapoursynth-dll-f2e10bb3-loadplugin-fail-win32-7z) | win64 (http://ulozto.net/xC2yWeZv/vapoursynth-dll-f2e10bb3-loadplugin-fail-win64-7z)) that should provide more information than just "failed to load f3kdb.dll". Just replace the vapoursynth.dll found in Python's site-packages and type this in a Python prompt:

import vapoursynth as vs
c = vs.get_core()
c.std.LoadPlugin(r'C:\f3kdb.dll') # Or some other native plugin.

The last line won't be needed if get_core() already prints some error messages from the autoloaded plugins.

This means either "You have to update VapourSynth to run this plugin" or "You have to fix your plugin." It looks like the memory is corrupted, so I'd try loading only f3kdb, no BM3D and no video, nothing but the core= and LoadPlugin lines, and see if that changes the error.

Actually, what download are you using? There are several floating around, from the official release (https://github.com/SAPikachu/flash3kyuu_deband/releases) to a build from a few months ago (https://forum.doom9.org/showthread.php?p=1712577#post1712577). That might help narrow down the problem.

The weird version number is likely not memory corruption. The API version gained a "minor" part at some point in the last few releases. Older VapourSynth releases don't know the "major" part is now in the higher bytes of the version number.

[foxyshadis]

The weird version number is likely not memory corruption. The API version gained a "minor" part at some point in the last few releases. Older VapourSynth releases don't know the "major" part is now in the higher bytes of the version number.

Makes sense, the f3kdb repo still hosts the old vs.h, while the new build (without source) must use the new header. I'll update mine, then, since they still pass VERSION as 3.

[Windy Core]

What version of operating system are you using? Do the official included plugins (under core32/plugins and core64/plugins) can't be autoloaded as well?
My OS is windows 7.Yes,all offical included plugins can't be autoloaded

Windy Core and VEGETA: here is a vapoursynth.dll (win32 | win64) that should provide more information than just "failed to load f3kdb.dll". Just replace the vapoursynth.dll found in Python's site-packages and type this in a Python prompt

get_core() print error:
Python 3.4.3 (v3.4.3:9b73f1c3e601, Feb 24 2015, 22:44:40) [MSC v.1600 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import vapoursynth as vs
>>> c = vs.get_core()
Failed to load library 'C:\Program Files (x86)\VapourSynth\core64\plugins\assvapour.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\core64\plugins\avisource.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\core64\plugins\EEDI3.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\core64\plugins\genericfilters.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\core64\plugins\libhistogram.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\core64\plugins\libtemporalsoften.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\core64\plugins\RemoveGrainVS.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\core64\plugins\Vinverse.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\core64\plugins\VIVTC.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\plugins64\AddGrain.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\plugins64\BM3D.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\plugins64\flash3kyuu_deband.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\plugins64\libmvtools.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\plugins64\libnnedi3.dll'. Error code: 87. Error message:

Failed to load library 'C:\Program Files (x86)\VapourSynth\plugins64\vslsmashsource.dll'. Error code: 87. Error message:

>>>

[Myrsloik]

My OS is windows 7.Yes,all offical included plugins can't be autoloaded


get_core() print error:

Did you install all windows updates? This one may be required to make it work: https://support.microsoft.com/en-us/kb/2533623

[Windy Core]

Did you install all windows updates? This one may be required to make it work: https://support.microsoft.com/en-us/kb/2533623

It work.Thank you Myrsloik
And thanks jackoneill and HolyWu for your help.

Well I have learn a valuable lesson that I should install updates of OS in time.

[~ VEGETA ~]

Windy Core and VEGETA: here is a vapoursynth.dll (win32 (http://ulozto.net/xqCDFLhn/vapoursynth-dll-f2e10bb3-loadplugin-fail-win32-7z) | win64 (http://ulozto.net/xC2yWeZv/vapoursynth-dll-f2e10bb3-loadplugin-fail-win64-7z)) that should provide more information than just "failed to load f3kdb.dll". Just replace the vapoursynth.dll found in Python's site-packages and type this in a Python prompt:

import vapoursynth as vs
c = vs.get_core()
c.std.LoadPlugin(r'C:\f3kdb.dll') # Or some other native plugin.

The last line won't be needed if get_core() already prints some error messages from the autoloaded plugins.



this happens:

Traceback (most recent call last):
File "<pyshell#0>", line 1, in <module>
import vapoursynth as vs
ImportError: DLL load failed: The specified procedure could not be found.

it is when I do what you said.

I am using windows 7 32 bit (the one I tried this on) and have a dedicated server running windows 7 64 bit (didn't try it on it yet).

[jackoneill]

I installed everything but when running wibbly I get:

______________

The procedure entry point vsscript_creatscript@4 could not be located in the dynamic link library vsscript.dll

______________

and the same for wobbly. but @8 rather than @4.


All right. Here are some random questions, in the hope that one of them is the right one:

This is a 32 bit Windows 7, yes?

Which version of VapourSynth did you install?

Does the same thing happen with r27 and this r28-test1 (https://www.dropbox.com/s/wecntdf9xve68qc/vapoursynth-r28-test1.exe?dl=1)? What about r26?

Did you change anything at all in the installer, like the destination path?

Can you verify that vspipe.exe, vsscript.dll, vapoursynth.dll (both copies), vapoursynth.pyd, and your Python installation are all 32 bit? Perhaps the Properties window tells you this. If not, Dependency Walker tells you, in the "CPU" column. Where is each of these located? While you're there, Dependency Walker can tell you if your copy of vsscript.dll has the function that the error message is complaining about.

Does this KB2533623 (https://support.microsoft.com/en-us/kb/2533623) magically fix everything, if it's not installed already?

[~ VEGETA ~]

All right. Here are some random questions, in the hope that one of them is the right one:

This is a 32 bit Windows 7, yes?

Which version of VapourSynth did you install?

Does the same thing happen with r27 and this r28-test1 (https://www.dropbox.com/s/wecntdf9xve68qc/vapoursynth-r28-test1.exe?dl=1)? What about r26?

Did you change anything at all in the installer, like the destination path?

Can you verify that vspipe.exe, vsscript.dll, vapoursynth.dll (both copies), vapoursynth.pyd, and your Python installation are all 32 bit? Perhaps the Properties window tells you this. If not, Dependency Walker tells you, in the "CPU" column. Where is each of these located? While you're there, Dependency Walker can tell you if your copy of vsscript.dll has the function that the error message is complaining about.

Does this KB2533623 (https://support.microsoft.com/en-us/kb/2533623) magically fix everything, if it's not installed already?

Well, installing VS-r26-test1 worked well regarding previous problem of being unable to load native plugins... Now it does!

this script worked well:

import sys
import vapoursynth as vs
core = vs.get_core()
#core.std.LoadPlugin(r'D:\plugins32\ffms2.dll')
a = core.ffms2.Source(r'C:/video.mkv')
a = core.f3kdb.F3kdb(a, y=49, output_depth=10, dither_algo=2)
a.set_output()



However, the problem I reported regarding Wobbly still exactly the same.

About your questions, here are my answers:

1- I run Windows 7 32-bit. (My dedicated server Windows 7 60-bit, but didn't try r28 on it yet. Probably it will work)

2- Now it is r28. previously official r27. Didn't try anything else.

3- As I said above, loading native plugins now works well. The other problem of Wobbly didn't change. didn't try 26.

4- Did not change anything.

5- Hmm... vsscript.dll is located in system32. In properties window of vspipe.exe, it shows the options of Windows XP which indicates it is 32-bit (unless this info is wrong). Python is 32-bit.

Could not check the .dll files, but as I said above, it ran a script very well... So they must be 32-bit.

[jackoneill]

Ah, so VapourSynth is working correctly on your device now...

[~ VEGETA ~]

Ah, so VapourSynth is working correctly on your device now...

Yes. I ran the script shown above which previously didn't work at all.

[~ VEGETA ~]

I've tested the exact same VS-R28 on Windows 7 x64-bit (server), but it turns out it has the same problem.

it gives back:

Failed to evaluate the script:
Python exception: No attribute with the name ffms2 exists. Did you mistype a plugin namespace?
Traceback (most recent call last):
File "vapoursynth.pyx", line 1467, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:24719)
File "PATH\Untitled.vpy", line 4, in <module>
v = core.ffms2.Source(PATH/[SS] Dragon Ball 1-28 (Son Gokū Arc)(DVD.AAC)/[SS] DB - 01 (DVD.AAC)[68AED4FF].mkv')
File "vapoursynth.pyx", line 1088, in vapoursynth.Core.__getattr__ (src\cython\vapoursynth.c:18921)
AttributeError: No attribute with the name ffms2 exists. Did you mistype a plugin namespace?

the script:
import sys
import vapoursynth as vs
core = vs.get_core()
v = core.ffms2.Source(PATH/[SS] Dragon Ball 1-28 (Son Gokū Arc)(DVD.AAC)/[SS] DB - 01 (DVD.AAC)[68AED4FF].mkv')

v.set_output()

so the new VS-R28 solved the problem of not loading native plugins on windows 7 32-bit, but it is not solved in windows 7 64-bit.

[jackoneill]

Install https://support.microsoft.com/en-us/kb/2533623 and try again.

[~ VEGETA ~]

Install https://support.microsoft.com/en-us/kb/2533623 and try again.

That worked perfectly, thanks for your continuous efforts. So now with that Windows update and VS-R28... it should work on 32-bit and 64-bit Windows 7 (It is for me).