Re: [wsjt-devel] Errant callsign - WSJT-X v2.0.0-rc2 cc148d

2018-10-04 Thread DXer
nutes. Upon return, that is when I may see a false decode. Some coarse language has been used in the beginning for missing them, until I realized they were false decodes, as they are usually for DX I can only dream about. Regards, Vince, VA3VF On Thu, Oct 4, 2018 at 9:36 AM DXer wrote: > I

[wsjt-devel] Errant callsign - WSJT-X v2.0.0-rc2 cc148d

2018-10-04 Thread DXer
I thought it was just the 'price to pay' for AP and deep decoding. If this is being treated as a bug, I'm also seeing it. Something like 2 to 3 times an hour, just to frame it in a period of time. There is another interesting situation happening, but only if you use JTAlert to monitor and initiate

[wsjt-devel] RC2.

2018-10-03 Thread DXer
A returnee from JTDX. RC2 has been great, no problems so far. Decoding is very good. One request. In addition to the CQ only box, would it be possible to also offer a 73/RR73 box that would add to the CQ only option? Thanks and 73. Vince, VA3VF _

Re: [wsjt-devel] WSJT-X Dev observation.

2017-10-03 Thread DXer
Another observation. Scenario: I'm following a QSO between 2 other stations. Before the station I'm interested in contacting sends his/her final 73, I set everything up for a tail ending call. However, when the 73 message is received, Tx is disabled, and I have to click enable Tx again, possibly

[wsjt-devel] WSJT-X Dev observation.

2017-10-03 Thread DXer
The following situation occurs when Call 1st is selected. I call CQ, two stations answer, Call 1st 'engages' with one of the stations, but I want the other one. The only way I found to override the Call 1st choice is to stop Tx, click on the station I want , and start Tx again. The time required t

[wsjt-devel] r8158 Observations.

2017-10-02 Thread DXer
1)W9MDB's first name is misspelled in the new Copyright Notice; 2)When Tx watchdog is reached, the red message appears, but it still Tx one more cycle, while also scrolling the waterfall as in normal receive. 73 de Vince, VA3VF -

Re: [wsjt-devel] Possible enhancement?

2017-10-01 Thread DXer
gnals would go a long way toward improving the situation. If it were automatic, then newbies would not be a problem. Ted K9IMM -Original Message- From: DXer [mailto:hfdxmoni...@gmail.com] Sent: Sunday, October 01, 2017 10:44 AM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel

Re: [wsjt-devel] Possible enhancement?

2017-10-01 Thread DXer
Hi Ted, I don't speak for the developers. I'm simply a user. What you are suggesting can easily be done now by a proficient operator. I use N1MM+, and what they did was mitigate poor operating practices, after all education attempts had failed. There are people out there that will click on a

Re: [wsjt-devel] Experimental changes in r8147

2017-09-30 Thread DXer
Jim, Joe, Working fine answering a CQ in JTAlert in the format CQ NA EA3RT JN01. 73 de Vince, VA3VF -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/

Re: [wsjt-devel] Experimental changes in r8146

2017-09-30 Thread DXer
2017-09-30 2:35 PM, DXer wrote: Sorry...I widthdraw this last comment. It does happen as Jim describes, even with Hold Tx Freq checked. On 2017-09-30 2:31 PM, DXer wrote: I can duplicate what you are seeing only if a check Hold Tx Freq. Vince, VA3VF On 2017-09-30 2:22 PM, James Shaver wrote

Re: [wsjt-devel] Experimental changes in r8146

2017-09-30 Thread DXer
Sorry...I widthdraw this last comment. It does happen as Jim describes, even with Hold Tx Freq checked. On 2017-09-30 2:31 PM, DXer wrote: I can duplicate what you are seeing only if a check Hold Tx Freq. Vince, VA3VF On 2017-09-30 2:22 PM, James Shaver wrote: Correction: when responding to

Re: [wsjt-devel] Experimental changes in r8146

2017-09-30 Thread DXer
I can duplicate what you are seeing only if a check Hold Tx Freq. Vince, VA3VF On 2017-09-30 2:22 PM, James Shaver wrote: Correction: when responding to a CQ via the UDP server using JTAlert, the RX will move and the TX does not unless you hold the control key down which may cause issues for s

Re: [wsjt-devel] Experimental changes in r8146

2017-09-30 Thread DXer
Interesting, not here. 73 de Vince, VA3VF On 2017-09-30 2:22 PM, James Shaver wrote: Correction: when responding to a CQ via the UDP server using JTAlert, the RX will move and the TX does not unless you hold the control key down which may cause issues for some. Sorry, my fingers are moving f

Re: [wsjt-devel] Experimental changes in r8146

2017-09-30 Thread DXer
Hi Jim, By using UTP server to respond, do you you mean clicking on the callsign in JTAlert? If yes, it's working for me, that is, both Tx and Rx move to the same frequency as the CQ calling station. 73 de Vince, VA3VF On 2017-09-30 2:19 PM, James Shaver wrote: Works well but when using the

Re: [wsjt-devel] Experimental changes in r8146

2017-09-30 Thread DXer
On the air with r8146. Everything working as described. 73 de Vince, VA3VF On 2017-09-30 2:00 PM, Joe Taylor wrote: Hi all, The following is the commit message for r8146: If you can build r8146 for yourself and try it on the air, please post your comments here. -- 73, Joe, K1JT ---

[wsjt-devel] r8144: Answering a CQ from JTAlert.

2017-09-29 Thread DXer
Bill, I was checking JTAlert to see what had changed, but it's working again on r8144. Not sure if it's related, just an FYI. 73 de Vince, VA3VF -- Check out the vibrant tech community on one of the world's most engag

[wsjt-devel] r8144: Lock Tx.

2017-09-29 Thread DXer
Thank you, K1JT. I think you found a good compromise for all the Tx=RX related wants and needs. 73 de Vince, VA3VF -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org!