Helpful ReplyRouting to a Buss

Author
ampfixer
Max Output Level: -20 dBFS
  • Total Posts : 5508
  • Joined: 2010/12/12 20:11:50
  • Location: Ontario
  • Status: offline
2016/07/03 17:46:00 (permalink)

Routing to a Buss

I'm trying to determine which is the best way to route tracks to busses. I can use a send from a track or I can simply set the track output to a buss. I typically just output the track to a buss and can't quite figure out why I'd want to use a send.
 
I'd love a bit of education on the benefits.

Regards, John 
 I want to make it clear that I am an Eedjit. I have no direct, or indirect, knowledge of business, the music industry, forum threads or the meaning of life. I know about amps.
WIN 10 Pro X64, I7-3770k 16 gigs, ASUS Z77 pro, AMD 7950 3 gig,  Steinberg UR44, A-Pro 500, Sonar Platinum, KRK Rokit 6 
#1
codamedia
Max Output Level: -67 dBFS
  • Total Posts : 1185
  • Joined: 2005/01/24 09:58:10
  • Location: Winnipeg Canada
  • Status: offline
Re: Routing to a Buss 2016/07/03 19:03:13 (permalink) ☄ Helpfulby ampfixer 2016/07/03 22:21:51
There are many ways to approach this. I am pretty "old school" so this is how I always do it.
 
If I create a bus as a sub mix, I route all corresponding tracks to that bus. EG: An electric guitar bus will have all electric guitars routed to it. A BG Vocal Bus will have all background vocals routed to it, etc... etc...
 
If I create a bus as an effect (Long Reverb, Short Reverb, Long Delay, Short Delay) then I will use "sends" to access each bus. The track itself will be routed to it's appropriate "bus track" (as mentioned above) but I can send signal to any of the "effect bus tracks" using sends. This gives every single track in the project access to any effect bus.
 
Sends also work well for parallel processing... but that an entirely different topic.
post edited by codamedia - 2016/07/03 19:27:56

Don't fix it in the mix ... Fix it in the take! 
 

Desktop: Win 7 Pro 64 Bit , ASUS MB w/Intel Chipset, INTEL Q9300 Quad Core, 2.5 GHz, 8 GB RAM, ATI 5450 Video
Laptop: Windows 7 Pro, i5, 8 Gig Ram
Hardware: Presonus FP10 (Firepod), FaderPort, M-Audio Axiom 49, Mackie 1202 VLZ, POD X3 Live, Variax 600, etc... etc...
#2
ampfixer
Max Output Level: -20 dBFS
  • Total Posts : 5508
  • Joined: 2010/12/12 20:11:50
  • Location: Ontario
  • Status: offline
Re: Routing to a Buss 2016/07/03 22:03:30 (permalink)
Perfect. That's exactly what I was hoping to hear and it makes perfect sense. Thanks.

Regards, John 
 I want to make it clear that I am an Eedjit. I have no direct, or indirect, knowledge of business, the music industry, forum threads or the meaning of life. I know about amps.
WIN 10 Pro X64, I7-3770k 16 gigs, ASUS Z77 pro, AMD 7950 3 gig,  Steinberg UR44, A-Pro 500, Sonar Platinum, KRK Rokit 6 
#3
timidi
Max Output Level: -21 dBFS
  • Total Posts : 5449
  • Joined: 2006/04/11 12:55:15
  • Location: SE Florida
  • Status: offline
Re: Routing to a Buss 2016/07/03 22:31:12 (permalink)
Yea, what Sean said.
 
Along the same lines, I'm wondering what folks do with the outputs of their effect return busses? I have problems sometimes in that usually I send the outs of these busses to the master, But, if there is any processing on the other instrument subgroups, I tend to get artifacts, or oddness, out of the effect busses because the sends of those instruments usually come from the track sends . Hope that makes sense.

ASUS P8P67, i7-2600K, CORSAIR 16GB, HIS 5450, 3 Samsung SSD 850, Win7 64, RME AIO.
 
https://timbowman.bandcamp.com/releases
 
#4
sven450
Max Output Level: -72 dBFS
  • Total Posts : 945
  • Joined: 2004/03/16 08:11:49
  • Status: offline
Re: Routing to a Buss 2016/07/04 11:13:37 (permalink)
codamedia
There are many ways to approach this. I am pretty "old school" so this is how I always do it.
 
If I create a bus as a sub mix, I route all corresponding tracks to that bus. EG: An electric guitar bus will have all electric guitars routed to it. A BG Vocal Bus will have all background vocals routed to it, etc... etc...
 
If I create a bus as an effect (Long Reverb, Short Reverb, Long Delay, Short Delay) then I will use "sends" to access each bus. The track itself will be routed to it's appropriate "bus track" (as mentioned above) but I can send signal to any of the "effect bus tracks" using sends. This gives every single track in the project access to any effect bus.
 
Sends also work well for parallel processing... but that an entirely different topic.


Exactly what I do too.

Sonar Platinum/Bandlab Sonar
Roland Octa-Capture            
Win 10 
i7 6700  16 Gig Ram
Some songs
Covers:  https://soundcloud.com/cygnuss/sets/covers
Originals:
 https://soundcloud.com/cygnuss/sets/originals
#5
chuckebaby
Max Output Level: 0 dBFS
  • Total Posts : 13146
  • Joined: 2011/01/04 14:55:28
  • Status: offline
Re: Routing to a Buss 2016/07/08 07:40:03 (permalink)
back in the old days when all I had was a 4 track recorder, this was really the only option.
you had 2 sends on each track. All outputs of those 4 tracks went to the master bus.

as you can see in the example above. going from bottom to top= there is a volume / pan / 2 sends
on each track. don't be misunderstood this is NOT an 8 track (5-6+7-8) Those last 2 faders (to the right)
were stereo inputs used in conjunction with the 2  1/4 inch jack sends located on the back.
in other words, you hooked up your hardware's outputs to 5 thru 8.
-The sends controls the amount of signal that goes to your hardware (the input).
-The faders controls the amount that comes from the hardware (output).
 
so now we go to a realistic approach in something like Sonar.
you typically never use a send for something like compression. unless of course your using it as an effect.
IE= Parallel Compression. 
You will however find a send is very productive in FX like Delay, Reverb, Chorus, Flange.
 
Example=
lets say I have 3 vocal tracks (1 lead vox / 2 background vox) 
I want the lead vocal to have a good amount of reverb but I don't want the background vocals to have as much.
(you want to be able to distinguish the tracks. putting the same amount of reverb to all 3 vocal tracks will make them muddy and dare I say: blurry.)
there is no way possible to accomplish this using a bus. your only other option is to put a single reverb FX on each individual track. which lets face it, that is chewing up CPU.
so what we do is:
 
1-create a bus.(set the bus output to the master)
2-insert a reverb in to the FX bin of the bus.
3-insert a send to each of the 3 vocal tracks (the 1 lead vox / 2 background vox).
4-turn the lead vox send to around 5 o'clock.
5-turn the 2 background vox sends to 3 o'clock.
 
taking it one step further, you can automate the sends. which IMO is one of the best parts
about using sends vs. a bus.
if there's a long vocal note. apply automation to crank up the send during just that one part.
of course all the while being thoughtful and aware of what too much reverb does (drowns the sound).
 
Sends are critical in saving resources and mastering the tool.
 
post edited by chuckebaby - 2016/07/08 08:19:10

Windows 8.1 X64 Sonar Platinum x64
Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GB
Focusrite Saffire 18I8 - Mackie Control
   
#6
mettelus
Max Output Level: -22 dBFS
  • Total Posts : 5321
  • Joined: 2005/08/05 03:19:25
  • Location: Maryland, USA
  • Status: offline
Re: Routing to a Buss 2016/07/08 08:14:02 (permalink)
Sends also give you additional controls of the levels, in addition to pre/post fader. Not sure if that was specifically hit above, but dovetails to side-chaning (ducking, gated reverbs, yada yada).

ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
#7
Jump to:
© 2024 APG vNext Commercial Version 5.1