System 6000 newbie needs help

[echoRausch]

New to the TC 6000 I need some help. I have some problems to get the routing work for my demands...

Let's say I have a setup of 4 engines in serial. Loaded the routing patch 4 engines serial AES. Ok, the output of E4 goes to AES 1+2.

So far this is what I want.

AES 1+2 goes to my converter (d/a with monitors), but then I want to have the same signal as it goes to the converter (in fact the output of E4) on AES 3+4 to route it directly into the DAW (to record it).

How does that work? Does it? Therefore I would need to setup 2 outputs of E4 1/2 what is not possible.

The only way I found is to leave E4 empty, then I can route the outputs of E3 to AES 3+4 and the input of E4 to the output of E3. So the routing would be what I need but I could only use 3 (or 1 in 96 kHz!) engines anymore.

Did I overlook something? Is there a general setup to mirror outputs?

I wanted to have an ADA-card to have the ability to put a pair of monitors directly to the 6000 but then I would need another AES output to the DAW in parallel anyway.

I never thought this would be a problem as the 6000 is considered to be ultra flexible in terms of routing but I didn't find a solution so far.

I would be very happy if someone can help here... Thanks .

[Andy Krehm]

Originally Posted by echoRausch

New to the TC 6000 I need some help. I have some problems to get the routing work for my demands...

Let's say I have a setup of 4 engines in serial. Loaded the routing patch 4 engines serial AES. Ok, the output of E4 goes to AES 1+2.

So far this is what I want.

AES 1+2 goes to my converter (d/a with monitors), but then I want to have the same signal as it goes to the converter (in fact the output of E4) on AES 3+4 to route it directly into the DAW (to record it).

How does that work? Does it? Therefore I would need to setup 2 outputs of E4 1/2 what is not possible.

The only way I found is to leave E4 empty, then I can route the outputs of E3 to AES 3+4 and the input of E4 to the output of E3. So the routing would be what I need but I could only use 3 (or 1 in 96 kHz!) engines anymore.

Did I overlook something? Is there a general setup to mirror outputs?

I wanted to have an ADA-card to have the ability to put a pair of monitors directly to the 6000 but then I would need another AES output to the DAW in parallel anyway.

I never thought this would be a problem as the 6000 is considered to be ultra flexible in terms of routing but I didn't find a solution so far.

I would be very happy if someone can help here... Thanks .

I'm sorry to say that my technical support guy sets up things for me here, like routing, so I can't really help you with that!

But, I can tell you that at 96k, you cannot just use any setup you like and expect to be able to use 4 engines.

For instance, I have a standard set-up in 44.1k that uses 4 engines but when I work at 88.2 or 96k, I have to drop one engine.

So that is probably why you are having to leave one of them empty at the double SRs. The TC 6000 is really old technology, which works really well when you stick to what it does, but the resources are NOT unlimited!

[echoRausch]

Thanks Andy. The thing is I knew about the loss of one or two engines when working @96 kHz, but I never thought it would be a problem to mirror a pair of outputs.

The thing is the 6000 is technically capable to do it, but I can't set it up just because the user interface doesn't support this kind of operation.

The user manual says:
"To distribute a single Output of an Engine to several physical Outputs:
• Route the Engine Output to a physical Output.
• Route the same Engine Output through a passive channel of an algorithm loaded in another Engine. E.g. channels 7 and 8 of the Toolbox-5.1."

Doesn't help. I can't route E4 through anything because it's the last engine. It describes somehow the workaround I figured out for myself (with the loss of an engine). Frustrating!

[PBM]

Originally Posted by echoRausch

New to the TC 6000 I need some help. I have some problems to get the routing work for my demands...

Let's say I have a setup of 4 engines in serial. Loaded the routing patch 4 engines serial AES. Ok, the output of E4 goes to AES 1+2.

So far this is what I want.

AES 1+2 goes to my converter (d/a with monitors), but then I want to have the same signal as it goes to the converter (in fact the output of E4) on AES 3+4 to route it directly into the DAW (to record it).

How does that work? Does it? Therefore I would need to setup 2 outputs of E4 1/2 what is not possible.

The only way I found is to leave E4 empty, then I can route the outputs of E3 to AES 3+4 and the input of E4 to the output of E3. So the routing would be what I need but I could only use 3 (or 1 in 96 kHz!) engines anymore.

Did I overlook something? Is there a general setup to mirror outputs?

I wanted to have an ADA-card to have the ability to put a pair of monitors directly to the 6000 but then I would need another AES output to the DAW in parallel anyway.

I never thought this would be a problem as the 6000 is considered to be ultra flexible in terms of routing but I didn't find a solution so far.

I would be very happy if someone can help here... Thanks .

The solution here is to send to the DAW from the t.c.6000, then monitor the DAW signal (i.e. send that out to the d/a etc). You can use the t.c. as the central clock that way too.

Cheers,

Eric

[echoRausch]

Thanks Eric. I was hoping there would be a better solution but it seems to be the only way to go... Or maybe the purchase of a Z-Sys Detangler...

What makes me feel sick is the fact that I need another device in the chain or inconvinient DAW routing just to distribute the signal to its destinations. I never thought TC's flagship can't handle this by itself...

[PBM]

Originally Posted by echoRausch

Thanks Eric. I was hoping there would be a better solution but it seems to be the only way to go... Or maybe the purchase of a Z-Sys Detangler...

What makes me feel sick is the fact that I need another device in the chain or inconvinient DAW routing just to distribute the signal to its destinations. I never thought TC's flagship can't handle this by itself...

I see your point, but I actually like this solution - monitoring from the recorder - and don't see it as a compromise: it's what used to be called `confidence monitoring' back then when we were recording live classical music.

Cheers,

Eric

[MOBMastering]

TC is probably the worst technical support you can get on this planet...

[echoRausch]

I can't say anything bad about them so far. They replied me but unfortunately there is no other solution.

The only thing they could do is to change the user interface software but I'm not Bob Katz so they won't change the software just for me...