Small UI bug/string in 4.2.18

Hi Jonathan,

That’s really helpful, thank you.

It’s an interesting shift in how the feature is framed. I completely understand the trade-off around phase distortion and group delay, particularly in higher speed HF modems. With modes such as STANAG 4285/4539 or other MIL-STD waveforms, where coherent demodulation and tight symbol timing recovery are critical, excess filter latency and non-linear phase can start to impact equalisation performance and overall decode reliability.

In those cases, reducing group delay through lower order filtering can be beneficial, especially where the modem is already working close to the edge in terms of SNR or dealing with selective fading. That said, the compromise in adjacent channel rejection is quite significant, so it becomes a balancing act depending on band conditions.

PACTOR does feel like a slightly unusual headline use case here, given its relatively robust ARQ design and tolerance to channel impairments. I might have expected this to be positioned more broadly around phase-sensitive or high symbol rate modes where latency directly affects demodulation accuracy.

Appreciate the clarification, it makes sense in context.

73, Steve G0RFC

Thank you @Mike-VA3MW that clears that up. Did some work many years ago on a hardware/software modem suite and all the nuances of the varying requirements around each mode has come flooding back 😂😂😂

73