Even if you get the dev version working the majority of users will still have
problems with the compound sign autosequencing problem.
I've resigned myself to wait until rc2 is released for my W9MDB/QRP sign. Once
the majority of users upgrade (you can see on pskreporter what versions are
being used) I'll start trying again.
I did a little testing over the weekend and made a couple QSOs....but it took
the responders several iterations before they figured out what they had to do
to continue the QSO.
de Mike W9MDB
From: Scott Bidstrup <[email protected]>
To: [email protected]
Sent: Monday, August 28, 2017 5:15 PM
Subject: [wsjt-devel] Signalink USB issue
Folks,
As the God-cursed holder of a compound callsign, I'm *desperate* to get
off the current -rc1 release version with its compound callsign handling
problems in FT8 Autosequence.
I've tried a recent development version that has fixed that issue, but
it failed to run, saying that input audio failed due to an "unrecognized
format on device." I am using a Signalink USB interface, and I have
heard from other Signalink USB users that they have had similar problems
as well. I had to uninstall it and, sadly, go back to the aggravating
-rc1 release version.
As the problems with the compound callsign handling in -rc1 are serious
for me as they are for other DX stations forced to use them, I'm
desperate to get off of the -rc1 release version. They make QSOs very
time consuming and confusing to the other guy, who, more often than not,
does not understand what is going on. This is a serious problem when
trying to handle a pileup, which I do more often than not on 6m, and
often doubles, or more, the time required to complete a QSO.
My question is this: Is there a build available that 1) has the
compound call fix, and 2) also supports Signalink USB? If there is, I
would be deeply grateful if given access to the binary so I can download
and install it - and give lots more folks a rare grid square and a new
country during our all-too-infrequent 6m opening pileups, than I am able
to do now.
I would also like to take this opportunity to campaign for an -rc2
release as soon as possible so that we can get the -rc1 version
displaced among the user base, with the serious operational problems it
is causing due to users who are naïve to the problem. Often as not,
they'll turn on autosequence, send a reply to me, but their software
won't advance the sequence, causing the same sequence to be sent over
and over and over and over (for more than two minutes, till the band
faded out, in once case I remember) And the offender either isn't there
(assuming autosequence is going to complete his Q while he's off to
work), or is totally clueless and confused as to what to do about the
endless repeats...
Regards to all from sunny TI,
Scott Bidstrup
TI3/W7RI
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
