I am having an issue after installing custom sound files on my ZSE50. When I play the custom files, I hear a random sound artifact immediately before the custom sound plays. The artifact only appears after the speaker has been idle for 5 seconds or more. The artifact plays for about 250 ms, then I hear my custom sound.
Before installing my custom sound files, the factory-supplied sound files play without the artifact. After I install the custom files, I hear the artifacts on both the factory-supplied sound files and my custom files. I have tried both .mp3 and .wav custom files. No difference.
I generate the sounds with the Mac ‘say’ command, e.g.,
say -v Victoria "[[slnc 500]] Motion alert: Front Door" -o front_door.wav --data-format=LEI16@44100
After copying the files from my Mac to the ZSE50, I also execute:
dot_clean -m /Volumes/NO\ NAME
to clear up the Mac dot files.
Any ideas on how to eliminate the initial artifact/buzz when my custom sounds play. They’re annoying!
I’ll +1 this – I’ve seen it a couple times now, but not consistent. I have not noticed it on multiple plays in a minute, and my use case is much less frequent than a door open/close. I’ll see if I can correlate it to a set idle time as well. That’s great additional data to try out over here.
I have found better overall device behavior if I remove ALL files and reapply them sequentially if I’m making any changes or additions. I’m not using a mac, but perhaps the subsequent cleanup is playing into it…
I have noticed that the artifacts seem to ‘disappear’ after a few hours – or maybe it’s after a few plays. It seems like things ‘settle down’ after a bit. This makes no sense to me, but I guess I could live with that.
I haven’t tried deleting everything and reloading. I’ll try that soon.
All useful anecdotal evidence–and indication we’re not crazy or hearing things!
Considering at some level there’s a D to A converter (the audio is stored digitally, but the speaker is fed an analog signal), it could be simply a timing issue resulting in a quick, significant ramp-up of the output vs. a gentle ramp up from a zero-crossing point of the audio waveform. Just speculating here…
Hi all! We appreciate all the valuable feedback and patience while our team looked into the issue. We were finally able to pinpoint the issue and found that after updating the audio files on the ZSE50 and once the file name scan is completed, the device will continue scanning the duration of all audio files in the background. The 1–2 seconds of random noise heard during playback is caused by this background duration‑scanning process. Once the duration scan is fully completed, these 1–2‑second random noise fragments will disappear.
We have beta firmware available that should resolve the issue; please reach out directly and I’ll be happy to provide the beta file if you’d like to give it a test
