DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=sbcglobal.net;
  h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=nRP3Vnv6bS4Yu7dSjXeJRLh6xZjDjdm6ZDDpTE6qFkk2Rz5SPMOfP3IbtkSerLWSeHMmoXlDl0qUhwvC8l6pE/yNCajdtOQZF7i58NCI/BE+XCAXadjqHkixcb1uFvYwdq9vn1gsP3ne43ZBrR5QvyU6CNDElQo0tjxsJ3VmWf8=;
References: <8D468B5D9DCA4B6D90ED557E68BB66AF@White> <508F157E.9040108@iup.uni-heidelberg.de> <508FAB27.2050909@psk31.plus.com> <508FD677.2050807@iup.uni-heidelberg.de>
Message-ID: <1351611128.60803.YahooMailRC@web181304.mail.ne1.yahoo.com>
Date: Tue, 30 Oct 2012 08:32:08 -0700 (PDT)
From: John Langridge <jlangridge@sbcglobal.net>
To: rsgb_lf_group@blacksheep.org
In-Reply-To: <508FD677.2050807@iup.uni-heidelberg.de>
MIME-Version: 1.0
Subject: Re: LF: JT9-1 and 2, echoes, waterfall
Content-Type: multipart/alternative; boundary="-1455435280-926053607-1351611128=:60803"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org


---1455435280-926053607-1351611128=:60803
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

The bursts you were seeing were resolved by several of us here stateside by=
 =0Aselecting a different audio codec under setup/options.  I know of two o=
f us that =0Apersonally found the Direct-X HD codec listed in the drop down=
 box to work well =0Afor Vista and Win7 64.=0A=0A73,=0A=0AJohn KB5NJD/WG2XI=
Q=0A=0A=0A=0A=0A________________________________=0AFrom: Stefan Sch=E4fer <=
Stefan.Schaefer@iup.uni-heidelberg.de>=0ATo: rsgb_lf_group@blacksheep.org=
=0ASent: Tue, October 30, 2012 8:33:26 AM=0ASubject: Re: LF: JT9-1 and 2, e=
choes, waterfall=0A=0AHi Eddie, LF,=0A=0AAm 30.10.2012 11:25, schrieb g3zjo=
: =0AHi Stefan=0A>=0A>I found the lack / loss of decodes annoying, one caus=
e was slight frequency =0A>drift in my transverter, WSPR is not effected bu=
t JT9-2 is.=0A>I feel there were other periods of unexplained non de-codes =
too.=0A>=0A>Was it you who mentioned the burst at the end of the signal. I =
was hearing a =0A>tuneful diddle at the end of G3XIZ transmission, I hear a=
 burst of distorted =0A>rattle on my own signal.=0A>=0A>Eddie=0A>=0ANo, it =
was DF6NM who mentioned the burst at the end but i saw it as well. It was =
=0Apart of the end of my signal.=0A=0AWith the new version things became a =
bit better. The initial crashes didn't =0Ahappen any more for me. As i assu=
me, this is probably due to the decoder that =0Ahas to much work to do in a=
 1 minute period when the range is set to center+-50 =0AHz and if the CPU p=
ower is relatively low or other task have to be performed to =0Athe same ti=
me. When reducing the range to e.g. +-10 Hz there was no problem on =0Amy X=
P PC (512 MB RAM)  (no decodes though). On my Win7 PC (32 bit, 4GB RAM) =0A=
there were no problems and i got successful decodes.=0A=0AProbably there ha=
ve to be some improvements on the decoder. We all confirmed =0Athat these p=
roblems are not present in WSPR, so Joe may already know what the =0Aculpri=
t is.=0A=0AIt's one of the first releases of the software so we obviously h=
ave to be =0Apatient for some more time.=0A=0AOn request of DU1GM i will tr=
ansmit JT9-30, beginning arround 15 UTC on 137.44 =0AkHz (+- a few Hz), ful=
l power!=0A=0A73, Stefan/DK7FC=0A
---1455435280-926053607-1351611128=:60803
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:Courier New,courier,monaco,monospace,san=
s-serif;font-size:12pt"><div>The bursts you were seeing were resolved by se=
veral of us here stateside by selecting a different audio codec under setup=
/options.&nbsp; I know of two of us that personally found the Direct-X HD c=
odec listed in the drop down box to work well for Vista and Win7 64.<br><br=
>73,<br><br>John KB5NJD/WG2XIQ<br></div><div style=3D"font-family:Courier N=
ew, courier, monaco, monospace, sans-serif;font-size:12pt"><br><div style=
=3D"font-family:times new roman, new york, times, serif;font-size:12pt"><fo=
nt face=3D"Tahoma" size=3D"2"><hr size=3D"1"><b><span style=3D"font-weight:=
 bold;">From:</span></b> Stefan Sch=E4fer &lt;Stefan.Schaefer@iup.uni-heide=
lberg.de&gt;<br><b><span style=3D"font-weight: bold;">To:</span></b> rsgb_l=
f_group@blacksheep.org<br><b><span style=3D"font-weight: bold;">Sent:</span=
></b> Tue,
 October 30, 2012 8:33:26 AM<br><b><span style=3D"font-weight: bold;">Subje=
ct:</span></b> Re: LF: JT9-1 and 2, echoes, waterfall<br></font><br>=0A=0A=
=0A=0A=0A  =0A=0A=0AHi Eddie, LF,<br>=0A<br>=0AAm 30.10.2012 11:25, schrieb=
 g3zjo:=0A<blockquote type=3D"cite">=0A=0A  =0AHi Stefan<br>=0A  <br>=0AI f=
ound the lack / loss of decodes annoying, one cause was slight=0Afrequency =
drift in my transverter, WSPR is not effected but JT9-2 is.<br>=0AI feel th=
ere were other periods of unexplained non de-codes too.<br>=0A  <br>=0AWas =
it you who mentioned the burst at the end of the signal. I was=0Ahearing a =
tuneful diddle at the end of G3XIZ transmission, I hear a=0Aburst of distor=
ted rattle on my own signal.<br>=0A  <br>=0AEddie<br>=0A</blockquote>=0A<br=
>=0ANo, it was DF6NM who mentioned the burst at the end but i saw it as=0Aw=
ell. It was part of the end of my signal.<br>=0A<br>=0AWith the new version=
 things became a bit better. The initial crashes=0Adidn't happen any more f=
or me. As i assume, this is probably due to the=0Adecoder that has to much =
work to do in a 1 minute period when the range=0Ais set to center+-50 Hz an=
d if the CPU power is relatively low or other=0Atask have to be performed t=
o the same time. When reducing the range to=0Ae.g. +-10 Hz there was no pro=
blem on my XP PC (512 MB RAM)&nbsp; (no decodes=0Athough). On my Win7 PC (3=
2 bit, 4GB RAM) there were no problems and i=0Agot successful decodes.<br>=
=0A<br>=0AProbably there have to be some improvements on the decoder. We al=
l=0Aconfirmed that these problems are not present in WSPR, so Joe may=0Aalr=
eady know what the culprit is.<br>=0A<br>=0AIt's one of the first releases =
of the software so we obviously have to=0Abe patient for some more time.<br=
>=0A<br>=0A<b>On request of DU1GM i will transmit JT9-30, beginning arround=
 15 UTC=0Aon 137.44 kHz (+- a few Hz), full power!</b><br>=0A<br>=0A73, Ste=
fan/DK7FC<br>=0A=0A=0A</div></div>=0A=0A=0A=0A</div></body></html>
---1455435280-926053607-1351611128=:60803--