New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vapoursynth plugin and script folders need update #16
Comments
Okay, but what does it mean for Simple x264 Launcher ❓ I just tried with latest Python 3.7.3 and latest VapourSynth R45. And everything seems to work as expected, even though I don't how to install "plugin from the VS repository through Python". I just install plugins by placing them in the "plugins32" or "plugins64" directory, respectively. This seems to work as always. But, anyways, I think it is VapourSynth's job to pick up the plug-ins from the correct directory, right? Can you please elaborate what exactly you think should be changed on the Simple x264 Launcher side? Regards. |
There's the VSRepo plugin manager now that we can get plugins from without looking for them elsewhere. And it installed them on the paths I listed above. Vapoursynth will look for plugins from those location as well as the native plugin32/plugin64 folders. I have most of the plugins in my vsrepo plugins path but not in the native plugin64 folder and Simple x264 Launcher gives me errors about missing plugins when I loaded in the script. |
Well, still my question: What exactly needs to be changed on the Simple x264 Launcher side? 😨 Simple x264 Launcher is just a GUI front-end that launches I think you should try to load your script with For example:
Can you get that to work with the "problematic" script ??? BTW: You are using 32-Bit or 64-Bit VapourSynth? Keep in mind that Simple x264 Launcher defaults to the 32-Bit version, but the 64-Bit version can be activated (if available) via the "Preferences". Whatever VapourSynth version (32-Bit or 64-Bit) you are using, the plug-ins need to have the matching "bitness"! |
I"m using 64 bit Vapoursynth and Simple x264 Launcher was set to use 64 bit. I ran the that vspipe command on my script in the terminal and it worked. I loaded the script in vs editor and it worked too. But Simple x264 Launcher complains about missing plugin when trying to encode
|
If the invocation After all, Simple x264 Launcher does nothing but just launching BTW: If you run |
It only works when I only use filters from the vs plugin64 folder in my script. In my test script here, I have KNLMeansCL.dll in the vsrepo plugin folder and plugin64 folder don't, and then the program complains about it. If I removed the knlmeanscl call in the script, it worked. |
But why should VapourSynth behave differently and load plug-ins from some additional directory only when you run Only possible explanations I can think of:
Unless you can figure out what exactly makes the difference, I can't help. I can only speculate 😟 |
Can you reproduce the issue with the vsrepo plugin folder on your machine? If it doesn't work either then I'll report the issue to the vapoursynth thread. |
I usually just put plug-ins into the |
VSRepo came with the latest Vapoursynth installer, recently there's a VSRepoGUI that make it a lot easier to use, just download this GUI and run it and plugins can be installed in one click: For the test, just install any plugin in VSRepoGUI that is not on your native plugin64 folder, and then call that plugin in the script and see if Simple x264 Launcher can encode that. |
Never mind, I got it to work. After some testing it seems to me that VapourSynth ( Anyway, I added a workaround to set up Regards, |
Please give it a try with the latest TEST version: |
It works, no more error |
Thanks for confirming! Here is another small update: So I hope we can finally close this issue now 😌 |
New version of Vapoursynth now can get their plugin from the VS repository through Python, which default storing path for Windows is
The text was updated successfully, but these errors were encountered: