dante wrote:Does this sum it up ?
. Open Scope basically liberates Scope from the Project Window.
. The only way to do that previously was to use XTC mode and integrate with a sequencer (albeit bound by the model of existing Scope devices).
. Now it would be possible for a host developer to write (or modify existing) sequencer app (a'la ProTools) on Host that used XITE DSP as its audio engine.
. The integration between sequencer GUI and DSP would be a lot more seamless, versatile and reliable than XTC.
. But the audio engine for this sequencer would still be running 21065 code on the Scope hardware in the absence of a 21369 based SDK.
Not really - the above is quite limiting. The #1 point should be something like this :
- Open Scope basically liberates the Scope hardware from the Scope application.
All previous versions of the Scope application talk directly to the hardware, but SC have decided to make a new Open Scope API - basically a communication layer between the software and the hardware. Scope 6 will communicate with this layer and not directly as before - the very good thing is that SC have made it possible for anyone (who have interest in developing) to get access to this new layer (can communicate with the hardware).
* One could make an application similar to the rack setup in Reason with completely different plugins - where on the back you do all the routing. You could start this application without starting the Scope application - it's completely separated. You might never use Scope 6 again or switch between them.
* Another could make a large modular synth which transforms XITE to a large hardware modular synth - no Scope environment in sight.
* DAW makers could integrate the Scope hardware into their applications - not running the Scope plugins, but their own plugins on the hardware.
And it's not limited to the above - It's about giving the Scope hardware multiple functions.