That (every 4 ticks) would probably work - but only if you make the qsk delay high enough.
?
That delay stops the waterfall/decoder display from updating, and that seems to be taking a bit more time than the current loop allows, one tick is not 1ms, but a bit over 2.
I think it would be fine to do the screen updates less frequently even when receiving, I like a slower waterfall, but that's one of the tradeoffs that I'm sure Farhan has considered and will fine tune.
?
Erik
