Hi, I set the recording period in local time format (UTC+8), and the device recorded at exact period.
but the problem is, the time created on .wav file are still appeared as UTC
is there anyway I can fix it?
Thanks a lot.
Hi, I set the recording period in local time format (UTC+8), and the device recorded at exact period.
but the problem is, the time created on .wav file are still appeared as UTC
is there anyway I can fix it?
Thanks a lot.
Hi, You also need to update the firmware on the actual device to support the time stamps appearing in local time on the SD card. I assume the file names you got still appeared as eight character hex numbers, rather than human readable file names.
Hi Alex, I've done updated my device, the Firmware version showed 1.2.0 (This is the latest version, right?)
the filename are in correct format, the only problem is time stamp on .wav file are still appeared as UTC but not in local time (UTC+8).
am I missing any steps?
Yes, that's the correct version. Can you email me the file (alex.rogers@cs.ox.ac.uk). The time stamp with time zone is also included in the comment section of the WAV file header - if you can read that it would be useful as well. What was the time zone and local time that the recording was actually made?
Was local time actually selected when you pushed 'Configure AudioMoth' - you can toggle backwards and forwards between using UTC and local time, and the state that the device is in when you actually push 'Configure AudioMoth' is the one that is used. The actual recording times will be the same but the device will use local time or UTC for the timestamps as appropriate.
Sure, i'll email you the file now.
I ticked the 'Local Time' option first, then i push the 'Configure AudioMoth' button
The recording period are set between 6PM-7PM, recording duration 20s, sleeping duration 120s
but the timestamp in WAV file still appeared 8 hour late than the actual recording time.
Okay. That's our bug. The recording times will be correct but the timestamps will always be in UTC. We'll push out an updated to the configuration app - version 1.2.1 - to fix this tomorrow.
Great! appreciated for the quick response, Thanks alot
The updated configuration app is now out. Let us know if you have any more problems.
Hi,
Please can you confirm: if the AudioMoth is configured to record in local time that the filename timestamp will also be in local time? Do I need to use firmware to make this happen or can I just set the configuration app to local time?
Also, do you know of any software that I can download which will convert the timestamp? I will not have internet to be able to use epoch converters online while deploying AudioMoths. Or is there some R code / excel function that can do this?
Thanks
Hi, Yes if you have the latest configuration app, and at least version 1.2.0 of the firmware (it is best to update to version 1.2.1) the filenames will all now appear as human readable strings (no need to do the epoch conversion) in either local time or UTC depending on the mode in the configuration app when the device was configured. The same for the 'file created' and 'file last modified' fields when you view the file in the filesystem. The timezone used is also written into the comments on the file so you can see the details there if you change the filename at any point. Alex
Hi Alex, found this question while looking for information on AudioMoth behavior in local time. I was wondering if it would be possible to add the time zone to the WAV filename a la ISO 8601--otherwise filenames from files that are localized to UTC look the same as filenames that are localized to a different timezone, which is potentially misleading.
Yep. In the next version of the configuration app we have a couple of new utilities to expand and split WAV files, so it might be worth having some that will also rename files to add prefixes, add timezones, etc. That way we can keep the default behaviour so we don't break anyone's existing workflow but make it easy for others to manipulate the files to their requirements.
That sounds great--thank you!