HI:)
 
ACT works perfect for me with my own genericpluginparams.xml
 
File DIR is C:\Users\[User]\AppData\Roaming\Cakewalk\ACT Data
 
But CbB DATA is in C:\Users\[User]\AppData\Roaming\Cakewalk\Cakewalk Core
 
I can see a ctrlsurface.dat...
 
Is this affecting the old ACT with genericpluginparams.xml?
 
How does it work in the future?  At the moment it has not changed anything for me, but it was a lot of work to get all my plugins to work proper with AZController, so what if BandLab changes this?
 
Thanks;)
 
Bassman.
 

Alexey's AZController uses the standard Cakewalk Surface API, as does everything Cakewalk provides in the Shared Surfaces folder.
 
If this were to change, it would mean rewriting all of these, which I doubt the bakers want to do at this point - bearing in mind this API hasn't really changed in a long time.
 
The only thing that could perhaps have an impact on this would be support for the new MIDI-CI specification, but I suspect that could implemented as an additional surface plugin using the existing API.
 
So I think you're probably fine for the foreseeable future.

ctrlsurface.dat always was in version specific directory, "Cakewalk Core" is just another version of Sonar, so it has its own.
I do not think they will intentionally break ACT till they completely rewrite the engine.

HI:)
 
Thank you very much for this satisfying answers! So I just keep going on:)
 
@azslow3
 
Hi Alexey:) Könntest du bitte mal kucken.... Wenn ich ein Keyboard Command auf einen Rotor lege, funktioniert "Shift" nicht, also "Ctrl+Up" geht, aber "Ctrl+Shift+Up" geht nicht, dasselbe mit "Down". Hab in deinem Forum schon geschrieben. Danke;)
 
Bassman.
 

Entschuldigen, Ich habe es vergessen..

No problem, it's not absolutely necessesary to have it;) A nice feature to have both on 1 Rotor(Enlarge All Tracks and enlarge 1 Track)
 

For the moment, I can just confirm that really does not work. I will dig into it later, probably not before Sunday.

I have replied on my forum, but just in case someone search for the topic there...
Shift+<Arrows> and some other combinations require special processing. Theoretically that should be for all <Arrows> use, but practically everything works "as is", till combinations with Shift.
Corresponding part of Sonar API has no way to specify required flags (or I have not found it), I will try to workaround using Windows API directly.