No DAX audio available for 3rd party apps

k3Tim

I note someone had similar problem, ie., can not access DAX from FLDIGI or WJTX. This occurred after a Windows 10 update. The Flex radio is 6500 - HW Version V3.2.39.3374

Analysis to date:

1). Audio is heard on the Win 10 machine via the PC Audio tab/connection.

2). The sound manager shows Dax channels active (green "Vu" bar graphs active) and audio is heard if "listen to this device is checked".

3). Win10 system Event log does not show any issues.

4). Device mgr shows

5). Uninstalled DAX, reboot, install DAX, reboot - no change (as expected actually).

6). The DAX channels were set to 24bit whereas they are only 16b. I assume this is irrelevant, correct? This same question was asked previously but no reply.

_..--

TiM

JustTheDAXpse.jpg

Mike-VA3MW

Hi Tim

1. DAX and PC audio paths are not related. You can 1 without the other
2. good
3. good
4. ??
5. correct
6. shouldn't be an issue

Your picture didn't show the sound inputs selected for your WSJT. Can you post that please.

You do have Audio leaving the radio on DAX 1, which is good.

You may have an DAX installation corruption issue, but I need to make sure you have the correct sound input selected in WSJT.

73

k3Tim

4). Device mgr shows no obvious problems

GM Mike,

Corrected item #4 and display the sound settings for WSJT

Thanks,

Tim

PS 10 meters is rockin' !

Mike-VA3MW

In your first picture, you are using DAX Audio Stream 1.

In WSJT, you are using DAX Audio Stream 2.

If you change WSJT to RX 1, you should be good to go.

73

k3Tim

Tried uninstalling the RX Dax drivers using the uninstall bat file as well as going into the device manager panel, show hidden devices and removing the Rx audio and RX audio Reserved. Rebooted. Then installed the Rx audio devices using the BAT file, rebooted. Same problem, WSJT, FLDIGI and Spectrum Lab can't open the Dax RX Audio xx devices. (The Green Vu bars are moving on the sound control panel - Playback.

Looked at the details from the latest updates by Microsoft but nothing obvious in them to explain this.

Continuing to troubleshoot.

Mike-VA3MW

Did you see you had the wrong sound input selected?

You had DAX 1 on your radio setup and DAX 2 on your 3rd party app. Based on that, SmartSDR is working as designed.

k3Tim

Hi Mike,

If only it were that easy.... The WSJT would not throw an ErrorBox up based on the incorrect DAX channel selected, but simply display no spectrum. Below is a correction based on your post with the pop-up error box still appearing.

Using Visual Studio debugger the following occurs each time the sound channel is opened. I am exploring the cause.

'wsjtx.exe' (Win32): Unloaded 'C:\Windows\System32\psapi.dll'

The thread 0x38a4 has exited with code 0 (0x0).

The thread 0x4310 has exited with code 0 (0x0).

'wsjtx.exe' (Win32): Loaded 'C:\Windows\System32\rasadhlp.dll'. 

'wsjtx.exe' (Win32): Loaded 'C:\Windows\System32\FWPUCLNT.DLL'. 

avcore\audiocore\client\audioclient\audioclientcore.cpp(1501)\AUDIOSES.DLL!00007FFFE8847415: (caller: 00007FFFE8824FE5) ReturnHr(1) tid(4154) 887C0076 The thread 0x4154 has exited with code 0 (0x0).

The thread 0x3e18 has exited with code 0 (0x0).

The thread 0x4288 has exited with code 0 (0x0).

'wsjtx.exe' (Win32): Loaded 'C:\Windows\System32\psapi.dll'. 

'wsjtx.exe' (Win32): Unloaded 'C:\Windows\System32\psapi.dll'

avcore\audiocore\client\audioclient\audioclientcore.cpp(1501)\AUDIOSES.DLL!00007FFFE8847415: (caller: 00007FFFE8824FE5) ReturnHr(2) tid(1934) 887C0076 The thread 0x1934 has exited with code 0 (0x0).

The thread 0x3af8 has exited with code 0 (0x0).

The thread 0x1268 has exited with code 0 (0x0).

'wsjtx.exe' (Win32): Loaded 'C:\Windows\System32\psapi.dll'.

Mike-VA3MW

Please open a support ticket.

http://helpdesk.flexradio.com

k3Tim

Ticket Opened;

Note- this previous problem seem similar if not identical:

https://community.flexradio.com/discussion/8025557/no-dax-audio-available-for-any-apps

See ya' on the other site.

k3Tim

Follow-Up - Ken @ Flex found the problem.

Privacy settings ==> "Allow apps to access your microphone"

was Off. Need to be On.

Sorry for the bother!

_..--

Tim

KD0RC

Thanks for the update Tim. I wouldn't have thought of that.