@tim-janik Yes, it is surprising, as I don't have this problem with other apps: they straight away connect to ALSA without any issues.
I don't build from source, I grabbed the .deb binaries from this page: https://beast.testbit.org/pub/deb/
Out of curiosity, I tried to fix the "mismatch" by changing my Jack configuration (frequency, buffer and periods) for it to match the settings listed in the ALSA: setup: lines, and I get a different output:
1536889849.386466 pcm-alsa: ALSA: opening PCM "null" readable=1 writable=1: Failed to configure device buffer
1536889849.389098 pcm-alsa: ALSA: opening PCM "pulse" readable=1 writable=1: Open failed
1536889849.393905 pcm-alsa: ALSA: opening PCM "sysdefault:CARD=PCH" readable=1 writable=1: Device or resource busy
1536889849.394195 pcm-alsa: ALSA: opening PCM "front:CARD=PCH,DEV=0" readable=1 writable=1: Device or resource busy
1536889849.394745 pcm-alsa: ALSA: opening PCM "dmix:CARD=PCH,DEV=0" readable=1 writable=1: Open failed
1536889849.395393 pcm-alsa: ALSA: opening PCM "dsnoop:CARD=PCH,DEV=0" readable=1 writable=1: Device or resource busy
1536889849.395531 pcm-alsa: ALSA: opening PCM "hw:CARD=PCH,DEV=0" readable=1 writable=1: Device or resource busy
1536889849.395668 pcm-alsa: ALSA: opening PCM "plughw:CARD=PCH,DEV=0" readable=1 writable=1: Device or resource busy
1536889849.414223 pcm-alsa: ALSA: opening PCM "sysdefault:CARD=Loopback" readable=1 writable=1: Failed to configure device buffer
1536889849.415426 pcm-alsa: ALSA: setup: w=0 r=1 n_channels=2 sample_freq=44100 nperiods=4 period=512 (2048) bufsz=2048
1536889849.415651 pcm-alsa: ALSA: setup: w=1 r=0 n_channels=2 sample_freq=44100 nperiods=4 period=512 (2048) bufsz=2048
1536889849.415709 pcm-alsa: ALSA: opening PCM "front:CARD=Loopback,DEV=0" readable=1 writable=1: OK
1536889849.469032 pcm-alsa: ALSA: retriggering device (r=PREPARED w=PREPARED)...
Still going to my PCM loopback and no sound.
Maybe that helps?
By the way, I always get the following right at the beginning, when starting Beast from the terminal, whatever the command, even after matching the Jack settings:
convolution: samplerate mismatch preset:48000 host:44100
convolution: samplerate mismatch preset:48000 host:44100
convolution: samplerate mismatch preset:48000 host:44100
convolution: samplerate mismatch preset:48000 host:44100
convolution: samplerate mismatch preset:48000 host:44100
convolution: samplerate mismatch preset:48000 host:44100
Cheers
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.