On 07/04/2016 22:33, Bill Somerville wrote: > 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. Hi Mike,
Here are a pair of patches for wsjtx and hamlib which are a quick and dirty proof of concept of a hamlib feature to set mode without changing the bandwidth. It is only implemented for the Omni-VII. Can you give it a try please? https://dl.dropboxusercontent.com/u/4192709/omni-vii_wsjtx.patch https://dl.dropboxusercontent.com/u/4192709/omni-vii_hamlib.patch 73 Bill G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
