M-Audio Fast Track C400 Interface not recognized by Sonar SOLVED

Author
Noisy Neighbour
Max Output Level: -81 dBFS
  • Total Posts : 460
  • Joined: 2011/06/12 15:33:41
  • Location: Amsterdam / NL
  • Status: offline
2012/11/29 10:26:56 (permalink)

M-Audio Fast Track C400 Interface not recognized by Sonar SOLVED


Hi,

Problem:
Sonar doesn't see M-Audio Fast Track C400 Interface (audio) anymore after the USB cable has been disconnected/reconnected from my machine due to upgrading ram from 8 to 16 Gig. It only shows up as midi device but not as audio device in the edit/preferences menu. It was running without any issues until it was disconnected. Latest drivers installed and windows also sees it as audio device. Double checked:  All my other audio interfaces work fine.
Any Idea anybody? (I've checked the Avid website, but didn't find any specific Info)

thanks in advance  : )

Daniel

post edited by Noisy Neighbour - 2012/11/29 12:37:36

Daniel

LAVA LAMP, Sonar Platinum  
Intel Core i7-2600 CPU 3.40 GHz, 16 Gig Ram, Windows 10 x64
M-Audio Fast Track C400
A-500 Midi Keyboard Controller, Yamaha MSP7, Yamaha HS50 Monitors,
(a bit of room treatment) plugins, guitars, 
 Take a Look Inside
#1

10 Replies Related Threads

    robert_e_bone
    Moderator
    • Total Posts : 8968
    • Joined: 2007/12/26 22:09:28
    • Location: Palatine, IL
    • Status: offline
    Re:M-Audio Fast Track C400 Interface not recognized by Sonar 2012/11/29 10:54:27 (permalink)
    Some audio interfaces can't handle being plugged into USB 3.0 ports.  This is true of the Presonus AudioBox 1818VSL.

    Try plugging into a different USB port - I think the USB 3.0 ports have some blue in them, or on laptops may have a little 'ss' next to then.

    Bob Bone


    Wisdom is a giant accumulation of "DOH!"
     
    Sonar: Platinum (x64), X3 (x64) 
    Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22
    Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64
    Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others
    MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es
    Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms  
    #2
    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re:M-Audio Fast Track C400 Interface not recognized by Sonar 2012/11/29 11:06:32 (permalink)
    Also sometimes USB devices can confuse the system if you switched to a different USB port. Are you using the same port? If not trying uninstalling the drivers then reinstall with the device hooked up to the port you want. If it's a plug and play like my M-Audio keyboard though IDK what you can do. 
    #3
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re:M-Audio Fast Track C400 Interface not recognized by Sonar 2012/11/29 11:13:45 (permalink)
    rename the AUD.ini file
    #4
    Noisy Neighbour
    Max Output Level: -81 dBFS
    • Total Posts : 460
    • Joined: 2011/06/12 15:33:41
    • Location: Amsterdam / NL
    • Status: offline
    Re:M-Audio Fast Track C400 Interface not recognized by Sonar 2012/11/29 11:44:03 (permalink)


    Thanks for reply guys!

    I've already tried different USB ports. Also"repaired" the install of the driver. No success.
    I don't understand the rename Aud.ini. file - process to be honest, (I'm only a guitar player:)) so I'll try Beebster's advice next and completely uninstall/reinstall the driver. See if that helps... can't do much damage. What puzzles me most is that Sonar actually sees the device, but only as a midi device...






    Daniel

    LAVA LAMP, Sonar Platinum  
    Intel Core i7-2600 CPU 3.40 GHz, 16 Gig Ram, Windows 10 x64
    M-Audio Fast Track C400
    A-500 Midi Keyboard Controller, Yamaha MSP7, Yamaha HS50 Monitors,
    (a bit of room treatment) plugins, guitars, 
     Take a Look Inside
    #5
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re:M-Audio Fast Track C400 Interface not recognized by Sonar 2012/11/29 11:48:06 (permalink)
    Aud.ini is the initialization file that contains the interface setup info. If you rename it, SONAR will rebuild it on startup. The file is located in your home directory in "AppData/Roaming/Cakewalk/SONAR X2 Producer." BTW, AppData is a hidden directory. Usually you would rename it rather than delete it, just in case you have some special setup stuff that you might want to copy back into the new ini file.
    #6
    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re:M-Audio Fast Track C400 Interface not recognized by Sonar 2012/11/29 11:49:41 (permalink)
    You might want to use CCleaner to uninstall it. I don't know how thorough M-Audio's uninstall feature is. 

    I'm certainly no expert but it does sound like the driver is being a jerk. Maybe it configured itself to use your system as it was with the lesser amount of RAM and now it's pooping itself... yanno, to use the technical term. ;-)
    #7
    sharke
    Max Output Level: 0 dBFS
    • Total Posts : 13933
    • Joined: 2012/08/03 00:13:00
    • Location: NYC
    • Status: offline
    Re:M-Audio Fast Track C400 Interface not recognized by Sonar 2012/11/29 12:02:31 (permalink)
    I'm pretty sure I had the same problem when I disconnected my computer to move it and plugged everything back in. My C400 wasn't being recognized. I just did my usual thing of stumbling along in the dark trying random things until it worked. Sorry I can't be more helpful! Just to let you know that it did get recognized again eventually, and I didn't have to do anything technical. 

    I think I probably reinstalled the drivers at some point, yes! It's all coming back to me....

    James
    Windows 10, Sonar SPlat (64-bit), Intel i7-4930K, 32GB RAM, RME Babyface, AKAI MPK Mini, Roland A-800 Pro, Focusrite VRM Box, Komplete 10 Ultimate, 2012 American Telecaster!
    #8
    Noisy Neighbour
    Max Output Level: -81 dBFS
    • Total Posts : 460
    • Joined: 2011/06/12 15:33:41
    • Location: Amsterdam / NL
    • Status: offline
    Re:M-Audio Fast Track C400 Interface not recognized by Sonar 2012/11/29 12:43:00 (permalink)


    its baaack !

    Thanks poeple, for assisting me here! 
    A complete de-reinstall of the driver did it. Sooo easy.

    The rockin' of this forum confirmed once again!

    regards,
    Daniel

    Daniel

    LAVA LAMP, Sonar Platinum  
    Intel Core i7-2600 CPU 3.40 GHz, 16 Gig Ram, Windows 10 x64
    M-Audio Fast Track C400
    A-500 Midi Keyboard Controller, Yamaha MSP7, Yamaha HS50 Monitors,
    (a bit of room treatment) plugins, guitars, 
     Take a Look Inside
    #9
    robert_e_bone
    Moderator
    • Total Posts : 8968
    • Joined: 2007/12/26 22:09:28
    • Location: Palatine, IL
    • Status: offline
    Re:M-Audio Fast Track C400 Interface not recognized by Sonar 2012/11/29 12:46:57 (permalink)
    One of my Yamaha keyboards gets forgetful driver syndrome if I don't always plug it into the same USB port.  I have to install its drivers again as well.

    Glad you are back in business.

    Bob Bone


    Wisdom is a giant accumulation of "DOH!"
     
    Sonar: Platinum (x64), X3 (x64) 
    Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22
    Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64
    Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others
    MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es
    Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms  
    #10
    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re:M-Audio Fast Track C400 Interface not recognized by Sonar 2012/11/29 13:03:30 (permalink)
    Awesome. Remember folks, when troubleshooting hardware issues more often than not it's gonna be a driver screw up. Uninstalling and reinstalling the driver may not work but many times it will and doing it doesn't hurt anything. Also always check for new driver releases from your manufacturer especially if you have updated your OS, programs or added any new hardware to your system. Cheers.
    #11
    Jump to:
    © 2025 APG vNext Commercial Version 5.1