10 May
2010
10 May
'10
5:24 p.m.
Hi,
i have another question to RME experts (hi Florian!).
the system i need to build should have 8 AES inputs and 24 AES outputs.
For that, i see two basic approaches 1) using two RME AES-32 (*) cards
in world-clock synch and 2) using a RME hammerfall with 24 ADAT
input/outputs and then several 8ch ADAT<->AES converters such as the
Aphex 144 (+), which costs about 400€ each 8ch unit.
Option 1 seems to me simpler and cheaper but i ignore if is feasible and
reliable: Have anyone had good experiences using two clock-synced RME
cards with jack?
Are there other options apart from 1 and 2?
Thanks a lot!
P
* http://www.rme-audio.de/en_products_hdsp_aes32.php
+ http://www.aphex.com/144.htm
10 May
10 May
5:32 p.m.
Pau,
the system i need to build should have 8 AES inputs
and 24 AES outputs.
For that, i see two basic approaches 1) using two RME AES-32 (*) cards
in world-clock synch and 2) using a RME hammerfall with 24 ADAT
input/outputs and then several 8ch ADAT<->AES converters such as the
Aphex 144 (+), which costs about 400€ each 8ch unit.
3) a MADI interface and any MADI-to-ADAT converter you want
What are those AES ports needed for anyway? I mean, this are 16 channels
in and 48 channels out. With that number of channels, using AES just
becomes a pita. Think of the cabeling alone - or use Tascam-style 25 pin
DSUB connectors.
Option 1 seems to me simpler and cheaper but i ignore
if is feasible and
reliable: Have anyone had good experiences using two clock-synced RME
cards with jack?
The driver can start the buffers synchronously, so you have
sample-synchronous output. To have jack working with multiple cards, you
can either use alsa magic to combine the cards, or use alsa_out (with
disabled resampling).
Flo
--
Machines can do the work, so people have time to think.
public key DA43FEF4 x-hkp://wwwkeys.eu.pgp.net
7:04 p.m.
El dl 10 de 05 de 2010 a les 17:32 +0200, en/na Florian Faber va
escriure:
Will try that with a couple of hammerfall 9632 we have in the lab before
buying the (two) AES-32.
Any recommended documentation or advice?
(Apart from this: http://alsa.opensrc.org/index.php/TwoCardsAsOne)
Thanks
P
Pau,
Right. But the MADI-to-AES alone (the ADI-6432) costs about 2800€. Far
beyond 1) and 2).
the system i need to build should have 8 AES
inputs and 24 AES outputs.
For that, i see two basic approaches 1) using two RME AES-32 (*) cards
in world-clock synch and 2) using a RME hammerfall with 24 ADAT
input/outputs and then several 8ch ADAT<->AES converters such as the
Aphex 144 (+), which costs about 400€ each 8ch unit.
3) a MADI interface and any MADI-to-ADAT converter you want What are those AES ports needed for anyway? I mean,
this are 16 channels
in and 48 channels out. With that number of channels, using AES just
becomes a pita. Think of the cabeling alone - or use Tascam-style 25 pin
DSUB connectors.
Yes AES makes it all over complex but it is a requirement not a
decision. It is all about connecting to existing boxes.
Option 1 seems
to me simpler and cheaper but i ignore if is feasible and
reliable: Have anyone had good experiences using two clock-synced RME
cards with jack?
The driver can start the buffers synchronously, so you have
sample-synchronous output. To have jack working with multiple cards, you
can either use alsa magic to combine the cards, or use alsa_out (with
disabled resampling).
7:18 p.m.
Pau,
Right. But the MADI-to-AES alone (the ADI-6432)
costs about 2800€. Far
beyond 1) and 2).
Well, you get what you pay for. Much less hassle, only one cable to
control clock, data and control information - up to several 100 meters etc.
Think of the setup and maintenance costs. This is the plug-in-and-forget
solution.
The RME cards are easy to set up: Just connect the internal sync port
using the cable that came with the cards and select "Internal" as sync
source on the slave card.
Flo
--
Machines can do the work, so people have time to think.
public key DA43FEF4 x-hkp://wwwkeys.eu.pgp.net
the system i need to build should have 8 AES inputs
and 24 AES outputs.
For that, i see two basic approaches 1) using two RME AES-32 (*) cards
in world-clock synch and 2) using a RME hammerfall with 24 ADAT
input/outputs and then several 8ch ADAT<->AES converters such as the
Aphex 144 (+), which costs about 400€ each 8ch unit.
3) a MADI interface and any
MADI-to-ADAT converter you want The driver can
start the buffers synchronously, so you have
sample-synchronous output. To have jack working with multiple cards, you
can either use alsa magic to combine the cards, or use alsa_out (with
disabled resampling).
Will try that with a couple of hammerfall 9632 we have in
the lab before
buying the (two) AES-32.
Any recommended documentation or advice?
13 May
13 May
3:14 p.m.
Florian Faber wrote
The RME cards are easy to set up: Just connect the internal sync port
using the cable that came with the cards and select "Internal" as sync
source on the slave card.
Just for the record: the two hammerfalls in sync with a virtual "multi"
device defined in .asoundrc worked like a charm, giving a total of 51
i/o channels. I tested both the capture and playback.
Below, the jack command and ~/.asoundrc file used.
Thanks!
P
----------
jackd -d alsa -d rmemulti
.asoundrc:
pcm.rme0 {
type hw
card 0
}
pcm.rme3 {
type hw
card 3
}
pcm.rmemulti {
type multi
slaves.a.pcm rme0
slaves.a.channels 26
slaves.b.pcm rme3
slaves.b.channels 26
bindings.0.slave a
bindings.0.channel 0
bindings.1.slave a
bindings.1.channel 1
bindings.2.slave a
bindings.2.channel 2
bindings.3.slave a
bindings.3.channel 3
bindings.4.slave a
bindings.4.channel 4
bindings.5.slave a
bindings.5.channel 5
bindings.6.slave a
bindings.6.channel 6
bindings.7.slave a
bindings.7.channel 7
bindings.8.slave a
bindings.8.channel 8
bindings.9.slave a
bindings.9.channel 9
bindings.10.slave a
bindings.10.channel 10
bindings.11.slave a
bindings.11.channel 11
bindings.12.slave a
bindings.12.channel 12
bindings.13.slave a
bindings.13.channel 13
bindings.14.slave a
bindings.14.channel 14
bindings.15.slave a
bindings.15.channel 15
bindings.16.slave a
bindings.16.channel 16
bindings.17.slave a
bindings.17.channel 17
bindings.18.slave a
bindings.18.channel 18
bindings.19.slave a
bindings.19.channel 19
bindings.20.slave a
bindings.20.channel 20
bindings.21.slave a
bindings.21.channel 21
bindings.22.slave a
bindings.22.channel 22
bindings.23.slave a
bindings.23.channel 23
bindings.24.slave a
bindings.24.channel 24
bindings.25.slave a
bindings.25.channel 25
bindings.26.slave b
bindings.26.channel 0
bindings.27.slave b
bindings.27.channel 1
bindings.28.slave b
bindings.28.channel 2
bindings.29.slave b
bindings.29.channel 3
bindings.30.slave b
bindings.30.channel 4
bindings.31.slave b
bindings.31.channel 5
bindings.32.slave b
bindings.32.channel 6
bindings.33.slave b
bindings.33.channel 7
bindings.34.slave b
bindings.34.channel 8
bindings.35.slave b
bindings.35.channel 9
bindings.36.slave b
bindings.36.channel 10
bindings.37.slave b
bindings.37.channel 11
bindings.38.slave b
bindings.38.channel 12
bindings.39.slave b
bindings.39.channel 13
bindings.40.slave b
bindings.40.channel 14
bindings.41.slave b
bindings.41.channel 15
bindings.42.slave b
bindings.42.channel 16
bindings.43.slave b
bindings.43.channel 17
bindings.44.slave b
bindings.44.channel 18
bindings.45.slave b
bindings.45.channel 19
bindings.46.slave b
bindings.46.channel 20
bindings.47.slave b
bindings.47.channel 21
bindings.48.slave b
bindings.48.channel 22
bindings.49.slave b
bindings.49.channel 23
bindings.50.slave b
bindings.50.channel 24
bindings.51.slave b
bindings.51.channel 25
}
The driver can start the buffers synchronously, so you
have
sample-synchronous output. To have jack working with multiple cards, you
can either use alsa magic to combine the cards, or use alsa_out (with
disabled resampling).
Will try that with a couple of hammerfall 9632 we have in
the lab before
buying the (two) AES-32.
Any recommended documentation or advice? 
11 May
11 May
10:38 a.m.
HI
I to would like the same info as I have two cards using adat to two DDX
mixes.
Would be nice to use both cards and not spend out on another mobo/card.
It's all running nice at the moment with 64studio
Cheers
Bob
On 10 May 2010 18:04, Pau Arumí <pau.arumi(a)barcelonamedia.org> wrote:
El dl 10 de 05 de 2010 a les 17:32 +0200, en/na
Florian Faber va
escriure:
Will try that with a couple of hammerfall 9632 we have in the lab before
buying the (two) AES-32.
Any recommended documentation or advice?
(Apart from this: http://alsa.opensrc.org/index.php/TwoCardsAsOne)
Thanks
P
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Pau,
Right. But the MADI-to-AES alone (the ADI-6432) costs about 2800€. Far
beyond 1) and 2).
the system i need to build should have 8 AES
inputs and 24 AES outputs.
For that, i see two basic approaches 1) using two RME AES-32 (*) cards
in world-clock synch and 2) using a RME hammerfall with 24 ADAT
input/outputs and then several 8ch ADAT<->AES converters such as the
Aphex 144 (+), which costs about 400€ each 8ch unit.
3) a MADI interface and any MADI-to-ADAT converter you want What are those AES ports needed for anyway? I
mean, this are 16 channels
in and 48 channels out. With that number of channels, using AES just
becomes a pita. Think of the cabeling alone - or use Tascam-style 25 pin
DSUB connectors.
Yes AES makes it all over complex but it is a requirement not a
decision. It is all about connecting to existing boxes.
> Option 1 seems to me simpler and cheaper but
i ignore if is feasible
and
reliable:
Have anyone had good experiences using two clock-synced RME
cards with jack?
The driver can start the buffers synchronously, so you have
sample-synchronous output. To have jack working with multiple cards, you
can either use alsa magic to combine the cards, or use alsa_out (with
disabled resampling).
5303
days inactive
5306
days old
linux-audio-dev@lists.linuxaudio.org
5 comments
3 participants
participants (3)
-
Florian Faber -
Frank Smith -
Pau Arumí