I think I have (with the help of ChatGPT) possibly fixed the sidetone
latency problem, and it's still a browser application. The solution
seems to be similar to what Gwen, NG3P, proposed except instead of
turning off the processing when the sidetone is detected the application
routes the sidetone AROUND the processing when the sidetone is
detected. The difference might be subtle but that keeps the noise
reduction intact for a proper recovery when the sidetone stops. I
wasn't able to detect a latency problem even well above 40 words per
minute, but my CW speed isn't good enough for me to be the best judge of
that.
The hang time for the rerouting is user definable, although I don't
think it can be set low enough for full breakin without generating audio
artifacts.
I still need to do some more testing, but things look promising.
I also created slightly different processing for SSB versus CW in order
to get just a little bit better performance for CW since single tones
are easier to handle. That also prevents the sidetone detector from
triggering on a voice frequency. The choice between the two is a simple
toggle button in the user interface.
When I'm satisfied with everything I'll upload the revised version to my
website.
73,
Dave AB7E
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
