Ok, I only wish people would understand that some of us who are having problems are actually the very keen Storm musicians users like me!
Storm3 is still extremely buggy:(
I've discovered 1 technique that seems to fix the screen redraw errors!
When your entire screen/page gets lost because you minimized or
opened up sample library whilst software is rolling etc, you can
hit SPACE bar on your keyboard and it can restore this problem!
On the other hand if you want to have problems....plug in your mic...
open EZtrack and start chatting to yourself whilst a sequence with a couple of modules are running, this really sets off the timing problems. And all this with total cpu useage under 15%.
I dunno what to do about it, I would have thought the devs would be talking to us in order to make the software perform correctly, maybe
with a Mac it does, I dunno, but, for now for me the regime to follow is,
1/save every few minutes, any longer and your gonna lose everything to a freeze!
2/forget about recording microphone content/using EZtrack, and basically
pray very regularly.
3/Think about buying a dedicated recorder because EZtrack ain't got the balls to make it all worth going through.
Oh yeh, also, EZtrack input Latency is pathetic! Maybe the devs should
not try and compress the audio at the input phase? (If that's what is happening {I'd swear that the audio being recorded by EZtrack is being compressed in real time}....Please tell me I'm wrong.....