18 Mar
2012
18 Mar
'12
10:22 p.m.
Hello all,
The first official release of zita-ajbridge is now available at
<http://kokkinizita.linuxaudio.org/linuxaudio/downloads>.
Quoting the README:
This package provides two applications, zita-a2j and zita-j2a.
They allow to use an ALSA device as a Jack client, to provide
additional capture (a2j) or playback (j2a) channels.
Functionally these are equivalent to the alsa_in and alsa_out
clients that come with Jack, but they provide much better audio
quality. The resampling ratio will typically be stable within
1 PPM and change only very smoothly. Delay will be stable as
well even under worse case conditions, e.g. the Jack client
running near the end of the cycle.
You will also need the latest zita-resampler and zita-alsa-pcmi
libraries.
All feedback welcome.
Ciao,
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
19 Mar
19 Mar
6:03 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/18/2012 10:22 PM, Fons Adriaensen wrote:
Hello all,
The first official release of zita-ajbridge is now available at
<http://kokkinizita.linuxaudio.org/linuxaudio/downloads>.
Quoting the README:
This package provides two applications, zita-a2j and zita-j2a.
They allow to use an ALSA device as a Jack client, to provide
additional capture (a2j) or playback (j2a) channels.
Functionally these are equivalent to the alsa_in and alsa_out
clients that come with Jack,
alsa_in/out work fine with alsa dmix/dsnoop devices. zita-a2j does not.
I am using a alsa-loopback device (for non JACK apps such as Flash..)
and alsa_in/out to connect the alsa-loopback to jack. The .asoundrc (in
use is the one from
http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge#aso…
# zita-a2j -dcloop
Can't open ALSA capture device '-dcloop'.
# alsa_in -dcloop
selected sample format: 16bit
delay = 7626
..
works OK.
The other way' round starts fine, but there's no signal coming though.
# zita-j2a -dploop
Starting synchronisation.
Detected excessive timing errors, waiting 15 seconds.
This may happen with current Jack1 after freewheeling.
Starting synchronisation.
Detected excessive timing errors, waiting 15 seconds.
This may happen with current Jack1 after freewheeling.
..
[It's jack2 and no freewheeling at all.]
# alsa_out -dploop
works as expected.
best,
robin
PS. NTL I've created man-pages (based on the README) and packaged it for
debian: http://rg42.org/gitweb/?p=zita-ajbridge
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk9nZsUACgkQeVUk8U+VK0L84wCeO3SaVm0YglXc33a270XkPufm
llMAoLtssHBOa22+nt+cEhXl0NzoJQEc
=BeVu
-----END PGP SIGNATURE-----
21 Mar
21 Mar
12:54 p.m.
Hi Fons,
I gave it a shot yesterday evening. It was not meant to be a thorough test but just a
check whether I could just replace alsa_in/out with zita_a2j/j2a in my environment:
- Core 2 Duo 2 x 2.4GHz (cpufreq disabled)
- kernel 3.2 from liquorix (debian i686) with thread_irq enabled (but no complete
preemption patch)
- RME HDSP + Multiface II
- jackd2 (latest from svn, before it got moved to github) running in sync mode, at 96kHz,
buffer size 2 x 256 frames
- zita_a2j running on ALSA loopback (loopback card with only two pcm substreams enabled
when loaded to the kernel)
My .asoundrc is described in the unofficial ALSA WIKI page about the loopback device used
as a bridge for non-jack apps. I basically set the loopback card h/w and s/w parameters to
match my jack setting.
The result is not as good out of the box as with alsa_in. I have a wav file which is a
440Hz signal running for 2mn. When I play it through mplayer -ao alsa and alsa_in on the
other end of the ALSA loopback, I get no interruption at all. Your zita_a2j app quickly
introduces interruptions (dropouts probably) which happen when it displays something about
synchronization in the terminal. I played with the resampling factor but it did not
improve anything in terms of dropouts. On the other hand, alsa_in was just fine.
Not sure whether you can use this at all as a data point, but something is not optimally
running. I have no time to do more thorough tests.
Cheers!
J.
________________________________
From: Fons Adriaensen <fons(a)linuxaudio.org>
To: Linux Audio Users <linux-audio-user(a)lists.linuxaudio.org>rg>; Linux Audio
Developers <linux-audio-dev(a)lists.linuxaudio.org>
Sent: Sunday, March 18, 2012 10:22 PM
Subject: [LAD] First release of zita-ajbridge
Hello all,
The first official release of zita-ajbridge is now available at
<http://kokkinizita.linuxaudio.org/linuxaudio/downloads>.
Quoting the README:
This package provides two applications, zita-a2j and zita-j2a.
They allow to use an ALSA device as a Jack client, to provide
additional capture (a2j) or playback (j2a) channels.
Functionally these are equivalent to the alsa_in and alsa_out
clients that come with Jack, but they provide much better audio
quality. The resampling ratio will typically be stable within
1 PPM and change only very smoothly. Delay will be stable as
well even under worse case conditions, e.g. the Jack client
running near the end of the cycle.
You will also need the latest zita-resampler and zita-alsa-pcmi
libraries.
All feedback welcome.
Ciao,
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
2:34 p.m.
On 03/21/2012 12:54 PM, James Warden wrote:
Hi Fons,
I gave it a shot yesterday evening. It was not meant to be a thorough
test but just a check whether I could just replace alsa_in/out with
zita_a2j/j2a in my environment:
- Core 2 Duo 2 x 2.4GHz (cpufreq disabled)
- kernel 3.2 from liquorix (debian i686) with thread_irq enabled (but
no complete preemption patch) - RME HDSP + Multiface II
- jackd2 (latest from svn, before it got moved to github) running in
sync mode, at 96kHz, buffer size 2 x 256 frames
- zita_a2j running on ALSA loopback (loopback card with only two pcm
substreams enabled when loaded to the kernel)
My .asoundrc is described in the unofficial ALSA WIKI page about the
loopback device used as a bridge for non-jack apps. I basically set
the loopback card h/w and s/w parameters to match my jack setting.
The result is not as good out of the box as with alsa_in. I have a
wav file which is a 440Hz signal running for 2mn. When I play it
through mplayer -ao alsa and alsa_in on the other end of the ALSA
loopback, I get no interruption at all. Your zita_a2j app quickly
introduces interruptions (dropouts probably) which happen when it
displays something about synchronization in the terminal. I played
with the resampling factor but it did not improve anything in terms
of dropouts. On the other hand, alsa_in was just fine.
Not sure whether you can use this at all as a data point, but
something is not optimally running. I have no time to do more
thorough tests.
I've been debugging this use-case with Fons over the last 24 hours.
Meanwhile he's at zita-ajbridge 0.2.1 (still unreleased) and it
currently runs [mostly] find as a drop-in replacement for alsa_in/out
[for loopback devices].
There's still some issues to be sorted out though.
robin
4676
days inactive
4679
days old
linux-audio-dev@lists.linuxaudio.org
3 comments
3 participants
participants (3)
-
Fons Adriaensen -
James Warden -
Robin Gareus