Use Case : A decode cycle is missed due to any number of reasons. Print out
info to that effect to better inform the user what is going on.
1. In my case I had buffer delays at low CPU. Very hard to tell except that
I saw activity in the waterfall and ran a second laptop off the same feed and
verified it should have decoded.
2. No signals or no usable signals present - dead band, different protocols,
full capture but nothing decodable
3. "Monitor" enabled in the middle of a cycle - need enough audio captured
in a cycle to process successfully. At program startup if enabled and when a
user hits the button.
Suggestion: Write out to screen and/or file that nothing happened and why
1. If print blank lines is enabled, print the blank line every cycle, not
just when there was activity decode.
* If there was nothing to decode and no problem detected, print the
equivalent blank line text to a file (like ALL.txt). Add "Nothing to decode"
or similar text.
2. If there was an incomplete audio capture, print to the Activity Window
and a file (like ALL.txt) that a problem exists and append the reason why
(incomplete audio capture for example).
* I see this in JTDX at times like startup.
* Print out the number of buffer requests achieved (such as "Frames 47
of 50" for the values of m_ihsym and m_hsymStop variables. Provides instant
tell of audio dropout issue going on.
Tnx!
Mike K7MDL
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
