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]

Originally Posted by chainik_svp

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]

Originally Posted by 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?

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 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]

Originally Posted by chainik_svp

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]

Originally Posted by Pat357

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]

Originally Posted by 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?

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

[Q3CPMA]

Originally Posted by jackoneill

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]

Originally Posted by 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)

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]

Originally Posted by 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.

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, garbled segment. (I hope it's okay with the rules; it's only a less than 2s segment ). 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?...postcount=2088

[Q3CPMA]

Originally Posted by sneaker_ger

Can you test latest RC?
http://forum.doom9.org/showpost.php?...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.