Any Carbon users who were using UAD Apollo before?

[Mark Ziebarth]

Originally Posted by chrisdee

So if I turn on Carbon DSP in PT it will handle all the mixing, routing, and aax dsp plugin duties on the track where it is turned on?

Any idea how big sessions I can run purely on the onboard DSP if Carbon befor it maxes out?

You’re right. I tested for tracking and maxed out the DSPs with the following:
24 Avid Channelstrips (on all inputs)
4 Sends on each channel to the headphones
5 Avid Pro Limiter, one on the Mix Bus and one per Headphone to avoid overs
2 ReVibe II
1 Tape Echo
2 Eleven
You have to consider how the plugs behave on the DSPs. A ReVibe II instance takes 57 percent of a DSP but two of them fit on one DSP. Eleven takes a whole chip etc.

Best

Mark

[quicksticks4]

I was (maybe still am?) an Apollo user attempting to make the switch to Carbon. As far as tracking goes, Carbon wins hands down. As a drummer, being able to run a 12 mic tracking session with the lowest latency is a game changer.

The one category that Apollo seems to win flat out is the i/o flexibility regarding third party software. I have started a specific thread regarding this, but it's relevant to this one as well since we're talking Apollo vs Carbon.

I do a lot of live streaming and Zoom drum lessons. The Apollo, for whatever reason, can easily route all audio being monitored (including computer playback) directly into other software such as Zoom, OBS, etc. It's as simple as choosing Apollo as the mic input.

I've spent far too much time trying to get Carbon to do the same thing. There are lots of clunky workarounds floating around including a separate interface listening to the headphone outs of Carbon, additional software that is doing limited routing within carbon, or having a second DAW open for monitoring. But there doesn't appear to be a straight up "route audio from Carbon to Zoom" option, for whatever reason.

So far this is truly my only knock on Carbon. But it's a big enough one that I'm still eyeing the return window, unfortunately.

[K Roche]

[QUOTE]

Originally Posted by chrisdee

So if I turn on Carbon DSP in PT it will handle all the mixing, routing, and aax dsp plugin duties on the track where it is turned on?

Yes and any tracks it is routed to as well (sends or output)

The way a work (arranging/porducing/mixing) It would be best to leave the CPU purely for VI's and always run all plugins on Carbons aax dsp to offload my CPU.
Any idea how big sessions I can run purely on the onboard DSP on Carbon befor it maxes out?

In my work flow I don't run very many VI's usually not more than 1-4 max. and seldom more than 10 -15 maybe 20 tracks total
But as far as Max DSP use I did this short screen recording Which I linked in my 1 week thread.. Don't know if will help inform your use but it's here

https://youtu.be/0Qz2lcE9I0Y

[chrisdee]

Originally Posted by Mark Ziebarth

You’re right. I tested for tracking and maxed out the DSPs with the following:
24 Avid Channelstrips (on all inputs)
4 Sends on each channel to the headphones
5 Avid Pro Limiter, one on the Mix Bus and one per Headphone to avoid overs
2 ReVibe II
1 Tape Echo
2 Eleven
You have to consider how the plugs behave on the DSPs. A ReVibe II instance takes 57 percent of a DSP but two of them fit on one DSP. Eleven takes a whole chip etc.

Best

Mark

Great, thanks for testing.

As I only record one track at a time sounds like I'v be able to reserve one DSP for a vocal recording audio track and use the other 7 on whatever tracks I need.

How about instrument tracks?
How does that work. Will the VI be disabled if I put aax dsp plugins after and turn on DSP?

[Mark Ziebarth]

Originally Posted by chrisdee

Great, thanks for testing.

As I only record one track at a time sounds like I'v be able to reserve one DSP for a vocal recording audio track and use the other 7 on whatever tracks I need.

How about instrument tracks?
How does that work. Will the VI be disabled if I put aax dsp plugins after and turn on DSP?

Native only plugs are bypassed when DSP mode is activated but you can exclude plugs from bypassing. The standard example is a reverb plug on an aux track: You leave it in native mode via excluding it from bypassing and take the latency as a pre-delay. I didn’t test with VIs but guess they will behave as other native only plugs.

[Kyle Splittgerber]

Originally Posted by Mark Ziebarth

Native only plugs are bypassed when DSP mode is activated but you can exclude plugs from bypassing. The standard example is a reverb plug on an aux track: You leave it in native mode via excluding it from bypassing and take the latency as a pre-delay. I didn’t test with VIs but guess they will behave as other native only plugs.

Yup, all VIs are Native-only so they are automatically bypassed in DSP Mode.

[chrisdee]

Originally Posted by Kyle Splittgerber

Yup, all VIs are Native-only so they are automatically bypassed in DSP Mode.

Thats a bummer. Sounds like I will have to change my workflow completely and either freeze or bounce all my VI tracks befor I will be able to use the onboard aax dsp?

Sounds like Carbon is more for the recording of audio with plugins and not for a work in progress senario with no actual workflow, latency or resource improvement for recording and mixing VIs on the fly?

[Kyle Splittgerber]

Originally Posted by chrisdee

Thats a bummer. Sounds like I will have to change my workflow completely and either freeze or bounce all my VI tracks befor I will be able to use the onboard aax dsp?

Sounds like Carbon is more for the recording of audio with plugins and not for a work in progress senario with no actual workflow, latency or resource improvement for recording and mixing VIs on the fly?

No, you don't need to do that. If you want to process VIs through DSP plugins you can route the Instrument/Aux track running the VI to an Aux running DSP plugins.

And, yes the priority for DSP power with Carbon is for recording workflows. But, you can still use it for offloading mix processing as mentioned above. Or, by ensuring that you run all DSP plugins on the track (although not an option for tracks with VIs or other Native-only plugins).

[chrisdee]

Ohh, thats great to hear. Thank you.

[Kyle Splittgerber]

Originally Posted by chrisdee

ohh, thats great to hear. thank you.

👍🏼