AviSynth+ 3.5: Linux, macOS, and BSD support

[stax76]

Only source filter, same result with ffms2 and l-smash.

[Groucho2004]

Originally Posted by stax76

Only source filter, same result with ffms2 and l-smash.

Explicit or implicit load? Again - how did you install Avisynth?

[stax76]

Explicit load, I've not installed but uninstalled avisynth.

I just modify the path env var.

        If Not WasInitialized Then
            Package.Python.AddToPath()
            Package.AviSynth.AddToPath()
            Package.VapourSynth.AddToPath()
            WasInitialized = True
        End If

That was all to make it work for staxrip, av2pipemod and x264, child processes inherit the path.

[qyot27]

http://git.videolan.org/?p=ffmpeg.gi...e2c2e6136931eb

28 * Safe function used to open dynamic libs. This attempts to improve program security
29 * by removing the current directory from the dll search path. Only dll's found in the
30 * executable or system directory are allowed to be loaded.

Everything you listed as being affected uses libavformat. In such a case, say you've put AviSynth.dll in the same directory as mpv.com and mpv.exe and a simple Version() script named testver.avs,

In cmd.exe you can do:

mpv.com testver.avs

And it'll spit back the video window with the output of Version().

In bash or PowerShell, however, this will fail because those shells do not silently interpret the current directory as being on the PATH, and while you can execute mpv as a program (because Windows' filesystems and permissions systems don't map to the same execution bits that *nix does, it treats all files as executables), it won't load any other .dlls unless they're in a directory on the $PATH. But when you explicitly call the program's executable path:

./mpv.com testver.avs

It works.

[stax76]

Thanks for the clarification qyot27. I don't know what I should think about overwriting Windows default behavior, appears to be over-zealous. If somebody made a feature request to enable path search via switch, do you think there is a chance it gets accepted?

If I put the tools in the same directory I confirm that it's working.

[qyot27]

Originally Posted by stax76

Thanks for the clarification qyot27. I don't know what I should think about overwriting Windows default behavior, appears to be over-zealous. If somebody made a feature request to enable path via switch, do you think there is a chance it gets accepted?

I highly doubt it.

However, there is a workaround. Just create symlinks in the ffmpeg/mpv/mpc directories using the Windows mklink command.

[stax76]

I've never used mklink even though it appears to be a useful command. Unfortunately I'm not able to create a hardlink in a cmd admin console.

C:\Users\frank\Desktop\bin>mklink /h .\Apps\Support\mpv.net\AviSynth.dll .\Apps\Support\AviSynth.dll
The system cannot find the file specified.

Same command without /h works.

[qyot27]

You don't want hard links, so /h not working isn't an issue.

[stax76]

I successfully created soft links for AviSynth.dll and DevIL.dll in the mpv.net folder but mpv.net still does not open avs.

I think portable vapoursynth has worked in mpv.net even without soft links.

Even if I can get it work it's probably not useful for staxrip users or are soft links portable?

I can offer a portable version putting everything in the same directory, it's just not clean.

[ChaosKing]

Originally Posted by stax76

Even if I can get it work it's probably not useful for staxrip users or are soft links portable?

Soft links yes, hard links no. But you can't have relative soft links I think!? So not really portable then.

[stax76]

If I could get it work with soft links staxrip could recreate the soft links whenever it notices that it was started from a new location.

[qyot27]

I checked mpv.net portable x64 5.4.6.0 just now with AviSynth.dll in a subdirectory and a symlink to it next to mpvnet.com|exe. No issues opening a Version() script, or with one loading a local FFMS2.dll and invoking FFVideoSource.

[ChaosKing]

@qyot27 Does it affect the symlink if you copy the whole folder elsewhere?

[stax76]

And avisynth was not located in system32? Here it's not working.

I tested now with vapoursynth, renamed the installed core folder to core- so the installed version cannot work. mpv.net opens vpy using portable vapoursynth (checked in Process Explorer). Even ffmpeg opens vpy using portable vapoursynth, but not mpc be (who cares...).

[qyot27]

Originally Posted by ChaosKing

@qyot27 Does it affect the symlink if you copy the whole folder elsewhere?

Yeah, in that case Windows follows the symlink and does a full copy of the DLL.

[qyot27]

Originally Posted by stax76

And avisynth was not located in system32? Here it's not working.

I tested now with vapoursynth, renamed the installed core folder to core- so the installed version cannot work. mpv.net opens vpy using portable vapoursynth (checked in Process Explorer). Even ffmpeg opens vpy using portable vapoursynth, but not mpc be (who cares...).

What's in system32 is a symlink to E:\Programs\AviSynth+\AviSynth64.dll, so all I have to do to disable it is rename E:\Programs\AviSynth+\AviSynth64.dll and the link can no longer find the DLL, resulting in the same error as if it wasn't installed.

[stax76]

Thanks for helping! I don't know what I could miss so have to give up for now.

[chros]

Originally Posted by ChaosKing

Soft links yes, hard links no. But you can't have relative soft links I think!? So not really portable then.

I use hardlinks in script on Win8/10 as a normal user, but I can't use softlinks as normal user.

[stax76]

It's working now after a reboot.

The German Wikipedia article on symlinks says that Windows soft links support relative paths, I hope that this is portable across machines.

In mpv.net I added a workaround.

        bool wasAviSynthLoaded;

        void LoadLibrary(string ext)
        {
            if (!wasAviSynthLoaded && ext == "avs")
            {
                WinAPI.LoadLibrary("AviSynth.dll");
                wasAviSynthLoaded = true;
            }
        }

It's working, vapoursynth works without such workaround, reason unknown.


edit:

it's probably not portable:

https://superuser.com/questions/7560...portable-links

[Groucho2004]

Originally Posted by stax76

        bool wasAviSynthLoaded;

        void LoadLibrary(string ext)
        {
            if (!wasAviSynthLoaded && ext == "avs")
            {
                WinAPI.LoadLibrary("AviSynth.dll");
                wasAviSynthLoaded = true;
            }
        }

Did you leave out the error handling or is that the actual function?

Edit - The reason I'm asking: Is there some built-in error handling in .net when for example WinAPI.LoadLibrary("AviSynth.dll") fails?