We’ll see. For the time being, it appears you’re in the right and I have bad taste: https://audiosex.pro/threads/sjoerdvankreel-infernalsynth-was-anyone-able-to-get-this-to-work.69579/ 
1 Like
after installing in Renoise after first boot I immediately get;
"Ouch. The VST3 plugin ‘Infernal: InfernalSynth Generic (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!"
Pressing away the error, the gui shows up tiny like;
For what it is worth I set the scaling to 125% in Renoise and use a resolution of 3840X1080 in windows.
Hey! Tried out the dpi scaling but I don’t seem to have any problems with it. What windows and what renoise version is this?
windows 10 & latest Renoise.
Should be fully supported, but you’re not the first one to have troubles with it. Just found and fixed 1 major bug, see here https://sjoerdvankreel.github.io/infernal-synth/dist/infernal-synth-1.1.1-0bpmfix.zip for new binaries. Would you care to give it a try? You want the release/infernalsynth folder in there, if that still doesn’t work, the debug/infernalsynth version also won’t work but if lucky it will provide some more info.
What about a Mac build?
Unfortunately no, I just don’t have the hardware to test on.
exactly the same issue with the 1.1.1 version;
"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)
Windows 10 Home
22H2
19045.2604
Thanks.
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/.
I checked with CPU-Z and AVX2 instructions are supported here.
Obviously not what I wanted to hear but thanks again.
1 Like
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.
1 Like
@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.
If not, could your perhaps run the plugin (preferably the debug version of it https://sjoerdvankreel.github.io/infernal-synth/dist/infernal-synth-1.1-debug.zip) through this validation tool GitHub - Tracktion/pluginval: Cross platform plugin testing and validation tool with the strictness level cranked up to max? It should spit out all that’s wrong with the plugin on the console output tab.
sorry man, really no time here right now, but will check somewhere this week. Perhaps someone else with windows 10 can try?
1 Like
NP, thanks for the effort so far. As far as I know you’re the only one on win10 having these issues.
Tried the debug version and this doesn’t throw up the error I previously got, though still wont show a gui / wont initialize. From the Renoise log;
"Vst3Plugs: Instantiating: C:\Program Files\Common Files\VST3\InfernalSynth.vst3\Contents\x86_64-win\InfernalSynth.vst3…
Vst3Plugs: Failed to load module: LoadLibray failed.
Audio Plugins: Failed to open plug VST3: FBFCEDA8782047CEA12E8A8C8C3407E9
Exception: Failed to initialize the plugin ‘VST3: Infernal: InfernalSynth Generic’.
Error Message: Failed to initialize the plugin ‘VST3: Infernal: InfernalSynth Generic’.
Vst3Plugs: Instantiating: C:\Program Files\Common Files\VST3\InfernalSynthFX.vst3\Contents\x86_64-win\InfernalSynthFX.vst3…
Vst3Plugs: Failed to load module: LoadLibray failed.
Audio Plugins: Failed to open plug VST3: 00AE86BB62E6495BBB947F2F7D98CC1A
Exception: Failed to initialize the plugin ‘VST3: Infernal: InfernalSynth FX Generic’.
Error Message: Failed to initialize the plugin ‘VST3: Infernal: InfernalSynth FX Generic’.
Application: Exit…
"