Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-de03.r1000.mx.aol.com (Internet Inbound) with ESMTP id 794DC38000092; Sun, 28 Oct 2012 19:08:44 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TSbxP-0001PR-9X for rs_out_1@blacksheep.org; Sun, 28 Oct 2012 23:07:51 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TSbxO-0001PC-ON for rsgb_lf_group@blacksheep.org; Sun, 28 Oct 2012 23:07:50 +0000 Received: from mail-wg0-f47.google.com ([74.125.82.47]) by relay1.thorcom.net with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77) (envelope-from ) id 1TSbxM-0004HY-Ur for rsgb_lf_group@blacksheep.org; Sun, 28 Oct 2012 23:07:49 +0000 Received: by mail-wg0-f47.google.com with SMTP id ez12so2467356wgb.28 for ; Sun, 28 Oct 2012 16:07:48 -0700 (PDT) X-DKIM-Result: Domain=gmail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=rSsDzZ2Ai2yXgY5nsYvFzImwVoa9h2u4rGWIVuX/VJI=; b=oAbx8pVXT8lTyewXRMpcTSG+Vrn1woYzWMt0cCDZu03Fjpyp4xe2VSWsUREObV7KE9 hns8jZS5WmkPhg234E0evPlQntsUKB2kD2c1PGlu9FoAuHCXuZUwYZv89r4X6HxSK12c gY+arkKlJdYHgJMwQ+Td3GZO7uMWmGwOf3aZsoyZ44UPNfrQjQKHYVMPaQdubqqM55H7 tuIud3N5Ca9IPyIg0VX/+8X4v35UFet4Q4Gs68Ls5t0FjMVROgZ7DZwQi/sOXqqC9GGG 5QQl5ZdKxrHH/+qIriAJxNpXpLV1Cjr+eHXssNUnBGkfIrl2nxrU82EW3WNTymolxtWq j/Kw== Received: by 10.216.202.138 with SMTP id d10mr16429498weo.46.1351465668079; Sun, 28 Oct 2012 16:07:48 -0700 (PDT) Received: from [192.168.0.3] (cpc4-cmbg17-2-0-cust740.5-4.cable.virginmedia.com. [86.14.226.229]) by mx.google.com with ESMTPS id fg6sm71428wib.3.2012.10.28.16.07.47 (version=SSLv3 cipher=OTHER); Sun, 28 Oct 2012 16:07:47 -0700 (PDT) References: <508D86B7.1030001@princeton.edu> <007e01cdb55b$e823e3d0$6401a8c0@JAYDELL> Mime-Version: 1.0 (1.0) In-Reply-To: <007e01cdb55b$e823e3d0$6401a8c0@JAYDELL> Message-Id: <67439166-1A40-4DEF-AC3D-7CC7178A4E4E@gmail.com> Cc: "" X-Mailer: iPod Mail (10A403) From: Roger Lapthorn Date: Sun, 28 Oct 2012 23:07:47 +0000 To: "rsgb_lf_group@blacksheep.org" 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: Fully agree with this. A super-WSPR would be a great complement to JT9-x if combining the 2 is not sensible. 73s Roger G3XBM On 28 Oct 2012, at 22:30, wrote: [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [74.125.82.47 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (rogerlapthorn[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 69d86b33142413363dd56bd312139bf4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Re: LF: JT9 vs.WSPR X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=TO_ADDRESS_EQ_REAL 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-de03.r1000.mx.aol.com ; domain : gmail.com DKIM : pass x-aol-sid: 3039ac1d40cb508dbafb1543 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Fully agree with this. A super-WSPR would be a great complement to JT9-x if c= ombining the 2 is not sensible.=20 73s Roger G3XBM On 28 Oct 2012, at 22:30, wrote: >> The question in my mind is the degree to which beacon-like features shoul= d be mixed with a mode designed for making QSOs. If beaconing behavior is d= esired, why not use WSPR? If it's important to have, say, 10 dB better sens= itivity than WSPR, then maybe a "slow WSPR" mode should be developed and use= d, rather than JT9. >=20 >> -- 73, Joe, K1JT >=20 >=20 > <2 cents> >=20 > Joe ... agree with your assessment that JT9 should be kept as a QSO mode p= rogram and not a combination QSO / beacon mode program. The two sets of requ= irements are significantly different and trying to make a combination progra= m may end up being a compromise. WSPR does such a good job for beacon mode a= nd the database works so well it may make more sense to develop that further= . A number of us have been testing 'slow' WSPR modes (thanks to the work of M= arcus and Wolf) and the results have been impressive ... although the 'proof= of concept' arrangement using additional software is rather 'clunky'. If it= were possible to modify WSPR for several slower speeds, equal the performan= ce of WSJT-X JT9 and continue to use the WSPR database that sounds like a go= od plan. It would really be something if WSPR could decode stations running d= ifferent speeds simultaneously ... and indicate in the decoded information /= database which mode was decoded ... but that may be too much to ask. >=20 > Jay W1VD WD2XNS WE2XGR/2 >=20 > >=20 >=20 >=20 >=20 >=20 >=20 > ----- Original Message ----- From: "Joe Taylor" > To: > Sent: Sunday, October 28, 2012 3:25 PM > Subject: Re: LF: JT9 buggy issues >=20 >=20 >> Hi Roger, >>=20 >>> After about 1 minute or so, the program just closes itself and disappear= s >>> from the PC screen. >>=20 >> Please open a command-prompt window and start the program from there. For= example, >>=20 >> C:\> cd \wsjtx >> C:\> wsjtx >>=20 >> When the program dies, send me any error message left in the command-prom= pt window. >>=20 >>> I am using a SignalLink VOX controlled sound card interface that I use f= or >>> WSPR. Also, when I reload the program I have to reload my callsign, grid= >>> etc.every time. >>=20 >> This makes it sound like you may have ignored the installation advice in t= he Quick-Start Guide: "Under Vista or Windows 7 be sure to install WSJT-X in= to its own directory (the suggested default is c:\wsjtx) rather than C:\Prog= ram Files\wsjtx." Please confirm. >>=20 >>> Although I very much hope to use the mode for QSOs please do not >>> underestimate the value of a weak signal beaconing function with an >>> internet database. This has proved extremely valuable on WSPR as people >>> sometimes leave a RX and PC running to monitor when they are busy and no= t >>> available for QSOs. There will be far more people able to receive and >>> report than TX on MF/LF. This is especially true on 136kHz. >>=20 >> Yes, I understand these points, and beacons have their place. WSPR would= not be there if I did not believe this. >>=20 >> The question in my mind is the degree to which beacon-like features shoul= d be mixed with a mode designed for making QSOs. If beaconing behavior is d= esired, why not use WSPR? If it's important to have, say, 10 dB better sens= itivity than WSPR, then maybe a "slow WSPR" mode should be developed and use= d, rather than JT9. >>=20 >> -- 73, Joe, K1JT >=20 >=20