Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id wACKkLh1028534 for ; Mon, 12 Nov 2018 21:46:23 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gMJ2F-0003ta-S8 for rs_out_1@blacksheep.org; Mon, 12 Nov 2018 20:42:15 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gMJ2C-0003tL-VL for rsgb_lf_group@blacksheep.org; Mon, 12 Nov 2018 20:42:12 +0000 Received: from 576e.8172.0000.0000.0210.4001.0d0f.7062.ip6.static.sl-reverse.com ([2607:f0d0:1004:120::2718:e675] helo=mx1.lylix.net) by relay1.thorcom.net with esmtp (Exim 4.91_59-0488984) (envelope-from ) id 1gMJ2A-0002iL-HK for rsgb_lf_group@blacksheep.org; Mon, 12 Nov 2018 20:42:11 +0000 Received: from no3m.local (dynamic-acs-24-144-206-160.zoominternet.net [24.144.206.160]) (Authenticated sender: eric@lylix.net) by mx1.lylix.net (Postfix) with ESMTPSA id C22EC6C0040 for ; Mon, 12 Nov 2018 15:42:06 -0500 (EST) To: rsgb_lf_group@blacksheep.org References: <0ddf61c2-de83-aeef-f929-a87b698f560c@n1bug.com> <1542028810096.76526@kuleuven.be> <1542038390327.50768@kuleuven.be> <1542052074466.76606@kuleuven.be> <17488f94-c94d-a83f-f268-1fd335872b35@n1bug.com> From: Eric NO3M Message-ID: Date: Mon, 12 Nov 2018 15:42:05 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <17488f94-c94d-a83f-f268-1fd335872b35@n1bug.com> Content-Language: en-US X-Spam-Score: -0.0 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Paul, et.al. Correct, the original timings were fit into a "window" vs. simple scaling.  Since the slowJT exe wouldn't run in WINE, I just ran a few commands to decode K5DNL: arecord -c 1 -r 12000 -f S16_LE capture.wav sox capture.wav capture_tmp.wav speed 2.0 jt9 -9 -d 3 -S 300 capture_tmp.wav cat decoded.txt [...] Content analysis details: (-0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record X-Scan-Signature: 49f0f587e44d6711c57b8a4e950ba850 Subject: Re: LF: SlowJT9 v0.9.02 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit 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=none 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 Paul, et.al. Correct, the original timings were fit into a "window" vs. simple scaling.  Since the slowJT exe wouldn't run in WINE, I just ran a few commands to decode K5DNL: arecord -c 1 -r 12000 -f S16_LE capture.wav sox capture.wav capture_tmp.wav speed 2.0 jt9 -9 -d 3 -S 300 capture_tmp.wav cat decoded.txt decoded.txt: 0000   1  -26   0.1   2400.   1   VVV DE K5DNL           JT9 jt9 is the standard executable decoder from WSJTX v1.9.1. 73 Eric NO3M On 11/12/18 3:12 PM, N1BUG wrote: > Eric brings up a good point. Forget what I said the other day about > beaconing with a U3S to be received by SlowJT9. I believe that won't > work because the U3S uses the original JT9-2, -5, -10, -30 symbol > lengths which are different. > > Probably (a guess) in the original, symbol lengths were chosen to > fill as much of the period as possible while leaving enough time at > the end for decoding. I would further guess there were specific > decoders for each submode, or one decoder whose parameters could be > modified for the current submode. > > 73, > Paul N1BUG > > > On 11/12/18 2:47 PM, Rik Strobbe wrote: >> Hello Eric, >> >> >> yes, a scale factor of 2 and 5 is used. >> >> I hadn't any information about the old JT9-2 and JT9-5 modes and >> those scale factors seemed the most straightforward to me and >> make the conversion to JT9 easy. >> >> >> 73, Rik ON7YD - OR7T >> >> >> >>