As it stands, Podium does not natively support Aux bussing, but using Tobybears MixBox, some of Jaltoh’s plugins or Senderella (See KvR to where to get them) it can be simulated.
I have used mainly mixbox, but what I have found with this applies elsewhere.
Basically all goes well, and the sends/ returns can be implemented efficiently, apart from when it comes to bouncing.
Scenario:
Master
|
---MixBox1 Send
| ---Track1
| ---Track2
---MixBox1 Send
| ---Track3
---MixBox1 Send
| ---DrumTrack1
| ---MixBox2 Send
| ---DrumTrack2
| ---DrumTrack3
| ---DrumTrack4
---Reverb
| ---MixBox1 Return
---Delay
---MixBox2 Return
All goes well here, feeds from all the tracks can get sent to their relevant ‘Aux Channels’. There is a bit of DrumTrack2 fed into a delay, as well as the reverb.
Now then, if the Drums are put into a group and bounced:
Master
|
---MixBox1 Send
| ---Track1
| ---Track2
---MixBox1 Send
| ---Track3
---MixBox1 Send
| ---Bounced Drums Group
| ---DrumTrack1
| ---MixBox2 Send
| ---DrumTrack2
| ---DrumTrack3
| ---DrumTrack4
---Reverb
| ---MixBox1 Return
---Delay
---MixBox2 Return
All the reverbs sound as before, but since the Drums Group is acting as a bounced track, anything going on WITHIN the group is no longer processed – so the send to the delay no longer happens.
To get around this, the Delay needs to be bounced at the same time as the rest of the track is bounced, and the audio from there stored something like:
Step 1:
---Delay
---MixBox2 Return
becomes
---Delay [DrumTrack2] Bounce
---Delay
---MixBox2 Return
Step 2:
---Delay Group
---Delay [DrumTrack2] Bounce
---Delay
---MixBox2 Return
That way everything is preserved.
It’s a bit fiddly, and you need to keep a clear head. Naming the tracks and clips with what they are is helpful.
I give this as a warning to Frits as well, that when implementing Auxes, it might be worth having this automated as an option [ie when creating a bounce, or aux send behind a bounce a warning should be made about it, and provision for individual bounces can be put in place].
Well there you go.
Hope that helps anyone else investigating this area.
DSP
Many thanks,
I have pondered over how to handle this, but it’s great to have an example scenario laid out as clean as this. I’m not far away from beginning implementation of bussing support, so I appreciate any input people may have on various bussing strategies.
Glad to be of service!
In automating the creation of what is needed when auxing behind a group, when a bounce enabled group is created an ideal process should be:
Start with:
---Send
| ---MyAuxedTrack
---Effect
---Return
Bounce created:
---MyAuxedTrack Bounce
| ---Send
| ---MyAuxedTrack
---Effect
---Return
Podium creates:
---MyAuxedTrack Bounce
| ---Send
| ---MyAuxedTrack
---Aux1 Group
---MyAuxedTrack Bounce
---Effect
---Return
When MyAuxedTrack Bounce is armed, change to:
---MyAuxedTrack Bounce
| ---Send
| ---MyAuxedTrack
---Aux1 Group
---MyAuxedTrack Bounce
---Effect
---Return
To record returned audio. When disarmed, return to
---MyAuxedTrack Bounce
| ---Send
| ---MyAuxedTrack
---Aux1 Group
---MyAuxedTrack Bounce
---Effect
---Return
Of course, this only suits the scenario of one track behind the group. If this is already setup, and another send is created, attention will be needed as to how to correctly slit out the new send..
This would of course be a pig to program, but when programmed properly will be pretty cool!
HTH
DSP
Frits,
Sony/Sonic Foundry Acid 4.0 implements bussing very very nicely! An ideal system, and one that parallels a real studio setup would allow you to:
1. Create as many Stereo Aux Buss sends as you need.
2. Allow the user to direct each track to any of those AUX busses.
3. Allow volume level automation of the buss.
…as it goes, so does NTrack Studio! at very minimal cost!
However, when the Podium version arrives I shall be a very happy man… rather than just the happy one I present to you today!
DSP