You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I reproduced the same on when I get audio data from the Frame mic: https://github.com/CitizenOneX/frame_audio_clip
In this app, recording is initiated by a button press on the phone, so the obvious idea that this could be due to tapping the side of Frame is not applicable.
Not sure where it's coming from, but only seems to be present in the first ~1500 samples (in my case, 16-bit samples at 8kHz), so if I trim the first 3000 bytes before playing the audio, the pop goes away.
The text was updated successfully, but these errors were encountered:
Frame firmware: v24.276.1359
First mentioned by halfprice06 in Discord:
https://discord.com/channels/963222352534048818/1242455966713253979/1293032517997432894
I reproduced the same on when I get audio data from the Frame mic: https://github.com/CitizenOneX/frame_audio_clip
In this app, recording is initiated by a button press on the phone, so the obvious idea that this could be due to tapping the side of Frame is not applicable.
Not sure where it's coming from, but only seems to be present in the first ~1500 samples (in my case, 16-bit samples at 8kHz), so if I trim the first 3000 bytes before playing the audio, the pop goes away.
The text was updated successfully, but these errors were encountered: