[arm-allstar] CW timing question

[Tom Whiteside]

Thanks for the comments on this and the cool work around!   I'm so happy
with my arm-allstar repeaters and appreciate the work and support you guys
do!

73 Tom N5TW

-----Original Message-----

Message: 2
Date: Fri, 29 Apr 2016 14:06:43 -0400 (EDT)
From: David McGough <kb4fxc at inttek.net>
To: Tom Whiteside via arm-allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] CW timing question
Message-ID:
	<Pine.LNX.4.44.1604291344430.12264-100000 at goliath.inttek.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII


Hi Tom,

I've never found the software generated CW to be a "precision" format.  
Depending of the hardware combo it can be slow, fast or nervous! It was
plain Schizo on one of my old ACID boxes from yesteryear!  LOL ....On
RPi2/RPi3/BBB hardware, it is typically fairly well behaved and I believe
adequate to satisfy the ID requirements. The timing is a compiled parameter,
requiring a re-compile to adjust.

Personally, I recommend just using a pre-recorded CW file for high-quality
results. That's really easy to do, using commands like:

echo "DE KB4FXC RPT" | tomorse -c 24 -s 20 > kb4fxc-rpt.wav sox
kb4fxc-rpt.wav -c 1 -r 8000 -v 0.25  kb4fxc-rpt-8kpcm.wav resample -ql

Unfortunately, the tomorse program isn't installed in our current ARM
codebase (perhaps in the next release?).  The source code is very small and
available here:

https://github.com/mathuin/tomorse/blob/master/tomorse.c


73, David KB4FXC