Received-SPF: neutral (google.com: 193.82.116.20 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org)
From: "Mike Dennison" <mike.dennison@ntlworld.com>
To: rsgb_lf_group@blacksheep.org
Date: Thu, 29 Mar 2007 14:26:23 +0100
MIME-Version: 1.0
Message-ID: <460BCC8F.11429.1742A6B@localhost>
Content-description: Mail message body
Subject: LF: Argo settings
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

When receiving a DX signal, many people use a faster Argo screen than 
the transmitted dot length. For instance, setting Argo to 60s dot 
when receiving a QRSS120 signal. But this is not common practice with 
more local contacts with faster speeds.

Is this effect because Argo does not work well at very slow speeds? 
Or is it something to do with DX propagation? Is it that Argo has to 
compromise between best S/N on a dash and the dot, and the dot loses 
out (which would affect DFCW worst)? Do other people experience this 
effect on other spectrograms (eg SpecLab)? 

I am not attempting to rubbish any software. I am just trying to 
understand why this deliberate mis-match of Tx and Rx speeds is done 
in practice when theory suggests that it should make things worse.

Mike, G3XDV
==========