Thank you for the sound trigger system. In general it seems to work quite nicely on completely calm nights with high filter set at 15kHz and 196, 250 and 384 samplings a good balance is found at a amplitude level of ~120-130. At low amplitudes below 80 intrumental effects create false alarms and trigger is not effective any more. I am quite satisfied, thanks for the wole team!

I had the same problem with win10. The download creates a (name).part file during the download, but fails to complete the download. Maybe the closing bit missing? What I did is that I removed the extension ".part" from the name. The remaining files worked fine for installation. My browser is the latest firefox.

I have been looking at spectrograms [will call these spectra for short] from 4 Audiomoths mainly at 384kHz but also lower sampling rates of 48 and 96kHz. The audiomoths have been physically far from each. I have placed them in vertical and horisontal positions. Furthermore the locations are such that no other source of electricity is not within 500m and most often not within 4km. At low sampling rates the spectra are quite clean, and make nice recordings. The sensitivity of the instrument at high frequenscies is good. At high sampling rates there are some problems. The good thing is that most of the instrument based issues show as vertical or horisontal bands (or their mix) only. I have not noted interference signals with siginificant "tilted" what you expected from most (European) bat calls, so in principle they are separable. However, the horisontal, internal (and external) electric like signals in the spectrum can mimic horseshoe bats and similar sounds. The most consistent non-thermal instrument noise at 384kHz is a wide spectrum buzz repeating at a rate of about 25 times/sec (which is close to the rate in a grasshopper warbler song!). This signal is mostly quite weak at audible frequencies at 384kHz sampling, but in one audiomoth it is clear all the way to ~0kHz. The same signal is present at 96KHz sampling but at at rate of about 6/sec, and appers significantly weaker. In time steps the interval of the buzzes seems to be 2^14 points = 16384 (the size of the write block?) independent of sampling. The reduction or abolition of this noise signal would clean up the spectrum significantly, and make noise triggering truly feasible. Another noise type present in all recordings and all my devices is a strong horizontal tone at ~20kHz which lasts about the same time as the previous signal, but shows many quite strong harmonics. This or its harmonics would cause most likely an extra trigger. Fortunately it occurs long intervals 2 to 22 seconds. The timing and the exact frequency varies a bit. The signal can recall a noctule bat in priciple. This sound appears to be repeted occasionally but normally followed by a loud "2^14 point type " session for a varying length of time and even up to 15 seconds.

Alex, I have comments about the non-trivialness of the triggering issue, but I will throw those comments in to the triggering thread in a few days with some images.

702 files, last 38 files of these 0 KB but showed a file name indicating time. 384kHz sampling, 295 s recoding, break of 5 seconds file size ~220MB. The bad files were mostly at the end: good ones, four bad, one ok, and 34 bad files. All good files were of the same size. Written amount on the card 139 GB (150 225 135 936 bytes). Quite a few bats and good rat recordings!

So far the largest number of files in one card is 476, but in a couple of days I should have my hands on a slightly larger set. Your suggested file name (ISO standard like) is very good (the old one was fine for mee too).

So do I now read correctly that cards larger than 32GB are not likely to work? So, eg a sandisk 256G is not likely to work? In that case not very good for me as I am running 128G already, end even these tend to fill fast in ultrasonic work. This is really quite critical information. According to the papers and specs the batteries are expected to last to fill the larger cards.