[600MRG] WSPRX resync question

[John Langridge]

Good info Larry.  Thank you.  While I realize that every system is a little different, perhaps at some point you could make the hacks that you discovered available for public consumption.  It would at least be a starting point for someone seeking to try to solidify WSPR9.

I recall that last summer I spent a lot of time trying to understand the source of choppy TX signal when using 9-x... It was a driver problem and I was forced to use the directX driver rather than my traditional native driver.  That is not the case with 2.11.  The sound mapper selection works great and it looks at the system settings...



<In my opinion 15 minute transmit periods is counter productive

I agree with this 100%.  None of my junk is stable enough over that time frame anyway HI!

73,

John/XIQ/NJD



________________________________
 From: Larry <larry at w7iuv.com>
To: John Langridge <jlangridge at sbcglobal.net> 
Cc: Pat Hamel <pehamel at cableone.net>; SHMRG <600mrg at w7ekb.com> 
Sent: Tuesday, September 3, 2013 11:03 AM
Subject: Re: [600MRG] WSPRX resync question
 


On 03-Sep-13 7:49 AM, John Langridge wrote:

btw, its my understanding from a number of guys that have been
      runing side-by-side tests that WSPR-X is not as sensitive for
      WSPR2.  I run version 2.11 and while I have X loaded here, 2.11 is
      just easier to run for standard beaconing...

John and everybody,

It is my opinion that WSJT9.x, MAP65, WSJT-X, and WSPR-X all have a
    deficiency that Joe and the development team refuse to acknowledge.

There are many reports from the field that claim those programs
    noted above have noticeably lower decode sensitivity than previous
    versions.

Joe claims the decoders are all the same and have been tested
    showing identical decode sensitivities. As best I can tell that
    statement is correct but does not go far enough. As obvious as it
    is, everyone seems to forget that there is much more to these
    programs than just a decoder.

The issues I have discovered are all related to the digital
    interface between the WSJT/WSPR applications and the soundcards
    and/or the radios (in the case of I/Q radios like the softrock,
    etc.)

Sample rates and timing (and phase for I/Q systems) are critical.
    Soundcard drivers/codecs/etc. all pre-process the digital audio in
    some manner and present it to the application. If in the process of
    trying to determine if the driver needs to process
    Dolby/Surround/THX/whatever, the sampling is modified, then the
    WSJT/WSPR application suffers.

I found that soundcard drivers will many times load background
    processes that cause problems with apparent decode sensitivy. These
    process are invisible to the casual user and can only be found by
    digging around in windows and maybe even the registry
In the case of my WSJT9.3 effort, it took several months of fooling
    around before I found and eliminated all those background processes.
    Now WSJT9.3 works flawlessly. I am still working on the MAP65
    installation. With an I/Q system it seems harder or maybe I'm just
    not a good enough windows mechanic to find all the crap.

I see no reason at all to use WSPR-X as long as WSPR 2/2.11 still
    works. In my opinion 15 minute transmit periods is counter
    productive.

73, Larry - W7IUV