Hello! I got this error message after trying to expand some T.wav files. They contain data, as I can examine them using different programs, but it would be very useful to recover the time of detections as well. One file is 6.08 GB for example. I inspected the wav header using a hex editor but I'm honestly not sure how I can fix it. How can I make the configuration app read and expand these files? Any recommendations? Thanks!
top of page
To see this working, head to your live site.
8 Comments
bottom of page
I see... yes these surveys started a while ago, before running firmware updates on the devices. Will send you the list soon. Thanks a lot for your help!
Ah. Yes, we fixed this in version 1.4.2. We hadn't really thought about the possibility of the AudioMoth making really long recordings and then we made it easy to do so by allowing the sleep cycle to be disabled. All the data is still in the file, it's just that the RIFF file size has overflowed as it only uses 32-bits to describe the length. If you can send me a listing of the cards showing the file sizes I'll figure out a work around - probably a script that will split the files in the same way that the new firmware does.
Yes, they were created using AudioMoth-Firmware-Basic (1.4.0). The AMs were deployed using the amplitude threshold but had the sleep cycle turned off, unfortunately. After switching date, the 2nd file probably got filled (?) and now gives trouble when trying to expand it. However, they do contain a lot of data, which would be even more useful if we could extract the time of detections.
Ok, I'll send you the CONFIG.TXT and ERRORS.TXT files too. Thanks!
Ah, I think the problem is the file size. Do you know what version of the firmware these files were created with? Can you also send the CONFIG.TXT file from the SD card. A WAV file is limited to 4.3GB and the firmware should avoid creating files that are larger than this. This is possibly the reason that the RIFF chunk error is being reported.
Yes, if you can email a link to alex@openacousticdevices.info I can look at the file.
Thanks for your response Alex. Well, in this case the files were taken directly from the SD card (without resaving them with other audio applications). I didn't find any additional metadata at the end of the file using a hex editor. Sure, it would be great if you can take a look at one of them, is there an email where I can send you a link to the file?
This file has been resaved by Kaleidoscope and generates errors. If you can send us the file we can try to understand what has happened.
Hi, Is it possible that you have re-saved the file using an audio application? These will typically add additional meta-data and the file may no longer be recognised by our application. If you have a hex editor, check the very end of the file as additional metadata often appears there. Alex