M Audio Mtrack 2x2 Driver

[Curtis Boykins]

SoI've been recording VO work using Adobe Audition with my M-Audio M-Track Plus and AT2020. Recently the levels on my recordings have all been stuck between -30 and -35db regardless of my gain settings on my M-Track Plus. I've double checked all my audio settings and the settings for my M-Track driver, but none of the settings seem to have been changed, so I'm not sure what could be causing this issue. Please help! Thanks!

You should really use the M-Audio ASIO drivers since these bypass the Windows operating system completely. So Audition will receive what the MTrack is sending it rather than letting Windows mess with the audio.

When I first attempted to use the ASIO driver, my system was indicating that it wasn't working. So I reinstalled the driver from the M-Audio site. The ASIO driver works now, but it hasn't fixed my issue... My recording is still coming in between -30 and -35 dB regardless of whether I have the input gain turned down or cranked up.

To test whether it was some setting I may have messed up in Audition I downloaded and did a test recording in Audacity. I got the same results there... Low dB in the -30 to -35 range regardless of where my gain was set.

Unfortunately that then seems like a problem with the MTrack interface. You should have a much larger range than you need using the gain control on the interface. How have you got the mic connected into the MTrack? It should be via an XLR cable plugged into one of the XLR sockets on the interface. The input should be switch to 'mic' and 48v should be turned on. What levels show on the meters on the front of the MTrack? Do they go up and down as you alter the Gain knob?

So I handheld the mic so I could see the signal levels on the MTrack. When holding the mic at the approximate distance that I usually record at it wouldn't register on the MTrack's meter, but when I held the mic right in front of my mouth it barely registered on the meter at -20. While doing this I also had the gain on my MTrack turned up to it's max...

After I set my mic back in place, readjusted my XLR cables, and reconfigured a few settings in Audition (like I'd tried to do so before) it's all working again. My levels are now adjusting like they should be when recording... Weird.

I have a Tascam US-600 that has already been discontinued and I purchased this interface. I did some tests and comparing with the Tascam and I came to the conclusion that the Tascam, even discontinued, is much better and has much more features than the M-Track DUO. I have resumed using the Tascam in the studio and am using the M-Track Duo only to record external work and respecting the simple specifications of the equipment.

1) When commanding the recording of a track, a click is inserted. That's why I couldn't command the recording at a time closer to where it will start. I had to command before and after to remove the click from the recording.

2) In the middle of recording using a condenser microphone SAMSON - C01 Studio Condenser, noises are generated at random times, as a kind of saturation (all care with proximity, cables, etc. has been taken). It seems to be something from M-Track, because when I record with Tascam it doesn't happen.

3) I had a lot of problems recording instruments with my Keystation 49es due to latency when recording with effects. I was only able to "zero" the latency when recording without effects in the project. On the other hand, I started to verify that when recording MIDI, several Pitch and Modulation commands are inserted without me having moved any of the controls on the equipment.

Anyway. I know there are several related situations, but they all appeared only after I installed the M-Track Duo whose hope was to overcome a discontinued interface like the Tascam US-600 to which I returned and resumed my projects.

I actually had one, but can't recall ever experiencing this. Had it for two months and sold it, I think i was unhappy with connection cables I had to get, 1/4jacks (Duo) to XLR (Monitors.) It sounded decent at the time for the Home Studio.

It might be fine, and I could be wrong but it's an old saying- You get what you pay for. The Behringer UMC 22 comes to mind as well. Both are sort of Mac oriented companies so the devices work great on a Mac but Windows and Cakewalk tend to be more picky about drivers.

Have you done all the proper ASIO driver set up including what you might want to set in Windows. Make sure there's no other drivers like Asio4all and Real tech etc. The Tascam driver will not interfere but make sure the M audio driver is showing in all the boxes in your audio preferences settings and especially the sync and cashing timing box.

Thanks a lot for the help.

Yes I have the M-track drivers correctly installed.

The video you attached is excellent and a tremendous way to get the interface installed.

I don't really know what's going on.

I thought the latency when recording instruments via my midi keyboard would be improved, but it remained the same as it had with the Tascam.

I don't agree that the issue is just the price of the interfaces, because if the equipment establishes that it can record with the settings it says it has, there shouldn't be many of the problems I found.

I don't know if it wouldn't be a matter of Cakewalk's own "relationship" with the Asio drivers of the interfaces. This is beyond my technical technical knowledge involved.

Thanks.

Yes I record vocals and the virtual instruments with my keystation 49es keyboard. I only get "zero" latency when turning effects off.

This on both interfaces.

Both interfaces are connected to USB 2.0 ports.

I don't know if in fact it's not a matter of Cakewalk integration with the Asio drivers of each interface.

M Audio M Track Duo- $ 140 Can. ( I was wrong about the $70, that was on E Bay ) So it's around the same price as a Focusrite Solo, Presonus Audiobox 96 or a Tascam 2x2 all which are excellent interfaces. M Audio has been around a long time I have a Fast Track Pro sitting on the self. The drivers are outdated like your Tascam.

The switch looks like it's either your input in mono or stereo or the USB but not both? That's very odd. I didn't think anybody made an interface these days without direct monitoring. FYI- Direct Monitoring = hearing the direct signal from your input mixed with the DAW playback. This results in Zero latency. This means you can record latency free at any buffer setting. But higher buffers equal more Round trip latency and you will not be able to use Input echo.

Thanks.

I always record 44100/16 as I always export in that configuration;

I didn't really understand the meaning of these 3 types of monitoring, because I didn't notice any kind of changes even increasing monitoring volumes via headphones or an external monitor.

Sorry, I can't help any further on this matter. Which I knew what was really wrong, but at this moment it's a guessing game. I personally didn't experience any of the above problems mentioned in the OP.

I too, use active monitors and only experienced about -3dB difference when Direct monitoring was enabled. Its not really something i (personally) would ever need. This being said: There was a difference other than the -3bB decrease in volume. Even with the Apollo twin which I use on the Mac its there.

All I can think of now is to try and clean out you fans in your system. Grab a brand new paint brush, remove the cpu fans and dust them off also check some USB HUBS (if you're using any.) Also, replace some thermal paste. Your latancy might be related to something else and not Cakewalk or your Interface.

Actually now I see this switch is unique because it has the mono option a handy dandy idea.

Still a Blend controller that you can select any amount of either input or playback works best.

RTL does not matter if you use direct monitoring. It only is noticeable when you turn on Input Echo on an audio track while recording.

Solution is Turn off input echo and use direct monitoring.

Solution bypass the effects while recording.

If your interested in a little educational material on these topics here are some of my videos that explain clearly how to set up and record both audio an midi.

It looks like none of these videos are available anymore. Such a pity. Cakewalk just freezes when I arm the track to start recording using my new Mtrack Solo. I can hear the music during playback only but at soon as I arm a track for recording and hit that record button nothing happens - it just sits...

Hi There!

I just updated My Cubase from 10:5 to 11 and using Tascam model 12 interface and I have similar issues when Starting to Record a track appears this message ASIO Driver not Running , tried many different ways and no one works.

Same problem here.

Windows 11

Cubase 12

Focusrite 18i8

Everything used to be fine but all of a sudden; no sound, no activity on audio meters and the same message appears when I try to record. Reinstalled focusrite driver and cubase, no change. Focusrite tested with other stuff; working absolutely fine.

The problem may be less with the hardware and more with your choice of software; Audacity isn't exactly professional-quality, and it doesn't come with ASIO support out of the box for licensing reasons. See _Audio_Interface for more information.

I had this same problem using the M-Audio Driver.I did find a fix for this problem. This will, of course be dependent upon a couple of factors. The speed of your computer and the speed of your USB audio device (2.0, 1.0, etc.).

3a8082e126