Skip to content
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

How to set input? #161

Open
Tracked by #166
ForceConstant opened this issue Jul 8, 2024 · 6 comments · May be fixed by #166
Open
Tracked by #166

How to set input? #161

ForceConstant opened this issue Jul 8, 2024 · 6 comments · May be fixed by #166
Labels
feature New feature or request

Comments

@ForceConstant
Copy link
Contributor

ForceConstant commented Jul 8, 2024

So I have a fresh ubuntu 22.04, that boots up into LXDE and installed Cavailer using flatpak. And I only get the "Lets Dance" screen. In the volume control mixer, I do see input under "Input Devices". I want to show what is coming in from the microphone.

@ForceConstant
Copy link
Contributor Author

Also I see cava_config, but this seems to get overwritten when starting. Is this a flatpak issue?

@nlogozzo
Copy link
Member

nlogozzo commented Jul 9, 2024

Is this a flatpak issue?

No i remember Cavalier sets its own cava config so that's why its getting overwritten

@nlogozzo
Copy link
Member

nlogozzo commented Jul 9, 2024

@fsobolev Do you have any insight?

@ForceConstant
Copy link
Contributor Author

So looking at it more, it seems that it is currently not possible, as cavalier writes the cava config file on startup, and only allows you to change the CAVALIER_INPUT_METHOD, as a feature request, could we get a CAVALIER_INPUT_SOURCE also that defaults to auto, but allows you to set to anything else?

@ForceConstant
Copy link
Contributor Author

#162

@nlogozzo nlogozzo added the feature New feature or request label Dec 27, 2024
@nlogozzo
Copy link
Member

Merged the PR, thanks @ForceConstant ! I plan on rewriting Cavalier in C++ now and bring it back to life! I will keep this issue open and close it once that update is out.

@nlogozzo nlogozzo linked a pull request Jan 20, 2025 that will close this issue
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants