Home Recording

M-Track Solo Drivers: Windows Install, Mac Setup, and Fixing Crackle

M-Track Solo Drivers: Windows Install, Mac Setup, and Fixing Crackle

By Mike · Published October 11, 2026

The M-Audio M-Track Solo is simple to use once the driver situation is sorted, and most problems people report trace back to that one step. The short version: on a Mac you install nothing, and on Windows you install M-Audio's driver before you plug the interface in. Everything below comes from the M-Audio M-Track Solo user guide unless it says otherwise.

Mac: no driver needed

The M-Audio guide states that no driver installation is needed for class-compliant operation with the M-Track Solo. Plug it in, choose it as the input and output device in your recording software or in the system sound settings, and you are done.

Windows: install the driver first

On Windows the guide tells you to install the drivers before connecting the M-Track Solo to your computer, and it points to m-audio.com/drivers for the download. Follow that order rather than plugging it in first.

Once the driver is installed and the interface is connected, your recording software should list it as an ASIO device. In the M-Audio guide the entry is called "M-Track Solo and Duo ASIO". In your DAW, set the audio device type to ASIO and choose that device. ASIO is the low-latency path for recording on Windows, so if your DAW is set to something like MME or DirectSound, switch it.

The guide also says the default Windows playback and recording format should be 2-channel, 16-bit, 48000 Hz, which Windows labels "Studio Quality". If you change the device sample rate in Windows and your DAW is set to a different one, you can get errors or distorted audio, so keep the two matched.

Do I need Focusrite drivers?

No. This comes up in searches because the Focusrite Scarlett Solo is the interface everyone compares the M-Track Solo to. Focusrite's software (Focusrite Control 2 for the 4th generation) manages Focusrite interfaces. The M-Track Solo is an M-Audio product and uses M-Audio's driver on Windows or no driver at all on a Mac. If you install Focusrite software for a Scarlett you also own, it will not do anything for an M-Track.

When it crackles, pops or lags

The M-Audio guide does not give latency or buffer advice, so these are standard audio troubleshooting steps rather than anything specific to the M-Track Solo. They fix most crackle on any budget interface:

Raise the buffer size. In your DAW's audio settings, increase the buffer (try 256 or 512 samples). A larger buffer is more tolerant and adds a little latency. Lower it again once the crackle is gone, as far as it stays clean.

Use a direct USB port. The M-Track Solo is bus powered and needs a USB 2.0 connection or higher. Plug it straight into the computer, not into a hub or a front-panel extension, and try a different port if the problem continues.

Close competing audio apps. Browsers, video calls and streaming apps can grab the same device or add load. Close them while recording.

Check your sample rate and driver choice. A DAW on the wrong driver type (not ASIO) or a mismatched sample rate are common causes of crackle on Windows. Re-check the two settings above.

If what you are hearing is a steady hum or buzz rather than crackle or dropouts, that is a different problem. See our guide to ground loops and noise in a home studio.

iPhone and iPad

The guide notes that iOS devices can't supply enough power for the M-Track Solo, so an iPhone or iPad needs a separate powered USB adapter between it and the interface.

If it still isn't working

If you have installed the driver, matched your settings and tried another port and it still misbehaves, the interface or the cable may be the issue. At this price, replacing the interface is sometimes cheaper than hours of troubleshooting. Our Scarlett Solo vs M-Track Solo comparison covers when stepping up makes sense, and the three-way budget interface comparison puts the M-Track next to the Behringer UMC22 as well.

Share this: X Facebook Reddit Email
About the author: Mike has been running MusicWide since 2004, back when getting your music heard meant burning CDs and mailing press kits. He writes about getting your music released, heard and paid for, without a label.