The main Reason I can see for ParseQ's existence is simply automation and control (of Scope devices/synths). XTC mode is a work-around, too unwieldy to manage all of Scope synth (or device) parameters and thier automation, either for programmers or users.Fluxpod wrote:So.After reading up on this whole scope 6-Parseq thing i am still not sure why the world needs another sequencer.
I know there are some that use XTC succesfully, but that doesnt exclude a new, better solution. Like Julian said - something like - 'a sequencer that knows whats happening in the Scope layer' and that could potentially yield benefits we cannot image right now. Like a control protocol not limited by 128 discreet values (the MIDI system) - just to start the ball rolling.
Forget ASIO latency, Silentway patching, the limitations of 8 bit MIDI streams and buggy XTC synths. A DAW with analog like control over FAT onboard synths that beat thin VST's in to a pulp and behave like real analog gear live is a comin ... ! Ay...men !