

The MADI-PCIe-to-X-MADI and the PCIe-Dante-to-X-Dante completes the trifecta of truly low-latency connections from the DAW to the M32. The ultimate connection to a tower-based DAW machine is a Lynx AES16e-50 with its AES50 capability directly into the M32. Headphone mix effects (EQ/compression/reverb, usually) are supplied via the M32 effects, so there are no latency issues in that arena.Īlso, the ASIO drivers have been solid, but the general latency available isn't inspiring for soft-synth users. That arming automatically mutes the playback of existing track material.

In the workflow I use for punch-ins, I usually arm the track(s) for recording on-the-fly for punch-in. If that's the function, then *no* the M32 isn't going to be controlled directly by Cubase functions. I suppose that the Cubase Direct Monitoring process is managing the muting of previously recorded tracks as punch-in's are added, and is allowing direct hardware control of headphone mixes via the Cubase software. I'm not a Cubase user, but I do use an M32 as the center of my studio. Nobody at all?I guess it's mighty quiet out there on this Direct-Monitoring process in Cubase. Studer to rme madiface xt to nuendo here. Thanks!!!in my experience, manufacturers of desks seem not to care much about drivers so i'd use an aes50 to aes10 converter and get an rme interface.ĭante could be less expensive dunno about midas'/klark's converters though ('cause i mostly gave up on any brand which went over to the dark side of evil b.). I have a Mac Late 2010 3.4GHz Intel Xeon for all you people who will ask my about my computer’s guts. If this has been an issue for anyone, PLEASE let me know, because this is my deciding factor before buying the M32. The option for it is literally greyed out if it’s not available. If interfaces, like Apollo twin and focusrite scarlett, have built in monitoring, the DAW won’t allow it’s proprietary direct monitoring to work.

Some interfaces don’t allow for the internal direct monitoring of Cubase to be active, while others do. My only question is, does the built in USB interface of the M32 work seemlessly with Cubase Pro? It’s my main DAW of choice. I’ve used it for live shows multiple times and love the clean pristine sound! It has tons of inputs and enough outputs for band mixes. I’ve been looking at the Midas M32 as the centerpiece and interface for my studio. I’m a professional engineer/producer that is looking to upgrade my studio gear to fill my growing need of recording inputs.
