simple one - > with some effects, reaching the max or min values can cause problems ... change that 0 to a 1 or 128 to a 127... it can help avoid cpu surges on certain machines - noolout
Put folder "MolarWaves" with used samples to path: C:\MolarWaves.
I ascertained there were certain problems with MolarVSTi. There weren't any problems in progress of live-acting. The problems appears during another opening of saved .bmx - a typical error "Mutex etc, etc." I noticed however that this error appears, when on the job with the MolarVSTi is used the MonoChromeVSTi. There is here no meaning whether we work in Buzz or NewBuzz.
Himself MonoChrome acts correctly in progress of live-acting. However calls wretched "Mutex...", when is in opening file.
Besides: Molar under Buzz is fully configurable through MIDI hardware and software. When You used piz's "midi2qwerty16" VSTi (http://thepiz.org/dl/?p=vst) You'll can control MolarVSTi only through MIDI controller-keyboard.
In my experiences all functions of MolarVSTi worked under Buzz. The mouse will not replace the controler monome, but the multioctave keyboard is already almost close of the ideal, especially during meta sequence recording.