On 10/06/2016 16:06, Joe Taylor wrote: > I think I see it the way Mike does: just leave monitor alone, let it > stay the way it was set when doing a band change.
Hi Joe & Mike, the thinking was that changing frequency in WSJT-X must mean that you want to listen to that frequency. I can't think of a good reason not to turn on monitor for a frequency change. OTOH because WSJT-X changes frequency automatically to the first defined working frequency for a mode when changing mode; this has the downstream consequence of enabling monitor. I'm not sure that a testing requirement to not have monitor come on while changing modes between playing back WAV files justifies disabling a potentially useful feature. As a possible alternative you could set up a configuration with no working frequencies defined. To do that: 1) clone the current configuration, 2) rename the clone to "testing" or whatever you wish, 3) switch to the new configuration, 4) in "Settings->Frequencies" click a working frequency, type CTRL+A, right-click and select "Delete". That will mean that whenever that configuration is selected mode changes will have no impact on rig control nor monitor state. 73 Bill G4WJS. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
