Date: Wed, 18 Jan 2017 09:02:12 -0500
From: Markus Vester <markusvester@aol.com>
To: rsgb_lf_group@blacksheep.org
Message-Id: <159b1e28cdd-ccc-4818@webprd-m102.mail.aol.com>
In-Reply-To: <159a6d4bb54-68ca-12c52@webprd-m75.mail.aol.com>
MIME-Version: 1.0
Subject: LF: New opds version
Content-Type: multipart/alternative; 
	boundary="----=_Part_23650_1246303330.1484748131546"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: RO

------=_Part_23650_1246303330.1484748131546
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Dear opds users,

I have recently discovered a minor bug in opds2h5c which could sometimes produce systematic false detections from partial correlations after the end of a strong Opera signal. This has hopefully been fixed in version 2h6:

 http://df6nm.de/opera/opds2h6.zip

This version should be completely compatible with existing configurations and ini files, so all you have to do is start opds2h6 instead of opds2h5c.

Differences are:
- potential false partial correlations are cross-checked against detections on the same frequency during the last 32 minutes, 
- to further reduce possible false detections triggered by strong non-Opera signals, the correlation threshold is now raised with signal strength. By default, it goes up linearly from 15 to 19 dB, starting at SNR -41 dBOp. If desired, this behavior can be modified by dedicated opds.ini entries,  
- the bug in the default filename pattern has been corrected, so the "pattern=*.txt" ini-line is no longer needed,
- unused parts of the code have been removed, resulting in a slightly smaller source and executable.

BTW For the old 16-bit QuickBasic versions before opds2h5b, I had recommended to prevent CPU-load peaks by running the process at lower priority. This seems to be no longer necessary. 

Best 73,
Markus (DF6NM)
------=_Part_23650_1246303330.1484748131546
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<div style=3D"font-size:10pt;font-family:arial,helvetica,sans-serif;color:b=
lack;"><p>Dear opds users,</p><p>I have recently discovered a minor bug in =
opds2h5c which could sometimes produce systematic false detections from par=
tial correlations after the end of a strong Opera signal. This has hopefull=
y been fixed in version 2h6:</p><p>&nbsp;http://df6nm.de/opera/opds2h6.zip<=
/p><p>This version should be completely compatible with existing configurat=
ions and ini files, so all you have to do is start opds2h6 instead of opds2=
h5c.</p><p>Differences are:<br>- potential false partial correlations are c=
ross-checked against detections on the same frequency during the last 32 mi=
nutes, <br>- to further reduce possible false detections triggered by stron=
g non-Opera signals, the correlation threshold is now raised with signal st=
rength. By default, it goes up linearly from 15 to 19 dB, starting at SNR -=
41 dBOp. If desired, this behavior can be modified by dedicated opds.ini en=
tries,&nbsp; <br>- the bug in the default filename pattern has been correct=
ed, so the "pattern=3D*.txt" ini-line is no longer needed,<br>- unused part=
s of the code have been removed, resulting in a slightly smaller source and=
 executable.</p><p>BTW For the old 16-bit QuickBasic versions before opds2h=
5b, I had recommended to prevent CPU-load peaks by running the process at l=
ower priority. This seems to be no longer necessary. </p><p>Best 73,<br>Mar=
kus (DF6NM)<br></p></div>
------=_Part_23650_1246303330.1484748131546--