Using AZ Controller for Cakewalk control of external audio mixer

[azslow3]

I don't know about "Record" State Set. You need to monitor "Transport" state and construct sent values yourself. State monitors don't provide distinct Values.

[norfolkmastering]

Hello Alexey

Thanks for your guidance.  I got confused!

Yes I can monitor Transport state and it conveniently outputs three values as follows:

STOP 0
PLAY 40
REC PLAY 7F

This is fine for my needs.

Best regards
Robert

[norfolkmastering]

Hello Alexey

I am working on controlling the flow of MIDI messages between Cakewalk/AZ Controller and my PIC microcontrollers when both systems are launched.

Can I please ask two questions:

1. When a Cakewalk project is opened, is there any way for AZ Controller to 'handshake' with an external MIDI controller?
So I mean either:

a. AZ Controller responds to a SYSEX type message and sends out some kind of acknowledgement
b. AZ Controller sends out a SYSEX type message when a Cakewalk project is loaded.

2. Currently, when I start Cakewalk, I am getting a small stream of MIDI messages, even when I have no controller loaded in Cakewalk/preferences/controllers (and before a project is loaded).
Are you aware of any default messages which Cakewalk sends out?
I have attached an image of the messages which are being outputted from Cakewalk.  They seem to be consistent in content each time the Cakewalk application is started.

Best regards

Robert

[Bassman]

Hi

I think Cakewalk do "Reset all Controllers" on startup. If it is activated in the preferences it does reset on Stopp  normally.

Bassman.

[azslow3]

1. AZ Controller can do event/time based activity in "Monitor"s. There is "Context" state set, which has "NoProject" state. You can organize state monitoring for it and update some defined by you state set, f.e. "Project" with states "Not Loaded"/"Loaded". Then using conditions update that set so it match the reality. Finally, you can monitor "Project" set and send something.

For initial handshake,  you can use timer based monitor conditioned with "Initialized" ("Yes"/"No") set, so it send something let say once per second till it gets expected response. For an example check build-in "Mack. Control" preset.

2. As Bassman has mentioned, Cakewalk sends some resets to all MIDI ports. You can set "Block all channel messages" + "Block all SysEx" in AZ Controller Options to prevent that for particular port (if you don't want disable these messages globally, f.e. you use some hardware MIDI synth). But something still can leak in case AZ Controller / Preset are not leaded yet at the time Cakewalk sends these messages (should not happened in practice...).