M-audio Sound Card Drivers Free Download
Thora Buckner
I installed Ubuntu studio and tried to make it recognize the audio card m-audio 2496. My efforts caused me to lose my system and now I've done a fresh install and was wondering how I should make the system recognize this card the right way.
I recently bought a Steinberg UR22 mkII, and installed the Cubase AI bundle that came with it. I am currently using WIndows 10, Cubase LE AI Elements 9.5.30, and the latest sound card drivers from Steinberg.
The only thing I can think of that I did before this problem began, was starting a cubase project without the sound card connected. I got a few error messages regarding audio channel routing. I simply pressed cancel and closed Cubase.
Update:
I found drivers named Generic low latency ASIO driver in a Steinberg folder in the start menu. I uninstalled it and that seems to have resolved the issue. Now every time I start the UR22 is correctly set as my audio device.
Nobody knows the exact number because these days almost all USB audio interfaces are class compliant, so they have no specific driver. Any company can bring out a new USB audio device and (assuming it is class compliant) it just works. It could be a totally new device from a totally new company or a minor variation of an existing device.
Do you have a particular audio interface you are looking to use in Ardour? I use Behringer UMC series, an old M-Audio 192 PCI card and most recently an Audient iD44. Everything works out of the box save for the ADAT optical connections on the iD44.
The rule of thumb for USB devices is if it is supported on iPhone / Android then it is USB Class compliant and works in Linux. Also if the device is supported on macOs but there is no driver download on the manufactures site, then the device is probably USB Class Compliant and works in Linux.
For audio in particular, there are zero closed source drivers on Linux. Unless you insist on building your own kernels and deliberately using non-maintained, out-of-kernel drivers from some non-conformant manufacturers. Essentially nobody does that.
If and when I come across an issue in Windows I work through the various Focusrite/Pyramix and other guides for optimizing Win10. On Linux, choosing a low-latency or realtime kernel often is all that is needed along with appropriate buffer settings in ALSA/Jack.
The important here is that you almost never improve performance or anything related by doing stuff to the device driver on Linux. The tweaks are all OS/kernel level, and they do not directly affect the device driver.
I do care. I care that my device allows me to be creative without holding me back in any way. If I achieve that state, then numbers, versions etc etc are meaningless (as a musician who likes to geek out, at any rate).
As you can see on Linux things can be both more and less complex than you are used to. Almost all audio runs through ALSA these days. ALSA tends to be shipped with the Kernel version as it is part of the kernel. You can update it separately, but it is not for most people to do honestly. All of these things are in one bundle. They are not provided by manufacturers separately, not are they really inherently seperate from the OS itself for most people.
I agree that 1536 samples (35ms latency at a sample rate of 44.1kHz) is a high value, especially as the Audiophile 2496's drivers are now very mature and reliable. Unfortunately it's almost impossible to track down the specific cause of your particular problem from a distance, but here are some general hints and tips.
First, always download and install the latest soundcard drivers. M-Audio's installer is extremely thorough, and starts by removing every trace of the existing drivers (including references to them in the Windows Registry), before installing the new drivers. This will ensure that you have a matched set of driver files, which may cure some problems. Next, make sure you're using the proper ASIO drivers in Cubase SX. Some people reporting high latency have been mistakenly using the ASIO Multimedia or Direct X drivers, and these won't go as low as the proper ASIO ones before you hear glitching.You should be able to achieve reliable performance and an acceptable degree of latency with M-Audio's Delta Audiophile 2496 soundcard. Downloading and installing the most recent drivers is the first step.
Sometimes tasks running in the background installed by other applications can cause the problems you describe. You can bring up a list of the tasks currently running on on your PC by right-clicking on the Taskbar and selecting the Task Manager option. You may be lucky and spot one task occasionally taking more than its fair share of CPU, but it can be a daunting task, especially as there are generally so many obscure tasks running.
However, if you want to find out exactly what each of them does, by far the best web site to visit in my experience is the 'Task List Programs' section of Answers That Work (www.answersthatwork.com/tasklist_pages/tasklist.htm). Not only does this contain detailed descriptions of what all the tasks do, and what applications may have installed them, but it also provides recommendations on whether or not to uninstall them, and how to do it.
For many musicians faced with a high-latency problem that resists all sensible attempts at resolution, the ultimate solution is to reformat your hard drive and start again from scratch, installing first Windows from its original CD-ROM, and then your applications. This approach has solved many a ticklish and long-standing problem that just wouldn't go away otherwise, but it's unwise to take this route lightly, and certainly not before backing up all your data and making an image of the current contents of your drive using a utility like Norton Ghost, so you can restore any file that you later find you've forgotten about but still need.
All contents copyright SOS Publications Group and/or its licensors, 1985-2024. All rights reserved.
The contents of this article are subject to worldwide copyright protection and reproduction in whole or part, whether mechanical or electronic, is expressly forbidden without the prior written consent of the Publishers. Great care has been taken to ensure accuracy in the preparation of this article but neither Sound On Sound Limited nor the publishers can be held responsible for its contents. The views expressed are those of the contributors and not necessarily those of the publishers.
I recently re-imaged my PC to XP and reinstalled Logic 5.5 Platinum. My soundcard is the M-Audio Delta 1010lt. When I previously had Logic installed, I was able to select between 4 inputs from the soundcard on the track mixer window. This enabled me to record via the SP/DIF input using my Podxt Pro rack. However, now I am only able to choose between the default 2 inputs!
When I open an old track and select inputs, there are four there but inputs 3 and 4 are greyed out meaning I'm not able to select them. In windows I've selected the souncard for every default and have done likewise in Logic selecting M-Audio ASIO driver and M-Audio multi for everything else I can see. Sound is played from logic, but there I'm just missing these damn inputs!
If it works the same on PC as it does on Mac, then Logic's audio settings are independent of the OS audio settings. But some interface drivers don't like it when several apps are trying to use it at the same time.
Also make sure you check the audio interface drivers for compatibility with your audio interface and your OS version. You may want to contact the audio interface manufacturer to make sure you've got the correct driver version.
It seems to be a little more complicated than drivers. I had this all set up before I reimaged my PC and I'm absolutely kicking myself now trying to figure out how I had it set up before. Nothing should have changed except the configuration inside Logic. I've worked out a way of getting all 12 inputs set up from my soundcard using the desired "ASIO" configuration, however, I then can't hear any sounds from Logic! I'm not entirely sure what "PC AV" means but unless I have this ticked, no sound comes out of Logic. And even when I have this ticked, the sound is played really slowly and blurred until an error pops up saying something about sample rates. The sample rates in Logic are set to the same as the soundcard so I don't understand why that is popping up.
I sat there for an hour at least last night trying every single tick box in different configurations with each other but still no dice. I know that I need Logic configured to ASIO in order to record from the soundcard, but not sure about the PC AV settings, and also the EASI direct sound drivers etc...
I am going to start testing this app to do live broadcast as a replacement for the on camera mic. I do live events and this app could be a God send. I have a FireWire asio profire 2626. Also M-Audio usb Fasttrack.
However the high latency for the Windows audio system makes it impossible to record or play live, both audio and midi data. The asio driver I use is called ASIO4ALL and seems pretty universal and worsk across the board of most sound cards and can be found at along with loads of info.
Yesss please!!! I use a lot of apps with ASIO, like I have Toneboosters Equalizer app that I like to play all my music thru on my pc. This also means when I use say, soundcloud, I have it routed thru a virtual audio cable, into my eq app, where it is routed into (typically) my actual sound output device. I have tried every which way I can think of to be able to send my sound into audiorelay, either by streaming from my soundcard output in app, additional virtual outputs, and even using an additional soundcard with an auxiliary cable from the main out, into the second soundcards line-in. Nothing works! lol
Hi,
i am having m-audio 1010LT card , i want configure 10 lines of the card as a asterisks channels.
is anybody can help me to solve this probleam.
presently i am working on RHEL4 machine.
thanks
roopesh