SoundTrap Click Detector

If you are using a SountTrap recording device with built in click detection from Ocean Instruments, you may need to use a modified version of the Click Detector.

The SoundTrap click detector allows you to detect and store clicks at high frequencies (say 384kS/sec), suitable for odontocete echolocation clicks, and at the same time, record audio data files at a lower frequency (e.g. 96 or 48kS/sec). This optimises disk space usage and makes long deployments of several months possible without running out of data storage.

Having two sample rates present within a single PAMGuard configuration is possible using Decimator modules. However such configurations become particularly complicated to configure when the sample rate of the recorded files is lower than the sample rate of the click detector.

We therefore recommend that you use a modified version of the Click Detector, which manages it’s own sample rate and channel information based on information extracted from the SoundTrap data.

Note that the SoundTrap click detector should only be used for clicks automatically detected by the SoundTrap. If you want to detect clicks from the SoundTrap recordings, then use a normal Click Detector in the normal way.

Creating an instance of the SoundTrap Click Detector

From the File>Add modules>Detectors menu, or from the pop-up menu on the data model display, select ‘SoundTrap Click Detector’ near the bottom of the Detectors list. Enter a descriptive name for the new detector and press Ok.

Importing SoundTrap Data

SoundTrap data are stored in proprietary files called SUD files.

There are two ways in which you can get data from SUD files into the SoundTrap Click Detector.

The Old Way

The ‘standard’ way of using SoundTrap data was to inflate all of the data from the compressed SUD files. For details of this process, see the SoundTrap user manuals and the SoundTrap Host software.

Normally, several inflated files are generated from each sud file:

  1. A wav file: Audio data in standard wav file format
  2. An XML file: Metadata on the SoundTrap configuration, file start times in various formats, etc.
  3. If the click detector was running BCL and DWV files, which contain the times of clicks and click waveforms respectively.

To convert the SUD files to the binary storage format used by PAMGuard, working in the PAMGuard Viewer, create a Binary Store, a SoundTrap Click Detector and also create a ‘SoundTrap Detector Import’ module. Then use the import module to import the BCL and DWV data into PAMGuard. Once imported you can run Click Classifiers and use other Click Detector offline functions to mark events, etc.

If you want to run additional analysis on the WAV file data (for example to make noise measurements or to detect whistles), create a different PAMGuard configuration to process those data.

The (better) New Way

Current versions of PAMGuard can read SUD files directly, without first unpacking them into WAV, XML, BCL and DWV files. This not only reduces the amount of disk space you need by about x4, but also saves a lot of time.

Better still, you can now set up PAMGuard in normal mode to simultaneously process the audio data in the SUD file with one set of detectors, and simultaneously extract the click detector data into appropriate files for a SoundTrap Click Detector.

Start PAMGuard in Normal Mode and add a Sound Acquisition module. Add a SoundTrap Click Detector, a Binary Store store and a Database module (optional). In the Sound Acquisition dialog select a single SUD file or a folder of SUD files. At this point, the SoundTrap Click Detector will be automatically configured with the correct sample rate (which won’t be the sample rate displayed in the Sound Acquisition module).

Configure any Click Classifiers you want to be run on the SoundTrap click data as it is imported.

You can then add any other detectors and measurement processes you want to run on the SoundTrap audio data, this may include instances of the normal Click Detector module if you want to detect clicks in the lower frequency audio data.

Process the data in the normal way and clicks will automatically be generated within the SoundTrap click detector

Further process you data using the PAMGuard Viewer in the normal way.

SoundTrap Dates and Timezones

Soundtrap dates can be confusing (to be polite about it)

sud file names generally use a local time for the computer that either set up the soundtrap, or downloaded the files from the soundtrap.

However, the sud files contain a UTC time stamp, which will be correct if the local time and time zone on your computer were correct - basically, they will be correct if your computer is connecting to the internet and settings it’s own clock. PAMGuard will extract this UTC time and use it for output file names and for data.

So, for example, if you were on the US East coast (UTC-5) and collected data at 1700 (5pm) on 10 August, 2025 you’d get a sud file called 8565.250810170000.sud, which would generate a binary file called SoundTrap_Click_Detector_SoundTrap_Click_Detector_Clicks_20250810_210000.pgdf, i.e. at 5pm on the East Coast, it’s 2100 UTC.

When processing sud file data, you should therefore leave the timezone information in the Acquisition module on it’s default setting of UTC - zero offset.

If you’ve been fiddling with the time settings on your computer, this may no longer be the case in which case you may be able to correct the times in the data to UTC using the time zone settings in the Acquisition module. Generally though, you shouldn’t touch it!

Similarly, if you’ve unpacked the sud file data, the wav file will have the same name as the sud file. However, PAMGuard is smart, and will look in the xml file (again, has the same name) for the correct UTC time and use that. So keep all the files you extracted from the sud file together. You’ll get different results if you take the wav files without the xml files to what you’ll get if you keep the xml files with them wav’s.