KVR Audio

Caine123 · Post by **Caine123** » Tue Apr 19, 2022 8:55 am

hi guys, i got with a rescan of plugins a lot of errors, always the same error with Synthedit VSTs, mostly these are old 32bit ones but i wonder if someone else has/had this problem? i also opened a case with IL. thx

TIMT · Post by **TIMT** » Tue Apr 19, 2022 11:06 am

Had errors, but mostly related to SynthEdit effects being detected as instruments, and even if you change them to FX, they show up in the instrument channels. Been a thing since FL20, so i don't see it being fixed

Caine123 · Post by **Caine123** » Tue Apr 19, 2022 11:11 am

TIMT wrote: Tue Apr 19, 2022 11:06 am Had errors, but mostly related to SynthEdit effects being detected as instruments, and even if you change them to FX, they show up in the instrument channels. Been a thing since FL20, so i don't see it being fixed

oh crap, i need to test it in FL12 etc. i got a case open on IL page, hope they will check it, it really is annoying and shows this is no single plugin issue but all synthedit ones.

Trancit · Post by **Trancit** » Tue Apr 19, 2022 11:36 am

Perhaps it´s more and more time to say goodbye to these old stuff!

Synthedit was always crappy and as more times move on it won´t get better for sure

Caine123 · Post by **Caine123** » Tue Apr 19, 2022 11:47 am

Trancit wrote: Tue Apr 19, 2022 11:36 am Perhaps it´s more and more time to say goodbye to these old stuff!

Synthedit was always crappy and as more times move on it won´t get better for sure

thx a lot, i just had a reply of IL, in FL12 i just tested a few and they work. IL says it is synthedit not FL's fault but yes it is FL20 error not the plugin they work pre-fl20

Trancit · Post by **Trancit** » Tue Apr 19, 2022 1:22 pm

Caine123 wrote: Tue Apr 19, 2022 11:47 am
Trancit wrote: Tue Apr 19, 2022 11:36 am Perhaps it´s more and more time to say goodbye to these old stuff!

Synthedit was always crappy and as more times move on it won´t get better for sure
thx a lot, i just had a reply of IL, in FL12 i just tested a few and they work. IL says it is synthedit not FL's fault but yes it is FL20 error not the plugin they work pre-fl20

That´s not what I meant...
Synthedit stuff was always very "sensible" and if IL changed now something that these plugins got problems please do not expect they will put much time into investigating or reverting any changes...

If something like this happens it´s often the more "stressless" decision to let go dead stuff and concentrate on maintained plugins

AnX · Post by **AnX** » Tue Apr 19, 2022 1:28 pm

Trancit wrote: Tue Apr 19, 2022 11:36 am

Synthedit was always crappy and as more times move on it won´t get better for sure

Fake news

Trancit · Post by **Trancit** » Tue Apr 19, 2022 10:55 pm

AnX wrote: Tue Apr 19, 2022 1:28 pm
Trancit wrote: Tue Apr 19, 2022 11:36 am

Synthedit was always crappy and as more times move on it won´t get better for sure
Fake news

Really??

I never really bothered with them but I can remember very well in the time as synth edit plugins were all around that if somebody had problems with a plugin it was often a synth edit one...
If there was a warning where to stay away from... it was synth edit...
If there were high CPU usage problems...it was synth edit...

That´s enough for me to call them crappy... and now as developers stop to support 32bit plugins more and more I do not see any chance why this should improve in future...

AnX · Post by **AnX** » Wed Apr 20, 2022 5:11 am

SE is 64bit now, has been for a long time

Trancit · Post by **Trancit** » Wed Apr 20, 2022 1:47 pm

And all the old available plugins the people are using??
Are they automatically ported to 64bit too???

The answer is: No!

As nearly nobody is still making any synthedit plugins anymore it serves a sh*t that the actual enviroment is now (or longer) 64 bit as long as all the existing ones aren´t updated by their developers which are mostly out of business already...

You can ride on the theory as long as you like but the practice shows only one truth: get rid of them as fast as you can or face the trouble they are causing already now (or already long time) which will get worse and worse.

Teksonik · Post by **Teksonik** » Wed Apr 20, 2022 2:20 pm

As much as I love and use FL Studio it has become a bit wonky here in recent versions and has always had the "Fixed Size Buffer" issue when dealing with third party plugins.

One plugin developer who I won't name had the following to say:

"It seems that you are using FL Studio as a DAW. It has a badly designed audio-architecture with lots of jitter that causes CPU spikes. As a result it can crackle when plugins process blocks of data. It affects also plugins for other companies.
I was in touch with Image Line for several times about the issue, but it was ignored by them. Since Image Line did not fix the issue for a decade I added a special workaround for FL Studio in the recent updates of the plugins".

At least one other developer I can think of off the top of my head had to release a special fix of his plugin for FL Studio as well.

These are not Synth Edit plugins. To be honest I can't remember then last time I actually installed an SE plugin let alone use one in a project. It's probably been at least a decade or more.

But FL can have issues with top tier plugins from well known developers who do not use SE or Flowstone.

Teksonik · Post by **Teksonik** » Wed Apr 20, 2022 2:24 pm

Caine123 wrote: Tue Apr 19, 2022 8:55 am hi guys, i got with a rescan of plugins a lot of errors, always the same error with Synthedit VSTs, mostly these are old 32bit ones but i wonder if someone else has/had this problem? i also opened a case with IL. thx

Do you have a link to one of the SE plugins that causes a scan error (if it's freeware)? I'll install it on my test system and see if I get the same results.

AnX · Post by **AnX** » Wed Apr 20, 2022 2:34 pm

Trancit wrote: Wed Apr 20, 2022 1:47 pm And all the old available plugins the people are using??
Are they automatically ported to 64bit too???

The answer is: No!

As nearly nobody is still making any synthedit plugins anymore it serves a sh*t that the actual enviroment is now (or longer) 64 bit as long as all the existing ones aren´t updated by their developers which are mostly out of business already...

You can ride on the theory as long as you like but the practice shows only one truth: get rid of them as fast as you can or face the trouble they are causing already now (or already long time) which will get worse and worse.

Or you could just not use them if they are making you spit the dummy, and let the grown ups carry on using a perfectly good modular environment for their musical creations.

Never had a single problem with any SE stuff here.

sjm · Post by **sjm** » Wed Apr 20, 2022 5:06 pm

Caine123 wrote: Tue Apr 19, 2022 11:47 am
thx a lot, i just had a reply of IL, in FL12 i just tested a few and they work. IL says it is synthedit not FL's fault but yes it is FL20 error not the plugin they work pre-fl20

Fl 20 broke a while bunch of plugins, including vst3 that worked previously. If they worked before, I don't see how that's the plugin's fault, whatever il say.

Vortifex · Post by **Vortifex** » Wed Apr 20, 2022 5:08 pm

Edited

Synthedit vst problems with FL Studio?