I installed the 4.0 firmware in my M32 about 2 hours ago.

So far, I've run the Oblique RTL test a 44.1k, and noted that the RTL at 64 samples has risen from 5.23ms to 6.05ms in ASIO Win10 with the 4.26 X-USB driver. In macOS HiSierra the 64-sample RTL measures 7.77ms with the same 4.0 firmware.

I don't have/haven't looked for the 3.08 firmware measurements at 44.1k in both OS's, but that same 7.77ms RTL was obtained in Sierra at 48kHz sampling rate.

Perhaps more importantly, the output sample delay was 66-samples with the 4.11 driver and the 3.08 firmware using a 64 sample buffer. It's now 110 samples output delay with the 4.26 driver and the 4.00 firmware; so a whole millisecond was sacrificed somewhere. MacOS has an output sample delay of 91 samples using a 64 sample buffer, so it's probably perceived as being a very cooperative player for softsynths.

When the ambition strikes, I'll put together a complete set of numbers, or if someone wants my spreadsheet to do the homework for us all, just send me a PM.

In general. The upgrade didn't remember my network IP settings or the MIDI input port settings in the 'Remote' tab, so don't forget to check that. I think I like the new color scheme. I'll see how much closer to world peace we get now that there's the granular 1:1 routing in place.

Oh, yeah, it still plays music through it just fine.

I find it quite good. Certainly as good or better than any non boutique level usb interface would be.

All my synths are connected to my X32 rack via Art T8 isolators. I have zero noise, zero 60 cycle hum, zero ground loop noises

My Midas M32 testing has yielded some additional information; some of which seems to overturn earlier observations. The Oblique RTL Utility was used for all measurements with an XLR loopback cable from the left monitor output to input-1.

I only show results for 64-samples buffer because that's all I am concerned about right now. CoreAudio measurements were done in HiSierra; Win10 Pro 1809 with latest security updates. The 64-samples happens to also be smallest buffer setting that the 4.11 ASIO driver would list in Win10. For reference, my MADI ExpressCard/PCIe attached through the X-MADI expansion card is included.

RME MADI ExpressCard ASIO 3.09 fw...........44k 64s RTL=4.58ms
M32 USB ASIO 4.59 driver 3.09 firmware .....44k 64s RTL=5.24ms
CoreAudio M32 USB 4.0 firmware ................44k 64s RTL=7.78ms
M32 USB ASIO 4.59 driver 4.0 firmware .......44k 64s RTL=6.05ms
M32 USB ASIO 4.11 driver 3.12 firmware .....44k 64s RTL=6.49ms

RME MADI ExpressCard CoreAudio 3.09 fw....48k 64s RTL=5.31ms
M32 USB ASIO 4.11 driver 4.0 firmware .......48k 64s RTL=6.10ms
M32 USB ASIO 4.59 driver 4.0 firmware .......48k 64s RTL=5.73ms

HTH

I have a X32 question I'm hoping someone here can help me with;
I'm running the soundcard in 32 in 8 out mode. I only want 2 (maybe 4) outputs running back into the desk just so I dont have to switch soundcards between recording hardware and listening back to the recording. As far as I can see I have to make a block of 8 outputs take up channels 25 - 32. This is a problem as I already have 25 analogue inputs. Is there a way to route the card outputs to mix buses only? The only other routing I can see is the Aux ins, which is also a problem as Im using all 6 as FX send/returns

An update to my own question for others looking at using the X family for synth/ studio recording:

I can route the USB interface straight to outputs, which is fine to run into my Mackie Bigknob to monitor what Ive recorded. I hope I can route 4 outputs through the interface so I can use Ominsphere whilst making music and record it into Cubase with all the other hardware layers. Thinking further... I guess I can run the USB straight to outputs, then back into 2 or 4 channel inputs and into the DAW. Thats just 4 more XLR cables.

Yes, major game changer right there!

Now the X32 will almost surely be the replacement for all the analog mixing in my studio.

A handy tip, if I am understanding what you are looking for

In addition to the regular ins and outs, you also have an entire input and output matrix dedicated to the P16 personal monitor

Since most studio studio setups are not using the P16 this allows you the ability to send whatever you wish to the P16 slots 1-16 and then have those route back to the USB outs regardless of how your physical outs are set and what is driving them

It's talked about towards the end of this video

fantastic enjoy

Any particular reason you went with rack + x-touch vs. just the standard X32 console?

Space. The Standard X32 is pretty big compared with the X-touch

Factor in all the audio cables and it's a huge mess

Most of my gear is rack mount so all the audio cables are hidden

Has anyone used any of the advanced OSC features of the X32?

In particular, I'd like to hear about anyone's experience managing the point-to-point routing using the remote control protocol (OSC).

I have messed around with it

What exactly are you trying to do?

As far as routing goes any cheap Android Device or Windows PC will run the Behringer App and routing on the app is dead simple and all or part of it can be saved. I am not sure why you would want to mess around with OSC for that

The PC or tablet doesn't even need to be connected to the mixer to do routings

The X32 is also very controllable via MIDI using CCs. I do that all the time using my sequencer even to sequence various things like Panning on the mixer

In fact devices like the Novation SL Remote Zero MKII are FANTASTIC with it since you can easily program the buttons, faders and knobs to output whatever CCs you want.

You've pretty much anticipated my needs. Mainly looking at getting the rack version and trying to use some control surface (or combination of surfaces) to control it. Don't really want a "giant" mixing desk in the studio if I can help it. Would also be nice to allocate channel strips only to active gear currently in use. Since I'll be using both AES50 buses to get everything plugged in, I'm anticipating being in the routing setup screen quite a bit in order to keep my channel strips active on whatever gear is actually in use. Wonder if that might be automatable but it sounds like it is easy enough to just manually make that patch.

Are you going to use more than 32 inputs? For example cascading multiple SD16 and then selecting which to drive to what inputs?

Or are you just going to use up to 32 inputs or less

If 32 or less you can just use MIDI to mute or unmute channels, panning, levels etc and have your DAW or Sequencer spit that out at the beginning of each track

If you are doing more complex things just save everything as a preset and launch it either remotely or via the unit itself

I HIGHLY RECCOMEND getting an X-Touch as its not super huge and when you save your settings in the X32 it also saves the X-Touch settings, including the Scribble Strips which are super handy

I'll be cascading multiple SD16 units in addition to the on-board inputs. So I'm anticipating having to do a bit of routing.

It would be nice to be able to send a message to the X32 that says, "Put the MC-707 on channel strips 6 & 7 and show 'MC-707' in the scribble strips and set the background color to blue" rather than having to manually look up the input numbers and bus and assign them to the channel strips and make all those settings. This is just a minor workflow dream, although from analyzing the OCR protocol it seems doable.

You actually can quite easily using Snippets

When you save a scene it saves everything, every parameter on the board to a file

Snippets on the other hand just save a smaller group of parameters

You would manually have to set up the part of the board you want to save as a snippet then save it as a snippet its actually quite easily do

There is a software called Qlab that allows you trigger the snippets with MIDI commands

Other than the potential phantom power risk, what are the issues in connecting unbalanced synths directly to the X32 using over-the-counter TS-XLR cables, assuming a maximum length of 1m per cable? A scenario would be a lot of rack synths standing just next to the X32.

Use a XLR-TRS cable. If the synth has a balanced output, it will utilize the balanced line. If not, one side will short to ground and the X32 will handle the unbalanced signal just fine. Mind your synth's output volume and the X32's gain to minimize distortion: highest volume setting on synth, lowest gain setting on X32 to maintain a clean signal.

There may be some edge cases where you might need a DI but so far I've been patching gear into my X32 without issue using XLR-TRS cables.

Controlling the X32 via MIDI is very straightforward and I really like the OSC protocol because you just have to do basic string manipulation to build up commands.

You can send an OSC string over MIDI by ASCII-encoding it and wrapping it in a standard sysex header. The unofficial X32 OSC protocol document explains how to do this.

That document explains all the OSC strings. But, there is a ton of them so knowing where to start can be overwhelming. What I do is fire up X-32 Edit software in offline mode and initialize with a default scene. Then I make the change I'm interested in, and save it as a new scene file. Then I use Notepad++ to compare the base scene file and the new scene file. That will give you an exact OSC string to do whatever you need. If you need to tweak it, you can read more about the exact format and parameters in the protocol document.

Don't forget to enable "OSC over MIDI Sysex" in the Setup menu.

Thanks, great tip. Just tested.
How do you convert the OSC string to MIDI ASCII?

I also looked at the OSC protocol once and didn't quite understand the syntax.

best regards

You can use an online tool to do the conversion:
https://onlinestringtools.com/convert-string-to-ascii

Be sure to select "Hexadecimal Ascii" in the "Output Format" selector. Then, just paste in your OSC string in left box and you'll get the ASCII encoded version in the right box.

So if you paste in:

(This would turn the Input 1 strip to green and label it 'Test 01' with a keyboard icon)

You'd get these bytes:
Next, you need to add the sysex headers:
Send the above using your favorite MIDI tool or DAW to the X32's Midi input.

This is a very manual process but is fine for static strings. If you are doing something more dynamic, you'll have to write some code in your programming language of choice. My studio automation/control software is written in Node JS so I wrote a simple routine to convert my OSC strings to a MIDI byte array:

Hope that helps!