...because some of it reeks a bit of work in progress at the moment. I managed to crash it twice in the first half an hour of testing. The first crash happened as I was sustaining a big pad with a pedal and moved outside cubase to another window. (in fact I was just typing a message to a friend while playing the pad that "this synth rules dude you have to tr.." *crash* "oh shit".
) Cubase SX3 froze and I had to restart it.it crashed the second time when I was simply browsing through some of the more adventurous presets. The synth engine went in some kind of infinite loop and there was nothing I could do about it. This time it didn't crash the whole host, simply had to unload polyanna.
(Cubase SX3.1, latest version in a rock stable system.)
OK the GUI is big I can live with that, and the parchment theme makes things readable, but it has one seriously annoying "feature". When I open the gui it completely re-initialises itself, and this takes a good while every single time. This happens *every time* the GUI comes on the screen, whether from outside the host or from a different workspace. From programming my own plugin I know this is a trade off with bitmap mem usage vs. drawing the GUI on the screen, but how about you initialise the GUI bitmaps in constructor instead of in open()? it would make the synth feel much more robust and completely eradicate the slow opening of the already pig/big GUI. These days we have enough memory to keep the bitmaps in all the time so you wouldn't have to resort to the unnecessary mem saving by initialising the bitmaps in open(). (I'm speculating on your GUI code here, but I suspect I'm on the right track)
The midi learn implementation is the best I've seen in any synth to date.
)
)
