AZSlow

Hello Kevin,

This board is for AZ Controller, so after a while I will move the thread to AOSC board. But for the moment lets continue here.

AOSC is not the only accessible solution available. You can check alternatives for a possibility to do something AOSC can't. https://sites.google.com/site/patrickmaillot/x32
Some of these utilities also work on Apple. Especially note X32 emulator there. It really can imitate X32, I was using it during development since I never had real X32. And these projects are open source.

Once you have something loaded into real X32 or its emulator, you can save relevant sections as AOSC native presets. They are not the same for XAir, even for the same sections, so can't be used directly. But format is the same and all AOSC presets are text files. So theoretically, in case some page for XAir is close to related page in X32, text parser can be written. But I doubt such effort is simpler then manual recreating relevant settings.

I don't have Mac and so I don't and can't develop anything for it at the moment. AOSC is closed source program, sorry. I have developed it to be used for free, but not as open source. So it can't be a basis for other developers.

Good morning. I am a relatively new user to X Air access and am loving it.
A couple of thoughts and questions.
It would be fantastic to be able to load a sceen into the x32 version of this without a mixer plugged in so I could see channels and settings that I might be able to paste into  an X18 instance.
I have tons of presets that I've purchased from the x32 side, and I want to be able to cut them down to fit the parameters of the x18.
Is this were the sceen parser comes in?
What is the best way to somehow import .CHN files and convert them to your native presets so I can browse through them and load different channel, eq, and fx presets that were originally for an x32. .
My appologies if this is in the wrong forum, but since I'm wondering if there is a way to make it possible to load sceens offline, I thought I'd put it here to get some discussion going.
Also, if I wanted to hire a programmer to port this over to Mac, what might that look like. We really need a mac option for this because it's brilliant, and I'm willing to pay.

Thanks so much for any help you might be able to provide.

Kevin

Hello, have you tested with the newest version (91)

I don't think AZ Controller or other Sonar Surface API tool can help.

Sonar API is control surfaces oriented. It can filter incoming MIDI traffic with reasonable granularity, to avoid controls assigned for surface operations "leak" as normal MIDI messages into MIDI tracks. For MIDI output (and that is your case) from what I remember the possibilities are zero. The idea behind is to use device with just one MIDI port as normal MIDI input and surface. There is no such problem with output. While "control surface + MIDI keyboard" combination is common, I can't remember a single "control surface + synth" device.
Also there is "omni input" but no "omni output".

But even in case you somehow block what "song #2" sends on load. Before you play it, you want all that information is sent. So you need:
a) convince Sonar to re-send it at your will or
b) a program which can accumulate it  ("send suspended" state) and then play ("send resumed").
The first option is simpler to deal with, you just need to "block" before loading "song #2" and "unblock + sonar resend" before playing it.

I propose you ask on Cakewalk forum: https://discuss.cakewalk.com/
Don't write "Sonar X3", write just "Sonar". If you get some ideas for "new" Sonar, with high probability they will work for X3 as well  Noel and Mark are reading the forum. They know Sonar and they are smart.

---

If nothing from that is possible, you can re-work songs to avoid sending setup till you start playback. You can put all MIDI track options as explicit MIDI events (and deactivate every track control, if you ever touched it, f.e. 'Chorus', it is auto-activated and will send messages), explicitly send required SysEx / Bank changes / etc. Don't forget to unset "reset controllers on stop" in Preferences/Project/MIDI

That is also "future safe" approach. In case you ever change the DAW, copy MIDI with all related initialization will work (as long the DAW really support MIDI, not every DAW does that these days...) while related "in-daw" options may be significantly different (or not exist).

I posted this question on reddit and a helpful individual suggested I post it here.

We use sonar X3 and recently switched to a 2 laptop setup that both feed the same Motif rack for the midi sounds. When laptop #1 is playing song A and we load up song B on laptop #2 (to get it ready to play when song #1 ends), sonar sends the program change, volume, etc. info for song #2 and screws up song #1. In other words, as song #1 is playing through the motif, when song #2 is loaded (not started/playing) it sends all the midi commands to the motif.

Would AZ controller help us in any way? I opened up the documentation but nothing immediately jumped out at me.

Sorry it took so long. I have done a quick check under 2025.2 and it works as expected. I have uploaded version with modified manifest.
I wish some user could do compatibility tests when new NVDA version appears and report most overlays are or are not broken. For known reason, I am not using this software for myself, till something is incompatible in general, I will not notice problems during quick checks I do.

I have managed to check. In 1.9.0 OSC compatibility mode everything is working as expected.

The latest driver 1.276, from 9.7.25
Totalmix 1.99, was installed with this driver

So install the latest.

Got it, so if I'm understanding correctly the way things stand now, it makes sense at present to get 1.9.5 of TotalMix installed on the primary machine. Does 1.9.5 need a 1.9.0 fallback mode for OSC enabled, or is that a 1.9.6 addition that, even wen enabled, causes problems when routing or switching outputs?

I am not able to test compatibility with the latest RME driver till the middle of the next week.

Just to confirm: Driver version 1.95, not 1.96, is still the best way to access the full range of capabilities for the Babyface ProFS that AZOSC has to offer? I saw the post about 1.96's brokenness and wanted to ensure I did not install it if such was the case. New Babyface ProFS is arriving any day now. I'd be ok experimenting as I do have a second computer that I can easily install 1.96 on that has no intentions of being a DAW computer. So if the xml can in fact be modified for 1.96, is RME still approachable for getting updated OSC command sets?