Page 3 of 5

Re: InternalPortAudio error since windows 10 update

Posted: Thu Aug 13, 2015 5:45 pm
by dalchina
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.

Thanks

Re: InternalPortAudio error since windows 10 update

Posted: Fri Aug 14, 2015 3:57 pm
by Gale Andrews
dalchina wrote:HPG60 214EM laptop (originally Vista, no drivers from HP for Win 8 up).
So you have old hardware and your manufacturer has not provided fully matched drivers for the operating system you have now upgraded to.
dalchina wrote:Could I ask, what has changed in Audacity from v2.03 that is relevant to this?
Changes that were made to fix other significant problems on some machines.
dalchina wrote: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.
OK. There are supposedly not major changes in the audio architecture of Windows 10, so I would have expected most audio applications to work.


Gale

Re: InternalPortAudio error since windows 10 update

Posted: Sun Aug 16, 2015 2:57 pm
by RichardF
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.

Any idea when Audacity will have the fix?

Thanks

Re: InternalPortAudio error since windows 10 update

Posted: Mon Aug 17, 2015 1:59 pm
by Gale Andrews
RichardF wrote: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.


Gale

Re: InternalPortAudio error since windows 10 update

Posted: Tue Aug 18, 2015 8:53 pm
by dalchina
Thanks for your detailed reply.

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...

Re: InternalPortAudio error since windows 10 update

Posted: Wed Aug 19, 2015 4:59 pm
by ma5carena5
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.

Does anyone have any ideas?

Thanks.

Re: InternalPortAudio error since windows 10 update

Posted: Wed Aug 19, 2015 6:56 pm
by Robert2
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.

Re: InternalPortAudio error since windows 10 update

Posted: Thu Aug 20, 2015 1:48 pm
by ma5carena5
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.

Thanks.

Cordially yours,

Gastón

Re: InternalPortAudio error since windows 10 update

Posted: Thu Aug 20, 2015 4:27 pm
by Gale Andrews
ma5carena5 wrote: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.
Robert2 wrote: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.
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.
ma5carena5 wrote:This means that the method that Audacity uses to interface with the sound system is inadequate and is the root cause of the problem.
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.
ma5carena5 wrote: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.
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.

Failing that, please try Audacity 2.0.2 or 2.0.3 from http://www.oldfoss.com/Audacity.html.


Gale

Re: InternalPortAudio error since windows 10 update

Posted: Thu Aug 27, 2015 3:48 am
by ksgale49
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.

Ken