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. If that's the function, then *no* the M32 isn't going to be controlled directly by Cubase functions. In the workflow I use for punch-ins, I usually arm the track(s) for recording on-the-fly for punch-in. That arming automatically mutes the playback of existing track material. 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. The ultimate connection to a tower-based DAW machine is a Lynx AES16e-50 with its AES50 capability directly into the M32. 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. There is an article on my website that documents the latency of the M32/X32 X-USB (DN32-USB) adapter. I always worked with Cubase pro, years through a big console into 4 ADA8000 into RME ADAT card in my PC. Then after the console gave up, through USB into focusrite scarlett into PC. I can get a playback from cubase, but anyhow I am doing something wrong in the right connections, I cannot record from the M32 into cubase. Please, does anyone have here a step by step instruction here to install?īTW, I still have the RME adat card in my PC and I bought The KT m32 Adat card.

Is that a better solution? Please help me, have a lot of work to do and I can not go on. Thanks, sincerely, Johan Jansen Hey Johan, I can help. I'll cover the big steps because I'm just guessing about where you are in the installation process. Use the site > Support > Downloads and pick the Mixers > Digital > M32 > Drivers > DN32 Windows Driver.

Be your own windkeeper book amazon