Ok, first of all, I no longer think that changing the auto-detect order for
devices can solve our problem. As I understand it for, you
- have a duplex (non-default) device you want beast to use
- have a alsa non-duplex default device that you don't want beast to use
On the other hand, I
- have a duplex device I don't want beast to use
- have a alsa non-duplex default device (pulse) I want beast to use
So it seems to me that this cannot be automatically be resolved (so the patch
here cannot be improved to a state where it works out of the box for both of
us).
So we need explicit driver selection in the future. So eventually we will need
.bserc to have an entry for setting the audio driver. I can understand that
adapting beast-gtk may not be what we want to do, since it makes not much sense
to invest time in legacy ui code. I can also understand that adapting ebeast
may not yet be what we want to do, because it may need more time to develop
ebeast until it is time to add a configuration dialog. But that will happen
eventually.
So I suggest adding a .bserc option for selecting the driver, so that at least
I can test ebeast, and in the future the configuration dialog can make this
meaningful for average users.
And we need not necessarily solve the drift compensation issue before we even
have a usable ebeast ui that would benefit from it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/123#issuecomment-530792486
_______________________________________________
beast mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/beast
