15 Aug
2011
15 Aug
'11
8:26 p.m.
Hi,
Just experimented a bit with netjack these days... Which makes me
wondering, it's possible to transport audio data in different ways. What
are typical situations to use and what are the (dis)advantages:
1) spdif/adat
2) netjack
3) midi
4) ...
?
Best regards,
\r
15 Aug
15 Aug
8:29 p.m.
On Mon, Aug 15, 2011 at 2:26 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Hi,
Just experimented a bit with netjack these days... Which makes me wondering,
it's possible to transport audio data in different ways. What are typical
situations to use and what are the (dis)advantages:
1) spdif/adat
2) netjack
3) midi
one of these is not like the others.
MIDI is not a way to transport audio data.
8:35 p.m.
On 08/15/2011 08:29 PM, Paul Davis wrote:
On Mon, Aug 15, 2011 at 2:26 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
True :) (I had netjack in mind, which
does both)
\r
Hi,
Just experimented a bit with netjack these days... Which makes me wondering,
it's possible to transport audio data in different ways. What are typical
situations to use and what are the (dis)advantages:
1) spdif/adat
2) netjack
3) midi
one of these is not like the others.
MIDI is not a way to transport audio data. 
8:36 p.m.
On Mon, Aug 15, 2011 at 2:26 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Just experimented a bit with netjack these days...
Which makes me wondering,
it's possible to transport audio data in different ways. What are typical
situations to use and what are the (dis)advantages:
1) spdif/adat
2) netjack
3) midi
I tried using netjack to transfer audio between a Linux machine and a
Windows machine but netjack wasn't very stable on Windows (endless
xruns even when nothing was going on, plus I had to bridge the ALSA
MIDI to jack and back on both sides). The plan was to use Linux for
MIDI sequencing and recording and use Windows for hosting samples (via
Kontakt, PLAY, etc). A more stable solution for me was to send MIDI to
Windows via QMidiNet (using ipMIDI on the Windows side to receive the
MIDI), and send the audio back via SPDIF, and I have been using this
successfully for a while (using RME Multiface on Linux for all audio
output, so the Windows audio is all routed to Linux for monitoring).
This only allows one stereo channel at a time, though, which can be
tedious to record, so I am upgrading to using ADAT between the two for
audio (will give me 8 channels of digital audio between the two, for
now). I found an e-MU 1010 for less than $150, which is the perfect
card for standalone ADAT output.
--
Brett W. McCoy -- http://www.electricminstrel.com
------------------------------------------------------------------------
"In the rhythm of music a secret is hidden; If I were to divulge it,
it would overturn the world."
-- Jelaleddin Rumi
11:03 p.m.
On 08/15/2011 08:35 PM, Brett McCoy wrote:
On Mon, Aug 15, 2011 at 2:26 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Thanks, this was the kind of information I was looking for. I just
tested Linux <> Linux with netjack (seems to run stable), but it was my
plan also to test it with Windows <> Linux. Did you test it with the
latest jack2 on Windows?
What hardware do you need exactly to be able to use ADAT between the two
systems?
Regards,
\r
Just experimented a bit with netjack these
days... Which makes me wondering,
it's possible to transport audio data in different ways. What are typical
situations to use and what are the (dis)advantages:
1) spdif/adat
2) netjack
3) midi
I tried using netjack to transfer audio between a Linux machine and a
Windows machine but netjack wasn't very stable on Windows (endless
xruns even when nothing was going on, plus I had to bridge the ALSA
MIDI to jack and back on both sides). The plan was to use Linux for
MIDI sequencing and recording and use Windows for hosting samples (via
Kontakt, PLAY, etc). A more stable solution for me was to send MIDI to
Windows via QMidiNet (using ipMIDI on the Windows side to receive the
MIDI), and send the audio back via SPDIF, and I have been using this
successfully for a while (using RME Multiface on Linux for all audio
output, so the Windows audio is all routed to Linux for monitoring).
This only allows one stereo channel at a time, though, which can be
tedious to record, so I am upgrading to using ADAT between the two for
audio (will give me 8 channels of digital audio between the two, for
now). I found an e-MU 1010 for less than $150, which is the perfect
card for standalone ADAT output.
11:37 p.m.
On Mon, Aug 15, 2011 at 5:03 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Thanks, this was the kind of information I was looking
for. I just tested
Linux <> Linux with netjack (seems to run stable), but it was my plan also
to test it with Windows <> Linux. Did you test it with the latest jack2 on
Windows?
No not yet, but might give it a try when I am done with some of my
current projects.
What hardware do you need exactly to be able to use
ADAT between the two
systems?
Well, like I said, on the Linux side, I am using an RME Multiface II
(with PCI interface card), and on Windows I am using an e-MU 1010 card
(it's very barebones, much cheaper than the RME), both support ADAT
I/O, and you need a TOSLINK (optical) cable between the two. I don't
have any monitors connected to the Windows machine, everything is
routed into the RME and I monitor all of the audio through that.
You should be able to accomplish the same thing with netjack, with
fewer cables and your slave machine doesn't even need a souncard.
--
Brett W. McCoy -- http://www.electricminstrel.com
------------------------------------------------------------------------
"In the rhythm of music a secret is hidden; If I were to divulge it,
it would overturn the world."
-- Jelaleddin Rumi
4854
days inactive
4854
days old
linux-audio-user@lists.linuxaudio.org
5 comments
3 participants
participants (3)
-
Brett McCoy -
Paul Davis -
rosea grammostola