Minor update to the configuration app to bring in some bugfixes uncovered by your usage, as well as some tweaks to functionality.
Expanding amplitude thresholded recordings now allows you to set the maximum length of the resulting files. If a generated file would be empty then it isn't created, resulting in a smaller dataset.
Make sure you're using the latest version before making a post in the support forum, as the issue you're having may have been fixed in a subsequent update.
In order to use the new features added in versions 1.3.0 and greater of the Configuration App, you'll need to update your AudioMoth firmware to the latest version (1.4.0).
Apply the firmware to your devices using the AudioMoth Flash App.
Hey everyone, in response to your feedback we've re-enabled sleep periods of less than 5 seconds. There's a warning informing you that performance will vary based on the speed of your SD card, but you'll be able to use sub-5 second sleep periods again.
Check it out here
Great new features, thanks to the whole team!
Would it be possible to have custom 'maxim file length' in the Expan AudioMoth Recordings? We normally split files into 5 seconds, and sometimes into 2 seconds, depending on the survey. Besides, 5 seconds files is quite common among bat surveyors and researchers.
Many thanks!
Agreed Davidlee, well put, that works. +1 for configurable sleep below 5sec
@Peter Prince
Thanks for the update. However - re the 5sec minimum sleep time - by "covering all bases" you have arbitrarily degraded performance for people who never previously had a problem.
I have 4 AudioMoths (v1.0.0 & 1.1.0) recording to 32GB Sandisk cards - 3×Extreme & 1×Ultra - formatted exFAT. I've never had any problems recording with a 2 sec sleep time, even with the Ultra card. Also if I set the sleep time to zero the detectors default to a pause between recordings of 2 seconds. Can I suggest that a better way of truly covering ALL bases would be to remove the sleep time restriction but add a message to the config app warning that sleep times shorter than 5 seconds are not supported and may lead to problems, so performance should be checked before deployment.
Just downloaded version 1.3.3 and works fine as expected. Thank you much.
Just pushed a fix. Download version 1.3.3 here and the sleep input should work as expected, with a limit of 5 seconds minimum.
Peter
Open Acoustic Devices
Apologies, I misunderstood the issue you were having. I'll get a bugfix out shortly.
Peter
Open Acoustic Devices
If I enter 180 seconds for the sleep duration of 5 seconds, it writes 580 seconds. The problem is with the 5 - if I enter 300 seconds for the sleep duration, it writes 500.
Hi Peter, I will state my issue differently, I wanted to set the sleep duration to 180 seconds and the recording duration to 420 seconds, but the sleep duration could not be changed from 5 seconds. Is there a trick I missed. I had no problem to change the recording duration from 55 seconds to 420 seconds, but not the sleep duration.
Could you not default to 5sec, but allow 2 or 3 seconds with a warning. The Amp Threshold has not worked well for Bats with me so far, so ideally I'd like to go back to 18 sec on, 2 off continual.
(the low pass is useful, thanks!)
Hi everyone, the 5 second minimum is to give each recording time to close the file. The amount of time required to do this varies depending on the speed of the SD card used, so 5 seconds covers all bases.
If you don't want to miss any audio, you can switch off the sleep period altogether and files will be created the length of each scheduled period.
Peter
Open Acoustic Devices
I was not able to change the sleep duration from 5 seconds to my required sleep duration. Can you fix this. Meanwhile I'm using Configuration App 1.3.0
+1 on "why a minimum sleep duration of 5s" in this new version
Why a minimum sleep duration of 5s?