X3 producer/interface problems

Author
yellowcake64
Max Output Level: -87 dBFS
  • Total Posts : 186
  • Joined: 2008/12/07 11:10:23
  • Location: Kent UK
  • Status: offline
2016/01/24 15:37:07 (permalink)

X3 producer/interface problems

Hi folks

Got a weird interface thing going on. I have a Tascam US-4x4 and Sonar Producer X3. Sometimes when I'm working away in the software, X3 will strangely lose all the Tascam interface ASIO settings. In then of course reverts to no interface being set up and I basically have to shutdown X3, reboot it, and then everything's OK.

Probably happens 50% of the time. Any thoughts would be greatly appreciated!

Dave

Yellowcake
Sonar Platinum; Core i7 4790K Quad core 16GB DDR 3 RAM; Windows 10 (64-bit); Tascam US-4x4 interface; Roland Juno D synth; KRK Rokit 6 monitors; V-Amp2; V-Amp Bass.
#1

10 Replies Related Threads

    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re: X3 producer/interface problems 2016/01/24 16:16:44 (permalink)
    Have you turned off "Windows Sounds" in the Windows Control Panel?
     
    Sounds like the system is stealing/mucking with the interface.
    #2
    yellowcake64
    Max Output Level: -87 dBFS
    • Total Posts : 186
    • Joined: 2008/12/07 11:10:23
    • Location: Kent UK
    • Status: offline
    Re: X3 producer/interface problems 2016/01/24 16:29:09 (permalink)
    It's a good call Beep. I guess this could happen intermittently?

    Dave

    Yellowcake
    Sonar Platinum; Core i7 4790K Quad core 16GB DDR 3 RAM; Windows 10 (64-bit); Tascam US-4x4 interface; Roland Juno D synth; KRK Rokit 6 monitors; V-Amp2; V-Amp Bass.
    #3
    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re: X3 producer/interface problems 2016/01/24 16:38:22 (permalink)
    yellowcake64
    It's a good call Beep. I guess this could happen intermittently?

    Dave



    Well if the system (or more accurately Windows) decides to make some kind of beep or blop or boop the it could (depending on the settings you have) reach out to the interface to do it. Windows sounds are 44.1 16bit by default (I think) so if your project is something different then it takes over the interface and changes your settings.
     
    Or something like that. Best to just have Windows Sounds disabled anyway even if that's not the problem.
     
    The other issue it could be... now that I think of it... is a faulty connection. So if that's a USB device then maybe your cable is pooched or your USB port is pooched. That would explain why you lose all sign of the interface in your Prefs (if that's what's going on).
     
    So in that case try a new USB cable or switch to another available USB port on your system.
     
    If you switch to another port though it's probably a good idea to disconnect the device, uninstall the driver, reconnect the device to the new port and then reinstall the driver according to the manufacturer instructions.
     
    Also make sure you have the most current driver for you device and operating system (of course). I would also say that sometimes the LATEST driver may not be the best thing so maybe do a google search of the device and drivers to see what other users are experiencing and be very careful if the driver install includes irreversible firmware updates (like my Focusrite does).
     
    Usually you'll be fine but it's always best to go in armed with as much info as possible.
     
    PS: I am not a computer tech. Just an ultra meticulous and paranoid bugger when it comes to this crap and have had USB connectivity issues in the past.
     
    Hope it works out.
     
    Cheers!
    #4
    slartabartfast
    Max Output Level: -22.5 dBFS
    • Total Posts : 5289
    • Joined: 2005/10/30 01:38:34
    • Status: offline
    Re: X3 producer/interface problems 2016/01/24 17:09:05 (permalink)
    I think no one has yet mentioned the most common cause, Windows sleeping or powering off a USB hub to save battery/energy. You should make sure your power settings keep everything on all the time.
    #5
    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re: X3 producer/interface problems 2016/01/24 17:24:19 (permalink)
    slartabartfast
    I think no one has yet mentioned the most common cause, Windows sleeping or powering off a USB hub to save battery/energy. You should make sure your power settings keep everything on all the time.




    Oh... yeah. Massive omission on my part. Sorry about that.
     
    Set your Windows Power Management scheme to "Performance"... or whatever the equivelant is in Win10 (so make sure all USB, CPU, Drives, etc NEVER power/idle down).
    #6
    yellowcake64
    Max Output Level: -87 dBFS
    • Total Posts : 186
    • Joined: 2008/12/07 11:10:23
    • Location: Kent UK
    • Status: offline
    Re: X3 producer/interface problems 2016/01/26 16:40:18 (permalink)
    Still no joy with this guys. I've narrowed it down to it happening when I try and change settings once I'm in a session of Sonar. For example, if I set up a session then say go to change the Recording mode from Comping to Sound on Sound, the whole thing bombs. Changing the setting definitely causes the drivers to drop out. It's not limited to Recording Mode - it could happen on anything like changing the count-in parameters. It's really weird. Any other suggestions would be gratefully received. 
     
    Dave

    Yellowcake
    Sonar Platinum; Core i7 4790K Quad core 16GB DDR 3 RAM; Windows 10 (64-bit); Tascam US-4x4 interface; Roland Juno D synth; KRK Rokit 6 monitors; V-Amp2; V-Amp Bass.
    #7
    AlanSJackson
    Max Output Level: -90 dBFS
    • Total Posts : 27
    • Joined: 2015/01/11 15:13:47
    • Status: offline
    Re: X3 producer/interface problems 2016/01/26 16:52:55 (permalink)
    Go to the advanced power options and from the Change advanced power settings pop up menu set the USB selective suspend setting to Disabled.
    Make sure the power is set to high performance and the turn off display and computer sleep is NEVER.
    I'm assuming the device has a Win 10 driver. I had a similar problem with a Roland V-studio. Every time I pulled a different USB connection SONAR believed I'd pulled the interface. Driver problem. Reinstall the driver from the devices menu, it may have been overwritten or messed up with a Win update.


    Check the device is default via the Windows sound icon, and the settings are suitable for recording. 
     
     
     
     
    #8
    robert_e_bone
    Moderator
    • Total Posts : 8968
    • Joined: 2007/12/26 22:09:28
    • Location: Palatine, IL
    • Status: offline
    Re: X3 producer/interface problems 2016/01/26 18:39:42 (permalink)
    You might try making sure Windows doesn't also have itself using your audio interface ASIO drivers as the Windows Default Audio Device, if you are still getting conflicts.
     
    If you do change the default audio device for Windows, you can either feed the output from the internal sound chip back into your audio interface, or get a set of inexpensive computer speakers, or do what I do, which is have the Windows Default Audio Device set to use my HDMI video/audio output to route both to one of my two HDTV's that I use as display monitors for Sonar.
     
    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  
    #9
    yellowcake64
    Max Output Level: -87 dBFS
    • Total Posts : 186
    • Joined: 2008/12/07 11:10:23
    • Location: Kent UK
    • Status: offline
    Re: X3 producer/interface problems 2016/03/06 17:59:30 (permalink)
    You know what guys, I think I've finally solved this. As is often the case with stuff like this it's something simple. The problem was that I had the US-4x4 plugged into a USB 3 (high speed port). Out of sheer desperation last night I just swapped it over into a USB 2 port and voila - no problems so far. Fingers and everything else crossed!
     
    Dave

    Yellowcake
    Sonar Platinum; Core i7 4790K Quad core 16GB DDR 3 RAM; Windows 10 (64-bit); Tascam US-4x4 interface; Roland Juno D synth; KRK Rokit 6 monitors; V-Amp2; V-Amp Bass.
    #10
    Anderton
    Max Output Level: 0 dBFS
    • Total Posts : 14070
    • Joined: 2003/11/06 14:02:03
    • Status: offline
    Re: X3 producer/interface problems 2016/03/06 20:42:58 (permalink)
    Make sure your USB ports aren't set to automatically to a power-saving.The settings are in Device Manager, if you don't know how to do this I'll walk you through it. Also disable the power-saving mode in the 4x4 control panel.
     
    The 4x4 is what I use in my office and the 2x2 when on the road (and a 20x20 at home as a true USB 3 interface). I've used both the 4x4 and 2x2 with USB 3 interfaces without incident, but USB 3 can be a little squirrely sometimes, depending on the computer's chip set.

    The first 3 books in "The Musician's Guide to Home Recording" series are available from Hal Leonard and http://www.reverb.com. Listen to my music on http://www.YouTube.com/thecraiganderton, and visit http://www.craiganderton.com. Thanks!
    #11
    Jump to:
    © 2025 APG vNext Commercial Version 5.1