On 08/15/2011 08:35 PM, Brett McCoy wrote:
On Mon, Aug 15, 2011 at 2:26 PM, rosea grammostola
<rosea.grammostola@xxxxxxxxx> 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.
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
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user
