I've just installed the latest image aiyprojects-2018-02-21.img.xz on my Voicekit.
In the past I have adjusted the assistant's voice level by using either the alsamixer or the little loudspeaker GUI control on the desktop. That no longer works - instead I have adjusted the volume level by asking the assistant to increase/decrease it by x percent.
I've noticed that alsamixer shows "PulseAudio" as the soundcard
If I go back to my previous installation by swapping over SD cards and go into alsamixer the soundcard is shown as snd_rpi_googlevoicehat_soundcar
Is this deliberate????
My Voice kit (aiyprojects-2018-02-21.img.xz) has same problem.
Mixer volume is too loud to listen to music (sound noisy and distorted)
When I changed volume at amixer or at GUI, actual speaker volume does not change at all. Even I muted the sound at GUI, I hear still loud sound.
Same for me, can't adjust the volume ... the guy or amixer doesn't affect the volume, and in assistant_grpc_demo.py, every command i try doesn't affect it ... when asking what's the volume, the answer is always 50% ...
Thanks for the report! The switch to PulseAudio is intentional, but disabling the volume control was not intentional. We're working on a new image that will fix this.
How do I update to a working volume control if I'm on the 2018-02-21 img?
Experiencing similar issues, and this is a school project for me... Has this been fixed yet? Is there an alternative way to control audio that could bypass this?
Really appreciate it, drigz.
Would you guys mind releasing a fix rather than a new "image"? or an alternative to choose "not an image"?
I have done many times re-image... and everytime I have to sacrifice losing the work on top of the existing image.... : (
We now install https://freedesktop.org/software/pulseaudio/pavucontrol/ by default.
Changes to Pulse Audio in gui have no impact on the speaker. It remains painfully loud. In the interim, I'm just going to toss a potentiometer inline with the speaker and manually drop the volume that way.
Most helpful comment
Thanks for the report! The switch to PulseAudio is intentional, but disabling the volume control was not intentional. We're working on a new image that will fix this.