Re: Uwe, DG2YCB via wsjt-devel
> Some users complain that "U.S.A." is displayed as "U.S.A. of America".
> The reason for this is that the maintainers of the CTY.DAT file have
> suddenly changed the name from "United States" to "United States of
> America".
The weird part is that the change was onl
Am 20. Juli 2023 19:58:21 OESZ schrieb Marco Calistri via wsjt-devel
:
>New Hamlib looks a bit better because with just one manual frequency band
>correction, the sequences RX/TX keep stable for the rest of my FT8 operation.
>
>But the undesired behavior at the beginning (2 KHz shift after two RX
Re: William Smith via wsjt-devel
> So now we would require cryptographic signing of QSOs? I mean, I'd be ticked
> if someone used one of my callsigns, but I wouldn't rally the entire amateur
> community around a complex solution to the 'problem'.
>
> It was hard enough for me as a computer prof
Re: Reino Talarmo via wsjt-devel
> Just a minor point, I assume. If that is programmed into wsjt-x, then the
> change will not be backwards compatible. The CQ part of the message is
> actually a specific pretty long bit string (28 bits, ‘c28’). There could be
> another bit string for the CQF, bu
Re: Matt Melling via wsjt-devel
> Thanks Mike l. My understanding is that at some point in the past there were
> some patches needed for Hamlib. Is that no longer the case?
Debian has been building wsjtx with the stock upstream hamlib for ages
without issues.
Christoph DF7CB
__
Re: Joe Taylor via wsjt-devel
> We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc5 is
> ready for download and use by beta testers. This release introduces
> SuperFox mode, a powerful new tool designed to help DXpeditions make
> digital QSOs at very high rates.
Hi,
where can we f
Re: Alex Lelievre via wsjt-devel
> Unfortunately I found out that this part of the code is actually closed
> source! There goes the neighborhood!
Well that's a real pity. I've been using wsjtx as an example of "ham
radio done right" - developed openly, with an open specification, with
and for th
Re: John Nelson via wsjt-devel
> I can understand why this choice (closed code) has been made because of the
> non-collegiate actions of others. The question is how to propagate binaries
> in a trusted way - perhaps involving particular distributors (eg Debian,
> M1/2/3) to have source code on
Re: Joe Taylor via wsjt-devel
> WSJT-X is a complete and independent program. Its full source code is
> available to anyone. One of its many operating modes makes use of short,
> uncomplicated exchanges with three independent programs that are licensed
> separately and made freely available for A
Re: Jakob Ketterl DD5JFK via wsjt-devel
> Just in case you're in doubt about the latter, this is the contents of the
> copyright declaration included in the WSJT-X 2.7.0-rc6 Debian package,
> downloaded 15 minutes ago:
The rc6 package I uploaded to Debian unstable some hours ago has the
sfrx/tx bi
Re: Black Michael via wsjt-devel
> The CQ sent out with the new SuperFox does not contain the grid.This means
> pskreporter spots do not occur unless the user types in the grid.
I've seen 3 CQs today, they included the grid and were the only
message during that cycle. There was a "verified" messa
After a QSO with EA8TH, I received a "cold" call from YO9IE which I
answered, but in the log window following that QSO, the -17 report
from the 1st QSO was reused:
201245 0 0.3 1202 ~ CQ EA8TH IL18 Canary Is.
...
201400 Tx 2607 ~ EA8TH DF7CB JO31
201415 -2 0.3 1202 ~ DF7CB EA8TH
> - Building on what platform? Windows, Linux, macOS, or other?
We (me and fellow developers) are maintaining the Debian package of
wsjtx. Platforms are all Linux architectures supported by Debian:
https://buildd.debian.org/status/package.php?p=wsjtx
> - What are your particular programming sk
Re: Brian Morrison via wsjt-devel
> One small thing, the .tgz file contains the src directory and inside the
> wsjtx.tgz archive within that both of the .desktop files have some
> terminators whereas in the same files in the git repo they
> have only . This trips up the Fedora spec files for build
Re: Christoph Berg via wsjt-devel
> Afaict the whole source tree has CRLF line terminators now. It would
> be nice if that could be reverted, it's making all the patches we have
> in the Debian package fail.
Attached is a patch that is suitable of inclusion (the others are
mostl
Re: Fred Price via wsjt-devel
> Do you have CV-I Transcrive turned off in the menu? If not turn off and test
> again.
Hi Fred,
I had bad problems with frequency readout with my IC-7610 through
rigctld when using the VFO knob - mostly in tlf, but wsjtx was also
affected (though less since there's
Re: Black Michael via wsjt-devel
> We need to do some testing but I'm considering changing Hamlib to put all
> rigs on FAST AGC (if AGC is not OFF) for WSJT-X operation. So a setting of
> medium or slow would get changed to fast.
That sounds like it should be done by wsjtx, not hamlib.
73,
Chr
Re: Black Michael
> Except you don't want give users a choice on that. Trust me -- they won't
> know what to do even if we put help in the manual.
> Lots of "what do I do" questions and arguments about what is best.
Have wsjtx set it, without a checkbox.
In hamlib, it's a layer violation.
Chri
Re: Joe Taylor via wsjt-devel
> We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc7 is ready
> for download and use by beta testers. This revision has many improvements to
> SuperFox mode: better decoding, more reliable message sequencing, and an
> open source, cryptographically soun
19 matches
Mail list logo
