sjoerd

Jup. Fruity edition v21.0.3. Have you tried the debug version? Anything interesting in the fl crash logs?

Trying again as my previous comment didn't come through. @moderator is it inappropriate to discuss FL studio related stuff over here? If so I'd be happy to move the conversation somewhere else. @dee: i9 should definately work. If you're up for it we can try to find out what's wrong, but that'll involve some help from you, too.

regarding flstudio, there are 2 folders in zip => Either of them should work. Even both side-by-side. But preferably, use the "1.1" version. also it says V1.1 not v 1.1.3 inside zip => Yeah, I should really clean up that version stuff someday. But it's probably not what's causing you issues. i have placed many vst in flstudio vst3 folder => That's exactly how infernal should be installed. Just download, unzip, copy to VST3 directory. please make clear video how to install => Attaching a zipped mp4 video of the installation and the plugin subsequently showing up in fl studio. In all fairness though I really don't think you did anything wrong with the "installation". Like you said, it's just download, unzip, copy. It's more likely that your machine/os is incompatible with the plugin. What os are you running? Is it 64-bit? Is your FL studio version 64-bit? (probably yeah, but just checking.) And of course, do you have a cpu with avx support? You can find out with a tool such as this: https://www.hwinfo.com/ infernal_install.zip

Hi all! Always nice to see my spare time hobby project spark a discussion. This plugin requires a CPU with AVX instructions to work - jup, but I could easily do an SSE4 or older CPU build. Would be a less performant plugin, of course. No Mac! - Never will be unless someone decides to buy me a mac. Working on linux support though, because I can just test on a VM. Not possible without buying OSX. Not working in flstudio, anyone has luck with it? - FL Studio is explicitly supported, it's one of the hosts I test myself. Even worked with image line to have a bug related to infernal fixed in fl studio, they were very supportive. If you like we can work together to find out whats wrong, but that'll take some time on your part, too. Unless you're on an old CPU without AVX, then I could just do an SSE build. I estimated there are between 2000 and 3000 parameters exposed - around 1600, actually, but "only" around 250 unique ones (e.g. not counting fx1 filter freq, fx2 filter freq, fx3 filter freq etc). I can't even make sense of how the signal path goes - the little triangles in the UI lay out exactly how the signal path flows, as does the routing diagram in the manual: https://github.com/sjoerdvankreel/infernal-synth/blob/main/MANUAL.md. If you want to know more, i'd be happy to clarify. Maybe once I swap out those images, I will be able to focus more on what each of the controls does. - See here https://audiosex.pro/threads/sjoerdvankreel-infernalsynth-was-anyone-able-to-get-this-to-work.69579/ for some nice alternatives :) Just to be very clear on what infernal is and is not, it's my personal playground/hobby project/learning project. I basically took every free/open source algorithm out there and decided to put it in a single softsynth. It's also my first plugin ever. Infernal contains absolutely nothing new in terms of synthesis possibilities. It's just that I tried to combine all that free stuff under a single roof, so to speak. The entire demo tune was done using infernal only, no samples, no other plugins. Apart from myself and a handful of other users, everyone and their mother seems to hate the ui. I'm currently trying to rewrite that to be a bit more traditional, but that's starting to look like a ~1year project. Here is a rough sketch of what the oscillator section might look like. Any feedback welcome. Also, if anything's not working as expected, just drop me a mail! My personal email is on the project website. Cheers! -Sjoerd