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. |
|
![]() |
|
Thread Tools | Search this Thread | Display Modes |
![]() |
#81 | Link | ||
Helenium(Easter)
Join Date: Aug 2017
Location: Hsinchu, Taiwan
Posts: 99
|
Quote:
What I mean by static is that ffmpeg will not require extra dlls at startup. Quote:
I just extracted VapourSynth64-Portable-R45, python-3.7.3-embed-amd64 and ffmpeg to the same directory and use that as a testing environment.
__________________
Monochrome Anomaly Last edited by Wolfberry; 28th May 2019 at 09:07. |
||
![]() |
![]() |
![]() |
#83 | Link | |
Helenium(Easter)
Join Date: Aug 2017
Location: Hsinchu, Taiwan
Posts: 99
|
Quote:
__________________
Monochrome Anomaly Last edited by Wolfberry; 29th May 2019 at 11:11. |
|
![]() |
![]() |
![]() |
#84 | Link | |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,084
|
Since I've now hammered out the kinks (hopefully), I'm able to answer this based on actually cross-compiling VapourSynth instead of using gendef on Windows dlls.
Quote:
The entire process is documented here (link goes directly to the VapourSynth section of the guide): https://github.com/qyot27/mpv/blob/e...ious.txt#L4396 One distinction is that when I'd tested with using gendef to handle VapourSynth too, I could get FFmpeg to link to it, but mpv refused to link to libavformat. gendeffing only Python and then cross-compiling VapourSynth like any other library results in both FFmpeg and mpv being able to link to it (importantly, mpv being able to directly play back scripts this way). 32-bit and 64-bit FFmpeg and mpv with static VapourSynth Said binaries include *both* VS demuxers. The upstream demuxer is still 'vapoursynth', and the other one is 'vapoursynth_alt'. It's easy to tell them apart because they return different data types as input: '-f vapoursynth' returns wrapped_avframe, '-f vapoursynth_alt' returns rawvideo. The upstream demuxer also doesn't honor relative file paths across directories (in just FFMS2? maybe in general?), while the alt demuxer does. Last edited by qyot27; 31st May 2019 at 17:47. |
|
![]() |
![]() |
![]() |
#86 | Link |
Registered User
Join Date: Dec 2005
Location: Germany
Posts: 1,040
|
Click on his signature link, you can find a newer version there.
__________________
AVSRepoGUI // VSRepoGUI - Package Manager for AviSynth // VapourSynth VapourSynth Portable FATPACK || VapourSynth Database || https://github.com/avisynth-repository |
![]() |
![]() |
![]() |
#88 | Link | |
Registered User
Join Date: Nov 2004
Location: UK
Posts: 2,412
|
Quote:
Wolfberry version does absolutely nothing- just ends without any print or error. |
|
![]() |
![]() |
![]() |
#89 | Link | |
Registered User
Join Date: Sep 2007
Posts: 3,982
|
Quote:
what does info say ? vspipe --info script.vpy - Post the script. |
|
![]() |
![]() |
![]() |
#90 | Link |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,084
|
Roll back VapourSynth (git) and Python (release) to versions that were current at the end of May. Trying to mix and match versions will fail spectacularly.
Or don't use a build from nearly 5 months ago; use a current one built against the now-current versions of those environments. |
![]() |
![]() |
![]() |
#92 | Link |
Registered User
Join Date: Aug 2015
Posts: 38
|
|
![]() |
![]() |
![]() |
#94 | Link |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,084
|
FFmpeg and mpv built with static VapourSynth/Python, 2019-10-10
VapourSynth: git-bae5d1a Python: 3.7.4 The incompatibility is most likely tied to the version of Python, but VS itself probably incurs *some* of the restriction too (it matters which version of Python the VS .dlls were built against, just as much as it matters which one is linked into FFmpeg). I still have Python 3.7.3 and the official release build of R47 installed system-wide, but built FFmpeg with Python 3.7.4 and VapourSynth's current git HEAD. It worked just fine. It seems to be okay as long as the Python and VapourSynth linked into FFmpeg are newer than the ones on the system, but the inverse situation will almost certainly fail. As before, both VapourSynth demuxers are present. The upstream demuxer is vapoursynth, the rawvideo demuxer patch provides vapoursynth_alt. |
![]() |
![]() |
![]() |
#96 | Link |
Registered User
Join Date: Nov 2004
Location: UK
Posts: 2,412
|
Seems to be working. Just getting this:
"Script exceeded memory limit" which I assume is about some cache in vs. How do I increase it ? With vapoursynth_alt speed is 3x better. Last edited by kolak; 12th October 2019 at 13:13. |
![]() |
![]() |
![]() |
#97 | Link |
Registered User
Join Date: Jun 2006
Posts: 432
|
The FFmpeg binaries work fine to play/process .VPY files directly ; the vapoursynth_alt demuxer seems faster than the build-in.
How to feed a.vpy directly to MPV ? Is there a way to specify which demuxer/format to use when playing a .vpy file using MPV ? Last edited by Pat357; 26th October 2019 at 01:37. |
![]() |
![]() |
![]() |
#98 | Link |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,084
|
--demuxer-lavf-format=vapoursynth (or vapoursynth_alt). The 64-bit mpv from the package I posted on the 10th also supports using VapourSynth as a video filter (for say, 24->60fps motion interpolation).
.vpy can associated with the above command in the config file, so you don't have to remember to use it: Code:
[extension.vpy] demuxer-lavf-format=vapoursynth |
![]() |
![]() |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|