JTDX BLANK LINES

[VK4ADC]

What causes blank lines between normal decoded lines?

I will start by stating that I do not use JTDX so some of the following is an assumption based on WSJT-X experience, and JTDX is derived from WSJT-X.

If JTDX doesn't understand/decode a 'line' correctly then it cannot display it correctly.  An instance of this is the likes of 
"191330  -7  0.2 1664 ~  <ZL/OE1HLB> EA5JEG -08" - which in itself should display just fine.

But occasionally both callsigns are in triangular brackets, particularly when in 'contest mode' or when both calls are "specials, extra length", and there may be additional data as well, like serial number and/or grid square details.  That is where I suspect JTDX comes unstuck - because my BandView software has exactly the same issue.  Normal exchanges decode fine but contest exchanges and two extra-length callsigns are not correctly handled and present as blank lines.

There is a way to see exactly what the cause is - if you are quick enough.  
The incoming data is stored in the file ALL.TXT in the C:/Users/**username**/Appdata/Local/JTDX folder ( **username** is YOUR username profile ) but before you access it via the Files / Open Log Directory menu option, after you see these blank lines, quickly press the Monitor button so that it doesn't keep decoding new data.  Then use the menu option noted before, select the ALL.TXT file (double-click) and scroll to the bottom of it (presumably it opened in Windows Notepad) and compare the last correctly-decoded line in JTDX to the lines showing in Notepad. It will be the subsequent decodes that are causing the blank lines in JTDX.

Once you have confirmed the cause, please post the details back here so others have the same info.

Doug VK4ADC