I had a test session with one user who can easily reproduce the audio dropouts.
Latency testing shows his system more than capable of handling realtime
audio.I got some timings from the dataSink.The Good plot is a normal/good
decode. One high time period is corrected on the next iteration.The
We need to add one statement here probably
void MainWindow::on_dxCallEntry_textChanged (QString const& call){ m_hisCall =
call; statusChanged(); statusUpdate ();}
Tovoid MainWindow::on_dxCallEntry_textChanged (QString const& call){ m_hisCall
= call; statusChanged(); statusUpdate (); set_da
FWIW I am running both WSJT-X v2 and JTAlert 2.12.10. I rarely shut down
either program and my computer and rig run 24/7. I never have this problem.
Of course saying it just now may cause it to start (Murphy’s Law).
__
Dan – K4SHQ
From: m...@handgunrepairshop.com [mailto:m...@handgun
I have also experienced this logging start time issue many times, at least back as far as v1.8, usually after an aborted/incomplete or abandoned QSO. I have no idea why the previously aborted QSO start time does not clear when the Esc. or F4 key is used to clear the QSO from the DX Call & DX Grid b
This happens to me all the time. When you stop using WSJT-X, then go back a
few hours later, many times it logs the next contact with a start time of when
you last made a contact a few hours earlier. The end time is correct. The QSOs
usually get flagged by eQSL as not being in the log. That's h
Bill,
Thanks for your response. The compound call issue is shared with me by many as
we see. As you mentioned ... after an FT8 exchange, I often send something
like "Aloha fm Virginia" and sometimes I send the grid too. There are some
considerations about that though. Number one - perhaps no
I need some testers for a new hamlib program I'm calling "rigctlcom". It is a
TS-2000 emulator that will allow programs that don't know FLRig or rigctld to
talk to those two programs.
App->COMX->COMY->rigctlcom->rig
This will allow you to run, for example, N1MM and WSJT-X both accessing your
ri
(WSJT-X V2.0.0, W 10 )
This may have been reported before ??
I was on earlier today and made several 80 contacts ending at 1319.
I left the radio running and came back at ~16:17 and changed bands to 17m.
My first contact on 17m was at 16:19 but the logs recorded that contact
time at 13:21.
AL
