Just downloaded the new ANA2 version and I noticed that if I try to open the plugin when play is on (by the way… this happens in FL Studio 20 latest release)… the sound keeps going but ANA2 instead of opening freezes the DAW completly.
One thing to notice is that the DAW itself is not recognized by windows as a “Not responding process” , it’s like the DAW is still working but it’s completly frozen… can’t explain better than this ^^‘’’
WIN 10 - FL Studio 20 latest → What are your computer specs ?
Do you have this issue with the VST2 or VST 3 specifically or both plugins ?
Also, is this happening when running a project with already a certain amount of channels or another virtual instrument that might already use quite some CPU or do you experience this even with a light project that you’re sure isn’t already taking too much resources ?
Not into development myself but from what I know from it, VST 3 are usually more resources consuming. Next to that, we have to keep in mind that it’s the first iteration of VST 3 for ANA 2, so the developers might improve the code in that regard in future versions.
As Phil wrote in another post, there’s no real benefits to use the VST 3, I know it provides certain features like automatic track name reading & such but it’s not something very useful for a synth in the end. So if you have no issue with the VST 2, it’s probably better to keep using it for now IMO.
Took a little while to get back at this… but I can now confirm that it freezes even when using the VST2 format.
I also confirmed that the only thing needed for it to freeze is to try and open up the ANA2 interface while the track is in play mode… actually happened in a sound design session with only kick, Hi Hats, Snare and ANA2 Bass (that I was designing) right now.
EDIT: New thing… I’m starting to believe there is an issue with the GUI loading because now it’s freezing also if I try and open up the troublshooting options of the wrapper and then go back to the GUI…
Track is not playing right now, it’s on stop… it still freezes the daw trying to open up the GUI.
This is looking very similar to this other issue that has been reported, looks like it’s specific to ANA 2 under Windows, for both VST 2 & VST 3 with latest v2.0.97 → ANA 2 fails to recal the GUI in certain circumstances ( like having several instances inside the DAW ) and leads to infinite loop that will freeze the DAW.
Also happening with Ableton Live, so this might not even be specific to FL Studio.
Let me start with the Update: ANA2 at the moment doesn’t even start… or well… to say it better… It emits sounds but it does not open the UI at all… and it still keeps freezing everything.
I’ve tried in:
Reaper ( I downloaded it with the specific purpose of trying this out)
In all of these three DAWs ANA2 now doesn’t open the GUI at all and freezes everything.
This said my question: does ANA2 upgrade on it’s own whan a change is made? Because otherewise I do not understand how is it possible that it got worse with no upgrade on my part in the last couple of days ^^‘’’
No, it does not upgrade on its own - Maybe you’ve changed the GUI skin ? Some people are using custom skins and those older skins won’t work, the GUI will just not open, so only use the “default” & “black” skins with v2.0.97 for now.
Try this to see if it solves the issue for now :
With your DAW & ANA 2 closed
Go to C:/Users/Your_User_Name/AppData/Roaming/Sonic Academy/ANA 2
Delete your ANA 2.settings file inside this directory
Restart your DAW & launch a new instance of ANA 2
This should reset ANA 2 to default settings and revert the GUI to the “default” skin & size.
Uhm well… I don’t even have custom skins and I usually just use the black one ^^‘’ Also… the GUI does not open not only in FL Studio… but also in Mixbus and reaper… just o be clear… I never ever opened ANA2 in mixbus… and I just downloaded reaper just for tests… so I guess it should just load the default ones but it doesn’t.
Following on this, I did try to open ANA 2 v2.0.97 inside MixBus this wk and it’s working on my end, so this might be something else. For info I’m running MixBus 32c v6.2 on Windows 10 Pro.
Maybe a manual uninstall and a new install could help with v2.0.97, but at this point I think you should ask support a link to a previous v2.0.94 installer, do a clean uninstall before running the installer and keep using this version until issues in v2.0.97 are solved with a future update.