Hi, ‘play’ works in Audacity 2.03 after upgrading from Win 8.1 to Win 10, but higher versions (2.05 up) report the InternalPortAudio error.
HPG60 214EM laptop (originally Vista, no drivers from HP for Win 8 up).
Conexant driver, v4.58.01, 2008
No later driver available.
Could I ask, what has changed in Audacity from v2.03 that is relevant to this?
Note: Of all the other varied programs I have installed under Win 8.1, from Aimersoft to Zoom player, so far only Audacity and Ashampoo progs fail as regards the sound card in Win 10.
I’m happy to Have seen Dalchina’s post. Like him, I upgraded to Windows 10, but have had to revert all the way back to v2.03 to get the Audio Devices recognised within Audacity. Windows 10 fully recognises and enables my devices OK, and I’ve not had audio problems with any other software.
The recommended fix is to install Windows 10 drivers (if available) for all the devices you are using (internal and external), obtained from the device manufacturers’ sites. You have not said what devices you have so we can’t comment further on those.
Or go back to your previous version of Windows. If you upgraded over the top of your previous Windows there is a button in the Settings app to go back to previous Windows. The button is there for a month.
Er hum… really, not use Win 10 for the sake of a couple of programs that aren’t compatible? (Ashampoo - noted a couple of programs that failed to find my audio card- and later Audacity programs).
Note: Nero Wave Editor, Cyberlink Wave Editor are fine…
I updated to Windows 10 and Audacity 2.1.1 didn’t work. I upgraded the Realtek High Definition Audio Codecs to R2.79 64-bit for Windows 10 and that did NOT fix the problem.
As Gale told you, "install Windows 10 drivers (if available) for all the devices you are using (internal and external), obtained from the device manufacturers’ sites.
I am using Audacity 2.1.1 on Windows 10. After upgrading my drivers as recommended by another user on this thread and as I specified on another post, Audacity still does not work.
I have many applications that use the sound system. This includes many that are not from Microsoft, such as Total Recorder, Real Player, and even one that I developed. All media applications are working without issues except for Audacity.
This means that the method that Audacity uses to interface with the sound system is inadequate and is the root cause of the problem.
Unfortunately, I depend a lot on Audacity and need its functionality almost daily. I would rather not try to find another application and have to go through its learning curve.
So I am asking that developers please give priority to solving this problem within Audacity itself.
It is obvious that people are migrating to Windows 10 at an unprecedented rate because it is free and the upgrade process is really slick. The impact of this issue is getting geometrically worse.
In other words, the “R2.79” drivers are from the Realtek site. They are generic drivers, not matched to your hardware, as the Realtek site says itself. Audacity may or may not be able to work with them, according to how “matched” they are.
Assuming you have a branded computer, go to their site (Dell, HP or whatever it is) and look for Windows 10 drivers for that specific computer model.
If you are also using an external audio device such as a mixer that depends on hardware-specific drivers, go the site of that device maker and look for Windows 10 drivers.
As an audio device developer I am sure you understand these points.
Audacity depends on the third-party PortAudio API. That API is fairly dependent on the user having appropriate (non-generic) audio drivers and its behaviour can vary according to the drivers that are presented to it.
Please see the system requirements for Audacity 2.1.1. Windows 10 is not yet officially supported.
You have not told us what audio devices you have, but Audacity is highly likely to recognise them if they all have manufacturer’s drivers meant for Windows 10. There is an issue seemingly specific to Windows 10 that if any of the connected devices lack appropriate drivers, current and recent Audacity versions may not recognise any devices, even if some devices do have appropriate drivers.
In other words, try disconnecting any external devices then see if Audacity can recognise the Realtek devices. Perhaps even quit Total Recorder or disable any virtual devices it has that appear in Windows Sound.
Interestingly, I took the advice to downgrade and install 2.0.2. Problem solved no more error messages in Win 10. Another point of interest is that my desktop had Audacity on it before the upgrade to Win 10 and after it still worked and it is 2.1.2. This laptop gave me the audio error when I installed it for the first time after the upgrade to Win 10 from 7. Something your team should look into is why legacy versions work in 10 but in new installs don’t unless you go back to older versions.
Another solution if Windows 10 drivers for your audio device are available would be to install those drivers, as you would when upgrading to any new version of Windows.
Audacity 2.1.2 has not been released yet.
As above, it depends what drivers the audio device on each machine has.
I had the same Win 10 problem previously reported, using the latest version of Audacity. I disconnected my web cam (a Creative model) and rebooted the computer with no external mic connected. Windows did some kind of device install when it restarted without the web cam and I was able to reset Audacity to Windows WASAPI and select my Realtek motherboard sound system for input and output. Works fine now.
I would not expect it to. Driver-finding utilities are at best hit-or-miss, and more typically will infect your computer with adware or worse unless you exercise extreme care. I would run an anti-virus scan after experimenting with any driver update or tune-up apps.
This program is advertising supported and may offer to install third party programs that are not required for the program to run. These may include a toolbar, changing your homepage, default search engine or other third party programs. Please watch the installation carefully to opt out.
The best thing to try first is always to look yourself on the web site of your computer or motherboard manufacturer for the latest Windows 10 audio drivers intended for your computer model.
I’ve been using Slimdriver for a couple of years and it never tried to install any third party programs. The driver updates come from the manufacturer of the products it’s updating from what I’m seeing.
Interestingly, after installing 2.0.2 and running a test on it, I still had 2.1.1 on the computer and now it works as well. Go figure. Fluke?
For what it’s worth, I upgraded from Windows 7 Pro 64-bit to Windows 10 Pro 64-bit. For audio interfaces, I have a Saffire Pro 14, and an Mbox3
I was running Audacity 2.1.1 on Windows 7, and after updating to Windows 10, I am also getting the InternalPortAudio Error. I made sure I am up to date on the audio drivers for both devices.
I uninstalled Audacity several times, including the Reset Preferences.
I then tried Audacity 2.0.6, with the same results.
I then tried Audacity 2.0.3, and it works just fine.
Reaper 5.01 worked fine right off the bat after the Windows 10 upgrade.
Hi Gale, I posted a while back and you stated I had not given the model of my sound card.
I did however quote the exact model of my laptop.
HP G60 214 EM.
For completeness, since Audacity v2.03 works and later versions don’t in Win 10:
Conexant High Definition Smart Audio 221
Driver 4.58.1.0
NVidia High Definition Audio
There is no later driver available that I can find by any means whatsoever.
Many other programs can play audio without problems. Only Ashampoo programs can’t find an audio card in Win 10 (and they worked in Win 8.1 form which I upgraded).
Ashampoo asked me to run several diagnostic programs and acknowledge the issue and are working on it.