Many thanks Alex. It was set to 1, however I had scrubbed out the noise files and the resulting output files weren't maintained with the correct scales - the original files open up fine. I guess I can't use that feature with such a low sample rate. Simon

The intention was to focus on 'big bats' Nnoc, Nlei and Eser (as seen in screenshot) by only recording in the 15-35khz range (or at least focussing around that). I understand that 96000 sample rate will limit the max Fq to 45300hz and I hoped the band-pass would trim things down a little also. However when I open in Kaleidoscope the Fq and timescale is out by x10 for each. I haven't previously tried such a low sample rate but changing from default to max doesn't end in a similar result. What is causing this? the AM or Kscope? thanks, Simon p.s. I'm not worried about the upside down Ppip calls!

Device ID : 240435055C7A144A Firmware : AudioMoth-Firmware-Basic (1.6.0) Time zone : UTC+1 Sample rate (Hz) : 96000 Gain : High Sleep duration (s) : 10 Recording duration (s) : 10 Active recording periods : 1 Recording period 1 : 19:45 - 21:45 (UTC) Earliest recording time : ---------- --:--:-- Latest recording time : ---------- --:--:-- Filter : Band-pass (7.0kHz - 40.4kHz) Amplitude threshold : 320 Minimum trigger duration (s) : 2 Enable LED : Yes Enable low-voltage cut-off : Yes Enable battery level indication : Yes Always require acoustic chime : No Disable 48Hz DC blocking filter : No Enable energy saver mode : Yes

Hi Alex, I just thought I'd let you know I figured out what I think happened. Quite simple really - I had set a recording period desired and then selected 'local time' which resulted in the time period being shifted 1 hour. I don't think this was an issue with earlier config apps as I'd expect I would have done this at some point before without thinking about it and had the issue sooner (this is 1.5.0 and it does the same with 1.5.1). Maybe something to change in the next config app version? regards Simon

Thanks Alex, I'm sure it was playing up but does appear to be fine now. Either that or I'm losing the plot a bit which is quite possible also! enjoy the rest of your weekend. Simon

Hello Alex, thanks for your reply. It appears to be exactly 1hr out....or at least was. I re-flashed the firmware before the above test just in case and I have reset the time a few times recently as I have been trying out some new batteries. However I am now doubly confused as I put it out last night & it appears to have recorded correctly and a test just now worked correctly. At 14:00 I set it to record between 13:55 & 14:05 and it did so, but the config file says the time was 1 hour before what was in the config app (see below) - I have not noticed a difference in the time in the config file and what is entered in the app before. I'm not great with keeping track of lots of numbers in my head, so I may have mixed something up, however I have not noticed any differences before in what I have set, what has recorded and what the config file says. If it now records at the time I want it to, then that's fine, regardless of what the config says, but if it keeps changing then that will of course be of no use!! Does it look like the device is working properly and I'm getting in a muddle or does it look like something is not right to you?! many thanks Device ID : 240435055C7A144A Firmware : AudioMoth-Firmware-Basic (1.6.0) Time zone : UTC+1 Sample rate (Hz) : 48000 Gain : Medium Sleep duration (s) : 5 Recording duration (s) : 55 Active recording periods : 1 Recording period 1 : 12:55 - 13:05 (UTC) Earliest recording time : ---------- --:--:-- Latest recording time : ---------- --:--:-- Filter : - Amplitude threshold : - Minimum trigger duration (s) : - Enable LED : Yes Enable low-voltage cut-off : Yes Enable battery level indication : Yes Always require acoustic chime : No Disable 48Hz DC blocking filter : No Enable energy saver mode : No

The constant ticking is caused by the AM, I get this and it varies as to exactly what it looks like/how bad it is depending on the batteries used. Non-rechargeable good quality batteries should minimise this - I think it may be to do with not supplying a high enough voltage (I'm not aware that it affects the operation of the AM in any other way). Regarding the 1600 files - the only tool to reduce this currently is the amplitude and filtering (fingers crossed the triggering software isn't too far away from being made available!). I use a high pass filter set to 15khz and amplitude threshold of 384 (the next step up starts to eliminate the quieter bat passes but should keep the example you have provided), though the latest software just released now uses a percentage for the amplitude threshold and I have yet to discover what the equivalent is! There is software from other companies that can scan the recordings and remove those without bat calls in (as well as suggest the species recorded), however they are relatively expensive (in the £100s). It may also be worth testing the AM in dry weather out of the box to check how the vent affects the recordings - these can reduce amount of higher frequency sounds reaching the microphone (albeit around 100khz+ which isn't too bad, but can could cause issues when you really get serious with bat call analysis!). I'd strongly suggest buying the book "Bat Calls of Britain and Europe A Guide to Species Identification by Jon Russ" when it is released in August. It'll tell you all you need to know about what bats you're recording as well as having info the species and how to record bats and analyse the calls. There is an earlier version "British Bat Calls" also by Jon Russ, which is still great for starting out, but I'm expecting the new book to supersede it (quite a lot has been learned about bats calls since). I expect you'll be able to pick up some cheap 2nd hand copies when the latest version is released if you don't fancy spending so much. Also check out the "Bat Call Sound Analysis Workshop" on facebook - a great group with both beginners and experts where you can upload recordings and ask for help etc. Hope that all helps!