Re: [wsjt-devel] Hamlib fork repository

2023-11-08 Thread Christoph Berg via wsjt-devel
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: [wsjt-devel] CQ Hound mode

2023-11-05 Thread Christoph Berg via wsjt-devel
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,

Re: [wsjt-devel] Callsign Security

2023-10-12 Thread Christoph Berg via wsjt-devel
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

Re: [wsjt-devel] VFO readout on FT8 shutdown

2023-07-20 Thread Christoph Berg via wsjt-devel
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

Re: [wsjt-devel] "U.S.A" displayed as "U.S.A. of America"

2023-05-17 Thread Christoph Berg via wsjt-devel
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

Re: [wsjt-devel] #Bug - Frequency Tracking Error - IC9700 (and IC-7300)

2023-01-16 Thread Christoph Berg via wsjt-devel
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

[wsjt-devel] Typo patch

2022-08-23 Thread Christoph Berg via wsjt-devel
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 mostly bui

Re: [wsjt-devel] Release Candidate WSJT-X 2.6.0-rc3

2022-08-23 Thread Christoph Berg via wsjt-devel
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

Re: [wsjt-devel] Are you building WSJT-X ?

2022-04-25 Thread Christoph Berg via wsjt-devel
> - 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

[wsjt-devel] Log uses rcvd report from previous QSO

2021-08-12 Thread Christoph Berg via wsjt-devel
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