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

Comments on taking ALSA to the next level #1

Open
zamaudio opened this issue Aug 21, 2018 · 3 comments
Open

Comments on taking ALSA to the next level #1

zamaudio opened this issue Aug 21, 2018 · 3 comments

Comments

@zamaudio
Copy link

zamaudio commented Aug 21, 2018

Please leave your feedback on https://github.com/linuxaudio/Linux-Audio-Workgroup/wiki/Towards-Fixing-ALSA here.
Suggestions to add to the discussion, typos, general comments, etc. The wiki should reflect the current conclusions reached.

@fundamental
Copy link
Member

One thing which could anchor the arguments and future discussions is linking each one of the technical issues with a concrete use case which depends upon them. It might seem verbose, but I think going from user level problem to technical level problem to solution could work as a better flow.

@zamaudio
Copy link
Author

Done

@trebmuh
Copy link

trebmuh commented Aug 30, 2018

One proposition from a user point of view.

This might be added to this FAQ if you guys think it's relevant since I'm not 100% sure if it's ALSA/JACK/PulseAudio/whatever related, not being a code insider. I'm leaving that to your knowledge.

  1. User: "Why can't I live-switch from a sound interface to another one without restarting alsa/jackd/my_random_software ?"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants