Same here and I have had this happen many times when preselecting (setting up to call a wanted station) on a split and then TX but no audio so it not necessarily a instant change that triggers this. I have two sounds cards built in and add on and it does this with either as source. Both with cable connected audio. WA4MIT Morris On Friday, December 14, 2018, 4:29:47 PM CST, Bill <brightl...@gmail.com> wrote: I have also reported this problem several times but have never received any responses as to why this is happening. This is not windows specific since it happens to me on both Mac and PC. It also isn't related to version number since it happens with the older 1.9.1 and newer 2.0 versions. It happens to me with a radio (FT991A) with a built in sound card and also a radio (FT1000MP) using an external MicroHamUSB III interface. The only thing that seems to apply is that it usually happens when I change my transmit frequency slot. The transmitter keys but no audio. This is fixed by immediately hitting halt tx then going back to enable. This isn't a very common occurrence but it does happen to me at least several time a week, of course especially when I am trying to work a new dx! 73 Bill - AK6A On Fri, Dec 14, 2018 at 2:01 PM Morris Wideman via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:
I agree this phenomenon has been with me for a long time now, stopping TX and restarting resumes the audio. No one has provided a reason or fix. It does not seem to follow any particular pattern that I have been able to pin down.73 Morris WA4MIT On Friday, December 14, 2018, 2:20:19 PM CST, Al Pawlowski <k6...@almont.com> wrote: The occasional “no audio” on Tx has been around since I started using WSJT-X a couple of years ago. Usually, just disabling Tx and reenabling fixes the problem until next time - it has been so seldom for me that I have just ignored it. I use an ANAN-100B with OpenSDRmrx now. However, I think this happened when I was using a USB Signal Link and Icom 745. Closing WSJT-X also recovers normal Tx. However, it does take some seconds for all of WSJT’s tasks to stop after the window closes. OpenSDRmrx also takes several seconds after its window closes to completely shutdown. Seems like a Windows thing. I am using Windows 10 Home now on a 2.4GHz I5, but it was the same on Windows 7pro and Windows 10pro on a 3.2GHz I3. Al Pawlowski, K6AVP Los Osos, CA USA Date: Fri, 14 Dec 2018 18:28:58 +0000 From: David Fisher <dsfis...@outlook.com> To: WSJT software development <wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] TX function lost, then have Task Manager problem I run a FLEX 6600 and I see it too. This problem has been around for a while; it is not due to the WSJT protocol change. Since the transmitter engages we know that the transmit command is getting through the CAT system to the radio. I?m not aware of any evidence of a problem like this occurring in other modes, SSB for instance. That suggests that DAX is not getting the signal through to the radio. It would be interesting to learn if RTTY and PSK users ever see an error like this. I?ve never heard of one. If all of that is true (we?re guessing now) then the WSJT/DAX channel interface looks suspicious. Like Al, I?ve seen the stuck WSJT and have had to kill them off by hand. I haven?t noticed the CPU spinning, but I haven?t looked for it. Dave / NX6D _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel