Share via

Windows 10 Stops Recieving Input From ASIO Device

Anonymous
2021-10-22T20:35:22+00:00

I recently upgraded my audio interface from a TASCAM iXR to a TASCAM Model 12. My DAW, Reaper, can send audio to the Model 12 and receive audio back from the Model 12 no problem, but for some reason in most Windows 10 apps like Voice Recorder, Zoom, Teams, audio goes to the Model 12 but none of the audio from my microphone comes back to Windows. I've verified the latest version of firmware and installed the latest drivers on 3 Windows 10 computers and get the same behavior. What's interesting is if I open up Reaper, create a track on inputs 1 and 2 (where I have the master mix from the Model 12 going) or even other tracks and arm the track I can not only get the audio into Reaper, but it suddenly starts working in all of the other Windows apps I mentioned above. As soon as I disarm the track in Reaper it stops working. Similarly on one of the 3 computers I've tried if install and start ASIO Link Pro as soon as I "Start ASIO" it starts working -- even without patching any audio in ASIO Link Pro or using any of the virtual audio devices associated with it -- the default "Model 12" input just starts working on its own.

It makes me think something is causing the input disable itself, then when certain programs like Reaper or ASIO Link Pro start talking to it, it wakes up and is available to other Windows programs, even non-ASIO-specific ones.

I've tried uninstalling and reinstalling the drivers and gone through the sound control panel settings and tried different settings with no change the the above behavior. On one of the computers I've also tried removing all other ASIO drivers and devices before re-installing the Model 12 drivers to get as clean of a start as possible.

At least one of the computers is running 20H2 -- most likely the other 2 are as well.

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

7 answers

Sort by: Most helpful
  1. Anonymous
    2021-10-27T03:59:37+00:00

    I found a workable way around this problem -- in the Sound Control Panel for the Model 12 recording device on the Advanced tab, if I change the Default Format from "2 channel, 24 bit, 48000 Hz (Studio Quality)" to "12 channel, 24 bit, 48000 Hz (Studio Quality)" it starts working immediately. Whatever is going to the Stereo Mix on the Model 12 shows up on in the Sound Control Panel meters and applications like Zoom, Teams and Discord can use the Model 12 as an input.  Oddly enough, Voice Recorder stops working -- it fails with "Your microphone is not working" but I can live with that. Note that the option for 12 channels is not available until after installing the drivers from TASCAM.

    FYI, I also sent the following to TASCAM support but have not heard back from them:

    The Model 12 shows up as both a input (mic) and output (speaker) devices when connected via USB. The speaker function works as expected-audio from Windows can be routed to channels 1&2 on the M12, however the mic function does not. Audio from the M12 is not sent back to Windows, even in stereo mix mode to outputs 1&2. Windows apps like Voice Recorder, Zoom or sound control panel do not see any input from the M12. Same behavior either before or after installing the TASCAM drivers.

    ASIO works as expected and interestingly, launching a application using the ASIO interface like Reaper causes the Windows input to start working as long as Reaper is in the foreground. Reaper is minimized or I switch to another window, the mic stops working, then works again if Reapers is back in the foreground. Arming any track on in Reaper or playing any audio, even silence, to the M12, the mic input in Windows also continues to work.

    It's almost as if the USB output of the M12 goes to sleep and stops communicating to the Windows audio interface and having any active ASIO application wakes it up. The behavior is very repeatable and I have reproduced it on a total of 4 different Windows 10 computers ranging from 1909 to 20H2 to 21H2. One of which has other audio applications on it, another is a clean system with just bare-bones Windows 10.

    In comparison, my iXR works perfectly after installing its drivers on a computer -- both input and output to/from Windows applications works without having to launch any ASIO applications to get it to start sending audio back to Windows.

    The M12 came with firmware 1.22 and I even tried reinstalling 1.22 to make sure it was correctly installed, but that made no difference. It does not seem like I can downgrade the firmware to 1.21. In Device Manager, it shows the TEAC Corp driver 1/10/2020 15.43.39.95 under the Sound, video and game controllers section and the Microsoft driver 12/6/2019 10.0.19041.1 in the Audio inputs and output section.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-10-23T00:48:17+00:00

    Thanks for reporting back on your progress, Alan.

    Keep us posted on your progress, which will help others searching for this issue.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-10-23T00:25:20+00:00

    I tried TASCAM phone support -- they were helpful in making sure I had the Model 12 configured right and that audio was going to the master mix and set to send the stereo mix to outputs 1&2 but it seems like the Model 12 itself is working okay since it communicates with my DAW and other ASIO-based programs. Thanks for the links -- I'll definitely try posting the same question to the TASCAM forum as it's probably a combination of how the driver is configured and Windows audio, not purely a TASCAM only issue. It would be helpful to find other users with similar setups and verify how theirs is or isn't working compared to mine.

    Interestingly the when launching the ModelMixer control panel for the first time it says something about being verified to work with 1909 but unfortunately I've kept all of my computers up to date and don't have anything still on 1909 to try a comparison test with.

    I'll post updates if I make any progress in case it can help anyone else with the same issue.

    Thanks,

    Alan

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-10-22T21:26:50+00:00

    HI Alan. I'm Greg, 10 years awarded Windows MVP, specializing in Installation, Performance, Troubleshooting and Activation, here to help you.

    Have you contacted Tascam Support which is included for the first year, during which under law they must get it working properly or replace it?
    Go here: https://tascam.com/us/support/contact/product/t...

    They also have a User forums here: https://www.tascamforums.com/

    You will also get better help for this in an audio enthusiasts forums than in a general Windows forums where audio specialization isn't emphasized. Here are the best forums for the audio enthusiasts who will know these issues:

    https://audiofederation.com/catalog/links/index...

    https://www.whatsbestforum.com/forums/

    https://www.kitchenknifeforums.com/threads/what...

    https://www.avsforum.com/forums/

    https://www.stereophile.com/forum

    Hopefully one of those helps. If not I may have other suggestions. I will be here to help until this case is resolved.

    ______________________________________________

    Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

    Was this answer helpful?

    0 comments No comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more