Ebeast has PCM / MIDI device selection now.
--
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-573305914___
beast mailing list
Closed #123.
--
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#event-2940547367___
beast mailing list
beast@gnome.org
> Ok, first of all, I no longer think that changing the auto-detect order for
> devices can solve our problem.
I think we can get very close to 0-config for most users by doing this:
1) Pick Jack driver if and only if Jackd is running.
2) Pick Pulseaudio if it is available, note that this does
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
A bit of evaluation on Ubuntu 18.04:
- Bitwig defaults to opening JACK and issues a warning if that fails. It
provides JACK, ALSA and PulseAudio drivers. For the ALSA driver, the user has
to select one of the available ALSA hardware drivers (hw:*).
- Reaper defaults to opening JACK and issues
This patch causes a regression on my system (Ubuntu 18.04 with pulseaudio) when
opening media/Demos/stereo-through.bse. Without the patch, I can play this:
BSE_DEBUG=snd pasuspender -- out/beast-gtk/beast-0.15.0
out/media/Demos/stereo-through.bse
snd: bse_device_open:
