-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High CPU usage after speaker.Init()
called
#159
Comments
It seems that speaker.Init() launches a goroutine that polls update() continuously: https://github.com/faiface/beep/blob/master/speaker/speaker.go#L52, even when nothing is playing. It can be stopped with Close(), but then the speaker needs to be re-Init() before next Play() |
What I think is happening is that either It may be a nice addition to add a valid sample rate check in |
Sorry to comment on a closed issue and to take such a long time to get back to this: I tried this:
Neither the |
Hey psaffrey, faiface/beep isn't being maintained anymore but we maintain a fork over at gopxl/beep. I've copied your comment to our repo: gopxl/beep#14 (comment). Let's continue the conversation there! :) |
First of all, thanks for Beep and the excellent documentation.
I've written a doorbell in Go that listens to an MQTT channel and then plays a ding-dong noise when a button is pressed. I can deploy the code to multiple hosts on different platforms, which is the appeal of using Go for this.
My code runs as a systemd unit, starts up and initialises the sound streams using Beep's speaker package. However, I've noticed that the baseline CPU usages is pretty high - I have two wav files open and this is using ~15% CPU - even on a puny Celeron box this seems excessive. I've written some minimal code to reproduce this:
Save the snippet above as play.go and then run with
go run play.go <wavfile>
. During thetime.Sleep
(after init, but before the sound is actually played) you can see the usage intop
.I can reduce the CPU usage by reducing the sample rate in the
Init
call - withtime.Second
it was down to about 1% - but that still seems high since it should be completely idle. I also tried using buffering as per the wiki, but that didn't make any difference. Did I miss something here? I'm using go1.18.1.The text was updated successfully, but these errors were encountered: