Converting Tap files...

TapWav just works with Version 1 Tap files. For best results they should be "clean" and, possibly, data integrity should be checked first.
TapWav automatically detects "clean" files by calculating their purity (see ahead) and comparing it with a threshold value of 10. The value 10 is still considered a very good value for Tap files.
The program warns the user by showing the following dialog box in case it detects more than 10 variations:

Once a valid Tap Version 1 file to convert is opened, the following information will be displayed:

File location: full path and name of the Tap file opened;

File size: Tap File size (bytes);

Size Check: result of the check done between file size and data length information contained in the Tap file header;

Purity: number of different pulse values in the Tap file.

The save option will now be enabled, so that WAV files can be produced, using the chosen settings. Tapwav offers 5 sampling settings:

Sample Freq: to set the sampling frequency of the generated audio file; 3 values are possible, with a default selection of 44100 Hz;

Waveform: to set the sample shape; 2 values are possible, with a default "Square" selection. "Smoothed" solves some overrange problems occurring at a high sampling frequency around waveform edges;

Reverse samples: some soundcards seem to reverse samples during audio files playing. In order to obtain working tapes you need to select this option if your soundcard reverts samples;

Use NTSC timings: MTap from Markus Brenner (a Tap generation tool) supports Tap making at NTSC machines clock frequency, so this option may be used for Tap files generated with that option. It is suggested not to use this option;

Force long pulses being encoded as pauses: to produce a mute signal when a long pulse is found in the Tap file. When this option is active, edges are introduced at the beginning and at the end of the mute signal to guarantee a correct hardware triggering.

Here there's a shot of TapWav working on a clean Tap file:

In some cases TapWAV will signal the occurrence of some "aliasing warnings" (3 in the following example):

It means any square wave was syntetized using less than 10 samples (which is considered a safe value).
This fact may produce aliasing problems during Digital to Analogic conversion (i.e. when playing the Wav file on your PC). To avoid them, either use "clean" Tapes or try to increase the sampling frequency and retry. Note that increasing sampling frequency needs hi-fi performances of both your soundcard and audio recorder for producing a corresponding audio output.
If you meet permanent warnings and you are sure about your tap file quality, contact me.