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;
Message-ID: <531F4D30.6030701@freenet.de>
Date: Tue, 11 Mar 2014 18:51:44 +0100
From: wolf_dl4yhf <dl4yhf@freenet.de>
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: <mppllsntwipx3rr2uwaakpiu.1394490205976@email.android.com>
In-Reply-To: <mppllsntwipx3rr2uwaakpiu.1394490205976@email.android.com>
Subject: Re: LF: WSQ2 new version uploaded
Content-Type: multipart/alternative;
 boundary="------------050104040404040701090408"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org

This is a multi-part message in MIME format.
--------------050104040404040701090408
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Domenico,

At the moment, there is only a subtle difference in the way the center 
frequency is measured (it uses interpolation between the center bin and 
its neighbours). The difference is neglectable unless the tones fall 
'right between two FFT bins'. But there will be further refinements 
soon. When finished, I will document them in my modified sourcecodes 
(the current one doesn't have the interpolation algorithm enabled).
Actually, as tested by DL3ZID recently, there seem to be cases where the 
interpolation *degrades* the decoding process, for reasons I don't fully 
understand yet ... maybe a bug in my algorithm, or maybe a problem with 
the principle itself :o)

More later,
   73,   Wolf .


Am 10.03.2014 23:27, schrieb ing.lindo:
> Good evening Wolf and all,
> Wolf, can you briefly explain differencies in algorithms of  ZL2AFP 
> and DL4YHF decoders?
> Thanks in advance.
>
> 73 Domenico, iz7slz
>
> Sent by Saturn 3S.90 with okitex
>
> -------- Original message --------
> From: wolf_dl4yhf
> Date:09/03/2014 11:49 PM (GMT+01:00)
> To: rsgb_lf_group@blacksheep.org
> Subject: Re: LF: WSQ2 new version uploaded
>
> Hi Michel,
>
> Ok, thanks for testing, and nice to hear the synthesizer 'drive' works 
> properly again.
>
>
> You wrote:
>> Re: LF: WSQ2 new version uploaded
>>
>> - According to me, sentence "/Select another comport to turn off 
>> PTT/" is wrong and confusing.
>>
>
> Maybe the intention is to emphasize 'after selecting another COM port, 
> the PTT is initally off" because that's what the function calls in the 
> PTT dialog window, after "OK", are doing.
>
>> The new serial port, if any, is not saved, therefore the correct port 
>> number has to be set in setup.txt
>> The serial port is opened at launch time if the Synthesizer checkbox 
>>  is already checked. Sometimes it's better to
>> open the port just before outputing data and release it when done, 
>> sometimes not  ( ie bluetooth serial port)
>>
> So we will have the option "leave the serial port open" or "close 
> after switching from TX to RX" added in the configuration.
> IMHO, 'setup.txt' should describe the synthesizer hardware but not the 
> port to which it is connected (on a particular machine). Here, for 
> example, windows has the bad habit to assign different COM port 
> numbers for the same hardware (an old 'Prolific' USB<->RS-232 
> adapter), depending into which USB port / hub / etc it is plugged : 
> "COM4 today, COM5 tomorrow" :o)
>
> 73,
>   Wolf .
>


--------------050104040404040701090408
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi Domenico,<br>
      <br>
      At the moment, there is only a subtle difference in the way the
      center frequency is measured (it uses interpolation between the
      center bin and its neighbours). The difference is neglectable
      unless the tones fall 'right between two FFT bins'. But there will
      be further refinements soon. When finished, I will document them
      in my modified sourcecodes (the current one doesn't have the
      interpolation algorithm enabled).<br>
      Actually, as tested by DL3ZID recently, there seem to be cases
      where the interpolation *degrades* the decoding process, for
      reasons I don't fully understand yet ... maybe a bug in my
      algorithm, or maybe a problem with the principle itself :o)<br>
      <br>
      More later,<br>
        73,   Wolf .<br>
      <br>
      <br>
      <br>
      <br>
      Am 10.03.2014 23:27, schrieb ing.lindo:<br>
    </div>
    <blockquote
      cite="mid:mppllsntwipx3rr2uwaakpiu.1394490205976@email.android.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div>Good evening Wolf and all,</div>
      <div>Wolf, can you briefly explain differencies in algorithms of
         ZL2AFP and DL4YHF decoders?</div>
      <div>Thanks in advance.</div>
      <div><br>
      </div>
      <div>73 Domenico, iz7slz</div>
      <div><br>
      </div>
      Sent by Saturn 3S.90 with okitex<br>
      <br>
      -------- Original message --------<br>
      From: wolf_dl4yhf <dl4yhf@freenet.de> <br>
        Date:09/03/2014 11:49 PM (GMT+01:00) <br>
        To: <a class="moz-txt-link-abbreviated" href="mailto:rsgb_lf_group@blacksheep.org">rsgb_lf_group@blacksheep.org</a> <br>
        Subject: Re: LF: WSQ2 new version uploaded <br>
        <br>
        <div class="moz-cite-prefix">Hi Michel,<br>
          <br>
          Ok, thanks for testing, and nice to hear the synthesizer
          'drive' works properly again.<br>
          <br>
          <br>
          You wrote:<br>
        </div>
        <blockquote cite="mid:1299579.20140309232921@mterrier.net"
          type="cite">
          <title>Re: LF: WSQ2 new version uploaded</title>
          <meta http-equiv="Content-Type" content="text/html;
            charset=UTF-8">
          <br>
          <span style=" font-family:'Calibri'; font-size: 12pt;"><br>
            - According to me, sentence "<i>Select another comport to
              turn off PTT</i>" is wrong and confusing. <br>
            <br>
          </span></blockquote>
        <br>
        Maybe the intention is to emphasize 'after selecting another COM
        port, the PTT is initally off" because that's what the function
        calls in the PTT dialog window, after "OK", are doing.<br>
        <br>
        <blockquote cite="mid:1299579.20140309232921@mterrier.net"
          type="cite"><span style=" font-family:'Calibri'; font-size:
            12pt;"> The new serial port, if any, is not saved, therefore
            the correct port number has to be set in setup.txt <br>
            The serial port is opened at launch time if the Synthesizer
            checkbox  is already checked. Sometimes it's better to <br>
            open the port just before outputing data and release it when
            done, sometimes not  ( ie bluetooth serial port)<br>
            <br>
          </span></blockquote>
        So we will have the option "leave the serial port open" or
        "close after switching from TX to RX" added in the
        configuration.<br>
        IMHO, 'setup.txt' should describe the synthesizer hardware but
        not the port to which it is connected (on a particular machine).
        Here, for example, windows has the bad habit to assign different
        COM port numbers for the same hardware (an old 'Prolific'
        USB&lt;-&gt;RS-232 adapter), depending into which USB port / hub
        / etc it is plugged : "COM4 today, COM5 tomorrow" :o)<br>
        <br>
        73, <br>
          Wolf .<br>
        <br>
      </dl4yhf@freenet.de></blockquote>
    <br>
  </body>
</html>

--------------050104040404040701090408--