[TURICUM]

Hello
Sorry my English, Google Translator is helping me :/
Recently I acquired a UA Apollo Quad Core interface.
I'm using a Thunderbold connection with my MacBook Pro without any problems..

The issue is that I have another interface (Echo Audiofire pre8), that I want to connect with the Apollo to increase my XLR channels.

Well, I connect the ADAT output of the Echo with the Apollo ADAT01 imput.
I also connect a BNC cable to the Apollo clock output with the Echo clock input.

This done, I open the console of the Apollo on my Mac and I dont get any signal on channel ADAT. I think something should already appear.

Either way, I also can not open the Echo console, since I'm only sending (or trying to send) digital signal.

But I can do it, if I connect the Echo firewire 400 output with the Apollo firewire 800, so I can "see" the two interfaces on the Mac audio settings and also open the consoles of the two making the necessary selections. However this in no way changes the ADAT signal that does not get in the Apollo.

Due to this Firewire connection, in Pro Tools I receive signals from one or another interface, but even in selecting the two in the "Pro Tools Agregate" I can not receive the signal of both interfaces simultaneously.

I really need your help because I need more of these channels.

grateful

[Scott Dorsey]

TURICUM wrote:
I'm using a Thunderbold connection with my MacBook Pro without any problems.

The issue is that I have another interface (Echo Audiofire pre8), that I wa=
nt to connect with the Apollo to increase my XLR channels.

Well, I connect the ADAT output of the Echo with the Apollo ADAT01 imput.
I also connect a BNC cable to the Apollo clock output with the Echo clock i=
nput.

This done, I open the console of the Apollo on my Mac and I dont get any si=
gnal on channel ADAT. I think something should already appear.

And... what happens if you try this with the Apollo interface removed? Can
you then see the Echo?

What happens if you try it with the drivers for the Apollo interface removed?


You don't say what version of MacOS you are running but my suspicion is
that the Apollo drivers are preventing the Echo drivers from loading.
If you type "dmesg" at the prompt (you will need to be root so you may need
to do "sudo dmesg" you should see a whole bunch of messages from various
drivers loading and unloading. Look through that and you should see some
error messages from the Apollo and Echo drivers.
--scott

--
"C'est un Nagra. C'est suisse, et tres, tres precis."