Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and 2.4rc1 COM port

2021-02-15 Thread Black Michael via wsjt-devel
A couple of complaints from those who were using a single instance were having problems with the constant open/close of the serial port.So it was changed to support the simple case and those that want the more complex case of multiple apps have to use the additional file as WSJT-X authors have d

Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and 2.4rc1 COM port

2021-02-15 Thread Alex Artieda, HB9DRI
Hello Bill Following your instructions I use your file (looks the same as I use before) and I place in the properly log directory for each of the WSJT-X (totally 4) and doesn’t work, the PTT is not share. I wonder why if in WSJT-X 2.2.2 the PTT com port was share by default now is not?

Re: [wsjt-devel] Clipping

2021-02-15 Thread Black Michael via wsjt-devel
Patch to fix the problem index 8e442d05f..81a978852 100644 --- a/widgets/mainwindow.cpp +++ b/widgets/mainwindow.cpp @@ -1288,6 +1288,7 @@ void MainWindow::readSettings()    // setup initial value of tx attenuator    m_block_pwr_tooltip = true;    ui->outAttenuation->setValue (m_settings->valu

Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems

2021-02-15 Thread David Tiller
No wheel, only Mac touchpad (wheel emulation w/ 2 finger slide stinks). No easy page up/down either. > On Feb 15, 2021, at 11:24, Larry B. via wsjt-devel > wrote: > > Or the wheel on your mouse. > > 73 -- Larry -- W1DYJ > > > From: Bill Somerville > Sent: Monday, February 15, 2021 10:01

Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems

2021-02-15 Thread Larry B. via wsjt-devel
Or the wheel on your mouse. 73 -- Larry -- W1DYJ From: Bill Somerville Sent: Monday, February 15, 2021 10:01 To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems Hi David, you can already do that by selecting the slider and using the u

Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems

2021-02-15 Thread Al
(2.4.0_rc1 64 bit )   I too noticed a difference in TX audio levels when I first started to use 2.4.0 RC1.  In fact the change of levels was the same as the difference in levels between the v2.2.2 32 bit vs. 2.2.2 64 bit ( ~8 db ).   But after 3 days of using 2.4.RC1 with the higher level, for s

Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems

2021-02-15 Thread David Tiller
Bill, Selecting the slider often changes it, at least on a Mac, so you have no idea what the original setting was. Having a way to adjust it without having to be a touchpad ninja would help. > On Feb 15, 2021, at 10:01 AM, Bill Somerville wrote: > > Hi David, > > you can already do that by

Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems

2021-02-15 Thread David Tiller
Bill, I don't know about anyone else's setup, but my max power, no ALC power slider values are radically different per band. There is no one analog drive level adjustment on my interface (RigExpert Standard) that'll give reasonable power levels on all bands. My rig is a 756PRO, BTW. > On Feb 1

Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems

2021-02-15 Thread Sam W2JDB via wsjt-devel
Hil, You can also use the mouse wheel if available. 73, Sam W2JDB -Original Message- From: Bill Somerville To: wsjt-devel@lists.sourceforge.net Sent: Mon, Feb 15, 2021 10:01 am Subject: Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems Hi David, you can already do that

Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems

2021-02-15 Thread Bill Somerville
On 15/02/2021 14:35, Rich - K1HTV wrote: I noticed that while running WSJT-X v2.4.0-rc1, the original WSJT-X "Pwr" control setting produced excessive AGC levels on my K3 transceiver. TX levels are over 5 dB higher with WSJT-X Version 2.4.0-rc1 than with previous versions. Unless a software ch

Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems

2021-02-15 Thread Bill Somerville
Hi David, you can already do that by selecting the slider and using the up and down arrow keys. Page up and down for 1 dB increments. 73 Bill G4WJS. On 15/02/2021 14:58, David Tiller wrote: You wrote: "How about adding a small "dB' box right under the "Pwr" label" If you add that (and I hop

Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems

2021-02-15 Thread David Tiller
You wrote: "How about adding a small "dB' box right under the "Pwr" label" If you add that (and I hope you do), please make it a spinner box so we can adjust it with up/down arrows by preferably 0.1 dB increments. > On Feb 15, 2021, at 9:35 AM, Rich - K1HTV wrote: > > I noticed that while run

Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems

2021-02-15 Thread Alan Groups
Haven't tested this version yet but something else that might be good in my view is to have a CAT command to vary maximum power output available from the rig, for those rigs that support it? Alan G0TLK On 15/02/2021 14:35, Rich - K1HTV wrote: I noticed that while running WSJT-X v2.4.0-rc1, the

[wsjt-devel] Rc4 Tx levels will cause future QRM problems

2021-02-15 Thread Rich - K1HTV
I noticed that while running WSJT-X v2.4.0-rc1, the original WSJT-X "Pwr" control setting produced excessive AGC levels on my K3 transceiver. TX levels are over 5 dB higher with WSJT-X Version 2.4.0-rc1 than with previous versions. Unless a software change is made so TX audio levels match those of

Re: [wsjt-devel] Clipping

2021-02-15 Thread Reino Talarmo
Mike, Did you checked what happens in your computer(s) in following combinations: 15 s wav, Flatten, Low sidelobes 15 s wav, Flatten, Most sensitive 15 s wav, non-flatten, Low sidelobes 15 s wav, non-flatten, Most sensitive 45 s wav, Flatten, Low sidelobes 45 s wav, Flatten, Most sensitive

Re: [wsjt-devel] Clipping

2021-02-15 Thread Bill Somerville
Mike, the "nastiness" you refer to is more than 65 dB down. As far as we have been able to determine it is due to either Windows or VAC. My money is on Windows since VB Cable exhibits the same behaviour, although that is not conclusive. Note that 65 dB down is below the distortion added by al

Re: [wsjt-devel] Clipping

2021-02-15 Thread Black Michael via wsjt-devel
It's not just the waterfallthat nastiness gets transmitted too. Mike W9MDB On Monday, February 15, 2021, 02:53:44 AM CST, Reino Talarmo wrote: Hi Mike and Bill, I looked those *.wav files using v2.4.0-rc1 and noted interesting presentation difference, when I had Flatten activa

[wsjt-devel] Clipping

2021-02-15 Thread Andy Durbin
"40 dB down is pretty good for most consumer systems, but could produce spurs from it to someone who hears us very loud . If, for example, someone is 40 dB over S9, harmonics that are 40 dB over S9 would be S9! Sort of negates the advantage of some WSJT-X modes if the signal you're trying to cop

Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and 2.4rc1 COM port

2021-02-15 Thread Bill Somerville
Hi Alex, try the attached file. It needs to go in the log files directory of each WSJT-X instance ("Settings->File->Open log directory"). 73 Bill G4WJS. On 15/02/2021 05:41, Alex Artieda, HB9DRI wrote: Hello Mike Sorry I didn’t answer to the list; I create a file named hamlib_settings.jso

Re: [wsjt-devel] Clipping

2021-02-15 Thread Jim Brown
Several observations. First, MANY years ago thoughtful engineers listened with headphones to the distortion output of instrumentation devices (like legacy distortion analyzers) as "ear training" to help us recognize a particular form of distortion. An very smart former Ampex engineer designed a

Re: [wsjt-devel] Clipping

2021-02-15 Thread Reino Talarmo
Hi Mike and Bill, I looked those *.wav files using v2.4.0-rc1 and noted interesting presentation difference, when I had Flatten activated or non-activated. Especially the waterfall display changed a lot. It was difficult to see those multiple sidebands in non-flatten display totally independent