Using the reference spectrum discards a short part of the front of the
period's received samples which may have contained a decode candidate.
As far as the MSK modes are concerned the reference spectrum
correction is probably not applicable anyway.
Comment from Steve K9AN after offline discussions about this:
"In any case, I don’t think that there is any reason to apply the
reference spectrum correction to the MSK modes. I do think that we are
paying a performance penalty in the MSK modes for non-ideal filter
responses at the TX and RX ends of the link — but we would need to
implement an equalizer that looks at the received sync words as a
“training sequence” in order to come up with anything that could
improve the results. This would take into account the receiver and
transmitter filters, and would probably be different for every
TX/RX/meteor burst. My current thinking is that for the low SNRs that
we are most interested in, and with the short sync words that we use,
we wouldn’t be able to do a very good job of estimating the
coefficients of the equalizer..."
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@6776 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Move the FFTW3 cleanup into the main routine as it should only be
called once rather than every time the settings configuration is
changed or reset (MultiSettings).
Call the new fini_ldpc_ routine before exiting in the main routine to
free the LDPC resources.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@6764 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
These include the wide graph window not being suppressed when starting
the application in a fast mode.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@6762 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Qt does its best job laying out widgets consistently across platforms
if all unecessary constraints are removed. Widget layout policies can
almost always be used to achieve the required layout without reverting
to hard coded pixel values.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@6759 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
These were discovered when running under teh valgrind MemCheck tool. I
have also checked in a suppressions file (wsjtx-valgrind.linux.supp)
suitable for use on Linux when running the valgrind MemCheck tool.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@6755 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Highlight, in the CQ colour, CQDX ... and QRZ ... messages and
process correctly for worked before and DXCC entity.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@6753 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Refactor the save WAV file routine to return an error string as a
promise and then get that result and report in a QMessageBox.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@6752 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
The BWFFile class correctly indicates errors like file access issues
and problems reading or writing headers using the BWFFile::error() and
BWFFile::errorString() operations.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@6751 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Pass file path for peg-128 files to fast_decode(). (Inelegant, but it works.)
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@6741 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
save, to avoid what appears to be a stack overflow on Windows.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@6728 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
