Message-ID: <3D53E33C.A829ED40@usa.net>
Date: Fri, 09 Aug 2002 17:43:56 +0200
From: "Alberto di Bene" <dibene@usa.net>
Organization: None
MIME-Version: 1.0
To: rsgb_lf_group@blacksheep.org
Subject: LF: Re: G4JNT and SM6LKM Jason beacons
References: <17chZQ-13Oc8eC@fwd05.sul.t-online.com>	 <5.1.0.14.0.20020808182124.00b0a1b0@gemini.herts.ac.uk>	 <005701c23f26$3e24c720$162565d5@oemcomputer>	 <17cwaH-07Lv5UC@fwd11.sul.t-online.com>	 <5.1.0.14.2.20020809073006.009f6690@mail.pncl.co.uk> <5.1.0.14.0.20020809115706.00a8a048@gemini.herts.ac.uk> <3D53C21E.83A9554@usa.net> <001501c23faf$dbdcc2e0$09dc9384@jka>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Sender: <majordom@post.thorcom.com>

John Andrews wrote:

> This brings to mind some WOLF recordings I made of M0BMU in March, 2001. The
> noise was dominated by static crashes and impulses, rather than the usual
> neighborhood buzz. The decoding process was greatly helped by the "-b"
> blanker option in WOLF. Then I processed the file through a brick-wall
> limiter in Cool Edit. That worked even better. As I recall, the limiter was
> created by yanking up the limiter curve so that everything above -60 dB was
> brought up to 0 dB. Nasty sounding, I can assure you.
> [...]

I have Jason V0.95 ready for release, but now maybe I could try to implement
into it that brick-wall limiter you mention John. Do you have any idea why the
Cool Edit processing didn't work with other files ?
What do you all think ?

73  Alberto  I2PHD