Hi all - Have spent the weekend giving this build as much "air time" as I could stay awake to provide. Here's some comments with regard to its operation.
OVERALL: An excellent build. Pluses outweigh a meager few minuses. It's a good candidate for release. The Plus side: - Outstanding improvement to both speed and depth of decoding. Even with the decode option set at "deepest" and using the JT9+JT65 mode for the entire weekend, decoding is almost immediate following a JT9 transmission, and a little quicker when that longer signal is not present. Too, much weaker signals are now being decoded as opposed to "SIG WEAK AGN?" and "SRI NO DECODE" situations with prior builds. - I've experienced the first occasion of the 14 call sign windows displayed by my JTAlert-X being populated, with the Band Activity window on the WSJT-X front panel displaying even more decodes. - A great feature is having signal reports populate the Log QSO window when it pops up at "73" time. Only need to insert a name, hit "OK" and it's off to the logger. - The addition of selectable standard message generation for type 2 compound call sign holders is quite welcome as well. Choices are three: Full call in Tx1; Full call in Tx3; and Full call in Tx5 only. Neat options to help the "distant end" recognize your full call prior to signing 73. The Minus side: - More of a matter of unfamiliarity and confusion on the "distant end," the use of the above reported new selection for standard message generation resulted in more broken QSOs and much longer QSOs. Of course, if you don't sign a type 2 compound call sign, most of these minuses are invisible. - Out of 57 QSOs, 8 were complete without problems, 38 required repeating the signal report a second (or third) time using XXXXXX YYYYYY R-09 instead of the initial DE YYY/YYYYYY R-09 report. The other 11 QSOs ended after sending the signal report and the "distant end" vanishing without a trace. - Additionally, responding to an incoming call with DE YYY/YYYYYY -12 appears to leave the "distant end" wondering who it is, among the pile-up of callers, that received the "-12," necessitating retransmission with the "old style" message. - The only software "tick" discovered was that when "Full call on Tx5 only" is selected for standard message generation, the signal report that you send to the "distant end" via "R+dB" doesn't populate the Log QSO pop- up window. Wanting more solid QSOs, I stuck with "Tx5 only" after the 57 test QSOs. Messages generated are as before, but the other benefits that are available will soothe the spirit. A hearty "Well done!" and a heartfelt "Thank you" to all of the developers who put this build together and offered it up for testing. I wonder what next could top it? Best 73 from the Philippines, Paul DU2/WA8UGN ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
