Air Access 18

[Brian_dk]

HI,
I just want to say a huge thank you for this update. I'm so happy that you still support this great unit! I still hope for the ability to use RTA on this unit, when out gigging. I know that it doesn't have an ocilator like the Behringer X32 but it can analyse an incoming signal and tell what frequences are bad. But besides that this program really rools!

[Tomecki]

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

[azslow3]

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

[Tomecki]

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?

[azslow3]

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.

[Tomecki]

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.

[azslow3]

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.

[jtsoundtech]

Hello, I am so grateful this project exists!!  At first I was very sad when my organization got an X-Air 18, and I worried that I wouldn't be able to mix live sound for them anymore.  But this project showed me that it is, in deed, still possible. 

I have a question though:  I would love to use an X-Touch control surface with physical faders.  Ideally, I'd love to be able to touch a fader and have NVDA report the channel name or number and current level before I move it.  I'd also love for it to confirm when I've muted or unmuted a channel.  I'd also really love to be able to control FX parameters with the control surface when I enter those pages.  Is this something that is currently possible through Air Access 18?  Would I connect the X-touch directly to the mixer, or would I connect it to the Windows laptop / tablet running AOSC and Air Access?  Would it use the Mackey protocol or would I have to do MIDI mapping?  Thanks for any insights you may have, and thanks for your work on the project. 

[azslow3]

AOSC does not support control surfaces on its own. And so AOSC can't define what you control nor reace when you just touch a fader.
The only report you can get is from Tracking mode on AOSC. When some parameter defined in AOSC is changed in the mixer, it will focus corresponding element in AOSC and your screen reader will do the trick.
So if something in X-Air is controllable by X-Touch, you will get corresponding feedback from AOSC. When you change something, not just touch. I think it should work for most parameters, but I never had X-Touch and so don't have real experience.

You connect X-Touch to X-Air. The protocol is not strictly Mackie, Behringer has designed specific approach for the combination.

AOSC Tracking is working for any changes, so you also get report from Behringer app, in case sighted mates are using it.


X32 Producer has 17 strips instead of 9 of X-Touch, so less banks switching during live mixing, apart from other advantages. And the price is not drastically higher then X-Air plus X-Touch combination. Gerad took that way.  If it is not too late, may be you can consider that as well.

[jtsoundtech]

Thank you for this clarification.  Having any changes reported from any means of controlling the mixer would still be awesome.  How does one place Air Access into tracking mode?  I'm assuming this means tracking changes to the mixer rather than "tracking" as in recording. 

I will continue to research using the X-touch with X-air to determine if it will work for our situation.  Unfortunately, the decision regarding the X-Air 18 has already been made.  It was donated to them several months ago. 

[azslow3]

There is Tracker option in the OSC menu, shortcut F4. The term comes from me and may be it is not the best, means focus tracks changes in the mixer. Sorry if there is already a good term to describe the behavior.

Don't forget to switch it off when operating AOSC since any external changes will auto-navigate throw the interface and can be confusing.