An equaly dumb question

[Wookiee]

I presume, which is always a tricky one I need to work though a preset adding all the controls I require.

i.e all my faders pan controls and any other bits specific to that preset.

Please forgive my alien stupidity but I am furry on the inside as well 

[azslow3]

Yes, AZC has no idea which controls you have. So you should define all of them, one by one.

Note that I speak about hardware control definition in the Options Tab ("<New control>", type the name, select the type, "Save") and then assign MIDI to all of them in the Hardware Tab (touch the control, select it, "Attach", "Assign MIDI"). I guess it can take up to 10-15 minutes for surface with 50 controls, if you do this for the first time...

Complicated configurations for encoders and sliders can be copy/pasted, as explained in the tutorial.

Sure, you should plan like several hours for ACT MIDI and more for complicated cases. Mackie Control took already like a week for me and I am not done yet (but I do that in program, not in the interface). But you can get the configuration you want, something not possible with any other plug-in.

[Wookiee]

Cheers you confirmed what I thought now I can have a fun  moment configuring it.

Just as a thought have you planned to have a library of configs that could be download or upload for peeps to try?

[azslow3]

You are welcome to contribute... The configuration is saved as a preset. SONAR Plug-ins Manager is a good tool to work with these presets.

I am working to provide MCU preset. May be later I write a wizard  to generate ACT MIDI preset for X sliders,Y encoders and Z buttons. But you should look at this plug-in from another angle. Unlike other approaches, where you can change several settings at most, that is like SONAR for making music. Does it make sense to prepare "a library with SONAR projects"? As examples yes, but even than they should be like tutorials.

AZC is an interpreter for specific visual programming language. Like Web Browser for HTML/JavaScript, Excel for Basic and SONAR for CAL, AZC interpret Control Surface Definitions. The result can be MCU, VS-XXX, Automap, ACT MIDI as well as anything else someone program into it.

I have done my best to provide a way for not programmers be able to write these programs. Not sure I was successful with that...

[Wookiee]

Cheers for update I intend to have an in depth play today see what I can come up with.