Al, I suggest FSTW4 - 300s. I sometimes transmit that mode overnight, but tend to go back to WSPR just because not enough stations are decoding and reporting the new mode. I run three decoders on the same audio stream - FST4 - 60, FST4W - 300 and WSPR. 73, Glen W6GJB
On Tue, Nov 17, 2020 at 10:12 AM alawler mudhawk.com <alaw...@mudhawk.com> wrote: > HI Folks, > > I'm a bit late to the release candidate party. In addition to FT-8, I > have several SDR's that run wspr fulltime, and am anxious to devote some > of my receivers to fst4w. > > Looking at the UI, there are many now different possible TR intervals > for FST4w, and it exists alongside wspr as a separate mode. > > My concern is that all these new permutations will fragment the user > base somewhat, and as a newcomer, I'd like to be listening where there is > most chance of success. > > I have 2 questions around operational conventions: > > 1) What is the most common TR time interval for the folks on the list who > are currently actively transmitting via fst4w? > > 2) From the release notes, it seems as if this new mode is intended > mostly for MF and LF users, but is the ultimate vision for this mode to > replace wspr on the upper HF bands as well? > > Lastly, returning to the fragmentation issue, for users like me who > passively listen, it would be really cool if the software were able to > record a .wav file for the longest interval, then parse it for all > possible shorter TR intervals, as well as 'classic' wspr (possibly as a > post-processing activity, rather than in real time.) > > Thanks for any consideration! > > --al > WB1BQE > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel