One reason as to why using a narrow pass-band is less relevant today than in past versions of WSJT-X is the addition of multi-pass decoding where the software itself eliminates ( subtracts out ) a large number of signals before a second pass is run on the same sample. Second pass decoding changes the rules significantly from what "most" of us see as a "sensible operating practice".
Traditionally, eliminating spurious emissions or large signal strength stations through the use of variable BW controls, notch filters, or high quality mechanical filter was required in order to achieve a reasonable number of decodes. However, many of the new features added by Joe, Steve, Bill and others now circumvent the need for such each extreme receiver manipulation, evident by the sheer number of decodes per cycle achieved in extremely crowded band segments such as; 20m, 40m in early evening times, etc. I still catch myself wanting to wrench the receiver controls on occasion, mostly out of habit, but am finding less of a reason to do so with the new features present in the latest development branches of WSJT-X. Just my $0.02 cents worth. 73's Greg, KI7MT > > well, i guess i could be talked out of this practice. > As I think I see it, I am on JT9 and frankly don't care whats "too" far > of my cursor either side. > > Why swamp the passband when I am looking for only who I am calling? > > And if i recall correctly, NF's component contains bandwidth ... > > just gotta love the Collins-Type filters. > > And, for what's it's worth, this is wider than I am usually set. > ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
