core.sangnom.SangNomMod(..) vs core.sangnom.SangNom(..)

[Selur]

Would be nice if SangNomMod could use 'core.sangnommod.SangNomMod(..)'
otherwise when having both the sangnom and the sangnommod library inside the autoload folder of Vapoursynth, one get's something like:

vapoursynth.Error: Plugin load of /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib failed, namespace sangnom already populated by /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnommod.dylib

[theChaosCoder]

+1
But is there any reason to use this plugin at all if there is a much better alternative?

[Selur]

some scripts use it :)

[sl1pkn07]

ping(?)

greetings