26 Aug
2012
26 Aug
'12
4:44 p.m.
Can I output all audio from one computer on another computer's audio
device? If so, is networking the two computers via ethernet and
running jack with RT priority the best way to do this with as little
latency as possible?
- Grant
26 Aug
26 Aug
5:02 p.m.
On Sun, Aug 26, 2012 at 3:44 PM, Grant <emailgrant(a)gmail.com> wrote:
Can I output all audio from one computer on another
computer's audio
device? If so, is networking the two computers via ethernet and
running jack with RT priority the best way to do this with as little
latency as possible?
Netjack: Theres a couple of versions, research a bit for what best fits
your requirements:
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack2
Good luck! -Harry
7:03 p.m.
Can I output
all audio from one computer on another computer's audio
device? If so, is networking the two computers via ethernet and
running jack with RT priority the best way to do this with as little
latency as possible?
Netjack: Theres a couple of versions, research a bit for what best fits your
requirements:
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack2
Good luck! -Harry 
27 Aug
27 Aug
5:05 a.m.
On 27 August 2012 05:03, Grant <emailgrant(a)gmail.com> wrote:
Thanks Harry. Is Netjack a better choice for this
than PulseAudio?
jack is designed for low latency high-quality audio production and
processing. for any situation involving millisecond-critical timing,
i'd recommend jack over anything, including pulse
Would a minimal device like the SheevaPlug be suitable
as the
receiving/playback computer?
i don't see why not
there's no reason why jack won't run on whatever free unix-like distro
(debian, bsd, etc.) you use. have you selected what distro and audio
software you will be running on the sheeva plug yet?
the key question, is what you want to do, and the effects that will
have on latency.
--
robin
http://fu.ac.nz - Auckland's Free University
8:39 a.m.
On 08/27/12 05:05, Robin Paulson wrote:
Isn't there something about FPU and the SheevaPlug not having one? I
vaguely recall a thread about this. Maybe not in this list but jack-devel.
Best,
Jeremy
Would a
minimal device like the SheevaPlug be suitable as the
>receiving/playback computer?
i don't see why not
11:46 a.m.
Would a minimal device like the SheevaPlug be suitable
as the
>receiving/playback computer?
i don't see why not
12:03 p.m.
On 27 August 2012 21:46, Grant <emailgrant(a)gmail.com> wrote:
does the sheeva host hard drives via USB? if it's USB 2.0, you might
want to think what they can handle, that connection won't match SATA
in your desktop/laptop. having said that, it's still faster than the
100Mbit ethernet (if that's what your connection speed will be)
between the two computers
Isn't
there something about FPU and the SheevaPlug not having one? I vaguely
recall a thread about this. Maybe not in this list but jack-devel.
Thanks, I will look into that. Are there any other requirements I
should be aware of? Would 1G ethernet provide much lower latency compared
to 100M?
hmm, interesting question. i would guess not, latency and bandwdith
are different concepts, the latter shouldn't affect the former
latency is a function of the quality of the network interfaces, the
length of the wires/distance between wireless receiver, the number of
links and possibly buffer size. maybe some other things will affect
it, but i would guess these would be key
i found this quite useful for explaining the difference between the two:
http://compnetworking.about.com/od/speedtests/a/network-speed.htm
from that it appears that latency can affect actual bandwidth though,
in certain conditions
--
robin
http://fu.ac.nz - Auckland's Free University
12:23 p.m.
On 08/27/12 12:03, Robin Paulson wrote:
does the sheeva host hard drives via USB?
Depends, there are eSata and non-eSata models. I have a non-eSata model
and disk IO speeds barely exceed 20mb/s. But when using JACK that
shouldn't matter since you're not writing anything to disk (if I got
that correctly).
Best,
Jeremy
11:44 a.m.
Thanks Harry.
Is Netjack a better choice for this than PulseAudio?
jack is designed for low latency high-quality audio production and
processing. for any situation involving millisecond-critical timing,
i'd recommend jack over anything, including pulse
Would a minimal device like the SheevaPlug be
suitable as the
receiving/playback computer?
i don't see why not
there's no reason why jack won't run on whatever free unix-like distro
(debian, bsd, etc.) you use. have you selected what distro and audio
software you will be running on the sheeva plug yet?
the key question, is what you want to do, and the effects that will
have on latency.
4:47 p.m.
Can I output
all audio from one computer on another computer's audio
device? If so, is networking the two computers via ethernet and
running jack with RT priority the best way to do this with as little
latency as possible?
Netjack: Theres a couple of versions, research a bit for what best fits your
requirements:
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack2
28 Aug
28 Aug
12:43 a.m.
On 28 August 2012 02:47, Grant <emailgrant(a)gmail.com> wrote:
there are bridging applications to allow jack and alsa applications
(for instance) to work together. try:
zita-ajbridge
libjackasyn0 (for oss)
If so, is
Netjack:
Theres a couple of versions, research a bit for what best fits your
requirements:
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack2
Would all of the applications with audio output on the slave that are
sending the output to the master need to be jack-aware? there a way to send any and all audio output from the
slave to the
master so that each audio application on the slave doesn't need to be
aware of jack?
sorry, i'm not sure what you mean
--
robin
http://fu.ac.nz - Auckland's Free University
3:47 a.m.
On Tue, August 28, 2012 12:43 am, Robin Paulson wrote:
On 28 August 2012 02:47, Grant
<emailgrant(a)gmail.com> wrote:
there are bridging applications to allow jack and alsa applications
(for instance) to work together. try:
zita-ajbridge
libjackasyn0 (for oss)
If so, is
Pulseaudio can be a jack input/output device too so all desktop
applications that normally would be handled by pulse can be routed through
pulse->jack(slave)->netjack->jack(master).
In addition pulseaudio also has network capabilities independently of jack.
--
Patrick Shirkey
Boost Hardware Ltd
Netjack:
Theres a couple of versions, research a bit for what best fits
your
requirements:
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack2
Would all of the applications with audio output on the slave that are
sending the output to the master need to be jack-aware? there a way to send any and all audio output from
the slave to the
master so that each audio application on the slave doesn't need to be
aware of jack?
sorry, i'm not sure what you mean
8:18 a.m.
Netjack: Theres a couple of versions, research a bit
for what best fits your
requirements:
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack2
Would all of the applications with audio output on the slave that are
sending the output to the master need to be jack-aware? there a way to send any and all audio output from
the slave to the
master so that each audio application on the slave doesn't need to be
aware of jack?
sorry, i'm not sure what you mean
8:53 a.m.
On Tue, August 28, 2012 8:18 am, Grant wrote:
there are bridging applications to allow jack and alsa applications
(for instance) to work together. try:
zita-ajbridge
libjackasyn0 (for oss)
If so, is
Would something like this work in asound.conf:
pcm.!default {
type plug
slave.pcm {
type dmix
ipc_key 1024
slave {
some-kind-of-jack-specification
format S24_3LE
rate 44100
}
}
}
The idea being that I could let all apps send audio to the default
device and ALSA would send that audio to jack.
People have managed it in the past with varying degrees of success. The
standard method these days is to use pulseaudio's jack-sink over dbus.
I don't know why people still insist on making their lives more difficult
that necessary. Pulse works just fine as a jack client.
http://linux-audio.com/images/linux-audio-stack.png
--
Patrick Shirkey
Boost Hardware Ltd
Netjack:
Theres a couple of versions, research a bit for what best
fits your
requirements:
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack2
Would all of the applications with audio output on the slave that are
sending the output to the master need to be jack-aware? there a way to send any and all audio output from
the slave to the
master so that each audio application on the slave doesn't need to be
aware of jack?
sorry, i'm not sure what you mean 
10:32 a.m.
On 28 August 2012 18:53, Patrick Shirkey <pshirkey(a)boosthardware.com> wrote:
People have managed it in the past with varying
degrees of success. The
standard method these days is to use pulseaudio's jack-sink over dbus.
I don't know why people still insist on making their lives more difficult
that necessary. Pulse works just fine as a jack client.
because pulse is a dog, and its latency blows?
jackd also includes an alsa to jack bridge, as does the aforementioned
zita-ajbridge. both are easy to use, the latter is very low latency
--
robin
http://fu.ac.nz - Auckland's Free University
10:15 p.m.
On Tue, Aug 28, 2012 at 4:32 AM, Robin Paulson <robin.paulson(a)gmail.com>wrote;wrote:
jackd also includes an alsa to jack bridge, as does the aforementioned
zita-ajbridge. both are easy to use, the latter is very low latency
"bridge" is sort of the wrong word. both these tools make ALSA-supported
audio interfaces available to JACK clients, in addition to whatever backend
the JACK server is using. they do not "bridge" between an application that
uses ALSA and JACK.
sort of.
4 Sep
4 Sep
9:08 a.m.
jackd also
includes an alsa to jack bridge, as does the aforementioned
zita-ajbridge. both are easy to use, the latter is very low latency
"bridge" is sort of the wrong word. both these tools make ALSA-supported
audio interfaces available to JACK clients, in addition to whatever backend
the JACK server is using. they do not "bridge" between an application that
uses ALSA and JACK.
sort of.
12:46 p.m.
On Tue, Sep 4, 2012 at 3:07 AM, Grant <emailgrant(a)gmail.com> wrote:
backend
on OS X, any application that uses CoreAudio for audio I/O (which basically
means every application except JACK native ones) can use JACK as its input
and/or output device. configuring this is generally trivial.
on Windows, any application that uses ASIO for audio I/O (which basically
means most pro-audio/music creation applications) can use JACK as its input
and/or output device. configuring this is generally easy.
on Linux, any application that uses GStreamer (or a layer above it), ffmeg,
the regular ALSA PCM API or PulseAudio's audio API can use JACK as its
input/output device. configuring this can range from easy to quite tricky.
jackd also includes an alsa to jack bridge, as does
the aforementioned
zita-ajbridge. both are easy to use, the latter is very low latency
"bridge" is sort of the wrong word. both these tools make ALSA-supported
audio interfaces available to JACK clients, in addition to whatever the JACK server is using. they do not
"bridge" between an application
that
uses ALSA and JACK.
sort of.
Just so I understand, the practical result of this is that I can use
an audio application which lacks jack support (perhaps iTunes?) and
send its audio output to jackd?
5 Sep
5 Sep
11:36 a.m.
jackd also
includes an alsa to jack bridge, as does the aforementioned
zita-ajbridge. both are easy to use, the latter is very low latency
"bridge" is sort of the wrong word. both these tools make ALSA-supported
audio interfaces available to JACK clients, in addition to whatever
backend
the JACK server is using. they do not "bridge" between an application
that
uses ALSA and JACK.
sort of. 
28 Aug
28 Aug
10:39 a.m.
On 26/08/12 22:44, Grant wrote:
Can I output all audio from one computer on another
computer's audio
device? If so, is networking the two computers via ethernet and
running jack with RT priority the best way to do this with as little
latency as possible?
something left-field to try out if all machines are running X and you have full
control of those machines would be ssh - it can actually deal with devices and
forward them, though I believe this facility in X isn't always enabled by
default (obviously, for security reasons ... just because you let a user ssh
into a machine doesn't mean you want them to be able to listen to the
microphone!). You would want to set ssh to its least secure modes for this kind
of thing to minimise the security overhead, it has many relevant options.
I have not tried it, just read the docs a bit while looking for a similar
solution, but if both machines can be configured correctly it may be a way to do
it ... no idea if that would be better or worse latency than jack or pulse with
their various networking options. I would guess all options involve some
buffering, and it depends which system buffers the least, and direct forwarding
of the device seems a reasonable candidate for that.
Simon
4490
days inactive
4500
days old
linux-audio-user@lists.linuxaudio.org
19 comments
7 participants
participants (7)
-
Grant -
Harry van Haaren -
Jeremy Jongepier -
Patrick Shirkey -
Paul Davis -
Robin Paulson -
Simon Wise