Fldigi Audio Error "Port Audio Device not available" After Recent Windows 10 Update
|
Ditto.? I went around the world for days only to find that MS had "helped" me!!! On Sat, 2 Jun 2018, 09:28 , <eric15051@...> wrote: Thank you very much for posting this information. I've spent a couple of days trying to fix the problem, to no avail. It's unbelievable that it was this easy to fix. I really appreciate the information. |
|
Appreciate all the responses. I May have solved a tiny bit of the problem but still working to understand how or why. I see intense W10? learning priority for me. Believe the 'Port Audio Not Available MAY have been started by my selecting an incorrect device. In the Soundcard, Devices, PortAudio drop-down menu for both Capture and Playback if you look far enough there are 3 submenus with apparently identical selections as the 'main'. These are MME devices, Windows DirectSound devices, and Windows WDM-KS devices. Struggling to figure out why my fldigi was not (apparently) connecting to receive audio I think I selected from one of these 3 submenus and shortly thereafter was received the 'Port Audio Not Available' message. I completely uninstalled fldigi reinstalled and solved that problem.?
The reason I thought there was no connection was that the waterfall and other signal indications showed a very high signal level with high audio too and nothing I did with the receive audio from the radio (Flex 6400) including turning off the Flex had any effect on fldigi. Stumbling around I discovered as below in Win10 settings. The yellow highlighted device was set at 100%. Lowering this fixed the level issue. No other adjustment in the Flex settings made any difference. I could shut off the DAX move all the level controls even exit the Flex SmartSDR and this was the only control that had effect. Any help understanding the interplay of Win10 devices and applications with both fldigi and SmartSDR is appreciated. I also note that this device/app appears to be permanently 'in Win10' as it's there when the computer if brought up from a cold boot this morning. Thanks again -- W0MPM John |
|
Hi John, you are right, it seems the problem is when you select incorrect devices. And when start the program it get in a loop and don't let to correct the parameter.?
Maybe it's a bug.
?
I don't tried the reinstall option, but to blank the fields on the config? xml file and it's work!!.
?
I will describe the procedure.
First of all, make a backup of the config file!!?
The procedure it's a your own risk.
?
1) Go to folder C:\Users\ username\fldigi.files
2) The config file it's fldigi_def.xml. make a copy of this!
3) Open the file with any text editor. ex. Notepad or Notepad++
4) Find? <PORTINDEVICE> something</PORTINDEVICE> and erase the? data in the middle.?
After must look like this: <PORTINDEVICE></PORTINDEVICE>
Only erase the data in the middle!!
?
5) Make the same on??<PORTININDEX></PORTININDEX>
and <PORTOUTDEVICE></PORTOUTDEVICE>
and <PORTOUTINDEX></PORTOUTINDEX>
and ALERTDEVICE></ALERTDEVICE>
and <ALERTINDEX></ALERTINDEX> Take care about any wrong character you can delete or add.
Any typo could stop or make an error en the startup of the program.
?
If something goes wrong, you could rollback using the backup file and try again.
?
This will reset to default of configuration on the Port Audio configuration.
This is a screenshoot of my actual config for reference. I'm Using Windows 10 20H2 and Fldigi? 4.1.20.
?
73
Claudio
CX8FS
|
Mitch, AB4MW
John K2CIB
John W0MPM