Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-df02.r1000.mx.aol.com (Internet Inbound) with ESMTP id 9A69C38000084; Tue, 31 Jan 2012 03:07:06 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1Rs8ij-0007Pu-EY for rs_out_1@blacksheep.org; Tue, 31 Jan 2012 08:05:41 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Rs8ii-0007Pl-Fn for rsgb_lf_group@blacksheep.org; Tue, 31 Jan 2012 08:05:40 +0000 Received: from imr-ma02.mx.aol.com ([64.12.206.40]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1Rs8if-0005OG-Pt for rsgb_lf_group@blacksheep.org; Tue, 31 Jan 2012 08:05:40 +0000 Received: from mtaomg-mb02.r1000.mx.aol.com (mtaomg-mb02.r1000.mx.aol.com [172.29.41.73]) by imr-ma02.mx.aol.com (8.14.1/8.14.1) with ESMTP id q0V85W8k012112 for ; Tue, 31 Jan 2012 03:05:32 -0500 Received: from core-msc004c.r1000.mail.aol.com (core-msc004.r1000.mail.aol.com [172.29.233.205]) by mtaomg-mb02.r1000.mx.aol.com (OMAG/Core Interface) with ESMTP id E5620E000086 for ; Tue, 31 Jan 2012 03:05:31 -0500 (EST) References: <4F246297.4020304@charter.net><50DDDC5E26754BC284D529DCB4A1C2C3@White><4F258CB5.2090105@charter.net><4F25DA96.3080607@iup.uni-heidelberg.de><4F25F3D0.70503@iup.uni-heidelberg.de><4F26E06D.2000507@iup.uni-heidelberg.de><4F26E836.4010106@iup.uni-heidelberg.de> To: rsgb_lf_group@blacksheep.org In-Reply-To: X-MB-Message-Source: WebUI MIME-Version: 1.0 From: Markus Vester X-MB-Message-Type: User X-Mailer: Webmail 35412-STANDARD Received: from 77.191.130.60 by webmail-stg-m02.sysops.aol.com (64.12.222.101) with HTTP (WebMailUI); Tue, 31 Jan 2012 03:05:31 -0500 Message-Id: <8CEAE063CC0B209-1640-1BF3C@webmail-stg-m02.sysops.aol.com> X-Originating-IP: [77.191.130.60] Date: Tue, 31 Jan 2012 03:05:31 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20110426; t=1327997132; bh=isNSjlUxT5yXQb/N1F8Hm11eRjm7J+t7/F3BL/X3szk=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=Gz/K8i7yOU4glfunczzg+cW7ysq+UkpB9GzNG5d2ciTgcyCxy58Gp7hK/9O+Ckhn3 n5GShKqkVbVfV8uz+QLAJEJiNBkI+Vju5waoU3VN0ZZeGcg2U2F1n/LSEgiCaATp1Q tlVMeIzKsts42QoAE926CKTjpOUPtJU9OYTjMvrI= X-AOL-SCOLL-SCORE: 0:2:494363616:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-Spam-Score: 0.9 (/) X-Spam-Report: autolearn=disabled,HTML_10_20=0.945,HTML_MESSAGE=0.001,UNPARSEABLE_RELAY=0.001 Subject: Re: LF: WOLF Monkey Business Content-Type: multipart/alternative; boundary="--------MB_8CEAE063CC0B209_1640_6F42F_webmail-stg-m02.sysops.aol.com" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.1 required=5.0 tests=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-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:505092160:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-AOL-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-d277.2 ; domain : mx.aol.com DKIM : pass x-aol-sid: 3039ac1d40d64f27a1294120 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ----------MB_8CEAE063CC0B209_1640_6F42F_webmail-stg-m02.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Bill, thanks for the hint! A couple of days ago, I stumbled across this pro= blem but didn't get to the bottom of it. I had attempted to evade a slight = difference between the netbook's input and output samplerate at nominal 11.= 025. I tried 48000, 24000 and 8000 in WolfGui, and each time the output aud= io was low pitched. I ended up properly calibrating input and output SR sep= arately, entered the results (11025.387 and 11024.770 in my case) into the = config, and all was ok. Best 73, Markus -----Urspr=C3=BCngliche Mitteilung-----=20 Von: Bill de Carle An: rsgb_lf_group Verschickt: Di, 31 Jan 2012 3:44 am Betreff: LF: WOLF Monkey Business I have here two versions of the original WOLF command-line program:=20 0.51 and 0.61 - apparently there is also a version 0.62 which is used=20 by the GUI program. I wanted to duplicate what Stefan did using the GUI version: generate=20 a signal on 8970 Hz using 24000 s/s. It *seemed* to work OK but when=20 I examined the sound card output signal with Cool Edit, the frequency=20 was way low - about 8241 Hz instead of 8970. So I went back to the=20 original command line programs. I found that versions 0.51 and 0.61=20 apparently worked, generating 2,304,000 audio samples (exactly 96=20 seconds at 24000 s/s) to a file called WOLFX.WAV. Unfortunately the=20 samplerate in the .wav file header was coded as 8000 s/s, which means=20 if we played it back it would run for 288 seconds and the audio=20 carrier frequency would appear at 2990 Hz. So I went in and manually=20 changed the s/s field in the wav header to 24000 s/s. Then the file=20 worked OK. I was able to decode the message by mixing the 8970 Hz=20 down to 800 Hz and decimating the sample rate to 8000 s/s. Turning=20 again to the GUI version, I asked it to encode a .wav file at 24000=20 s/s with a carrier freq of 8970 Hz. It reported version 0.62 and=20 everything OK. However, when I examined the WOLFX.WAV file so=20 created, its .wav header said the samplerate was 22050 s/s instead of=20 24000 s/s! That explains why the real-time GUI uutput seemed low in=20 frequency: 8970 * 22050 / 24000 =3D 8241.1875 Hz. The upshot is we=20 need to manually check the wav header and set the s/s field to 24000=20 instead of whatever else it might say. And furthermore, don't trust=20 the real-time Tx soundcard output signal frequency with the GUI=20 version, especially when using odd-ball sample rates and high output=20 frequencies which may never have been tested. Be aware that WOLF=20 generates envelope-shaped audio, so it might be more difficult to=20 convert it to a clean square wave to drive a Tx, especially near the=20 phase transitions where the amplitude drops down to zero. 73, Bill VE2IQ ----------MB_8CEAE063CC0B209_1640_6F42F_webmail-stg-m02.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"
Bill, thanks for the hint! A couple of days ago, I stumbled acros= s this problem but didn't get to the bottom of it. I had attempted to = evade a slight difference between the netbook's input and output samplerate= at nominal 11.025. I tried 48000, 24000 and 8000 in WolfGui, and each= time the output audio was low pitched. I ended up properly calib= rating input and output SR separately, entered the results (11025.387 and 1= 1024.770 in my case) into the config, and all was ok.
 
Best 73,
Markus

-----Urspr=C3=BCngliche Mitteilung-----
Von: Bill de Carle <ve2iq@magma.ca>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org>
Verschickt: Di, 31 Jan 2012 3:44 am
Betreff: LF: WOLF Monkey Business
I have here two versions of the original WOLF command-line program= :
0.51 and 0.61 - apparently there is also a version 0.62 which is used
by the GUI program.

I wanted to duplicate what Stefan did using the GUI version: generate
a signal on 8970 Hz using 24000 s/s.  It *seemed* to work OK but when =
I examined the sound card output signal with Cool Edit, the frequency
was way low - about 8241 Hz instead of 8970.  So I went back to the original command line programs.  I found that versions 0.51 and 0.61 <= br> apparently worked, generating 2,304,000 audio samples (exactly 96
seconds at 24000 s/s) to a file called  WOLFX.WAV.  Unfortunately= the
samplerate in the .wav file header was coded as 8000 s/s, which means
if we played it back it would run for 288 seconds and the audio
carrier frequency would appear at 2990 Hz.  So I went in and manually =
changed the s/s field in the wav header to 24000 s/s.  Then the file <= br> worked OK.  I was able to decode the message by mixing the 8970 Hz down to 800 Hz and decimating the sample rate to 8000 s/s.  Turning again to the GUI version, I asked it to encode a .wav file at 24000
s/s with a carrier freq of 8970 Hz.  It reported version 0.62 and
everything OK.  However, when I examined the WOLFX.WAV file so
created, its .wav header said the samplerate was 22050 s/s instead of
24000 s/s!  That explains why the real-time GUI uutput seemed low in <= br> frequency: 8970 * 22050 / 24000 =3D 8241.1875 Hz.  The upshot is we need to manually check the wav header and set the s/s field to 24000
instead of whatever else it might say.  And furthermore, don't trust <= br> the real-time Tx soundcard output signal frequency with the GUI
version, especially when using odd-ball sample rates and high output
frequencies which may never have been tested.  Be aware that WOLF
generates envelope-shaped audio, so it might be more difficult to
convert it to a clean square wave to drive a Tx, especially near the
phase transitions where the amplitude drops down to zero.

73,
Bill VE2IQ

----------MB_8CEAE063CC0B209_1640_6F42F_webmail-stg-m02.sysops.aol.com--