I was pointed to this project. It looks awesome!

This is probably not the right place to ask, but I'm curious what is the typical (or maximum) power consumption of uMoth when streaming real-time recorded samples to a host over USB while acting as a microphone (i.e. without any SD card inserted, without any LED flashing, with only the minimum required filtering done on the MCU, with USB being in the "audio" isochronous mode)?

Do you think uMoth could be max 35mA?

I wonder whether uMoth could be extended to drive 2 microphones and then stream from both simultaneously over USB "audio" isochronous connection to a USB host (i.e. acting either as a stereo USB microphone or two mono USB microphones)?

If it's possible, how much would this extension affect the overall power consumption (I'm interested in the power budget discussed in #7 ).

The audiomoth firmware writes important info into the comment metadata field that is critical for attributing the sound file to a specific sound recorder. With each release, the text that reports serial number, DateTime, temperature, battery voltage etc, has been changing. This makes writing regexp to extract the info we need difficult if over the course of a project firmware was updated.

I propose that either these comments stay the same for evermore, OR the comment field is written as easily parsed data (json?) i.e. {"batt": "4.7V", "serial": "XXXXXX", "gain": "medium", "datetime": "YYYY-MM-DD HH:MM:SS", ...} that way it would be WAY simpler to parse.

Alternatively, these fields could be written as GUANO metadata into the waves allowing open-source tools to read these pieces of info as data instead of sentences, allowing the comment field to have whatever text you want.

Dear sir,
Thank you for this new and useful update version of firmware. I made a small change on the defalut filename and built successfully in an old version. But when I built this new version, it showed an error on function designFilter as the screenshot. How can I fix it? Thank you very much.

Feature Request:
Most sensors on the market write a prefix to files that specify by which sensor the file was made. This makes keeping track of files much easier as you do not have to have "correct" folder names to keep things organized or read the metadata.

I would request that the file name start with the serial number of the unit, and then follow the current naming conventions. serial_yyyymmddhhmmss.WAV

Good day!

I'm trying to compile the basic firmware with Ubuntu on Windows Subssystem for Linux, but keep getting this error:

I followed the instructions in the Wiki and I'm using the following make command (from MinGW):

If anyone could point me in the right direction, that would be great!

Best regards,
Jaro

Hello Maintainers,

I use AudioMoth for long-term bioacoustic monitoring and have recordings from multiple projects. The metadata stored in the WAV header is currently stored in a comment format that changes between firmware versions, making it difficult to parse programmatically.

I would like to request to add feature that stores the metadata in an easily accessible format, such as by using multiple subchunks in the WAV INFO chunk. This would make it easier to parse the metadata and manage AM recordings.

I am a big fan of AudioMoth and I am actively developing a Python package to help parse the metadata from previous versions. I would also be happy to assist in any way I can to make this feature a reality.

Thank you for your time and consideration.

Best regards,
Santiago Martinez Balvanera

Hello,

I have quite a few audio moths that were working well, and I upgraded a few to the newest firmware (1.10.1). I am now having an issue where recording fails intermittently (sometimes after a few minutes, sometimes after a few hours), particularly at higher sampling frequencies (>= 92 kHz). None of the devices on the new firmware have lasted the scheduled 48 hours (recording 55-secs ON/5-sec OFF). At first I thought it was an SD card issue, but it even happens with the supported SanDisk Extreme 128GB cards.

I've rolled back those moths to older firmware versions, but the issue is persisting. Is there a way to "hard reset" to older firmware versions? I'm happy to provide more context or other info that you need; just let me know.

Thank you!