M-Audio M-Track Plus?

[canhoto]

Hi.

Does anyone have any experience with M-Audio M-Track Plus USB audio interface?

Do you hnow if it works well with Linux? It's not on the ALSA Matrix list, but it's also quite new, I think.

Thanks

[j_e_f_f_g]

It's supposed to be class-compliant, so it should work.

But frankly, unless you need midi and/or spdif, a focusrite 2i2 is a better deal.

[canhoto]

Why is it a better deal?

And the Alesis IO2 Express or IO4?

[j_e_f_f_g]

Why is it a better deal?

The M-audio fast track line are a bit noisy on the pre-amps, and output analog. The fact it tops out at 48KHz suggests a number of corners were cut on the digital side too.

And the Alesis IO2 Express or IO4?

On par with the fast tracks.

Get a 2i2 if your budget is around $125.

[canhoto]

Why is it a better deal?

The M-audio fast track line are a bit noisy on the pre-amps, and output analog. The fact it tops out at 48KHz suggests a number of corners were cut on the digital side too.

And the Alesis IO2 Express or IO4?

On par with the fast tracks.

Get a 2i2 if your budget is around $125.

I'm talking about the M-Track, which seems to be a new line, and not the Fast Track line.

[lloydburnette]

I am having M-Track 1.0.6 but it works only with Windows 7 and 8, on both 32- and 64-bit architecture.I have no idea about Linux.

[sirex]

just jumping in here for the OP.

i have an m-track plus. works just fine in linux (fedora, 64 bit).

[tatch]

I've used an M-track on ubuntu linux without any problems, but like j_e_f_f_g I would also suggest getting a 2i2 instead.

[grantubuntu]

I found that if you're using Ubuntu Studio, you may experience strange glitchey pings and audio that crashes to white noise. It can be pretty terrifying when you have your music cranked, especially when the mix is quiet, and it suddenly crashes and burns in a horrific thundering hiss.

I fixed it by appending the

Code: Select all

load-module module-udev-detect

line in the

Code: Select all

/etc/pulse/default.pa

file with "

Code: Select all

 tsched=0

" as instructed here:
https://wiki.archlinux.org/index.php/Pu ... _crackling

I think it could be an IO synchronization issue with pulse's timer-based scheduling and the M-Track.

I've yet to see a crash since editing this.