[Lowfer] WOLF thoughts

[Jonathan Jesse]

Hi all,
This message was from Lyle last season (thanks Lyle).  With the WOLF tests
going on, I thought it would be a good idea to send it again.  It shows how
to use a batch file to process a number of WOLF captures unattended.  It
sure comes in handy.

73,
Jon W1JHJ



>Delivered-To: w1jhj@netzero.net
>Date: Wed, 28 Mar 2001 09:45:38 -0600
>From: Lyle Koehler <lyle@mlecmn.net>
>X-Mailer: Mozilla 4.5 [en] (Win95; I)
>X-Accept-Language: en
>To: Jonathan Jesse <w1jhj@netzero.net>
>Subject: Re: [Lowfer] WOLF thoughts
>
>Good thought. I think it can be done with a good old DOS "batch" file,
>with the help of a tip that John Andrews posted to the Longwave Message
>Board, and which I'll take the liberty of quoting here:
>
>"There are two redirection commands that may be useful in saving WOLF
>outputs to a text file.
>The command  
>    wolf -f 799.765 -r 8001.96 > test
>would execute WOLF with the parameters listed, but instead of sending
>the results to the screen, they would be saved in a text file called
>"test". If you were to run this line again, it would erase and overwrite
>the "test" file. On the other hand, 
>    wolf -f 799.765 -r 8001.96 >> test
>will save the output in the "test" file, but will append it to any
>existing text in that file. Note that in either case, the WOLF output
>will not appear on the screen. You'll have to look at the file with a
>text editor to see it."
>
>I think the batch file for processing a series of 4 RecAll wave files
>would look something like this. (In my case, the wave files and wolf.exe
>are in the directory WOLF on drive G.)
>
>G:
>cd\wolf
>wolf -q lek_1.wav -f 900.5 -r 7999.61 -l -b >> test
>wolf -q lek_2.wav -f 900.5 -r 7999.61 -l -b >> test
>wolf -q lek_3.wav -f 900.5 -r 7999.61 -l -b >> test
>wolf -q lek_3.wav -f 900.5 -r 7999.61 -l -b >> test
>
>You can use any text editor such as Notepad to create the file, making
>use of the copy and paste feature so that it's only necessary to change
>the wave file name. The file would be given a name like wolfer.bat and
>saved in any convenient location. I'll give it a try later today and
>report back if it works.
>
>Lyle, K0LR
>Jonathan Jesse wrote:
>> 
>> While decoding a nights worth of .wav files for later decoding through
>> WOLF, I had an idea (ut oh!).
>> I'm not a programer and I probably don't know what I'm talking about but
>> here goes.
>> 
>> Would it be possible to write a script that would decode WOLF .wav files
>> and send them to a text file for later viewing?  Maybe it could be set up
>> to launch the WOLF command line like "wolf -q lek_2.wav -f 900.5 -r 7999.61
>> -l -b"  Of course the commands would be set for what YOU need them set for.
>>  Then could it be set up so that after the first file is read, another file
>> would automatically be read in sequential order.  So now after decoding
>> "lek_2.wav", "lek_3.wav" would be read with the same command line and
>> dumped to the same or different text file.
>> If this could be done, I/we could have a whole overnights worth of data
>> decoded while at work.
>> Am I dreaming and or way off base?
>
>
----------------------------------------------------
Sign Up for NetZero Platinum Today
Only $9.95 per month!
http://my.netzero.net/s/signup?r=platinum&refcd=PT97