Return-Path: X-Spam-DCC: paranoid 1233; Body=2 Fuz1=2 Fuz2=2 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_40_50,HTML_MESSAGE,SPF_PASS autolearn=no version=3.1.3 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by paranoid.lipkowski.org (8.13.7/8.13.7) with ESMTP id u2K9RSIj030075 for ; Sun, 20 Mar 2016 10:27:28 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ahZZv-0005Kb-Mj for rs_out_1@blacksheep.org; Sun, 20 Mar 2016 09:23:19 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1ahZZv-0005KS-93 for rsgb_lf_group@blacksheep.org; Sun, 20 Mar 2016 09:23:19 +0000 Received: from omr-a012e.mx.aol.com ([204.29.186.61]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.86) (envelope-from ) id 1ahZZs-00048S-I7 for rsgb_lf_group@blacksheep.org; Sun, 20 Mar 2016 09:23:18 +0000 Received: from mtaout-aag02.mx.aol.com (mtaout-aag02.mx.aol.com [172.26.126.78]) by omr-a012e.mx.aol.com (Outbound Mail Relay) with ESMTP id 42FAC380008B for ; Sun, 20 Mar 2016 05:23:14 -0400 (EDT) Received: from White (ipbcc05f3c.dynamic.kabel-deutschland.de [188.192.95.60]) by mtaout-aag02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id BC19F38000084 for ; Sun, 20 Mar 2016 05:23:13 -0400 (EDT) Message-ID: From: "Markus Vester" To: References: Date: Sun, 20 Mar 2016 10:22:41 +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 x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1458465794; bh=ipAJJqiu6jkbN60WEM2BB/izTzoYsqKhpA34WcBJeZk=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=XVRWNBd8SdvXgEje4W6AHzeB0pF6jDHJvOwfil80n7hBn4eSfQyi81TTnj7Jrm5Q4 tJL7RN07zQdQTIUO6hz91YuCQbfOBi+UiNUUIHyx6fZ6HOS1OnXPrEeBBEb1imDrDT P0J+pf7p/1/Tq5do9nRDSGB/Yis7U5ANunX8mjVM= x-aol-sid: 3039ac1a7e4e56ee6c013e0c X-AOL-IP: 188.192.95.60 X-Scan-Signature: 860e51ceecdf98b32e8eba101d9d472d Subject: Re: LF: JT9 Activity right now Content-Type: multipart/alternative; boundary="----=_NextPart_000_0022_01D18292.6F5FF210" 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-Scanned-By: MIMEDefang 2.56 on 10.1.3.11 Status: O X-Status: X-Keywords: X-UID: 7428 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0022_01D18292.6F5FF210 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Thank you Vinny, for the nice idea and the invitation to the party!=20 For me, it sure was a lot of fun, and resulted in a number of JT9 QSO's = with OR7T, DG0RG, SV8CS, SV3DVO, DL6II, DD2UJ, IW4DXW, LA8AV, F6CNI, and = DK7FC. Most signals were promptly decodable (except for my report from = DL6II which was lost due to temporary drift). A copy of my receive log = is at http://df6nm.bplaced.net/MF/jt9_party_160319.txt . But operating workflow was not easy for me. I don't have an MF SSB = transmitter available here, just an AD8950 DDS-board with a three-wire = serial interface. So I decided to modify my homemade WSPR software, such = that it reads a message from the command line, converts it to tone = numbers by calling Joe's JT9CODE.EXE, and plays it at the beginning of = the next minute. Lacking the "late-start feature", the text had to be = typed and ready on time, and it was practically impossible to = immediately reply to a decoded message. This was further exacerbated by = the lack of automatic message generation ("three click QSO"), and some = uncertainties of shorthand versus free-text length. I'm sorry if I have = been taxing the patience of my QSO partners! Regarding the receive software, if I had two free wishes this is what I = would suggest: - Show decodes as spectrogram labels:=20 Coming from visual QRSS, I like to "see" who I work. With many stations = in the spectrogram, it can be challenging to keep an oversight on who is = who, and on which frequency. It would be nice to see the decoded = messages as labels near or on the traces in a wide horizontal = spectrogram. replying by clicking on colour-highlighted labels would = seem more intuitive than clicking in the separate text decode window. - Show partial decodes: When the signal is not too weak, the software could already attempt to = decode a message before it has been completely received. Decoding zero = padded audio (e.g. two extra times after 30 and 40 seconds) would give = the operator significantly more time to think up an appropriate = (non-automatic) response. Best 73,=20 Markus (DF6NM) From: Vincent Stallbaum=20 Sent: Saturday, March 19, 2016 10:38 PM To: rsgb_lf_group@blacksheep.org=20 Subject: LF: JT9 Activity right now Ufb activity right now with a few new stations in JT9 mode. Feel free to = join the QSO party!=20 73=20 Vincent, DL6II ------=_NextPart_000_0022_01D18292.6F5FF210 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
Thank you Vinny, for=20 the nice idea and the invitation to the party!
 
For me, it sure was a lot of fun, and = resulted in a=20 number of JT9 QSO's with OR7T, DG0RG, SV8CS, SV3DVO, DL6II, DD2UJ, = IW4DXW,=20 LA8AV, F6CNI, and DK7FC. Most signals were promptly decodable (except=20 for my report from DL6II which was lost due to temporary drift). A = copy of=20 my receive log is at http://df6nm.bp= laced.net/MF/jt9_party_160319.txt .
 
But operating workflow was not easy for = me. I don't=20 have an MF SSB transmitter available here, just an AD8950 DDS-board with = a three-wire serial interface. So I decided to modify my homemade = WSPR=20 software, such that it reads a message from the command line, converts = it to=20 tone numbers by calling Joe's JT9CODE.EXE, and plays it at the beginning = of the=20 next minute. Lacking the "late-start feature", the text had to be = typed and=20 ready on time, and it was practically impossible to immediately = reply to a=20 decoded message. This was further exacerbated by the lack = of=20 automatic message generation ("three click QSO"),=20 and some uncertainties of shorthand versus free-text=20 length. I'm sorry if I have been taxing the patience of my QSO=20 partners!
 
Regarding the receive software, if I = had two free=20 wishes this is what I would suggest:
 
- Show decodes as spectrogram labels: =
Coming from visual QRSS, I like to = "see" who I=20 work. With many stations in the spectrogram, = it can=20 be challenging to keep an oversight on who is who, and on = which=20 frequency. It would be nice to see the decoded messages as = labels=20 near or on the traces in a wide horizontal spectrogram. replying by = clicking on colour-highlighted labels would seem more intuitive = than=20 clicking in the separate text decode window.
 
- Show partial = decodes:
When the signal is not too weak, the=20 software could already attempt to decode a message before = it has=20 been completely received. Decoding zero padded audio (e.g. two = extra times=20 after 30 and 40 seconds) would give the operator significantly more = time to=20 think up an appropriate (non-automatic) response.
 
Best 73,
Markus (DF6NM)
 
From: Vincent Stallbaum
Sent: Saturday, March 19, 2016 10:38 PM
To: rsgb_lf_group@blacksheep.org= =20
Subject: LF: JT9 Activity right now

Ufb activity right now with a few new stations in JT9 = mode. Feel=20 free to join the QSO party!=20

73 
Vincent, DL6II
------=_NextPart_000_0022_01D18292.6F5FF210--