Re: [wsjt-devel] Hashed callsign collisions?

2023-01-20 Thread Paul Kube via wsjt-devel
I would not be surprised if only the main call is used to compute the hash. Then this admittedly rare and apparently unforseen case, the same main call being used by multiple different stations at the same time, distinguished only by their slash "decoration", arises. Result: collisions among W1AW s

Re: [wsjt-devel] Hamlib errors please for RC4 #hamlib

2022-09-14 Thread Paul Kube via wsjt-devel
Hi Michael -- I have only so far seen warnings about dropped audio samples as shown below. I guess these have nothing in particular to do with Hamlib, but if you want more details, please let me know. 73, Paul K6PO [SYSLOG][2022-09-15 04:46:35.661153][00:00:00.000650][info] Log Start [SYSLOG][20

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

2022-01-15 Thread Paul Kube via wsjt-devel
On Fri, Jan 7, 2022 at 1:25 AM Fons Adriaensen via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > 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 > > t

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

2022-01-06 Thread Paul Kube via wsjt-devel
The problem is well known. As Bill G4WJS put it: 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. That's an awful way to run an audio subsystem, and I'm sure it annoys