Help get this topic noticed by sharing it on Twitter, Facebook, or email.

M-Audio AIR 192 ASIO Issues

1) "M-Audio AIR 192 6 ASIO" device stops working (playback gets stuck) anytime a plugin is added to FL Studio. Sometimes the DAW doesn't even have sound on startup. Switching to a different device (directsound, asio4all) and back fixes it (until you add another plugin, of course). ASIO4ALL drivers work flawlessly - is there any disadvantage to using them? They seem to take the same amount of CPU (at buffers 64 and up) as m-audio's native ones.

2) The USB/DIRECT knob set to 100% USB produces (clipping?) clicks and distortions when using ASIO (and even ASIO4ALL), it's fine when using DirectSound devices. Setting it to about 9 o'clock (as suggested here by other users) helps, but could lead to feedback when microphones are connected, right?

3) Can the USB/DIRECT knob be set to apply only to the headphones output? What sense does it make to send mics out of the speakers? This is hardly an interface for studios with separate control rooms, every normal self-recording musician is going to want to mix mics into his headphones and listen to pure "USB" on his speakers, not feedback noises.

Similar issues described by others:
https://forum.image-line.com/viewtopi...
https://forum.image-line.com/viewtopi...
https://getsatisfaction.com/m-audio/t...
https://getsatisfaction.com/m-audio/t...

As for the solutions suggested in the other threads:
Windows: USB selective suspend set to DISABLED - doesn't help
In FL: Audio device "auto close" setting doesn't help.
Buffer sizes anywhere between 16 and 2048 make no difference
I tried USB 2.0, 3.0, 3.1 and USB-c ports. Same story.

My system: AIR drivers v1.0.3, Windows 10 Pro 64bit 1909, AsRock B450M Pro4, AMD Ryzen 1600 (12nm), 64GB DDR4

M-Audio has always been famous for bad drivers, but this interface really makes me sad - It's SO beautiful and well made mechanically, that I don't want to return it. The big knob is just fantastic quality! And yet I just spent a day trying to make it work on a rather standard PC configuration and reading through support posts claiming that:

a) the interface doesn't support AMD (a brand that absolutely dominates retail CPU sales at the moment!), a fact that (if true) NEEDS to be spelled in giant red letters on every AIR 192 page, yet is nowhere to be found.

b) it's an FL Studio issue.. yet I've been unable to reproduce it with any other interface (including RME and even m-audio's own c600 and fast track pro)

This product feels like a pre-alpha release. I honestly can't beleive it's being sold in its current state and I basically paid to be a tester. Please, please tell me I've got it wrong somehow and there's a solution for these issues before I go on making what I suspect will be the first honest youtube review of the interface so far. Sorry if I came off too harsh, I'm just a very disappointed customer right now.
2 people have
this problem
+1
Reply
  • And also sometimes I'm getting choppy playback / weird stutters a few seconds after moving in a video's timeline (especially on youtube). It immediately goes away when I switch from m-audio to my onboard soundcard and comes back when I switch back.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited

  • I've been testing the interface on two more machines today:

    a) Hp Probook 4720s, i3-380M, Intel HM57 Express, Windows 10 64bit
    The FL Studio problem is exactly the same as on my AMD machine (things like adding a plugin force you to switch audio devices, otherwise no sound and no playback movement). Other than that, it seems to work ok (although the testing session was quite short).

    b) Windows 7 64bit, i7 2600k, Asus P8Z68-V
    The interface installed ok, but all playback in Windows stuttered horribly. After restarting, any application that tries to make a sound just stops responding (winamp, media player classic, reaper when set to DirectSound and output using maudio, even the Windows sound settings!!). ASIO in Reaper & FL Studion doesn't work either. I tried different ports, USB 2 & 3, reinstalling the drivers, restarts. Nothing helped.

    I don't seem to be able to reproduce issue 2 from my original post on these machines, so maybe it was user error, I will try again soon. Issue 3 is probably not really an issue, just a reason to buy 192|8 instead of 6, right? What stands, however, is issue 1, which i've been able to reproduce on different machines. Also the interface's behavior on the i7 machine is absolutely unacceptable (it flat out doesn't work). That's my studio PC and it's had all sorts of audio interfaces connected to it over the years, yet I've never seen anything this horrible before. Any thoughts on that as well as issue 1 and maybe the weird stutters when skipping through videos?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Since this forum seems to be dead (support wise), is registering the product and contacting support directly the preffered way, even though at this point I'm very likely to return the product to the store in my two-week return period? Won't that pose a problem for me / the store / the future owner?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Back to testing on my Ryzen 1600 machine. YouTube audio (as well as media players & winamp) will get random stutters (not always, but once it starts, it happens to every video on every seek, unrelated to high CPU usage). ASIO playback (when it works) stutters/gets choppy in more instrument/effect heavy parts of the playlist, although CPU stays quite low (with other, even 15-year-old interfaces I start getting those around 95% CPU, here it's at 13-50%). M-Audio ASIO playback in FL Studio crashes (and requires switching drivers) when adding plugins and/or randomly during CPU heavier moments. Oh, and even ASIO4ALL playback is way more reliable and better performant via the onboard soundchip than the m-audio interface. Something is terribly, terribly wrong with that hardware (or its drivers, more likely).
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • I am also getting pretty much every issues above. Youtube hasnt lagged for me, but I havent really tried it.

    The most important issue is driver level on this, and its the device closing on vst load or patch change. Might be best to just return it if within return window. I just got this few days ago and not happy. My Creative EMU card from 2006 on 32bit PCI is light years ahead of this.

    You might notice your midi controllers pitch bend doesnt work in flstudio too? Mine doesn't...
    • Hey, thanks for chiming in! What's your system? Processor, motherboard, OS..? Maybe we can at least find a pattern here and help prevent other people from buying this travesty. I think the FL Studio problem is the only one we can realistically expect a solution for in the future, because FL Studio devs actually update their software - unlike m-audio, whose "latest drivers" are from October (!) despite numerous reported problems, and who even has the audacity not to warn people that it doesn't support most existing CPUs :-D For me, the device doesn't work OK on any PC I tried it with and tends to randomly produce stutters under 0 load, way, way worse than a "free" integrated soundchip.
    • I'm running an AMD 990FX system with 8350 CPU, 16GB of DDR3, & 64bit Win 7. System is MORE than capable of processing sound. ASIO4ALL seems to fix most of the issues in FLStudio for me, before my ASIO device was the audio interface itself, which had major issues. Youtube and all other general audio related things are fine.

      No pitch bend support in FLS anymore, and need to use ASIO4ALL driver instead of interface itself. That seems to help a TON! I haven't needed to use 'Auto Close', 'Mix in device buffer', or 'triple buffering' etc. since.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited

  • I’m very disappointed
    Hi. I use M-Audio AIR 192 6 and have a similar problem: get random stutters while listening to music or playing guitar. The hardware is Asus rog with AMD Ryzen 4800HS. It really seems like a drivers'' problem because, it is much better when they are deleted (but not for playing).
    I also thought that they probably do not support AMD, while I did not have such problems with intel''s processor (m7-6Y75). The system is Windows 10 in both cases
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • After my own research and now reading this thread. It seems 100% clear that M-Audio 192-4 (which is what I recently purchased) is NOT compatible with AMD Ryzen CPUs. Plain and simple. Thanks M-Audio.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited

  • This reply was removed on 2020-06-02.
    see the change log
  • I have the AIR 192|6 and an AMD CPU. I think the issue lies in samplerates and buffersizes.

    A (stupid) workaround for the stuttering when watching Youtube:

    1. Open an audio stream (e.g. internet radio) in your browser and let it stutter till it normalizes.
    2. Mute this tab while it's still playing.
    3. Now you can watch Youtube and jump back and forth, without the audio stuttering.
    4. Profit :P

    Also: setting windows and the interface to the same samplerate (44100) and lowering the interfaces buffersize via M-Audios Control Panel reduced these issues for me.

    Hope that helps anyone.

    PS: I've never had these issues with other interfaces (RME Fireface 400 or MOTU Micro Book) on Win 7. Guess the latest and greatest is not always better...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited

  • i'm having the same issues on my air/14. stutters , shutdowns , no sound. im very dissapointed and cant find any fix.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited