Re: [wsjt-devel] VAC issue

2021-11-12 Thread Chris Elmquist via wsjt-devel
On Friday (11/12/2021 at 07:03PM +), Bill Somerville wrote: > > Hi Chris, Hi Bill, > I assume you are using an HDMI connected monitor. If so it is the audio > connection associated with that which is causing the issue. Can you disable > the HDMI audio devices in Device Manager, if you can th

Re: [wsjt-devel] VAC issue

2021-11-12 Thread Jim Brown via wsjt-devel
On 11/12/2021 9:14 AM, Chris Elmquist via wsjt-devel wrote: I apologize for resurrecting an old thread but I came back to the list because I continue to have a problem in this very same space. See the post I just made responding to another ham 2 minutes ago about grounding and bonding in your

Re: [wsjt-devel] VAC issue

2021-11-12 Thread Bill Somerville via wsjt-devel
On 12/11/2021 17:14, Chris Elmquist wrote: On Tuesday (07/27/2021 at 09:53AM +0100), Bill Somerville via wsjt-devel wrote: On 27/07/2021 06:51, Bjorn via wsjt-devel wrote: Hello Maybe this is a known issue. But anyway: I have 10 VAC channels going here and I use 1 and 2 towards the WSJT-X soft

Re: [wsjt-devel] VAC issue

2021-11-12 Thread Chris Elmquist via wsjt-devel
On Tuesday (07/27/2021 at 09:53AM +0100), Bill Somerville via wsjt-devel wrote: > On 27/07/2021 06:51, Bjorn via wsjt-devel wrote: > > Hello > > > > Maybe this is a known issue. But anyway: I have 10 VAC channels going > > here and I use 1 and 2 towards the WSJT-X software. > > > > When I start t

Re: [wsjt-devel] VAC issue

2021-07-27 Thread Bill Somerville via wsjt-devel
On 27/07/2021 11:54, Fons Adriaensen via wsjt-devel wrote: 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

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 William Smith via wsjt-devel
They use an API called QT5, and AFAICT it's not that easy. I've been advocating for a 're-do lookup' button, or 'de-do loopup on error' feature, but in the meantime, shut it down and start it up, and it works again. And go through all your USB (and HDMI) devices in Device Manager and disable an

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] VAC issue

2021-07-27 Thread Bill Somerville via wsjt-devel
On 27/07/2021 06:51, Bjorn via wsjt-devel wrote: Hello Maybe this is a known issue. But anyway: I have 10 VAC channels going here and I use 1 and 2 towards the WSJT-X software. When I start the WSJT-X I get RX on ch1 and TX on Ch2. But after it has been running for sometime, say RXing for a

[wsjt-devel] VAC issue

2021-07-26 Thread Bjorn via wsjt-devel
Hello Maybe this is a known issue. But anyway: I have 10 VAC channels going here and I use 1 and 2 towards the WSJT-X software. When I start the WSJT-X I get RX on ch1 and TX on Ch2. But after it has been running for sometime, say RXing for a day. And I then hit TX it uses Ch6 for some reason. R