Re: [wsjt-devel] Not a Bug, But a PITA
On 21 Dec 2019 at 12:47, Jim Brown wrote: > This morning, I fired up to work AG6EE on 6M with MSK144 on an > expedition to a couple of rare grids in the desert along the US/Mexico > border. He was on 50.265 to stay out of the way of casual QRM, and I > worked him in one of those grids yesterday. This morning, online chat > told me he was now using NA VHF Contest mode, so I set that and returned > to monitoring. When I did, WSJT-X moved me to 50.260. I had a bunch of > decodes on the screen from before I had switched to Contest mode, and I > wasn't certain whether I had been on .260 or .265 when I decoded them. > MUCH wasted time figuring that out. PITA Jim: Do you use separate configurations for the various modes, or do you just stay in the default configuration (or a variant thereof) and then select whichever mode you want to use from the drop-down list under the Mode menu and/or the Settings > Advanced > Special operating activities options? From your description it sounds like you're doing the latter. I believe the 'issue' you deem to be a PITA wouldn't arise if you switched between configurations because each configuration starts decoding and displaying the decodes from scratch after start-up - there would be no ambiguity whatsoever about which decodes had been generated on which frequency and in which mode. For example, you could have one configuration specifically for 6m MSK144 and another one for NA VHF Contest mode (presumably also on 6m?); switching between them would take little or no more time than going into the Mode menu and/or the Special operating activities options. Each configuration can have its own set of frequencies which might or might not overlap, thereby helping to minimise or eliminate any ambiguities in the listed decodes. --- Martin, G0HDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Not a Bug, But a PITA
> WSJT-X's tendency to change frequencies when you switch in or out of contest, fox / hound mode, etc is annoying and unexpected. Fortunately the frequency is prominently displayed in the WSJT-X window (and on the front of my radio). I've learned to always check it after any mode or band change, and adjust as necessary. Not hard to do, just hard to remember to do at first. I think Jim K9YC was complaining about a slightly different thing though: WSJT-X decodes when displayed are only tagged with the band and audio offset, not the exact base VFO frequency, and that would be useful sometimes. 73, Paul K6PO On Sat, Dec 21, 2019 at 2:17 PM Jon Anhold wrote: > I agree that WSJT-X's tendency to change frequencies when you switch in or > out of contest, fox / hound mode, etc is annoying and unexpected. > > On Sat, Dec 21, 2019 at 3:50 PM Jim Brown > wrote: > >> This morning, I fired up to work AG6EE on 6M with MSK144 on an >> expedition to a couple of rare grids in the desert along the US/Mexico >> border. He was on 50.265 to stay out of the way of casual QRM, and I >> worked him in one of those grids yesterday. This morning, online chat >> told me he was now using NA VHF Contest mode, so I set that and returned >> to monitoring. When I did, WSJT-X moved me to 50.260. I had a bunch of >> decodes on the screen from before I had switched to Contest mode, and I >> wasn't certain whether I had been on .260 or .265 when I decoded them. >> MUCH wasted time figuring that out. PITA >> >> 73, Jim K9YC >> >> >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Not a Bug, But a PITA
I agree that WSJT-X's tendency to change frequencies when you switch in or out of contest, fox / hound mode, etc is annoying and unexpected. On Sat, Dec 21, 2019 at 3:50 PM Jim Brown wrote: > This morning, I fired up to work AG6EE on 6M with MSK144 on an > expedition to a couple of rare grids in the desert along the US/Mexico > border. He was on 50.265 to stay out of the way of casual QRM, and I > worked him in one of those grids yesterday. This morning, online chat > told me he was now using NA VHF Contest mode, so I set that and returned > to monitoring. When I did, WSJT-X moved me to 50.260. I had a bunch of > decodes on the screen from before I had switched to Contest mode, and I > wasn't certain whether I had been on .260 or .265 when I decoded them. > MUCH wasted time figuring that out. PITA > > 73, Jim K9YC > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Not a Bug, But a PITA
This morning, I fired up to work AG6EE on 6M with MSK144 on an expedition to a couple of rare grids in the desert along the US/Mexico border. He was on 50.265 to stay out of the way of casual QRM, and I worked him in one of those grids yesterday. This morning, online chat told me he was now using NA VHF Contest mode, so I set that and returned to monitoring. When I did, WSJT-X moved me to 50.260. I had a bunch of decodes on the screen from before I had switched to Contest mode, and I wasn't certain whether I had been on .260 or .265 when I decoded them. MUCH wasted time figuring that out. PITA 73, Jim K9YC ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
