Testing a new internal build here and confirming this one as well, only happens with the VST2, no issue with the VST3.
Tested with latest Bitwig Studio 4.0.6 on Windows 10 pro here: the VST2 GUI window won’t close automatically when closing the Bitwig project, you need to close the GUI window manually in order to be able to access Bitwig main menu and load a new project.
Yep, I’ve gone back to previous version as I spend most of my time in Bitwig and VST3 is not an option.
Looks like this is fixed with this new build 
Still some testings to do, tho.
ANA 2 beta v2.0.992b is now available from your accounts : My Account / My Downloads / Plugins
As usual… Let us know 
@Darcey One at a time please… We haven’t planned to implement agile development yet 
…Just kidding… 
Hi @Tekalight
Beta V2.0.992b Tested and the results are fresh in! 
NOTE: I have typed comments in the video as I am testing for you…
. . . … . . . … . . . … . . .
No sound corruption on preset change and selection anymore!
Meat is back on the menu bitwig boys! erm I mean VST3… 
A lot better, it’s no longer sticking after preset selection, however…
Still present in both VST2 & VST3, better than it was, not sure but I think VST3 seems to scroll a bit better.
Scroll of main presets panel works most of the time but there are scenarios where it doesn’t work at all, especially if you are at the bottom of the preset list and select something, you seem to loose the up scroll capability. I think this is an offset issue, to where the visual mouse pointer is and where Ana2 coordinates for the mouse location actually is.
3. NEW, not a bug but an effect which could point to why some scroll issues exist.
If you note in the video at certain positions of mouse pointer when scrolling through presets on both VST2 and VST3, the preset that I am not hoving over one of the stars on the preset below (could be 1st to last star) as if it thinks the mouse is hovering over that star (hover state offset, it thinks the mouse pointer is somewhere else, which could mean this is why it can’t scroll at the bottom, that offset thinks its outside of the window in the lower section and scroll is lost???)… Maybe when at bottom those coordinates exceed the window dimensions thus scroll is lost?
It’s off by ?? on x and ?? on the y axis in positive values.
Fixed 
Did not occur in this test session, but it’s very random and I’ve not found a way to re-produce it. It could happen in the first 5 minutes or after 15 minutes. But it is only a cosmetic issue.
What you star in the VST3 is not persisted in the VST2 version, and visa versa.
Mouse scroll wheel enable lists for each pane/panel if they have enough content inside them that the scroll bar is visible, if not scroll the presets list (or just allow scroll if mouse is actually over that pane/panel).
Detect when the mouse is over the panes themselves (bounding box or get rect (TL,TR,BL,BR) for each? and mouse x,y relative to window top left x:0, y:0).
Then when the variable (string maybe) is set to presetsWindowMouseIsOver= “genres-pane”;
It then check that pane/panel to see if the scroll bar is enabled, if yes, mouse wheel scroll scrolls that pane. If not, 2 options.
I could see why option 1, scrolling anywhere in presets window mode would scroll presets if your anywhere other than over another scrollable plane but it also makes sense for scenario 2 as you logically you shouldn’t scroll something that you don’t have focus on (your mouse is not over).
Seems logical Jim…
As you will see in the video I couldn’t mouse scroll the genres pane while over it but the presets pane would keep scrolling…
And by request… 1 Video to rule them all…
Scrum meeting in the morning…
Does this mean I can add Software (VST) Tester to CV my
Fantastic! Tested it out and it looks like all the presets are playing properly in Bitwig. Very happy about that! Thank you!
Ana2 can replace so many other synths I honestly wonder why I have dozens of others now haha.
All it needs is a basic timestretch mode for the samples (to slow down and maintain the sample length/speed at different pitches), and mpe! 
This is being looked into by our dev. and they were able to replicate the issue and hopefully they’ll get a fix but while this is still under investigation it seems that turning the option “Plug-in Interface Scaling” off in Bitwig settings ( Windows Only ) is a possible workaround.
