AZSlow

Hi. I would like to try to create a tool that monitors and announces with sound or speech various events from the Mr18 and probably also the X-air18 mixers. I'm not a programmer and I use GPT Chat. The idea is this: we are not always 100% sure when we press a button. A finger may slip, a hand may shake, something may be pressed accidentally, etc. In live or radio performance situations, feedback is extremely important. I found a library that supports X-Air mixers and I think a few others. It can be found at https://github.com/onyx-and-iris/xair-api-python and it seems to work. I have several problems. First of all, it seems to me that in order to monitor the status of anything in the mixer, I have to query the device for each piece of information separately, and from time to time. Is there a way for the mixer to send information about changes itself so that you don't have to ask it about it every now and then? However, if this is the only way, maybe it is possible to send a query that causes the mixer to return the state of everything, so as not to send, for example, every half a second dozens if not hundreds of queries about the state of each fader, mute, solo and several other things. I don't know if I will be able to do it at all, because, as I have already written, I am not a programmer. It is true that the first steps are already behind me. I managed to write a simple script in Python that monitors the fader from channel 1 and announces its volume in such a way that 0db is a4 and every 1db the pitch changes by a semitone. Additionally, each half-decibel is signaled by a sound that is twice as short.

How you connect the mixer? I mean wifi or ethernet, throw router or directly? I remember we had quite some performance issues on WiFi, which was triggering timeouts.

I only have access to XR12 and even that is not in my room. Gerad no longer has XR18, it has upgraded to X32. I mean I can investigate problems and eventually fix, but that
will take quite some time and effort. Probably by connecting to you remotely and checking what is going on. And so if you can check yourself, that will be way faster.

AOSC is working by sending OSC messages, like in Debugger dialog. Scenes form what I remember are send not one by one, so with a bit different communication. The text file x.sct
define what to collect as a scene. So the first thing to check if scene file, also just text, has reasonable information about failing parameter.

I have debugging version of AOSC which write detailed log about what is going on, that will be the next step to troubleshoot.

Ok, thanks so much.

I tried clicking on everything possible in the table with files to download, but unfortunately it didn't help. I also tried to expand the "software" link on the product page, but also without success. Axes hammer and looking at the source of the page didn't help me either.

It looks like it's working. I tested a few things and it's basically ok, except that the send gain is adjusted in steps of 0.25db instead of 0.1db, which makes changing by 1 step difficult because the mixer updates the value very quickly to the closest possible one. Another thing is that after sending the /info command, it showed version v0.04, so it is probably very old, if it is the same as the firmware version. In theory, you can download firmware 1.22 on the website, but I was unable to do so. There is a blank line instead of the "download" link. Moreover, it would be useful to be able to check the version without entering the /info command manually.