Windows 10: Audacity Error Initializing Audio when I have USB audio interface on

A week ago I wasusing Audacity without any problems. Then midweek (Wed/Thursday) 11/11 or 11/12I launched Audacity and received the message "Error Initializing Audio.Could not find any audio devices. You will not be able to play or record audio.Error: Internal PortAudio error".
I read several postsin this forum and on www.tenforums.comthinking "what changed" did a patch come out? In the process ofreading and trying to figure out what happened. I did the following.
I am running Windows10 Pro 64 bit. I have been on Windows 10 now since the free upgrade in Augustwith no issues related to Audacity.
I was on Audacity2.1.0 and I upgraded to 2.1.1
I updated my RealtekHigh Definition Audio drivers to Version 6.0.1.7655 11/3/2015.
I saw one post aboutRealTek HD Manager not have the Default Format set. I checked that and it wasokay.
I have soundproduced through iTunes, Internet music streaming so everything checks on that.
Because I play musicI use Cakewalk Sonar and use M-Audio Fast Track Ultra USB audio interface. Idecided to power that down and to my surprise Audacity came up without the errormessage and it showed the Audio Device info.
I have notPersonally installed any new programs or updates on this computer except forwhat I mentioned above. I did notice that there have been some Windows patchesinstalled recently but nothing Windows 10 related. Just Printer, MS Office andWindows Malicious Software Removal Tool.
Have there been any patches lately that could have caused this?
Any thoughts?
Thanks

I posted this message on Audacity's forum site as well.

:)

 

I run my audio interface within 5 minutes the interface disconnects and windows tells me that there is an error.

Original Title: Audio interface.

I have a behringer FCA1616 USB audio interface running Cubase 5.1 and everytime I run my audio interface within 5 minutes the interface disconnects and windows tells me that there is an error and then it won't work until I restart my computer. when I reboot
it does it all over again. I have already tried to uninstall and reinstall device driver nothing has worked so far. How can I fix this issue?

 

USB Audio Codec Driver

Windows 10 Just doesn't see The AT-lp120-usb.

I also have an older crosley usb turntable and as soon as I plug into

a usb port , Microphone array(USB audio device) and Speakers(USB audio device)

pops up under Audio inputs and Outputs in My device manager. It also pops

up in devices and printers in control panel as UBS audio controller.

Usb Audio Device Also pops up in Sound, Video, and game controllers in
device manager.

And It works very well with audacity both play and record.

These usb audio devices disappear when I unplug the crosley and plug

my At-lp120-usb in. I plug them in at the same time and try recording

with each the crosley works the AT does not.

 

I have a Sonar Platinum studio (using a Roland Studio-Capture).

Normally (without any recording interface unit) Audacity defaults to the "Stereo Mix" (which should be set as the default recording device).

With my Studio-Capture powered on, Audacity on my Win 10 Pro 64 bit the default recording device is still Stereo Mix (see screenshot below). I used to have an M-Audio Fastrack Ultra 8R and don't recall the problem you are having.

 

I think Audacity is set to "default windows source" or similar and has problem to identify the source when your USB audio card is connected. Try setting it to a specific device from settings and then connect your USB. If it can start without issues you could then change the device to your USB.

 

@fireberd. I do have Stereo mix set as recording default. And this was working last week so I don't understand what changed.


@spapakons, I'm not sure I understand what you are suggesting. Could you re-phrase your statements.

 

I mean, if there are any settings inside Audacity, you can try setting the recording source to a specific device, not let it in "windows default". Then it should use this device even when you have your USB card connected without error messages upon loading. When inside Audacity with your USB connected you can then change the recording source to your USB.

 

Understood. If I have my USB audio interface connected and turned on, I get the error launching Audacity and there are no devices available to select.



If I turn of the audio interface I see the devices in Audacity.

 

Well, I haven't Audacity installed, so I cannot help you further.

 

I can't duplicate your problem with my Roland Studio-Capture. Audacity always defaults to the Stereo Mix when I start Audacity.

 

Thanks for trying firebird.

 

As I said before, try loading Audacity with the USB disconnected. Once there, look carefully at the settings/preferences/configuration (whatever is called). There should be a setting to select input and output source. Normally this is "windows default" or similar. Change it to a specific device so Audacity always uses this device ignoring any other devices. Close the program and connect your USB. Since Audacity now uses a specific device, it shouldn't search for other devices and give any error. Once successfully running Audacity with your USB connected you can then change the input and output to those of your USB from the same setting.

 

In reference to spapakons post about configuring. I didn't have Audacity installed on my Win 10 (I have it installed on Win 7) and installed it for this thread and to test. I didn't set any custom defaults. Just used the program defaults. In fact, I had my Studio-Capture powered on when I installed and first tested Audacity and it still used the Stereo Mix.

 

With what spapakons said I turned off my M-Audio device and started up Audacity. Here's what the Device Preference page looks like:



As fireberd said, it's defaulting to Stereo Mix.
I then looked at Devices Preferences - Audacity Manual and was thinking about playing around with the different host selections but I decided to see what happens if I turn on M-Audio while Audacity is running.
I wasn't expecting this.



I've got to head out for a bit so I'll try some host interface settings later. This page fault does tell me that these two devices are not having conflicts. Again, I'm not sure what cause this to happen when it had been working just fine until last week.

 

This BSOD indicates incompatibility with M-Audio drivers... Try installing different drivers.