Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mj02.r1000.mx.aol.com (Internet Inbound) with ESMTP id 0356538000293; Thu, 1 Nov 2012 13:59:30 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TTz2B-0001Ay-31 for rs_out_1@blacksheep.org; Thu, 01 Nov 2012 17:58:27 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TTz2A-0001Ap-Iq for rsgb_lf_group@blacksheep.org; Thu, 01 Nov 2012 17:58:26 +0000 Received: from imr-ma05.mx.aol.com ([64.12.100.31]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1TTz28-00084n-Gz for rsgb_lf_group@blacksheep.org; Thu, 01 Nov 2012 17:58:25 +0000 Received: from mtaout-mb03.r1000.mx.aol.com (mtaout-mb03.r1000.mx.aol.com [172.29.41.67]) by imr-ma05.mx.aol.com (8.14.1/8.14.1) with ESMTP id qA1Hw7eQ010299 for ; Thu, 1 Nov 2012 13:58:07 -0400 Received: from White (nrbg-4d073f27.pool.mediaWays.net [77.7.63.39]) by mtaout-mb03.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id B46D3E00010B for ; Thu, 1 Nov 2012 13:58:04 -0400 (EDT) Message-ID: <0B8C17D7D22F4AFEA3C165F0C72234A9@White> From: "Markus Vester" To: References: <508D92BE.2040500@broadpark.no> <508ED047.1000504@broadpark.no> <508EEDA9.7070905@princeton.edu> <50901CB0.2040405@princeton.edu> <50917D09.2030908@princeton.edu> <509299E8.7010608@princeton.edu> Date: Thu, 1 Nov 2012 18:58:03 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20110426; t=1351792687; bh=w7VIwNFqCCdTAfErSydApiR49VVULhTNcEULb9BYovc=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=IVeHEFkOZiIWNhXkzNxoKAzwKLaKLknasyQS44Csyw+51UlriCOgM5npACwtzxsmC kj6WYDAmIUTWp/WrslLqcrlfOvY2hiHWCrYDAa8bhQGPNZGAfLSECpjrpP92FRKQ0i yT2pS9B6n7S1Ojwr0T/Lhb6xQPkFyntUJyCtfNgE= X-AOL-SCOLL-SCORE: 0:2:444403136:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-Spam-Score: -0.7 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Joe, here the sound comes in definitely with 16 bits, and also the 16-bit wav files are at the right level. I was actually speculating that there might be a high/low byte (little vs big endian) issue when wsjtx reads its audio buffers. At least that would explain 48 dB too much sensitivity... [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [64.12.100.31 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (markusvester[at]aol.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: e6360f34ef88d0e1db765f70efb2bfe9 Subject: Re: LF: Soundcard issues Content-Type: multipart/alternative; boundary="----=_NextPart_000_0045_01CDB862.D1EA4730" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_OUTLOOK_NAME 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-AUTHENTICATION: mtain-mj02.r1000.mx.aol.com ; domain : mx.aol.com DKIM : pass x-aol-sid: 3039ac1d7b965092b8823095 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0045_01CDB862.D1EA4730 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Joe, here the sound comes in definitely with 16 bits, and also the 16-bit wav = files are at the right level. I was actually speculating that there = might be a high/low byte (little vs big endian) issue when wsjtx reads = its audio buffers. At least that would explain 48 dB too much = sensitivity...=20 I've tried different audio levels by taking the mixer slider from = "normal" which has the green bar mostly topped up at 60 dB, down to one = tick producing under 30 dB. But this didn't sem to make much of a = difference regarding decoding success. Looks like it's more a matter of = "too-high SNR" than absolute audio levels? BTW all the wav files seem to have 8 bytes missing in their header, = which prevents them from being played eg by Windows sndrec32. In a hex = editor, the first line shows up as 00000000 5249 4646 0000 0000 4500 0000 666D 7420 RIFF....E...fmt=20 while some software expects file length info and a "WAVE" tag, like 00000000 5249 4646 F08F 0600 5741 5645 666D 7420 RIFF....WAVEfmt . Of course this is not a problem for reading in WSJT, and good old = Spectrogram (the one by R. Horne) doesn't seem to mind either.=20 Best 73, Markus (DF6NM) From: Joe Taylor=20 Sent: Thursday, November 01, 2012 4:48 PM To: rsgb_lf_group@blacksheep.org=20 Cc: rsgb_lf_group@yahoogroups.co.uk=20 Subject: LF: Soundcard issues ... Could it be that those who report having to move audio level sliders far = downward are using 24-bit soundcards, and their drivers are sending the=20 low 16 bits (via portaudio) to WSJT-X? I do not presently have another=20 explanation. I do not find any level discrepancies here. Obviously, I=20 cannot test hardware I do not have access to. ... ------=_NextPart_000_0045_01CDB862.D1EA4730 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Joe,
 
here the sound comes in definitely with = 16 bits,=20 and also the 16-bit wav files are at the right level. I was=20 actually speculating that there might be a high/low byte (little vs = big=20 endian) issue when wsjtx reads its audio buffers. At least that = would=20 explain 48 dB too much sensitivity... 
 
I've tried different audio levels by = taking the=20 mixer slider from "normal" which has the green bar mostly topped up at = 60 dB,=20 down to one tick producing under 30 dB. But this didn't sem to make much = of a=20 difference regarding decoding success. Looks like it's more a = matter of=20 "too-high SNR" than absolute audio levels?
 
BTW all the wav files seem to have 8 bytes missing = in=20 their header, which prevents them from being played eg by Windows = sndrec32. In a=20 hex editor, the first line shows up as
 00000000  5249 = 4646 0000 0000=20 4500 0000 666D 7420  RIFF....E...fmt
while some software expects file = length info=20 and a "WAVE" tag, like
 00000000 =20 5249 4646 F08F 0600 5741 5645 666D 7420  RIFF....WAVEfmt=20 .
Of course this is not a problem = for reading in=20 WSJT, and good old Spectrogram (the one by R. Horne) doesn't seem = to mind=20 either. 
 
Best 73,
Markus (DF6NM)
 
From: Joe=20 Taylor
Sent: Thursday, November 01, 2012 4:48 PM
Subject: LF: Soundcard issues

...
Could it be that=20 those who report having to move audio level sliders far
downward are = using=20 24-bit soundcards, and their drivers are sending the
low 16 bits = (via=20 portaudio) to WSJT-X?  I do not presently have another=20
explanation.  I do not find any level discrepancies here.  = Obviously, I
cannot test hardware I do not have access to.
... ------=_NextPart_000_0045_01CDB862.D1EA4730--