breakmixer wrote:If you use it with 6? I guess it'll work with 5, so just need to wait to see if work continues to pick up like it seems to be doing atm and once I get my tax rebate if I can afford it then I'll be getting a Mopho, the UI looks nice btw. but if you can definately check it'd be a bonus, I've downloaded the demo - but with the Mopho itself cannot fully test(obviously)....
Well, in software nothing is sure before it's sure. So I'll still check it. But if you can already load it up in Cubase5 and select midi ports etc, there shouldn't be anything stopping it from working.
Oh oh oh.. You could even try it out with two instances of my editor!
You'll need to "install" them to two separate folders and rename the other dll, load them both up in Cubase5 and select one to send data and the other to receive. You'll also need to connect the midi out to the midi in on your interface with a midi-cable.. or use a loopback driver(they don't support sysex though). A very good, and the most stable free loopback driver is Copperlan. Highly recommended.
With this setup you can see that every control is sending and receiving.. and that the preset load up procedure is ok, even when opening a project-file (this is where most editors fail). On preset load the editor sends out a sysex of the patch, so this won't work with any loopback driver, you'll need the cable-approach.
I don't really blame SoundTower for not jumping to the VSTi market.. though i hate unfulfilled promises. The tech needed for this thing is quite complex and filled with problematic spots. Without full understanding of how threads work and how midi is handled it's going to be a major PITA to code. As can be seen from pretty much any other VSTi editor: A. they use huge amounts of CPU-time because of bad threading approach B. fill the midi-port with junk messages C. send way too many control messages when automated D. and even crash if automated too quickly..
Btw. If the control receiving is a bit laggy it's caused by the hacked up NRPN receiver in there. It's a feature i haven't perfected yet. Problem is only in the screen update. No messages are lost. I'll get to making it smoother soon. Priority now is Keyboard version and applying CC messages in tandem with the NRPN.. which equals to More Modulation Mayhem! without taxing out the midi-port too much.