R4 - error message in FL Studio recovering plugin state...

[Caine123]

hi, it seems i used the vst3 version in the past always (have vst3 and vst2 installed) well reloading the projects gives me this error:



sucks a**. i uninstalled R4 and updated it, still the same error.
i uninstalled it completely and just installed ONLY the vst2 version, f*ck it isnt compatible with the vst3 version... cause it only wants the VST3 version. ok wtf?

anyone knows this issue? afaik i never had this error with any other plugin.

of course i dunno what settings i had in each project i used this plugin...

[jtsterays]

one of the dev on the fl studio forum said the error occurred due to R4 using the old JUCE framework,it worked for me when i turned on "make bridged" in the processing tab so try do that
edit : also the vst2 version is pointless because its in mono

[Caine123]

one of the dev on the fl studio forum said the error occurred due to R4 using the old JUCE framework,it worked for me when i turned on "make bridged" in the processing tab so try do that
edit : also the vst2 version is pointless because its in mono

thx for your reply!

what? why would you relese a plugin only in Mono with VST2? wondering...

ok i just testetd it with bridge mode but it seems to not save the setting when i open a new instance, this is really strange, i need to fully rescan now and test

[jtsterays]

thats a bummer,i hope izotope updates these exponential reverbs to be stable because they sounds really nice,some of the best ive heard so far

[Caine123]

does anyone know why the vst2 version is in mono?

[NikkiA]

does anyone know why the vst2 version is in mono?

It's a FL bug somehow, it is correctly stereo in other DAWs. And I guess IL blames Izotope, who have no intent on supporting the Exp Audio plugins anymore, so noone is fixing it.

[Caine123]

does anyone know why the vst2 version is in mono?

It's a FL bug somehow, it is correctly stereo in other DAWs. And I guess IL blames Izotope, who have no intent on supporting the Exp Audio plugins anymore, so noone is fixing it.

i will let IL know, i also found out that my projects and state of R4 are loaded correctly in FL12 but not 20....

[NikkiA]

It's (the stereo bug) been reported on the IL forums before, so they should be aware of it already, I suppose more voices might make it a better chance that they'll do something rather than waiting for EA to do something.

[vitocorleone123]

It's (the stereo bug) been reported on the IL forums before, so they should be aware of it already, I suppose more voices might make it a better chance that they'll do something rather than waiting for EA to do something.

There is no EA and hasn't been for years. iZoptope has end-of-lifed these products (they want you to buy Neoverb), and I wouldn't expect any updates ever. I could be wrong, of course, but... I've moved on. I replaced R4 + Nimbus with Cinematic Rooms Pro + TaiChi.

[Caine123]

guys im back at R2 and R4 and i could solve some issues, but just to check the VST3 version of these plugins are fully stereo/working properly? i didnt test VST2 version again now, but im also trying to recover my settings from my projects and replace them with Liquidsonics Reverbs, as i got them some time now and didnt use yet ;D.

[Danilo Villanova]

I'm afraid we've all been "izotoped".

They still work fine in Reaper, Win10. I will continue to use them until they don't work anymore, and I will never give them money. Only second hand, so now I'm "izotoping" them.

[MJACau]

Have you tried a VST rapper loader like DDMF's Metaplugin or Bluecat's Patchwork to load the plugin?!
I've done that to work with some really old VST's that aren't stable in FL Studio.

[osiris]

Maybe an answer here:
https://forum.positivegrid.com/topic/50 ... 2-2-2-5090

Lots of people using Bias stuff had the problem, one person did this:

I wrote to Positive Grid support and waiting for their response now, but I have a solution already.
I just discovered that if I make the plugin bridged by going to Detailed settings > VST wrapper settings > Processing and checking the "Make bridged" radio button (screenshot attached) then the problem is no longer present and presets work correctly. You also have to make sure that all instances of bias have this button checked
(I seem to remember I had to do this with a badly behaving VST3 plug and it worked)

[Caine123]

thx a lot i will check this out! hope it works, though i try to replace these reverbs, i have no good feeling using izotope stuff anymore :/

[Caine123]

Maybe an answer here:
https://forum.positivegrid.com/topic/50 ... 2-2-2-5090

Lots of people using Bias stuff had the problem, one person did this:

I wrote to Positive Grid support and waiting for their response now, but I have a solution already.
I just discovered that if I make the plugin bridged by going to Detailed settings > VST wrapper settings > Processing and checking the "Make bridged" radio button (screenshot attached) then the problem is no longer present and presets work correctly. You also have to make sure that all instances of bias have this button checked
(I seem to remember I had to do this with a badly behaving VST3 plug and it worked)

thx again osiris, this seems to solve the issue, not from the old projects cause there i needed to STRANGELY open the projects in FL20.1 and in later versions the state wasnt recovered, it seems something broke this from IL's side. anyways i will update this case in IL Ticket i got and update the FAQ