InternalPortAudio error since windows 10 update

[Gale Andrews]

As some other people already told about it, the best solution is to update the audio drivers.
In my case, it was a Realtek "High Definition Audio Codecs".
The current version is R2.79 and with it, Audacity v2.1.1 can run perfectly under Windows 10.

Thank you. It is still a second-best solution because those drivers http://www.realtek.com.tw/DOWNLOADS/dow ... Down=false are generic (not properly matched to your hardware).

And in most cases you must already have a Realtek device (as opposed to for example IDT or SoundMax) to use those Realtek drivers.


Gale

[cryptoz]

I saw somewehre in the forum (I don't remmerber where) that an older 2.X beta version of audacity worked in windows 10, can you confirm that?

2.x versions are not betas, and no-one other than you has reported that 2.0.2 does not have the Windows 10 PortAudio initialisation error, but thanks for posting your finding and for the dxdiag report (which looks fine).

A few users find that versions of Audacity after 2.0.2 reset the audio output balance to equal, but that isn't specific to Windows 10.


Gale

Latest realtek drivers rc2.79 install but changed nothing for Audacity. Installed 2.0.6 with no change. Installed 2.0.0 and Audacity works!

[pryere]

can also confirm that version 2.02 works with Win 10.
missing all the latest features but it works! phew.

[pljones]

I have on board audio and a Firewire Echo AudioFire4 soundcard. Both are recognised by Windows. MPC-HC plays to both. Reaper 4.78 reports:
WDM: AudioFire4
DirectSound, WaveOut: Mix, Realtek, AudioFire4
ASIO: AudioFire4, JackRouter
WASAPI: Realtek, AudioFire4

I was running Audacity 2.1.0. That hit the error reported here.
I upgraded to 2.1.1, no change. Same with Aug-08 nightly. 2.0.6 same; 2.0.5 same; 2.0.4 same.

2.0.3 works.

I was wondering if it was actually PortAudio but I'm more thinking it's something to do with how the build is produced -- the PortAudio version itself has remained V19 but the build date is that of the release. All I can see in the release notes for 2.0.4 that stands out is WASAPI.

[Gale Andrews]

Thanks for the information.

I was wondering if it was actually PortAudio but I'm more thinking it's something to do with how the build is produced -- the PortAudio version itself has remained V19 but the build date is that of the release. All I can see in the release notes for 2.0.4 that stands out is WASAPI.

The v19 is only the major version. For most (not all) Audacity releases, we update to the latest PortAudio v19 "snapshot" available at the time. So the PortAudio version is relevant, even though that is not apparent from the Audacity interface.

Changes we made in our PortAudio support could also be relevant.

This gets tricky because there are often winners and losers when PortAudio changes or when we tweak our support for PortAudio. For example, changes we made to PortAudio for Audacity 2.0.3 so as to make most devices' Windows volume sliders move in tandem with the Audacity sliders caused some devices to reset their balance to zero when Audacity started up.


Gale

[pljones]

Hi,

Just to update, I finally found the updated Realtek drivers for my motherboard. Installing those has fixed the problem .
Motherboard: ASUS M5A99X-EVO-R20
I updated both the Realtek Audio and Network drivers.

Thanks,

-- Peter

[w3sz]

Running windows 10, I can confirm that when Audacity 2.1.1 or 2.0.6 is installed with the installer for version the error, "Could not find any audio devices. You will not be able to play or record audio. Error: Internal Portaudio error" occurs and Audacity does not work.

However, as was pointed out, version 2.0.2 when installed with the installer does work. No error occurs, and sound playback is as expected.

Thanks for pointing out that 2.0.2 works with Windows 10!

Great tip!

[lezman]

I was running version 2.1.0 on my desktop system and also had this problem when I did the Win10 upgrade. I'm using a Realtek onboard soundcard and a Generic USB mixing desk. Audacity came up with the "No Devices Found" error. Tried updating to 2.1.1 but no result. Did a driver update but my system already had the latest drivers. All other audio software had no problem playing or recording.

I did a system restore back to Win7 and all worked perfectly again.

Now that I've found this thread I'll try the Win10 upgrade again and see if installing 2.0.2 gives better results...I'll do it over the weekend so that I have plenty of time to reverse the process if it goes wrong again...unlike this morning when I did the restore in a mad panic!

Interesting to note, my laptop - which also uses Realtek sound drivers did NOT have this problem when upgrading to Win10.

I'll post my results here after I do the upgrade on the desktop.

[cyrano]

I've been following Win 10 update, mostly for audio. Installing the latest drivers for audio or even reinstalling existing ones seems to fix this error for most people.

It seems MS has done a great job on this one. Can't remember any update that had so little problems...

[Gale Andrews]

I was running version 2.1.0 on my desktop system and also had this problem when I did the Win10 upgrade. I'm using a Realtek onboard soundcard and a Generic USB mixing desk. Audacity came up with the "No Devices Found" error. Tried updating to 2.1.1 but no result. Did a driver update but my system already had the latest drivers.

How did you do the driver update? Going to the web site of the computer or motherboard manufacturer is the first choice method.


Gale