Hi Jose,
Interesting, how you did it?
73, Reino OH3mA
>El 27/7/21 a las 19:46, Bill Somerville via wsjt-devel escribió:
>> TxN buttons
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
El 27/7/21 a las 19:46, Bill Somerville via wsjt-devel escribió:
TxN buttons
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
On 27/07/2021 23:37, Jose Montano via wsjt-devel wrote:
-WSJT-X 2.4.0+repack-1 (experimental branch)
-OS GNU/Linux Debian testing
-In the button "TX1" the letter "X" is lowercase.
-When I call CQ, and someone answers me, for example with a dB-19
signal, the software responds giving the repor
-WSJT-X 2.4.0+repack-1 (experimental branch)
-OS GNU/Linux Debian testing
-In the button "TX1" the letter "X" is lowercase.
-When I call CQ, and someone answers me, for example with a dB-19
signal, the software responds giving the report -19, but if for some
reason, the station does not give
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
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.
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
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
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
