We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the list of supported audio hardware for the AIY VoiceHat V1, it currently just says that the hardware is supported with a /boot/config.txt modification. It would be great if it could say what that modification should be. It took me quite a while to figure that one out from other sources. https://github.com/OpenVoiceOS/community-docs/blob/bafacb20b008e3cfd218e2ff58b82c10739a4ba3/docs/011-hardware_audio.md?plain=1#L44
/boot/config.txt
Additionally, the path is no longer /boot/config.txt, but rather /boot/firmware/config.txt.
/boot/firmware/config.txt
For reference, the line to add to the config.txt file is:
config.txt
dtoverlay=googlevoicehat-soundcard
Optionally, disable the default audio source as well by commenting out or removing dtparam=audio=on.
dtparam=audio=on
The text was updated successfully, but these errors were encountered:
mikejgray
builderjer
No branches or pull requests
In the list of supported audio hardware for the AIY VoiceHat V1, it currently just says that the hardware is supported with a
/boot/config.txt
modification. It would be great if it could say what that modification should be. It took me quite a while to figure that one out from other sources.https://github.com/OpenVoiceOS/community-docs/blob/bafacb20b008e3cfd218e2ff58b82c10739a4ba3/docs/011-hardware_audio.md?plain=1#L44
Additionally, the path is no longer
/boot/config.txt
, but rather/boot/firmware/config.txt
.For reference, the line to add to the
config.txt
file is:Optionally, disable the default audio source as well by commenting out or removing
dtparam=audio=on
.The text was updated successfully, but these errors were encountered: