I am not making myself clear. The cw_poll nor modem_poll has any use of reading the keyer.
I hope it is clear. None of the polling routines are used expect to start the transmission.
The keyer is sensed by the isr routine that updates the global variables with the current state of the paddles.
It is the key_poll that reads and returns the state of the paddle 96,000 times a second.
I repeat, nothing to do with either the ui_tick nor modem_poll nor cw_poll.
It would be best if everyone read the detailed email I posted with reference to the exact line numbers of the code. We can then discuss the code.
- f
On Thu, Apr 3, 2025, 9:28 PM Gordon Gibby KX4Z via <docvacuumtubes=
[email protected]> wrote:
Calling anywhere from 5 to 10 times more frequently would probably result in significant improvement.? ? In the sBitx software, he increased it to 20 times more frequently and it was amazing.?
> On Apr 3, 2025, at 10:40, Mike Johnshoy via <mike.johnshoy=[email protected]> wrote:
>
> ?Ashar, no not cw_poll(), it is modem_poll() that is not getting called often enough.? In sbitx_gtk.c this call is at line #4257 inside of ui_tick().? modem_poll() in turn decides what to do for each of the modes, but in the case of CW modem_poll only gets called ~once per 20 milliseconds, so no matter how fresh the key_poll data is it doesn't get looked at enough.?
> --
> Mike KB2ML
>
>
>
>
>
