+- 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: [HELP] Hybrid keeps crashing (/thread-4392.html)
Pages:
1
2
RE: Hybrid keeps crashing - Selur - 30.05.2026
Settings should be fine, just make sure to resave them.
Cu Selur
RE: Hybrid keeps crashing - Oldermediaformats - 02.06.2026
I did a "standard" deinstall but after installing latest dev version, I still got a crash.
So I had to do a comprehensive deinstall, then installed most recent version, and tried a sample video with just one filter applied. It worked without a crash!
So I created a duplicate of the previous scripts subfolder, which contains my profiles and .json files of my custom filters saved for Avisynth and Vapoursynth. After the new install, my settings are located under a directory path like this:
C:\Users\[username]\AppData\Roaming\hybrid\profiles
My question is: should I drag and drop that archived scripts folder with my .json files into the new profiles folder
or when I'm in Hybrid's gui, should I manually import each filter one by one when I'm ready to apply them? Plus, re-save them.
Thanks!
RE: Hybrid keeps crashing - Selur - 02.06.2026
Doesn't really matter, what you should do is load and re-save old porfiles&co, otherwise they can break stuff over time.
If after that, you run into a crash create a proper debut output and share it, so I can look into it.
Cu Selur
RE: Hybrid keeps crashing - Oldermediaformats - 02.06.2026
Thanks. Is there a way I can generate individual debug output files on a per-job basis?
Because in the penultimate version of Hybrid, my settings were such that it kept populating a single Notepad file with one debug output after another. In other words, it wouldn't produce a separate file after I started and completed a different job. It just kept adding debugs to the same document.
RE: Hybrid keeps crashing - Selur - 02.06.2026
No, debug output is not meant to be kept turned on as a general option (since it logs too much for that).
Most of the stuff it logs is not job specific, so it would be hard to split by job.