Return-Path: Received: (qmail 87084 invoked from network); 4 Aug 2004 13:09:06 -0000 Received: from unknown (HELO ptb-spamcore01.plus.net) (192.168.71.1) by ptb-mailstore01.plus.net with SMTP; 4 Aug 2004 13:09:06 -0000 Received: from [192.168.67.3] (helo=ptb-mxcore03.plus.net) by ptb-spamcore01.plus.net with esmtp (Exim 4.32; FreeBSD) id 1BsLYH-000NGk-Eg for dave@picks.force9.co.uk; Wed, 04 Aug 2004 14:11:29 +0100 Received: from post.thorcom.com ([193.82.116.20]) by ptb-mxcore03.plus.net with esmtp (Exim) id 1BsLVy-000Lde-8P for dave@picks.force9.co.uk; Wed, 04 Aug 2004 14:09:06 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1BsLVX-0003Hv-46 for rs_out_1@blacksheep.org; Wed, 04 Aug 2004 14:08:39 +0100 Received: from [193.82.116.30] (helo=relay.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1BsLVW-0003Hm-KX for rsgb_lf_group@blacksheep.org; Wed, 04 Aug 2004 14:08:38 +0100 Received: from hestia.herts.ac.uk ([147.197.200.9]) by relay.thorcom.net with esmtp (Exim 4.34) id 1BsLVS-0006Js-VC for rsgb_lf_group@blacksheep.org; Wed, 04 Aug 2004 14:08:38 +0100 Received: from altair ([147.197.200.45] helo=altair.herts.ac.uk) by hestia.herts.ac.uk with esmtp (Exim 3.22 #1) id 1BsLV4-0002gY-00 for rsgb_lf_group@blacksheep.org; Wed, 04 Aug 2004 14:08:10 +0100 Received: from [147.197.164.230] (helo=JamesMorrits) by altair.herts.ac.uk with esmtp (Exim 3.36 #1) id 1BsLV3-0005pN-00 for rsgb_lf_group@blacksheep.org; Wed, 04 Aug 2004 14:08:09 +0100 From: "James Moritz" To: rsgb_lf_group@blacksheep.org Date: Wed, 4 Aug 2004 14:08:07 +0100 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-UH-MailScanner: No Virus detected X-Spam-Score: 0.6 (/) X-Spam-Report: autolearn=no,HTML_40_50=0.474,HTML_FONTCOLOR_UNKNOWN=0.1,HTML_MESSAGE=0.001 Subject: RE: LF: CW and other modes Content-Type: text/html; charset=windows-1252 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_40_50, HTML_FONTCOLOR_UNKNOWN,HTML_MESSAGE autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-Spam-Filtered: by PlusNet SpamCORE (v3.00) Content-transfer-encoding: 8bit

 

 

-----Original Message-----
From: owner-rsgb_lf_group@blacksheep.org [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of G4gvw@aol.com
Sent:
04 August 2004 13:05
To: rsgb_lf_group@blacksheep.org
Subject: Re: LF: CW and other modes

 

As a start John, we might have to define our terms as to what is acceptable as "speech transmission"!

Dependant upon the defined term we can commence with a series of logical steps toward such a goal.

At the "starter" end there is perhaps the simple "Voice-to-code, Code-to-voice" protocol of speech recognition to keyer

 

Dear LF Group,

 

In my rather limited knowledge, there seem to be two approaches. One is to encode the speech waveform in an efficient way that allows transmission at a relatively low data rate, whilst still allowing a reasonable facsimile of the speaker’s voice to be reconstructed at the receiving end. An example of this would be the “CELP” encoding used for GSM mobile phones. I think the problem for LF would be that the minimum practical bandwidth would still be fairly large – I recall G4JNT did some work on digital speech for HF in a SSB bandwidth – perhaps he could comment.

 

The other way would be not to worry about exactly reproducing the speaker’s voice, accepting that whoever the speaker was, they would always sound like Prof. Stephen Hawking at the receiver, but as G4GVW says, transmitting just the meaning of the spoken words. One way to to do this would be for speech recognition software at the transmitter to generate text that could be transmitted at maybe several 10s to a few 100 bits/s, and then fed into a speech synthesizer at the receiver. I think the problem with this is that speech recognition algorithms don’t seem to be very accurate – when used with word processors, etc. the user has to speak carefully, extensively “train” the software and make many corrections when the software identifies the wrong word. This is not so bad when the speaker reviews the text afterwards, but disastrous for a “real time” conversation in a difficult environment! I think that a possible way round this would be to break the speaker’s voice down into phonetic information rather than text – but perhaps someone knows better?

 

Cheers, Jim Moritz

73 de M0BMU