M-Audio FastTrack Ultra and Jack/ALSA

Talk about your MIDI interfaces, microphones, keyboards...

Moderators: khz, MattKingUSA

Posts: 1
Joined: Tue Jan 19, 2010 4:48 pm

Re: M-Audio FastTrack Ultra and Jack/ALSA

Post by Jeol »

I'm dying to know what is to be expected to work and what isn't. Could you who have it working tell if there still are any issues left?

Kind regards, Joel
User avatar
Established Member
Posts: 1737
Joined: Wed Dec 09, 2009 5:26 pm
Location: Beverwijk, The Netherlands

Re: M-Audio FastTrack Ultra and Jack/ALSA

Post by autostatic »

I would strongly advise against upgrading ALSA this way on Ubuntu, especially with options like --with-cards=all. If things go wrong you'll have no sound at all and you probably won't get it back either unless you know what you're doing.
User avatar
Established Member
Posts: 1766
Joined: Tue Apr 08, 2008 11:58 am
Location: Deventer, NL

Re: M-Audio FastTrack Ultra and Jack/ALSA

Post by raboof »

Is there any particular reason these patches haven't made it upstream yet?
Established Member
Posts: 5
Joined: Mon Jan 11, 2010 6:31 pm
Location: Italy

Re: M-Audio FastTrack Ultra and Jack/ALSA

Post by salvoinzk »

Hi you all

it seems that a french guy was able to make work the Fast Track Ultra (= FTU)

I don't understand the french language but, it seems, he applied the previous patch to the kernel and then recompiled it again, and now the FTU works.

here is the link:
http://www.linuxmao.org/tikiwiki/tiki-v ... ntId=16414

hope this help!

ps: here the english translation of the above site:
http://translate.google.com/translate?j ... auto&tl=en

Posts: 2
Joined: Wed Aug 26, 2009 8:50 pm
Location: Prague, CZ

Re: M-Audio FastTrack Ultra and Jack/ALSA

Post by _pedro_ »

Hi, musicians!,

in kernel 3.x there is support for FastTrack Ultra. Also there is support for the internal mixer. 128 faders :-). AnalogIn(1-8)->AnalogOut(1-8) and DigitalIn(1-8)->AnalogOut(1-8). Probably, still is not possible to control internal DSP effects and switch clock source to S/PDIF.

Posts: 1
Joined: Sun Dec 16, 2012 1:43 am

Re: M-Audio FastTrack Ultra and Jack/ALSA

Post by araoua »


Mod: Please do not post your e-mail address. And you can find the patch here: http://joegiampaoli.blogspot.nl/2011/06 ... linux.html
Posts: 2
Joined: Sun Feb 26, 2017 11:03 pm

Re: M-Audio FastTrack Ultra and Jack/ALSA

Post by mfares07 »

Hello ! did anyone solve it ?
I tried apply this patch....

Code: Select all

The MIDI interface is class compliant, and this is what's shown by Jack.
The audio interfaces are marked as vendor specific, so the driver needs
to be changed to support them.

Please try recompiling your kernel with the patch below.

Some M-Audio devices use big-endian samples, so beware of speaker-
killing noise.

It's possible that playback synchronization doesn't work completely.

Please check what happens when you try to play and record with different
sample rates.


--- linux/sound/usb/usbaudio.c
+++ linux/sound/usb/usbaudio.c
@@ -2235,6 +2235,10 @@ static void init_substream(struct snd_us
                case USB_ID(0x041e, 0x3f0a): /* E-Mu Tracker Pre */
                        subs->ops.retire_sync = retire_playback_sync_urb_hs_emu;
+               case USB_ID(0x0763, 0x2080): /* M-Audio Fast Track Ultra */
+                       subs->ops.prepare_sync = prepare_playback_sync_urb;
+                       subs->ops.retire_sync = retire_playback_sync_urb;
+                       break;
        snd_pcm_set_ops(as->pcm, stream,
@@ -2786,6 +2790,7 @@ static int parse_audio_endpoints(struct 
                case USB_ID(0x041e, 0x3020): /* Creative SB Audigy 2 NX */
                case USB_ID(0x0763, 0x2003): /* M-Audio Audiophile USB */
+               case USB_ID(0x0763, 0x2080): /* M-Audio Fast Track Ultra */
                        /* doesn't set the sample rate attribute, but supports it */
                        fp->attributes |= EP_CS_ATTR_SAMPLE_RATE;
--- linux/sound/usb/usbquirks.h
+++ linux/sound/usb/usbquirks.h
@@ -1864,6 +1864,33 @@
+       USB_DEVICE_VENDOR_SPEC(0x0763, 0x2080),
+       .driver_info = (unsigned long) & (const struct snd_usb_audio_quirk) {
+               /* .vendor_name = "M-Audio", */
+               /* .product_name = "Fast Track Ultra", */
+               .ifnum = QUIRK_ANY_INTERFACE,
+               .type = QUIRK_COMPOSITE,
+               .data = & (const struct snd_usb_audio_quirk[]) {
+                       {
+                               .ifnum = 0,
+                               .type = QUIRK_IGNORE_INTERFACE
+                       },
+                       {
+                               .ifnum = 1,
+                               .type = QUIRK_AUDIO_STANDARD_INTERFACE
+                       },
+                       {
+                               .ifnum = 2,
+                               .type = QUIRK_AUDIO_STANDARD_INTERFACE
+                       },
+                       /* interface 3 (MIDI) is standard compliant */
+                       {
+                               .ifnum = -1
+                       }
+               }
+       }
 /* Casio devices */
But i got these errors:

Hunk #1 FAILED at 2235.
Hunk #2 FAILED at 2786.
2 out of 2 hunks FAILED -- saving rejects to file usbaudio.c.rej
patching file usbquirks.h
Hunk #1 succeeded at 1818 with fuzz 2 (offset -46 lines).

Maybe if anyone help me step to step to recompile the kernel (because i read it got many errors for many people) i would be so grateful !
Thank you !
Established Member
Posts: 13
Joined: Fri Jul 31, 2015 8:27 pm
Location: California, US

Re: M-Audio FastTrack Ultra and Jack/ALSA

Post by AyeLinux »

My FTU worked "out-of-the-box" with 14.04. Audio for sure. MIDI ports show up, and I think I might have tested it once (I don't really use MIDI).

The only "special" thing I had to do was open an ALSA mixer (CLI or GUI both work) and make sure that each physical input was turned all the way up for its corresponding USB output, and all the way down for the other USB outputs. Also, all the physical ins to physical outs should be down all the way. The device remembers these settings, so you only have to do this once. All of the routing is available, including effects, etc. If you got it used, check the rest of the routing, too - you don't want unexpected reverb. The internal routing is nice for latency-free monitoring, too.
All in favor of Linux, say 'aye.'
Post Reply