"Ouch. The VST3 plugin ‘Infernal: InfernalSynth 1.1.1 (from Infernal)’ crashed in event, function or class: ‘IPluginView’, Thread: ‘GUI’
IMPORTANT: This is a fatal error. Please save the current document under a !new! name to prevent losing important data. Renoise will silently ignore any following errors from this plug-in.
DO NOT IGNORE THIS ERROR; DO NOT CONTINUE USING THE PLUGIN. THIS CAN DESTROY YOUR SONG OR CAUSE OTHER RANDOM CRASHES AND PROBLEMS!
It’s most likely that this is a bug in the VST3 plugin, so please also report this problem to the authors of this plugin in order to get the problem fixed!"
I’ll wait a few more versions and try again later on.
Sure, thanks for trying it out. Quick question though, could you specify exactly which windows version you’re using? (Start>Settings>System>Info/About, windows specs, version and build number)
Sorry to bug you again, but do you also happen to know if you run an AVX2-enabled CPU? If not, I should turn the compiler settings down a notch. You could check using a tool such as this: https://www.hwinfo.com/.
It will be most likely something with memory allocation/deallocation. Can you even replicate this? What does the Renoise log file say? What about running the debugger?
Cannot reproduce, unfortunately. Out of the dozen or so users that tested it, Djeroek has it crashing on Renoise, one person has it unable to load in any host at all, and 1 person is running win7 so i’m gonna write that up to a not-installed-msvc-redistributable thing (although i should provide statically linked versions too for older windows versions). Everywhere else it seems to run just fine. Renoise, bitwig, reaper, fruity, ableton at least. As usual the real fun is that I can test all those hosts locally without problems. Release builds, debug builds. VST3 built-in plugin validator no problems. This GitHub - Tracktion/pluginval: Cross platform plugin testing and validation tool really nice stress test suite, also no problems. I’m at a loss, tbh.
@Djeroek I’m really out of ideas here. In theory you have the perfect setup, newest software, up-to-date hardware, everything. I totally get that I’m basically asking random strangers on the internet for some of their free time, so if you’re done with it, i get that.
I’m at a loss here, really. Hate to see it’s not working for you. The only thing I can think of is delete all SevenSynth/InfernalSynth files, completely delete renoise’s VST cache and try again. But I bet you already tried that. Barring that, I got nothing. Will check back here if I find something that I think might be related.
Can’t think of anything else, in general don’t have many issues using plugins. In the error it says failed to load a module named ‘loadlibray’, is this a typo? Should it be loadlibrary?
Definately a typo. LoadLibrary failed generally indicates one of 2 things, 1) the plugin failed to initialize (i.e. crashed in the actual plugin code) or 2) some dependencies of the plugin could not be loaded. Obviously 1) is a fault on my end (and probably so), but since the thing’s going on fine for users on a very similar setup as yours, I’m gonna be hard-pressed to find it. Or 2), this could mean you need to install this https://aka.ms/vs/17/release/vc_redist.x64.exe, but that’s very unlikely as you’re on a recent windows version.
Thanks, that’s good to hear, too. Now to be honest it’s unlikely for me to change the product theme, because infernal basically implies dark and creepy. And I like that, too. If I were to go with something completely different I’d have to rename the project, set up a new github repo, new website etc etc. That’s not going to happen anytime soon. I do think people calling the thing “crowded” have a valid point, so that’s something I want to fix. So, vnext will still have the dark theme, but a changed layout that makes the thing a bit more user-friendly. Still contemplating how that will look like, though.
but thanks again.