Delivered-To: daveyxm@virginmedia.com Received: by 10.50.237.98 with SMTP id vb2csp59473igc; Thu, 13 Feb 2014 12:42:35 -0800 (PST) X-Received: by 10.180.188.229 with SMTP id gd5mr7559628wic.54.1392324154304; Thu, 13 Feb 2014 12:42:34 -0800 (PST) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id p7si4728016wic.65.2014.02.13.12.42.33 for ; Thu, 13 Feb 2014 12:42:34 -0800 (PST) Received-SPF: neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) client-ip=195.171.43.25; Authentication-Results: mx.google.com; spf=neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) smtp.mail=owner-rsgb_lf_group@blacksheep.org Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1WE2wr-0002Nn-Ow for rs_out_1@blacksheep.org; Thu, 13 Feb 2014 20:31:53 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1WE2wr-0002Ne-5B for rsgb_lf_group@blacksheep.org; Thu, 13 Feb 2014 20:31:53 +0000 Received: from mout3.freenet.de ([195.4.92.93]) by relay1.thorcom.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.77) (envelope-from ) id 1WE2wp-00012H-2O for rsgb_lf_group@blacksheep.org; Thu, 13 Feb 2014 20:31:52 +0000 Received: from [195.4.92.142] (helo=mjail2.freenet.de) by mout3.freenet.de with esmtpa (ID dl4yhf@freenet.de) (port 25) (Exim 4.80.1 #4) id 1WE2wo-0000qZ-Jv for rsgb_lf_group@blacksheep.org; Thu, 13 Feb 2014 21:31:50 +0100 Received: from localhost ([::1]:53704 helo=mjail2.freenet.de) by mjail2.freenet.de with esmtpa (ID dl4yhf@freenet.de) (Exim 4.80.1 #4) id 1WE2wo-0003w0-Fy for rsgb_lf_group@blacksheep.org; Thu, 13 Feb 2014 21:31:50 +0100 Received: from mx6.freenet.de ([195.4.92.16]:54322) by mjail2.freenet.de with esmtpa (ID dl4yhf@freenet.de) (Exim 4.80.1 #4) id 1WE2u0-0004Sl-Bh for rsgb_lf_group@blacksheep.org; Thu, 13 Feb 2014 21:28:56 +0100 Received: from blfd-4db00b62.pool.mediaways.net ([77.176.11.98]:4674 helo=[192.168.178.21]) by mx6.freenet.de with esmtpsa (ID dl4yhf@freenet.de) (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (port 465) (Exim 4.80.1 #4) id 1WE2tz-0007it-TJ for rsgb_lf_group@blacksheep.org; Thu, 13 Feb 2014 21:28:56 +0100 Message-ID: <52FD2B06.8070305@freenet.de> Date: Thu, 13 Feb 2014 21:28:54 +0100 From: wolf_dl4yhf User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <728ab.22f842d6.402d5511@aol.com> <52FBFDC2.3060700@freenet.de> <4C328A591DE1472DAD4F2F0E758FC116@F6CNI> <52FD1E29.8050904@broadpark.no> <52FD217F.6050602@freenet.de> <5E9B273DC80D49F9AC20963337C96390@White> In-Reply-To: <5E9B273DC80D49F9AC20963337C96390@White> X-Originated-At: 77.176.11.98!4674 X-Spam-Score: -0.6 (/) 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: Hello Markus, ok, that would be possible, actually I thought about adding the audio-I/O-DLL based interface into WSQ2. Also having the hard-coded 1000 kHz center frequency editable would (alone) bring a big improvement as it keeps out those NDBs and other qrm which blocks the receiver. Then I could switch in the 270 Hz IF filter (which produces a fixed audio center frequency at ~ 650 Hz in the remotely controlled MF receiver). [...] Content analysis details: (-0.6 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [195.4.92.93 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (dl4yhf[at]freenet.de) -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: d2180dc2ab86baf139677702972e08e3 Subject: Re: LF: De F6CNI : Test WSQ Content-Type: multipart/alternative; boundary="------------070401010600010707030702" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,HTML_MESSAGE 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 This is a multi-part message in MIME format. --------------070401010600010707030702 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hello Markus, ok, that would be possible, actually I thought about adding the audio-I/O-DLL based interface into WSQ2. Also having the hard-coded 1000 kHz center frequency editable would (alone) bring a big improvement as it keeps out those NDBs and other qrm which blocks the receiver. Then I could switch in the 270 Hz IF filter (which produces a fixed audio center frequency at ~ 650 Hz in the remotely controlled MF receiver). Cheers, Wolf . Am 13.02.2014 21:10, schrieb Markus Vester: > Wolf, > rather than adding features to the WSQ sourcecode, why not use SpecLab > as an audio preprocessor? A couple of nights ago, inserting the noise > blanker function seemed to make a big improvement on the WSQ.display, > and the mixer will be useful to become agile with my fixed frequency > receiver. Using the free version VAC 3.12 which doesn't do audio > reformatting, I had to set SpecLab to 32 kHz samplerate stereo. > Best 73, > Markus (DF6NM) > > *From:* wolf_dl4yhf > *Sent:* Thursday, February 13, 2014 8:48 PM > *To:* rsgb_lf_group@blacksheep.org > *Subject:* Re: LF: De F6CNI : Test WSQ > > Hi Steinar and Andre, > > Thanks for the 2nd QSO Steinar - after QSY, you were perfectly readable > until that carrier in the center of the WSQ passband got too strong. > > For me, 477.3 kHz instead of 477.5 "USB dial" seems to be a better > choice at the moment. > But I will continue to monitor the waterfall and see if other carriers > creep in there. > I consider using a longer FFT + inverse FFT as automatic notch filter > for those 'super stable' carriers, which would be nulled out after > multiple WSQ2 symbols. Will ask the author for the sourcecodes, since I > am quite familiar with "C". > > About 472.2 "dial" .. even with the 1 kHz audio tone added, collisions > with CW are more or less pre-programmed.. > So my vote would be for a weak-signal *QSO* frequency range at the end > of the band. > But before that, I will observe that rarely-used segment (except maybe > for a beaconing mode which I don't use) a bit longer. > > 73, > Wolf DL4YHF . > > > Am 13.02.2014 20:34, schrieb Steinar Aanesland: > > I have been in qso with Wolf on 477.50, but I lost him in heavy QRM. I > > will qsy 472.200 but I am probably to weak for you . > > > > LA5VNA S > > > > > > > > > > > > On 13.02.2014 19:59, André Guyé wrote: > >> HI all, > >> > >> I can transmit on WSQ mode now. > >> > >> Is somebody wants to try that ? > >> > >> I am on 472.200 dial USB, but I can change this QRG... > >> > >> 73 de F6CNI Andy. > >> > >> > >> --- > >> Ce courrier électronique ne contient aucun virus ou logiciel > malveillant parce que la protection avast! Antivirus est active. > >> http://www.avast.com > >> > > > > > > > > > > > > --------------070401010600010707030702 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hello Markus,

ok, that would be possible, actually I thought about adding the audio-I/O-DLL based interface into WSQ2.
Also having the hard-coded 1000 kHz center frequency editable would (alone) bring a big improvement as it keeps out those NDBs and other qrm which blocks the receiver.
Then I could switch in the 270 Hz IF filter (which produces a fixed audio center frequency at ~ 650 Hz in the remotely controlled MF receiver).

Cheers,
  Wolf .



Am 13.02.2014 21:10, schrieb Markus Vester:
Wolf,
 
rather than adding features to the WSQ sourcecode, why not use SpecLab as an audio preprocessor? A couple of nights ago, inserting the noise blanker function seemed to make a big improvement on the WSQ.display, and the mixer will be useful to become agile with my fixed frequency receiver. Using the free version VAC 3.12 which doesn't do audio reformatting, I had to set SpecLab to 32 kHz samplerate stereo.
 
Best 73,
Markus (DF6NM)

Sent: Thursday, February 13, 2014 8:48 PM
Subject: Re: LF: De F6CNI : Test WSQ

Hi Steinar and Andre,

Thanks for the 2nd QSO Steinar - after QSY, you were perfectly readable
until that carrier in the center of the WSQ passband got too strong.

For me, 477.3 kHz instead of 477.5 "USB dial" seems to be a better
choice at the moment.
But I will continue to monitor the waterfall and see if other carriers
creep in there.
I consider using a longer FFT + inverse FFT as automatic notch filter
for those 'super stable' carriers, which would be nulled out after
multiple WSQ2 symbols. Will ask the author for the sourcecodes, since I
am quite familiar with "C".

About 472.2 "dial" .. even with the 1 kHz audio tone added, collisions
with CW are more or less pre-programmed..
So my vote would be for a weak-signal *QSO* frequency range at the end
of the band.
But before that, I will observe that rarely-used segment (except maybe
for a beaconing mode which I don't use) a bit longer.

73,
   Wolf  DL4YHF .


Am 13.02.2014 20:34, schrieb Steinar Aanesland:
> I have been in qso with Wolf on 477.50, but I lost him in heavy QRM. I
> will qsy 472.200 but I am probably to weak for you .
>
> LA5VNA S
>
>
>
>
>
> On 13.02.2014 19:59, André Guyé wrote:
>> HI all,
>>
>> I can transmit on WSQ mode now.
>>
>> Is somebody wants to try that ?
>>
>> I am on 472.200 dial USB, but I can change this QRG...
>>
>> 73 de F6CNI Andy.
>>
>>
>> ---
>> Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active.
>> http://www.avast.com
>>
>
>
>
>
>



--------------070401010600010707030702--