MOTUnation.com

Robert Randolph wrote:

JSmith1234567 wrote: I've never understood why aux busses seem to take such a huge toll on processing power?

I can have a huge template, but adding even just a few auxes just slams the performance meter and slows things to molasses.

Because they interrupt the ability for the pre-gen system to work. Nothing on an AUX can be pre-gen'd.

So if there is no plugs on an Aux and use it as a sum the cpu hit will be less?

Did someone noticed that when recording automation, it works tweaking knobs, but it won't record bypass or enable on a plugin, that was working on previous version !
anyone can confirm that ?

cheers !

Just tried it with a 3rd party plugin, and it works fine here on DP 9.13, though not everything works correctly in this version.

waxman wrote:

Robert Randolph wrote:

JSmith1234567 wrote: I've never understood why aux busses seem to take such a huge toll on processing power?

I can have a huge template, but adding even just a few auxes just slams the performance meter and slows things to molasses.

Because they interrupt the ability for the pre-gen system to work. Nothing on an AUX can be pre-gen'd.

Do all DAW's have a slow down with Auxes? PT, Logic, Studio One etc... any better then another?

I run a ton of Auxes, always have. For m to mix like I want, I need a variety of sub group controls, Auxes are the way for me. Never realized they made DP crankier.

We too, use many many auxes in our scoring template. Have to. At least until someone shows us an alternate way to get all the subs we need for stems etc. Any ideas?

And would someone be kind enough to sum up why using lots of auxes is bad in one or two sentences. It would be appreciated as I am in the weeds with work and not much time for research.

labman wrote:We too, use many many auxes in our scoring template. Have to. At least until someone shows us an alternate way to get all the subs we need for stems etc. Any ideas?

And would someone be kind enough to sum up why using lots of auxes is bad in one or two sentences. It would be appreciated as I am in the weeds with work and not much time for research.

You won't get that reasoning from me. I use many aux busses all the time with no issues.

labman wrote:We too, use many many auxes in our scoring template. Have to. At least until someone shows us an alternate way to get all the subs we need for stems etc. Any ideas?

And would someone be kind enough to sum up why using lots of auxes is bad in one or two sentences. It would be appreciated as I am in the weeds with work and not much time for research.

cos it completely brings my system to a grinding halt!!

ghobish wrote:

labman wrote:We too, use many many auxes in our scoring template. Have to. At least until someone shows us an alternate way to get all the subs we need for stems etc. Any ideas?

And would someone be kind enough to sum up why using lots of auxes is bad in one or two sentences. It would be appreciated as I am in the weeds with work and not much time for research.

You won't get that reasoning from me. I use many aux busses all the time with no issues.

Same here.

Aux tracks are an essential part of my template to extract all my stems. There's no other way around it if that's what you need.
DP9.02 works mostly fine here (with huge room for improvements...).

gman wrote:Did someone noticed that when recording automation, it works tweaking knobs, but it won't record bypass or enable on a plugin, that was working on previous version !
anyone can confirm that ?

cheers !

Confirmed. It seems to effect some Waves and MOTU plugins in my experience. Only effects bypass automation.

I've found auxes in general not to be the problem. It's when sending many tracks to an aux and then bussing that aux to another aux that the CPU hit starts to increase. Do that a couple more times (not that there is always that need) and DP has a hard time keeping up. Hungry plugins like Eventide's Blackhole and Waves H-delay don't help. When I've taken those out of the aux chain, performance has improved.

On a technical note-
There could be a comparison between “grouping” tracks and creating an Aux bus. I have watched fader movement when grouping and determined that pulling vol up and down does not result in a equal change in value in a variety of circumstances, not the least of which is what happens when one fader reaches maximum or minimum before the others. Thus, a true 1:1 ratio of volume and other values can only occur through use of an Aux track.
In addtion, when I make Auxes, I want 100% isolation of that group for stems and mixing. For example, I will add a reverb. and various effects, ONLY to that sub group. Thus, if I bring down “electric guitars” on the master Aux fader, they have their own reverb, separate from other guitars and reverbs. It is this type of isolation that creates true control over a mix for me. Without axes, it would be far more difficult.
I am staying put at 9.02 because of various chokes and burps, and irregular behavior compared to 9.02 and DP 8. The fact that Auxes are handled differently than other tracks is something I have not quite wrapped my head around yet. But I am wondering of ONE way to get around all this inconsistent and controversial latency compensation, is to use Aux buses on everything?
besides routing my sub groups like guitars, I also route everything to a BAND AUX. Yet I am still not having a good experience with 9.13. Thoughts about using Auxes everyone to either improve or get around Latency Comp?

I just found out about this AUX buss issue, the hard way, last evening. I'm working on a project which is taxing my 12-core,64gb, 3 UAD-2 Octo, PCIe-424 system, even with the buffer maxed (pcie-424) at 1024, and I've been scratching my head as to why. So I turned off all tracks except the background vox and removed all plugins so that there was only the two back vox tracks and the 6 busses associated with them. Enabling this group of tracks takes my idle processor usage from around 20% to around 90% with a 256 buffer. Hitting play with them enabled chokes the system. Disabling them brings it back down to 20%. Again, this is with all the plugins removed and only audio routing. I don't know if I'm just remembering incorrectly, but using Aux busses didn't seem to tax the system as much as it is doing in 9.13.

Adding in the E.Guitar group's 4 aux busses, Acc Guitar Group's buss, Drum Group's 12 busses (bfd3 multi-out), Keyboard Group's 2 aux busses and bass turns my system into a pinwheel displaying piece of art more than a music creation system. With everything enabled and the buffer at 1024, when trying to edge edit an audio clip, you have to position the cursor on the edge, click, wait 30 seconds for the click to be acknowledged (and the pinwheel to go away) then you can slide the edge. Releasing the click is another 30-second pinwheel pause.

All this and I've yet to record the main vocal track and getting extremely frustrated with DP. To make matters worse, trying to load Falcon results in a crash with a "crash origin unknown" report and not much help from either MOTU or UVI (so far at least anyway).

Does this sound like typical behavior? Have any insight? I'd greatly appreciate any you could offer.

I wasn't going to post about this, but reading the aux buss posts above, changed my mind. Don't mean to hijack the thread and if this should have been a separate post, sorry.

The track routing for my example is: Two mono back vox audio tracks routed to a vox sub stereo buss for summing and feeding to composited fx. One send from the sub to a vox fx buss which feeds the two verbs (one for width and one for tails) and a mono send for sidechain triggering (using MOTU's compressor) for ducking the long tail verb during singing. All three of those busses go to a back vox mix buss, then to a 'All Vocals' buss and finally the Mix/Master buss.

Here is an image showing what track routing looks like, sans mix/master buss.

ccrane wrote:

gman wrote:Did someone noticed that when recording automation, it works tweaking knobs, but it won't record bypass or enable on a plugin, that was working on previous version !
anyone can confirm that ?

cheers !

Confirmed. It seems to effect some Waves and MOTU plugins in my experience. Only effects bypass automation.

Run the plugin in real time and it works, at least for me on MAS plugs. Didn't try Waves this evening.