On 07/04/2016 21:40, Michael Black wrote: > In 6589 no bandwidth change Hi Mike,
I suggested a minimal test of: "A minimal test is probably to set the rig to something other than USB then start WSJT-X, you may need to select a band in WSJT-X to get it to change the rig mode depending on settings." I see no evidence that you set the mode to something other than USB before running the test. I know what is happening now. The issue is due to using a new Hamlib API function to set split frequency and mode together in one step. This is essential for many rigs because setting the two separately takes many VFO swaps which is disruptive to the audio. The solution is to sort out Hamlib so that there is a way of setting the mode without touching the bandwidth. I've just noticed that the pbwidth_t type in Hamlib is a signed long so I think a -1 value could be co-opted to mean no change which may be a relatively easy enhancement. 73 Bill G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
