AZSlow

I started to work on integration of TASCAM DM24 console with Cakewalk.
I was hoping I can do this with AZ controller.
The DM24 uses MMC protocol for transport controls.
Simple commamnds like PLAY or STOP are not a problem.
However, I am struggling to implement track RECORD ARMING command.
The MMC command for this uses bitmap to identify track that should be armed for recording.
DM24 also awaits response from Cakewalk that the command was successful, such response is a MMC response, and part of it is the same bitmap as in the MMC command.

How do I:

1. Interpret the bitmap so that I can REC enable corresponding tracks in Cakewalk?
2. Send the same bitmap back to the DM24 console?
3. Construct and send to the DM24 new bitmap if user changes the rec enable status of a track using mouse in Cakewalk?

MMC messages are just SysEx messages.
I could use the SysEx action in the Logic tab,
but I need to construct the message based on the previous state of the bitmap.

Also, how do I define action when a user changes track enable status in Cakewalk?
I need to catch such event, update the remembered track bitmap, and again construct a SysEx message using that bitmap and send it to the controller.

For this I would need some variables to store the bitmap, som math functions to modify it,
and some way to include the variables in the outgoin SysEx messages.

Is this somehow possible?
If not, any other idea how to implement track arming functionality with MMC protocol?

Thank you very much

Apologies for the delay - I have finally done some more testing on conversion of projects using different clock settings in Cakewalk. So far projects using 240, 480, 960, 168, and 216 ticks per quarter note all convert fine with no timing issues. This is great news!

You have probably misunderstood my comment. I have absolutely nothing against competition to AZAOSC. I also can consider extending AZAOSC if you have good proposals. My point was different. Implementing any part of AZAOSC functionality is not one minute job, people may get such imagination based on the size of the executable and simplicity of using it.

I don't want to duplicate the capabilities of your program. It would be unnecessary work. I plan to make a simpler tool that won't compete with AZAOSC. I know the documentation for these mixers and I know that their automatic detection is not related to OSC.

Flags are internal for my OSC implementation. 393216 is really 0x60000 with meaning that program is a client to one peer and only one message per OSC packet should be sent. Outside AZAOSC that number has no meaning.

There is X32 OSC protocol unofficial documentation in PDF format, which you can find in Google. Works for XAir as well, with several exceptions in details.

Device discovery is Behringer mixers specific, not just OSC feature. Unrelated to the rest.

I don't know your background skills. Sending OSC request and getting mixer value is something anyone with minimal programming skills can manage. Recreating all features of AZAOSC requires way more knowledge and time.

Ok, I thought it was a bug, not a feature.
By the way, I wanted to ask about how to connect to x-air. I plan to create a small tool for reporting several values ��sent by the mixer using sounds. I'm wondering about the following line in the xml file:
<osc inport=10023 outport=10024 flags=393216 peer="192.168.1.24" enabled="yes"/>
I haven't found an explanation of these flags anywhere, nor a way to automatically find a device on the network. Can you suggest something?

This thread is about Air Access 18, the zip contains corresponding files. But you need AZAOSC v2 to use them, from https://www.azslow.com/index.php?action=downloads;sa=downfile&id=82 to use

In first post the zip file does not contains exe file.

Current versions works in REAPER only. 

Is this just targeted for reaper only? Or is there an add on for other online studios too?