Selur's Little Message Board
Using Hybrid without autoloading existing VS install - Printable Version

+- Selur's Little Message Board (https://forum.selur.net)
+-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html)
+--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html)
+--- Thread: Using Hybrid without autoloading existing VS install (/thread-4313.html)

Using Hybrid without autoloading existing VS install - GunplaXross2 - 31.01.2026

If having an existing VS install for other work, Hybrid seems to throw out errors due to plugins already being loaded or a different VS install. Is there a way to prevent Hybrid from looking for existing installs/ignoring them? 
File attached too*

File "src/cython/vapoursynth.pyx", line 3114, in vapoursynth.Function.__call__
vapoursynth.Error: Plugin C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll already loaded (systems.innocent.lsmas) from C:/Program Files/VapourSynth/plugins/LSMASHSource.dll


.zip   HybridDebugOutput.zip (Size: 33,25 KB / Downloads: 38)



RE: Using Hybrid without autoloading existing VS install - Selur - 31.01.2026

Hybrid does use a portable Vapoursynth (and Python), so it should not load stuff outside that scope.
I think the problem isn't really Vapoursynth, but vsViewer. Smile
Have you tried whether vspipe works?

Seems like vsViewer is using the wrong environment.
Does the attached vsViewer binary work?
Also try with the old, whether starting Hybrid and then Tools->vsViewer and enabling "Edit->Settings->Paths->Libraries form this list are loaded prior to Windows registry or system PATH" (and hitting apply) makes a difference.

Cu Selur

RE: Using Hybrid without autoloading existing VS install - GunplaXross2 - 02.02.2026

The EXE fixed it right away, thank you for that. Will this change be bundled with the dev branched, or is this a "me" problem? Smile

RE: Using Hybrid without autoloading existing VS install - Selur - 02.02.2026

I'll think about it, will have to modify:
a. vsViewer to make the change optional
b. adjust Hybrid to call vsViewer with the new parameter

Cu Selur

RE: Using Hybrid without autoloading existing VS install - Selur - 04.02.2026

Does the attached version work for you too?
(didn't remove the loading from registry, but moved it to be a last resort)

Cu Selur

Ps.: if it does, the changes wouldn't require additional adjustments, which would be nice.

RE: Using Hybrid without autoloading existing VS install - GunplaXross2 - 16.02.2026

New one seems to work, I'll let you know if it causes any issues once I start pumping more odd cases through it. But since I'm here, have you considered adding "Blackman" and "Blackmanminlobe" to the color resizer options? 

They don't ring as much as lanczos, but sometimes produce a more "faithful" downscale of the chroma for some content. Fmtconv includes them both, and they're a lot more sane than spline36 or lanczos at least in my opinion. For example, the avisynth convert option exposes it as a built-in resizer, so I think it's a nice idea to include as a sane default. I Apologize if you're not interested, I just really like the software you produce.

RE: Using Hybrid without autoloading existing VS install - Selur - 16.02.2026

Quote: Fmtconv includes them both, and they're a lot more sane than spline36 or lanczos at least in my opinion.
Personally I like the default bicubic for chroma resizing,.. and think it already is a sane default. Smile

I'll think about using fmtconv instead of or as alternative to the inbuilt resizers, which are currently used for chroma resizing.

In case I decide to do this will take a while since quite a bit of code needs to be adjusted for it.

Cu Selur