Choosing programs of the Oasys by name will be your smallest problem
Patch name scripts, whilst taking a decent amount of effort to produce, do not constitute integration and rather assume you never change your Programs. Or never create your own Programs.
So true! And definitely a big nuisance.
And to add another missed "integration" opportunity: While setting up the OASYS as an "External Controller" for DAW mixing functions in SONAR was quick and easy via ACT, I was *not* able to set it up to control Logic in a similar fashion, since there is currently no "driver/adaptation" for the OASYS in Logic. (I tried hacking the nanoKONTROL one with random results, and eventually abandoned the idea of using the O as a control surface.)
And while there are plenty of spots to save external control setups, not being able to "name" those settings is another miss.
Just to further reiterate what's been said here. As a self-contained system, the OASYS is great, although somewhat crippled by the archaic sequencer. Although perfectly workable, it just doesn't have the convenience of workflow or ease of use of the more full-featured visual DAWs. I think Charlie stated it plainly that when it comes to DAWs, "your Oasys will always look like an 'outsider'". I'm pretty happy with my own OASYS and Logic setup, and most projects are still a 50-50 use of O and software, with only a few other hardware components added to the mix as necessary. If it weren't for the sound quality of the O and its "Limited Edition" status, I might be more frustrated by the O as well as Daz has found. I've found the best way to make it work for me, but I can also certainly sympathize with those who are annoyed with their OASYSes feeling like "outsiders".