Re: [wsjt-devel] Subject: Feature request: Output audio device selection for alert sounds

2025-04-27 Thread Fons Adriaensen via wsjt-devel
On Sun, Apr 27, 2025 at 09:15:40PM +0100, alan2--- via wsjt-devel wrote: > I do it the other way around - cheap dongle set as Windows default, in-built > soundcard for WSJT-X and SDR's as on my PC it's better resolution etc. Using the default Windows device for SDR (or anything technical) might b

Re: [wsjt-devel] WSJT-X SuperFox Verification is flawed

2024-07-24 Thread Fons Adriaensen via wsjt-devel
On Wed, Jul 24, 2024 at 02:19:51PM +0100, Hibby via wsjt-devel wrote: > Identity and keysigning is a solved problem True. What is required here is a public-key signature scheme. The fox produces a key pair and publishes the public key which is then used by the hounds. The problem is that all p

Re: [wsjt-devel] Licensing Issue of SuperFox Mode

2024-07-20 Thread Fons Adriaensen via wsjt-devel
On Fri, Jul 19, 2024 at 03:07:34PM -0400, Joe Taylor via wsjt-devel wrote: > The following text is from "Frequently Asked Questions about the GNU > Licenses", https://www.gnu.org/licenses/gpl-faq.html : > > "[P]ipes, sockets and command-line arguments are communication mechanisms > normally used

Re: [wsjt-devel] Fwd: Enhancement suggestion - 30 second cycles

2023-05-08 Thread Fons Adriaensen via wsjt-devel
On Tue, May 09, 2023 at 03:06:34AM +1000, Adrian via wsjt-devel wrote: > On 9/5/23 02:49, Jim Brown via wsjt-devel wrote: > > > #3 is bogus. > > How would you know ? You lack the technical ability.. I'm not an AES fellow, but as another audio 'expert' I can only confirm that #3 is complete bog

Re: [wsjt-devel] The #$&% Windows 10 audio issue, and a proposal

2022-01-16 Thread Fons Adriaensen via wsjt-devel
On Sat, Jan 15, 2022 at 11:17:58PM -0800, Paul Kube via wsjt-devel wrote: > On Fri, Jan 7, 2022 at 1:25 AM Fons Adriaensen via wsjt-devel > > > So does this mean that when a new audio device becomes available > > while a music app is playing some file, the output from tha

Re: [wsjt-devel] The #$&% Windows 10 audio issue, and a proposal

2022-01-07 Thread Fons Adriaensen via wsjt-devel
On Thu, Jan 06, 2022 at 09:48:22PM -0800, Paul Kube via wsjt-devel wrote: > Any change to audio device availability on MS Windows is likely to renumber > the indexes of other devices, when this happens WSJT-X gets no notification > that it has happened. So does this mean that when a new audio dev

Re: [wsjt-devel] VAC issue

2021-07-27 Thread Fons Adriaensen via wsjt-devel
On Tue, Jul 27, 2021 at 06:37:18AM -0400, William Smith wrote: > They use an API called QT5, and AFAICT it's not that easy. Oh dear. That is probably the worst possible choice. Portaudio would come second. On Linux, use ALSA (via a lib such as zita-alsa-pcmi), or use Jack. Do not use PulseAudio.

Re: [wsjt-devel] VAC issue

2021-07-27 Thread Fons Adriaensen via wsjt-devel
On Tue, Jul 27, 2021 at 09:53:11AM +0100, Bill Somerville via wsjt-devel wrote: > WSJT-X saves audio device names in its settings file but to access the > devices we look them up and get an index number which we must use to > interact with them. These index numbers are somewhat volatile and can ch

Re: [wsjt-devel] Licensing and Copyrights in WSJT-X and related programs #Q65

2021-03-14 Thread Fons Adriaensen
On Sat, Mar 13, 2021 at 06:46:42PM -0500, Joe Taylor wrote: > We're not particularly interested in litigating nuances of wording. This is > just a hobby, for all of us. We're just asking for fair play. As the author of some GPL'd software myself, and having been in similar situations, I can and

Re: [wsjt-devel] Slackware: How I got WSJT-X installed & running

2021-02-25 Thread Fons Adriaensen
On Thu, Feb 25, 2021 at 11:45:20AM +, Bill Somerville wrote: > but having said that, what is wrong with installing at /usr/local? That is a > normal location for installing packages you have built from sources. Indeed it is, and installing locally built things in /usr can lead to trouble wit

Re: [wsjt-devel] FST4/W

2020-08-27 Thread Fons Adriaensen
On Thu, Aug 27, 2020 at 12:01:53PM +0100, Bill Somerville wrote: > you are ignoring those that would take the unfinished work in progress, > despite protocols not being finalized, and copy the code parrot fashion into > their so-called derivative products, which they then release as "complete" > b

Re: [wsjt-devel] 7 Digit Callsigns

2020-02-23 Thread Fons Adriaensen
On Fri, Feb 21, 2020 at 11:34:51AM +, Bill Somerville wrote: > where I say non-standard I mean within the constraints of the digital source > encoding used by the various modes in the WSJT suite of software. That does > not exactly align with all callsigns issued around the World, to do so wo

[wsjt-devel] build fails

2020-02-01 Thread Fons Adriaensen
Hello all, I'm tryng to build WSJTX from wsjtx-2.1.2.tgz downloaded from the WSJT home page, on an up-to-date Archlinux system. All works well until: In file included from /home/fons/build/build/wsjtx-prefix/src/wsjtx/qt_helpers.cpp:1: /home/fons/build/build/wsjtx-prefix/src/wsjtx/qt_helpers.hp