While using WSJT-X or DXLab WinWarbler in a mode other than CW or RTTY. If I leave
either application open on the desk top for a while (More than 5 mins)
and come back to it to use it. If I try to transmit the radio will key
but no sound is made. The only way I have found to fix the problem is to
restart the application. This is reproducible.
I have both applications set to use "DAX Audio TX (FlexRadio System" in the sound card settings.
I tried leaving the DAX Control panel open while doing this thinking the TX Streeming botton would be yellow or red but it remains blue.
This has been going on since before the latest SSDR upgrade. I feel it it some sort of Windows thing.
Radio: Flex 6500
Operating Sys: Win10
SSDR: 1.10.8.39
Thanks
73
Kent
NC6B
I have both applications set to use "DAX Audio TX (FlexRadio System" in the sound card settings.
I tried leaving the DAX Control panel open while doing this thinking the TX Streeming botton would be yellow or red but it remains blue.
This has been going on since before the latest SSDR upgrade. I feel it it some sort of Windows thing.
Radio: Flex 6500
Operating Sys: Win10
SSDR: 1.10.8.39
Thanks
73
Kent
NC6B
Posted 3 years ago
Jay
I never see anything pop up, no errors or security warnings so I would have to say that it is not a file permission problem. Just no sound.
Thanks
Kent
NC6B
I never see anything pop up, no errors or security warnings so I would have to say that it is not a file permission problem. Just no sound.
Thanks
Kent
NC6B
Kent
I'll be looking into reproducing the problem. I haven't seen it yet, but I'm going to be looking into Winwarbler in hopes it might be a solution for multi-slice digital app logging. So I might run into the same difficulties.
SDRgadgets
I'll be looking into reproducing the problem. I haven't seen it yet, but I'm going to be looking into Winwarbler in hopes it might be a solution for multi-slice digital app logging. So I might run into the same difficulties.
SDRgadgets
73, Jay - NO5J
Jay
WW is a great program. I started using the DXLabs suite about a year ago. The support is great!
I may call FRS tomorrow and see if they have a fix for my problem.
Thanks
Kent
NC6B
WW is a great program. I started using the DXLabs suite about a year ago. The support is great!
I may call FRS tomorrow and see if they have a fix for my problem.
Thanks
Kent
NC6B
I wonder if another application has taken control of DAX Audio TX. I'm not sure how to check that. At least make sure the Sound/Playback/DAX Audio TX configuration is not set to default (no check). I did a little googling but only found a mention of iTunes grabbing control. That post was pretty old so I'd suspect any oddity has been resolved by now.
Tim - W4TME, Customer Experience Manager
A few questions...
Are any of the DAX sound devices be marked by Windows as the default sound device? If so, this could be causing your issue.
Also, does simply shutting down WSJT and restarting it fix the issue? If so, then I'd focus my attention on that rather than a DAX issue.
If shutting down WSJT does not fix the issue, but shutting down the DAX control panel and restarting it fixes the issue, then I'd start investigating the possibility that your PC is experiencing some long duration DPC errors that may be causing some buffer corruption issues. Windows really isn't a good operating system for handling real-time audio and DPCs can exacerbate the problem.
Are any of the DAX sound devices be marked by Windows as the default sound device? If so, this could be causing your issue.
Also, does simply shutting down WSJT and restarting it fix the issue? If so, then I'd focus my attention on that rather than a DAX issue.
If shutting down WSJT does not fix the issue, but shutting down the DAX control panel and restarting it fixes the issue, then I'd start investigating the possibility that your PC is experiencing some long duration DPC errors that may be causing some buffer corruption issues. Windows really isn't a good operating system for handling real-time audio and DPCs can exacerbate the problem.
Tim
Something was very strange. I checked my Windows default devices in Playback and Recording. Under Recording the default device was DAX Audio TX. I know I had set it to the Mic on a webcam that I have a few months back. I changed back to the webcam and restarted the PC. After the restart DAX Audio TX is now under the Playback tab. Is that where it is suppose to be?
I will speculate that when I did the SSDR 1.9.13 install, back in October, Windows changed the default device to DAX Audio TX in the Playback ( I really hate Windows) and that is when the problem started.
As for the problem I will leave WW open for a while and comeback and check in a bit. I will post later this afternoon to confirm the problem is solved.
Thanks
73
Kent
NC6B
Something was very strange. I checked my Windows default devices in Playback and Recording. Under Recording the default device was DAX Audio TX. I know I had set it to the Mic on a webcam that I have a few months back. I changed back to the webcam and restarted the PC. After the restart DAX Audio TX is now under the Playback tab. Is that where it is suppose to be?
I will speculate that when I did the SSDR 1.9.13 install, back in October, Windows changed the default device to DAX Audio TX in the Playback ( I really hate Windows) and that is when the problem started.
As for the problem I will leave WW open for a while and comeback and check in a bit. I will post later this afternoon to confirm the problem is solved.
Thanks
73
Kent
NC6B
Tim - W4TME, Customer Experience Manager
First off, without knowing which sound devices you have installed and active in your PC, I can't say is what you have configured is "right". It is recommended that none of the DAX sound devices be your default sound device.
Windows will enumerate the sound devices and reassign the default device any time there is a change in the installed sound devices. This is why I am so adamant about not uninstalling DAX when you remove a version of SmartSDR so a re-enumeration is never triggered.
Windows has this annoying feature of not making a sound device active unless it is physically installed, so if you plug a mic into your PC sound card, that port becomes active and Windows re-enumerates all the installed sound devices. This is why I keep a pair of headphones plugged into my PC sound card all the time and designate them as the default sound devices.
Windows will enumerate the sound devices and reassign the default device any time there is a change in the installed sound devices. This is why I am so adamant about not uninstalling DAX when you remove a version of SmartSDR so a re-enumeration is never triggered.
Windows has this annoying feature of not making a sound device active unless it is physically installed, so if you plug a mic into your PC sound card, that port becomes active and Windows re-enumerates all the installed sound devices. This is why I keep a pair of headphones plugged into my PC sound card all the time and designate them as the default sound devices.
Tim
Stopping and starting DAX did not fix the problem.
Stopping and starting DAX did not fix the problem.
Tim - W4TME, Customer Experience Manager
OK. That tells me that the issue has something to do with WSJT. I'd try a different program like Fldigi to see if it has a problem to verify.
The problem happens in WinWarbler and WSJT-X.
Tim - W4TME, Customer Experience Manager
Try Fldigi. It is the program we use as a validator in support because it works very reliably.
Ok I have Fldigi going and have tested that I can transmit and the sound is being sent out DAX Audio TX. I have rebooted the PC now I will let things sit for 15mins and come back.
Kent
Kent
Tim - W4TME, Customer Experience Manager
That is a step in the right direction. GL OM.
Sorry I called away.
So using Fldigi, The problem does not happen. I have checked several times now and I do not lose the audio. Im not sure what this means. Is the problem with DXLab, WSJT-X, WinWarbler ot Windows?
Kent
So using Fldigi, The problem does not happen. I have checked several times now and I do not lose the audio. Im not sure what this means. Is the problem with DXLab, WSJT-X, WinWarbler ot Windows?
Kent
_large.jpg)
Kent,
I'm also running a 6500, V1.10.8.3, Win10
WSJT-X, Winwarbler 8.8.7 (and the rest of the DXLabs suite) and N1MM
I have not seen any issues with audio output switching from device to device at any time. I don't run WSJT-X much, but Winwarbler is up pretty much 24/7.
I just left WJST-X up (Winwarbler up at the same time) for the last 20 minutes, transmitted as it should.
I do have the speakers in one of my monitors set as the default playback device.
This info may be of zero help, but our setup is similar, so I'm throwing it out there.
Tom
I'm also running a 6500, V1.10.8.3, Win10
WSJT-X, Winwarbler 8.8.7 (and the rest of the DXLabs suite) and N1MM
I have not seen any issues with audio output switching from device to device at any time. I don't run WSJT-X much, but Winwarbler is up pretty much 24/7.
I just left WJST-X up (Winwarbler up at the same time) for the last 20 minutes, transmitted as it should.
I do have the speakers in one of my monitors set as the default playback device.
This info may be of zero help, but our setup is similar, so I'm throwing it out there.
Tom
Tom
Thanks.
I think at this point it may be a Windows problem that I may just have to live with.
Kent
Thanks.
I think at this point it may be a Windows problem that I may just have to live with.
Kent
Tim - W4TME, Customer Experience Manager
I believe this points the WSJT and DXLab WinWarbler as the place to start looking for the gremlins.
Two different applications built with two different tools sets, with no other reports of this behavior from other users of these applications?
Exactly what is it that these two applications could be doing to cause this behavior, Tim?
Exactly what is it that these two applications could be doing to cause this behavior, Tim?
Tim - W4TME, Customer Experience Manager
We have had and continue to receive multiple reports of this type behavior with WSJT apps. As a matter of fact, in Support, WSJT is the most reported app having audio issues. I wish I knew what the issue was, but we just don't have the resources to dig into problems with third-party apps.
I suspect it may have something to do with the type or version of the audio APIs the apps are using. I believe WSJT is using PortAudio.
I suspect it may have something to do with the type or version of the audio APIs the apps are using. I believe WSJT is using PortAudio.
(Edited)
Tim
Don't forget the Human element, aren't many of the trouble reports related to that?
Prove me wrong people!
SDRgadgets
Don't forget the Human element, aren't many of the trouble reports related to that?
Prove me wrong people!
SDRgadgets
73, Jay - NO5J
What action could an application take to cause the switch in DAX selection that Kent reports?
"I can see in the Sound Window that the level is moving on "DAX Audio TX". After a while I try to transmit and the level no longer moves on the "DAX Audio TX" but the level now moves on "DAX RESERVED MIC AUDIO".
"I can see in the Sound Window that the level is moving on "DAX Audio TX". After a while I try to transmit and the level no longer moves on the "DAX Audio TX" but the level now moves on "DAX RESERVED MIC AUDIO".
Tim - W4TME, Customer Experience Manager
When DAX is working properly, both ends of the audio conduit, the RESERVED device, and the non-reserved device will show audio levels in the Windows Sound Control panel. If audio is not seen on the non-reserved side of the audio conduit, then this usually indicates that something with the third-party application side has failed. In the description, once this happens only restarting the third-party digital app restore the connection.
Jay - the audio setup is straightforward; you set the input and the output to the appropriate sound device. There are usually no other parameters to set (mess up).
Dave, like I said, I don't know what is wrong. Apps like Fldigi just work and work reliably unless there is audio buffer corruption due to long duration DPCs. But we do not get reports of Fldigi just acting weird like this or stop working altogether. Others do not. It does not indicate something being systemically broken in DAX.
Jay - the audio setup is straightforward; you set the input and the output to the appropriate sound device. There are usually no other parameters to set (mess up).
Dave, like I said, I don't know what is wrong. Apps like Fldigi just work and work reliably unless there is audio buffer corruption due to long duration DPCs. But we do not get reports of Fldigi just acting weird like this or stop working altogether. Others do not. It does not indicate something being systemically broken in DAX.
(Edited)
Tim
To err is Human, insisting your right, is a known Human error. Maybe I'm wrong about that too. Can I blame others for that? Once in awhile maybe. But, the laughter is upsetting. YMMV, but my mileage gets me somewhere.
SDRgadgets
To err is Human, insisting your right, is a known Human error. Maybe I'm wrong about that too. Can I blame others for that? Once in awhile maybe. But, the laughter is upsetting. YMMV, but my mileage gets me somewhere.
SDRgadgets
73, Jay - NO5J
Tim - W4TME, Customer Experience Manager
To quote from Scarlet Begonias by the Grateful Dead...
"I Well, I ain't always right but I've never been wrong.
Seldom turns out the way it does in a song.
Once in a while you get shown the light
In the strangest of places if you look at it right."
"I Well, I ain't always right but I've never been wrong.
Seldom turns out the way it does in a song.
Once in a while you get shown the light
In the strangest of places if you look at it right."
(Edited)
Tim
I know Dave AA6YQ is watching this and my observation is the only thing in common with the 2 applications is they are controlled by DXLab.
I think the next thing I try will be to set up WSJT-X in a standalone setup and see if the problem happens.
As a last resort I may format the drive and do a clean install of windows.
Thanks
Kent
I know Dave AA6YQ is watching this and my observation is the only thing in common with the 2 applications is they are controlled by DXLab.
I think the next thing I try will be to set up WSJT-X in a standalone setup and see if the problem happens.
As a last resort I may format the drive and do a clean install of windows.
Thanks
Kent
Tim - W4TME, Customer Experience Manager
I think formatting the drive and doing a clean install of Windows is an extreme step at this point. Your "divide and conquer " troubleshooting technique is the best course of action.
Tim
As I said "last resort" and Im not there yet!
Thanks
Kent
As I said "last resort" and Im not there yet!
Thanks
Kent
Tim, I didn't ask you what was wrong, I asked you what action on the part of an application would cause DAX to behave in the manner that Kent has reported. Commander does direct a Flex 6000 to transmit via DAX 1 or DAX 2 as a function of split and the state of transmit/receive.
Kent, in a post earlier in this thread, you said that the problematic behavior first appeared "when I did the SSDR 1.9.13 install, back in October". Have you tried reverting to the version of SSDR you were using before you made this change?
Kent, in a post earlier in this thread, you said that the problematic behavior first appeared "when I did the SSDR 1.9.13 install, back in October". Have you tried reverting to the version of SSDR you were using before you made this change?
I left my radio and PC running over night with WSJT-X on. I tried to transmit this morning and the problem happened again.
Dave, I have just downgraded SmartSDR to the previous version 1.9.13 and will try to reproduce the problem. If the problem happens I will downgrade again and see what happens.
Thanks
Kent
Dave, I have just downgraded SmartSDR to the previous version 1.9.13 and will try to reproduce the problem. If the problem happens I will downgrade again and see what happens.
Thanks
Kent
Tim
Is there a way to tell if the DAX Audio TX has been turned off by Win10??
Kent
Is there a way to tell if the DAX Audio TX has been turned off by Win10??
Kent
Tim - W4TME, Customer Experience Manager
Not that I am aware of.
Well, there is a way to tell if Windows considers a driver disabled.
Go to Device Manager. First look for your devices in Audio inputs and outputs. Double click on one of the devices and check the Device status. It should say "This device is working properly."
A disabled device would have a status such as: "This device is disabled. (Code 22) Click Enable Device to enable this device."
While you are at it, scroll down on the list to Sound, video and game controllers and check the FlexRadio Systems audio devices there.
Also check you don't have any conflicts or unknown devices. This is usually indicated with a "!" beside the device. I think you are going to find everything is enabled properly. This doesn't sound like something Windows is doing on purpose.
I've been following the thread. I have always had a problem with WSJT-X where, randomly, it would just stop sending any tones. The rig would key and everything would look good except the power was way way down and there would obviously be no audio. For me, it doesn't happen on schedule. Maybe once every day or two or three. Restarting WSJT-X brings it back to life. I don't use WinWarbler so I can't tell you if the same happens to me. I do use fldigi and I cannot recollect an audio out problem with that.
Tim mentions above WSJT-X might use PortAudio. Not sure why he mentioned it or if there's a clue there. Fldigi uses PortAudio also.
Go to Device Manager. First look for your devices in Audio inputs and outputs. Double click on one of the devices and check the Device status. It should say "This device is working properly."
A disabled device would have a status such as: "This device is disabled. (Code 22) Click Enable Device to enable this device."
While you are at it, scroll down on the list to Sound, video and game controllers and check the FlexRadio Systems audio devices there.
Also check you don't have any conflicts or unknown devices. This is usually indicated with a "!" beside the device. I think you are going to find everything is enabled properly. This doesn't sound like something Windows is doing on purpose.
I've been following the thread. I have always had a problem with WSJT-X where, randomly, it would just stop sending any tones. The rig would key and everything would look good except the power was way way down and there would obviously be no audio. For me, it doesn't happen on schedule. Maybe once every day or two or three. Restarting WSJT-X brings it back to life. I don't use WinWarbler so I can't tell you if the same happens to me. I do use fldigi and I cannot recollect an audio out problem with that.
Tim mentions above WSJT-X might use PortAudio. Not sure why he mentioned it or if there's a clue there. Fldigi uses PortAudio also.
Kevin
When it does happen go look in the Windows Sound Control panel. Look at the level meters when you try to transmit. Mine switches from the DAX Audio TX to DAX RESERVED MIC AUDIO. I suspect yours will be the same. Like this:
Kent
When it does happen go look in the Windows Sound Control panel. Look at the level meters when you try to transmit. Mine switches from the DAX Audio TX to DAX RESERVED MIC AUDIO. I suspect yours will be the same. Like this:
Kent
I'm keeping my sound settings open. If I see the same symptoms I'll report back here.
Tim - W4TME, Customer Experience Manager
Kent - What is the default device in your recording tab?
Tim
It is a Microphone on a USB Webcam that I have.
Kent
It is a Microphone on a USB Webcam that I have.
Kent
Tim - W4TME, Customer Experience Manager
Open your DAX control panel. Do you have the Mic Stream channel ON? If so this is why you are seeing audio on the DAX end of the Mic Stream audio conduit.
Tim
No the button for the Mic Stream says off.
Kent
No the button for the Mic Stream says off.
Kent
Tim - W4TME, Customer Experience Manager
Now that is very interesting. The Mic Stream DAX channel is audio that comes from the radio's audio input. This input can be DAX or a microphone. If the Mic Stream DAX channel is enabled and there is a valid audio input, then you will see audio levels indicated on the DAX RESERVED MIC AUDIO device (playback) and on the DAX Mic Audio device (recording) in the Windows Sound Control panel. This is normal and is to be expected. If you turn off the Mic Stream channel in the DAX Control Panel, then you will no longer see audio levels in the Windows Sound Control panel.
Now if you are seeing audio levels indicated indicated on the DAX RESERVED MIC AUDIO device (playback) and on the DAX Mic Audio device (recording) in the Windows Sound Control panel when the Mic Stream DAX channel is off, and you did not make any changes to the radio, either manually or via a third-party application that can control the radio (CAT or an app using the FlexLib API), then something has messed with the DAX audio devices.
This is why I made a reference to PortAudio previously. Windows allows multiple audio APIs to manipulate sound devices. It is possible PortAudio has opened the DAX RESERVED MIC AUDIO device and is passing an audio bit-stream audio to it.
There is another possibility and this one is probably a little more plausible. You are using a USB audio device and it is your default device in the recording tab. This is a transient device, meaning that is it becomes disconnected, be it from powering down, physically disconnected or some other way, Windows is going to re-enumerate the audio devices. If this happens and the third-party app is assigning an audio pin (sound device) based on an index number, then it is very possible that the third-party app is not handling the state change well and could end up reassigning the audio output and passing audio down a different device in the playback tab, like the DAX RESERVED MIC AUDIO device. Bluetooth headsets and USB speakers are also transient audio devices.
If possible, what I'd to test this is to connect a set of speakers and a mic to the PC's embedded sound card and assign them as the default recording and playback devices. This configuration will not change and should prevent the
re-enumeration and subsequent reassignment of the Windows sound devices; essentially a more stable configuration. If this shows positive results, then I think the trigger mechanism has been found. The fix would be a fix to the third-party digital mode app to handle these re-enumeration state changes better.
Now if you are seeing audio levels indicated indicated on the DAX RESERVED MIC AUDIO device (playback) and on the DAX Mic Audio device (recording) in the Windows Sound Control panel when the Mic Stream DAX channel is off, and you did not make any changes to the radio, either manually or via a third-party application that can control the radio (CAT or an app using the FlexLib API), then something has messed with the DAX audio devices.
This is why I made a reference to PortAudio previously. Windows allows multiple audio APIs to manipulate sound devices. It is possible PortAudio has opened the DAX RESERVED MIC AUDIO device and is passing an audio bit-stream audio to it.
There is another possibility and this one is probably a little more plausible. You are using a USB audio device and it is your default device in the recording tab. This is a transient device, meaning that is it becomes disconnected, be it from powering down, physically disconnected or some other way, Windows is going to re-enumerate the audio devices. If this happens and the third-party app is assigning an audio pin (sound device) based on an index number, then it is very possible that the third-party app is not handling the state change well and could end up reassigning the audio output and passing audio down a different device in the playback tab, like the DAX RESERVED MIC AUDIO device. Bluetooth headsets and USB speakers are also transient audio devices.
If possible, what I'd to test this is to connect a set of speakers and a mic to the PC's embedded sound card and assign them as the default recording and playback devices. This configuration will not change and should prevent the
re-enumeration and subsequent reassignment of the Windows sound devices; essentially a more stable configuration. If this shows positive results, then I think the trigger mechanism has been found. The fix would be a fix to the third-party digital mode app to handle these re-enumeration state changes better.
Tim
Ok I have an old headset that I can hookup to the plugs directly on the sound card. I will then reboot the PC and if the mic and headphones have not been assigned as default I will make them that way then reboot again just to be safe.
I will let you know the results.
Kent
Ok I have an old headset that I can hookup to the plugs directly on the sound card. I will then reboot the PC and if the mic and headphones have not been assigned as default I will make them that way then reboot again just to be safe.
I will let you know the results.
Kent
Tim - W4TME, Customer Experience Manager
Thanks. Fingers crossed.
Tim
No joy!
The audio still switches to DAX RESERVED MIC AUDIO.
Do you think I should uninstall Smart SDRand then reinstall? Do you think it will make a difference??
Kent
No joy!
The audio still switches to DAX RESERVED MIC AUDIO.
Do you think I should uninstall Smart SDRand then reinstall? Do you think it will make a difference??
Kent
Tim - W4TME, Customer Experience Manager
Drats. It was a good working theory. I do not think reinstalling SmartSDR is going to make a difference. Let me think on it for a little while.
Tim - W4TME, Customer Experience Manager
So I have thought on this overnight. I looked at WSJT-X and it is using v5 of QT Multimedia Version 5.5 to be specific. The latest version is 5.7. I have no idea if this is a factor or not, as I have not found a changelog to look at the differences between 5.5 and 5.7.
I do not think reinstalling SmartSDR (specifically DAX and the virtual audio drivers) will make any difference. If you were seeing the same type of issue with all applications where you can assign DAX sound devices to them, then I'd be more inclined to take this approach.
I installed the latest version of WSJT-X last night and have been running it in WSPR mode for a little over 12 hours and it just works.
I do have one question. Are you doing any band hopping? That may be a trigger (I am not doing band hopping).
I do not think reinstalling SmartSDR (specifically DAX and the virtual audio drivers) will make any difference. If you were seeing the same type of issue with all applications where you can assign DAX sound devices to them, then I'd be more inclined to take this approach.
I installed the latest version of WSJT-X last night and have been running it in WSPR mode for a little over 12 hours and it just works.
I do have one question. Are you doing any band hopping? That may be a trigger (I am not doing band hopping).
Tim
I mainly use WSJT-X for JT65 and JT9 so no band hopping.
Could a transmit profile that I created be causing this. I created a transmit profile for WSJT-X that I just noticed was in the Global profile also. I did not make the one in Global. I have deleted both profiles in Global and Transmit. I am now going to try things out.
If that does not work Im going to uninstall and reinstall SSDR and DAX. It wont hurt to try.
Kent
I mainly use WSJT-X for JT65 and JT9 so no band hopping.
Could a transmit profile that I created be causing this. I created a transmit profile for WSJT-X that I just noticed was in the Global profile also. I did not make the one in Global. I have deleted both profiles in Global and Transmit. I am now going to try things out.
If that does not work Im going to uninstall and reinstall SSDR and DAX. It wont hurt to try.
Kent
Tim - W4TME, Customer Experience Manager
There is very little interaction in the profiles with DAX other than assigning a slice to a channel. The problem here is that WSJT-X is sending data to the wrong sound device (think sound card). I'd be interested to know if the reinstall helps.
Well it was a long shot but it did not work.
When I uninstall SSDR and DAX should I uninstall all versions of SSDR? I have 3 versions installed now. Also do I uninstall Flex VSP separately or does it uninstall with SSDR?
Kent
When I uninstall SSDR and DAX should I uninstall all versions of SSDR? I have 3 versions installed now. Also do I uninstall Flex VSP separately or does it uninstall with SSDR?
Kent
I have uninstalled everything to do with SSDR.
One obsevation, After the reinstall of SSDR v1.10.8 the default playback sound device was changed to DAX RESERVED MIC AUDIO. I changed it back to the speakers I have connected to the rear of the PC. The default device in Recording was not changed from the mic on my headset.
Kent
One obsevation, After the reinstall of SSDR v1.10.8 the default playback sound device was changed to DAX RESERVED MIC AUDIO. I changed it back to the speakers I have connected to the rear of the PC. The default device in Recording was not changed from the mic on my headset.
Kent
Tim - W4TME, Customer Experience Manager
Here is the procedure for removing all of SmartSDR.
https://helpdesk.flexradio.com/hc/en-us/articles/204975589-How-to-do-a-Complete-uninstall-of-SmartSD...
The reassignment of the default playback device is all due to Windows mucking with things when sound devices are disabled or removed.
https://helpdesk.flexradio.com/hc/en-us/articles/204975589-How-to-do-a-Complete-uninstall-of-SmartSD...
The reassignment of the default playback device is all due to Windows mucking with things when sound devices are disabled or removed.
Tim
I have uninstalled and reinstalled SSDR and DAX according to the directions above.
I am optimistic, I have had WinWarbler open for an hour now and it continues to transmit with audio. I will leave the radio on for a few hours and comeback and give it a check.
Kent
I have uninstalled and reinstalled SSDR and DAX according to the directions above.
I am optimistic, I have had WinWarbler open for an hour now and it continues to transmit with audio. I will leave the radio on for a few hours and comeback and give it a check.
Kent
Tim
Now after a few hours the problem has not happened again.
If it happens again Im going to put a different SSD in my PC and install everything from scratch.
Thanks for sticking with it!!
73
Kent
NC6B
Now after a few hours the problem has not happened again.
If it happens again Im going to put a different SSD in my PC and install everything from scratch.
Thanks for sticking with it!!
73
Kent
NC6B
If it helps, I've had the same issue as the original poster describes but on my 6700 for at least 6 months. After much tinkering, I found that exiting DAX and restarting instantly solves the issue. But, I don't know what technically causes the issue.
Mark
The issue is solved on mine. It was fairly painless. Just completely uninstall SSDR as described above.
Kent
The issue is solved on mine. It was fairly painless. Just completely uninstall SSDR as described above.
Kent
After taking the above steps the problem is NOT fixed. I still do not have sound after leaving WW or WSJT-X open for a time.
Kent
Kent
Here is what I found.
I open the Sound window. I scroll down to "DAX Audio TX". When I first open WinWarbler and transmit all is fine. I can see in the Sound Window that the level is moving on "DAX Audio TX". After a while I try to transmit and the level no longer moves on the "DAX Audio TX" but the level now moves on "DAX RESERVED MIC AUDIO".
Why is the audio changing from one to the other??
Kent
I open the Sound window. I scroll down to "DAX Audio TX". When I first open WinWarbler and transmit all is fine. I can see in the Sound Window that the level is moving on "DAX Audio TX". After a while I try to transmit and the level no longer moves on the "DAX Audio TX" but the level now moves on "DAX RESERVED MIC AUDIO".
Why is the audio changing from one to the other??
Kent
Click on recording then double click DAX Audio TX then Listen tab and click on Listen to this device and your transmit audio will play out the computer speaker.
Something else.
If I change the soundcard settings in WinWarbler to "DAX RESERVED MIC AUDIO", thinking the audio would then happen it does not. The level now moves on "DAX RESERVED IQ RX 4".
Kent
If I change the soundcard settings in WinWarbler to "DAX RESERVED MIC AUDIO", thinking the audio would then happen it does not. The level now moves on "DAX RESERVED IQ RX 4".
Kent
Bill
That did not work. No sound was played through the speakers.
Kent
That did not work. No sound was played through the speakers.
Kent
Do you have a PC speaker or headphones plugged into the computer and designated as the default device?
Tim - W4TME, Customer Experience Manager
NEVER USE THE RESERVED DAX DEVICES. Theses are the ends of the virtual audio conduit that is connected to DAX. The other end (not reserved) is connected to your digital mode app.
SRI picked the wrong one for the snippet
(Edited)
Reading this old post I am suffering from this now.
After monitoring only every 14 min I loose control of decoding in both PSK31, JT65 ETC
Does the upgrade to V2.0 fix this issue?
Ian
After monitoring only every 14 min I loose control of decoding in both PSK31, JT65 ETC
Does the upgrade to V2.0 fix this issue?
Ian
Tim - W4TME, Customer Experience Manager
No, it does not. This problem has been linked to long duration DPCs on the PC running DAX. If this is your issue, you can try to take mitigating action to resolve the condition.
Here are some relevant HelpDesk articles on the subject.
https://helpdesk.flexradio.com/hc/en-us/articles/202118398-What-are-DPCs-and-why-do-they-matter-
https://helpdesk.flexradio.com/hc/en-us/articles/202118698-Using-LatencyMon-to-collect-DPC-Latency-D...
Here are some relevant HelpDesk articles on the subject.
https://helpdesk.flexradio.com/hc/en-us/articles/202118398-What-are-DPCs-and-why-do-they-matter-
https://helpdesk.flexradio.com/hc/en-us/articles/202118698-Using-LatencyMon-to-collect-DPC-Latency-D...
Ian
I pulled my hair out for a long time with this. The only way I found to fix the problem was to reinstall Win10. It was fairly painless. I just backed up my personal files but if you go through Win 10 settings then "Update & security then "Recovery" It will keep all of your files in their original locations. When I reinstalled the programs most of my file were still there so it was not that hard to get things going again. It was just time consuming. The problem has not come back since.
Sorry!
Good luck
73 Kent
NC6B
I pulled my hair out for a long time with this. The only way I found to fix the problem was to reinstall Win10. It was fairly painless. I just backed up my personal files but if you go through Win 10 settings then "Update & security then "Recovery" It will keep all of your files in their original locations. When I reinstalled the programs most of my file were still there so it was not that hard to get things going again. It was just time consuming. The problem has not come back since.
Sorry!
Good luck
73 Kent
NC6B
Thanks Kent appreciate the info
Tim
Thanks for those tips and program I was able to track down the problem the past 3 hours all is working well.
Ian
Thanks for those tips and program I was able to track down the problem the past 3 hours all is working well.
Ian
Tim - W4TME, Customer Experience Manager
Excellent. Hunting down DPC culprits can be a challenge. Congratulations on your initial success.