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
{{ message }}
This repository has been archived by the owner on Feb 9, 2023. It is now read-only.
Is there a place in the code where we can adjust the volume level of the assistant response, because it is very low.
I know I can up the volume level of alsa, but that would be way to loud for when I want to play music with for example mpd (music player daemon).
Or is this something I should request/ask at the google api repo.
Off topic: Can we still make pull requests here since it seems everything is first prepared on an internal repo? If so, then for now we don't exactly know on which issues there is work being done on the internal repo. Could that be made more transparent? So that we don't need to invest free time into doing something that is all ready being handled. Thanks for any clarification on this.
The text was updated successfully, but these errors were encountered:
I find that the volume of the voice response does sometimes become very low. If I say a command like "turn up the volume" or "set the volume to maximum", it appears to resolve it.
@mpember Thanks, yeah that solved it, at least the volume is higher now. Still it would be nice to have some adjustment possible, so I could turn the range a bit up. Now at max it is still lower then my music. I know, I can turn on volume control in my mpd server, but that means more cpu power gets used.
Is there a place in the code where we can adjust the volume level of the assistant response, because it is very low.
I know I can up the volume level of alsa, but that would be way to loud for when I want to play music with for example mpd (music player daemon).
Or is this something I should request/ask at the google api repo.
Off topic: Can we still make pull requests here since it seems everything is first prepared on an internal repo? If so, then for now we don't exactly know on which issues there is work being done on the internal repo. Could that be made more transparent? So that we don't need to invest free time into doing something that is all ready being handled. Thanks for any clarification on this.
The text was updated successfully, but these errors were encountered: