We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
No sound when using zalsa_in plugin with a Loopback ALSA card.
zalsa_in
Steps to reproduce:
/usr/bin/jackd -dalsa -dhw:PCH -r48000 -p256 -n2 -i2 -o2 sudo modprobe snd-aloop pcm_substreams=2 jack_load zalsa_in -i "-d hw:Loopback,1,0 -L -r 48000" jack_connect zita-a2j:capture_1 system:playback_1 jack_connect zita-a2j:capture_2 system:playback_2 aplay -D hw:Loopback,0,0 -f S16_LE -r 48000 -c 2 < /dev/urandom
Starting aplay doesn't produce any sound. Using zita-a2j (v0.8.4) instead of zalsa_in plugin, produces the following messages:
aplay
zita-a2j
zita-a2j -v -d hw:Loopback,1,0 -r 48000 -L playback : not enabled capture : nchan : 2 fsamp : 48000 fsize : 256 nfrag : 2 format : S16_LE Starting synchronisation. 0.876 0.999698 0 0.305 0.999683 411 -0.274 0.999853 409 -0.192 0.999890 408 0.024 0.999841 407 Starting synchronisation. <-- aplay was started at this point Starting synchronisation. (repeats for ever)
Environment:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
No sound when using
zalsa_in
plugin with a Loopback ALSA card.Steps to reproduce:
Starting
aplay
doesn't produce any sound. Usingzita-a2j
(v0.8.4) instead ofzalsa_in
plugin, produces the following messages:Environment:
The text was updated successfully, but these errors were encountered: