Klanghelm IVGI released: new free saturation and distortion plugin for Win and OSX

[trueparadox]

Yeah it's not FL. They are solid as a rock on the laptop (vista 32). They just seem to dislike my main studio machine (win7 64).

Oh no! I was getting excited about this freebie (big thanks for the generosity, by the way!), and was already planning to buy the big one, but i'm using a win7 64 machine, i hope this works on it! I'll try it when i get back home this evening... I'm running reaper64. Hoping at that either the native or the bridged 32bit one will work... Ideal would of course be the 64bit, but the screenshots look too good to pass up, i'll just have to bridge it otherwise .

No worries, it WILL work. AFAIK, Johnny's the only user who experienced issues like that, and only in FL. The plugin has been widely tested in numerous hosts for about two months, from Nuendo to Logic to ProTools to Studio One. And Reaper of course...

Tony

That's great! Thanks for the swift replies everybody. Super excited to go home and try the freebie out, and can't wait for the "big brother" !

[Compyfox]

To those with the bug - it could be that this is a bug due to the JUCE framework? If Tony is using that Framework.

I know that because I've heard similar issues from other beta testings (the random crashes with two instances, and the crashes if the GUI is opened/reopened fairly quick). And this is usually a bug with the framework - which can be fixed, but can't be reproduced on all rigs.

If I were you, contact Tony, ask him about the framework, tell him that this bug is happening if more than one instance per channel is open. Maybe he can fix this for all his plugins.



BTW:
IIRC, IVGI uses a refined framework which offers him faster coding and maintenance capabilities. So will SDRR. And if I got that right from mails with him, he plans to port his other plugins as well.



Long story short - contact Tony, ask him if he's using JUCE, there are several bugs known/documented that clearly reflect what you encounter.

[audiosabre]

which plug-in format is crashing FL?

I have found the FL VST3 implementation to be problematic, and also bridged 64 bit VST2 plug-ins. I recommend users of Endless Series (which is built with the framework that Klanghelm is using) to use the 32bit VST2 version in 32bit FL Studio.

oli

32-bit and 64-bit VST both cause same issue in FL 32-bit. Bridged or not.

FL 64-bit recently went into beta. I'll also test them native @ 64-bit. Never had a chance nbefore.

AFAIK, the bug involves GUI redrawing whilst the DAW is playing back. If FL's playback is stopped, it doesn't break a sweat.

Oh, and like Tony said, seems to be win7 64-bit & FL only. They will not crash in cubase using the same steps.

Then again, they will not crash in Win Vista in FL at all. It's hard for me to point the finger solely at IL.

[audiosabre]

Long story short - contact Tony, ask him if he's using JUCE, there are several bugs known/documented that clearly reflect what you encounter.

Thanks for the input Compy. The framework is IPlug. I think I'm going to download some other IPlug based plugins in an attempt to rule this out once and for all. It seems like a decent framework, and the problem only happens to me, on a single machine. The identical problem with Satson makes it a suspect though.

Me and Tony did go back and forth over this and he was really responsive. Could never reproduce it though. Tony put work into refining his GUI code, & I felt guilty he was giving his time to help me out, even though I was/am not (yet) a customer. So I stopped putting the pressure on.

I'd feel better if he concentrated on his paying customers. But if it truly is a framework problem and can be fixed, my money is waiting. I'm a huge fan of Klanghelm plugins.

I did test IVGI this morning. I crashed it in 10 seconds. That's the only reason I posted here really. I'll level with you guys; I realised how awesome SDRR is going to be, and felt jealous, to be frank. Me want too

[DuX]

Just one notice about the SDRR GUI. I think the fake reflection on the "glass" is completely unnecessary and it only makes it hard to see the needle clearly. And the purpose of the display is to see the needle/value clearly, isn't it?

In general, I think fake reflections on the VST GUI displays/glass are completely unnecessary, and look ugly [it's not my room!]. They're static and distracting. It's like a stain on your LCD. It doesn't add anything to the functionality of the GUI, but it definitely takes away from the functionality of it.

It's really inconvenient on the hardware, too. If I had a reflection on the hardware display, I'd move the device to a darker place, where I could see the display clearly.

Thankfully IVGI, DC8C, and DC1A don't have "reflective displays". So why this obsession with fake reflections suddenly, Tony? It's really just a nuisance. It looks fun for the first 10 seconds, until you start working seriously with the plugin.

[audiosabre]

OK, I promise you this is the last I will mention this issue, unless I am specifically asked about it. I don't mean to hijack the thread, but I just confirmed my suspicions about the framework.

I had a look through this thread; a list of IPlug-based products: http://forum.cockos.com/showthread.php?t=122276

Anyhow, now a list of IPlug plugins that I've just crashed in the exact same manner...

Sonimus Satson
Sleepy-Time LISP
Sleepy-Time Transient
jsAudio Compshaper
Cerberus Audio Ice9
TSE R47 v1
TSE BOD v1
LVC Audio Clipshifter 2.1.0 32-bit (demo)

I stopped at this point. I'd wager that they all indeed have this exact issue on certain systems.

Anyway, if the IPlug guys want to fix this issue, I'd be very grateful. I'll even help if I can, seeing I can crash these plugins every single time

This is why I was reluctant to blame FL Studio. It's been pretty solid as a VST host and I have 1000s of working VSTs. The 'broken' are all IPlug-based.

[bootsie]

Hey Tony,

congrats to a great freeware release! I'm already impressed and can't wait to try out the upcoming SDRR release!

cu
Herbert

[Compyfox]

Anyhow, now a list of IPlug plugins that I've just crashed in the exact same manner...

Sonimus Satson
Sleepy-Time LISP
Sleepy-Time Transient
jsAudio Compshaper
Cerberus Audio Ice9
TSE R47 v1
TSE BOD v1
LVC Audio Clipshifter 2.1.0 32-bit (demo)
...

Let's just stop at this point and do a little bit of trouble shooting.

Why? Because most of these plugins do work(ed) on my rig.



For example:
What kind of rig are you using?

Important: CPU, built (like i7 Bloomfield in my case), RAM, Motherboard
OS: also important, the service packs (if installed)
Do youhave the visual C runtimes installed? (some plugins still need them - this might not be related to the IPlug framework, but just in case)
What is your audio card? Are the drivers up to date?
What is your GPU? Are the drivers also up to date?
What is your host revision?
Does this only happen with VST2 or VST3, or does this happen with both?

Can you try if this problem also happens in another host on your rig? For example: Reaper (in demo mode), Herman Seib's VSTHost, a demo of eXT, MUX or whatever. Just to rule out if this is the host or the rig.

The more detail, the better.




What I'm trying to aim at:
Let's say this happens on your rig in FL Studio, but not in another host. Then it's something that has to do with the host. If it's also happening in other hosts on your rig, then chances are it has something to do with the compiler.


I don't know how many FL users are in the Beta Team - but there will be ton of FL users out there that might use this plugin.

So if there is an FL user in here, that does NOT have the mentioned issues - please speak up!



I'm sure Tony is reading along. But just in case, send him an additional mail with your full detailed specs!

[codec_spurt]

A Master at work.

[codec_spurt]

Let's just stop at this point and do a little bit of trouble shooting.

Well I run VUMT and DC8C no problems on a win7 x64 system in FLStudio (32 bit).


FWIW.

[Compyfox]

Did you try IVGI yet, codec_spurt?

It's a refined engine, and also massively optimized compared to first beta's.


Also:
Are you using VST2 or VST3 versions in your 32bit host?

[codec_spurt]

Did you try IVGI yet, codec_spurt?

It's a refined engine, and also massively optimized compared to first beta's.


Also:
Are you using VST2 or VST3 versions in your 32bit host?

Not yet, just dl'd it and I'm in Linux for the moment and for a little while longer.

When you ask about VST2 or VST3, are you referring to Tony's plugins? I wasn't aware he made both of each. Or are you just asking generally? I use some Melda VST3 plugs, but only coz I installed them by accident. Plus a few others. I only run 32 bit hosts on my x64 system, even though I have 8GB RAM. I have x64 versions of Reaper and Podium for testing plugins, but I don't use them for production.


I'm definitely buying the full plug when it's released. I don't even care what it sounds like. And distortion sounds like crap anyway, so the crapper the better. J/K.
It's worth buying just to stare for a few minutes at those delicious GUIs as a distraction to making music. But somehow, coming from Mr. Sound Helmet himself, I'm sure they will put a bit of sparkle in my life.


cheers.

[Compyfox]

When you ask about VST2 or VST3, are you referring to Tony's plugins? I wasn't aware he made both of each.

Yes, I was asking about the Klanghelm Plugins, and yes, the download bundles usually come with VST2 and VST3 versions (ending in .dll and vst3 respectively).

VST3 makes sense if you're mainly using sidechaining, or if the plugin offers "communication between plugins" (which seems to be easier to code in the VST3 realm). But... your host needs to support VST3, and it should have a suitable sorting feature (I am looking at you, Cubase!).

I only run 32 bit hosts on my x64 system, even though I have 8GB RAM. I have x64 versions of Reaper and Podium for testing plugins, but I don't use them for production.

I also use 32bit hosts, since I don't see a need for x64 plugins (yet), and half of my plugin array is still locked to 32bit. But in terms of bugfixing, the more info the better.

You don't seem to have an issue - which is good.

It's worth buying just to stare for a few minutes at those delicious GUIs as a distraction to making music. But somehow, coming from Mr. Sound Helmet himself, I'm sure they will put a bit of sparkle in my life.

It's more versatile than it looks, but it's not as in your face as you expect (read: like SoundToys). Though that can happen real quick if you overdo it with the drive knob.

[codec_spurt]

When you ask about VST2 or VST3, are you referring to Tony's plugins? I wasn't aware he made both of each.

Yes, I was asking about the Klanghelm Plugins, and yes, the download bundles usually come with VST2 and VST3 versions (ending in .dll and vst3 respectively).

VST3 makes sense if you're mainly using sidechaining, or if the plugin offers "communication between plugins" (which seems to be easier to code in the VST3 realm). But... your host needs to support VST3, and it should have a suitable sorting feature (I am looking at you, Cubase!).

Do you know, I never realised that. I will go back and check. I'm a bit of a sidechain hound so I don't know how I missed this. True sidechaining is one of the things I miss in the ToneBoosters plugs as they are coded with the VST2.4 framework for compatibility.

I only run 32 bit hosts on my x64 system, even though I have 8GB RAM. I have x64 versions of Reaper and Podium for testing plugins, but I don't use them for production.

I also use 32bit hosts, since I don't see a need for x64 plugins (yet), and half of my plugin array is still locked to 32bit. But in terms of bugfixing, the more info the better.

You don't seem to have an issue - which is good.

I really don't need 64 bit plugins. Or hosts. The whole drive towards them and the vocal minority whinging about it has put an incredible strain on developers. All for the new shiny. But that is another argument for another day. I'll be sure to check all the Klanghelm versions in FLStudio though, just to be sure, in regard to this strange anomaly.

It's worth buying just to stare for a few minutes at those delicious GUIs as a distraction to making music. But somehow, coming from Mr. Sound Helmet himself, I'm sure they will put a bit of sparkle in my life.

It's more versatile than it looks, but it's not as in your face as you expect (read: like SoundToys). Though that can happen real quick if you overdo it with the drive knob.

Well, I know about subtlety from the other Maestro in the field - Bootsy. Ferric I find very very difficult to distinguish when it is ON. Subtlety is good on a plug of this type. If I get bored with that, I can always patch in my Boss HM-2 Heavy Metal pedal. Horrible it is. But does the trick sometimes...

I also have my Akai MG-614 with DBX type-1 NR.


Anyway, there are just so many uses for a plugin like this, if it is used sparingly. Harrison Mixbus is unusable on my windows system. And the Saturation plugs I have are extremely juicy on the CPU, excluding them from being used on every track. I was just about to buy TB ReelBus, but funds are short and I think I might wait for this. It certainly is prettier. And it couldn't be much heavier on the cpu.



cheers.

[118912]

fl studio user here and it works great on my win7 64 bit

cant wait for sdrr, it might be the first plugin i will buy from klanghelm