[ddots-l] Re: Auxiliary sends & track outputs

  • From: "Luis Elorza" <luiselorza@xxxxxxxxx>
  • To: <ddots-l@xxxxxxxxxxxxx>
  • Date: Tue, 3 Apr 2007 17:21:02 -0700

i only use the volume trim when i have automation on the volume control and i need an overall volume change .


----- Original Message ----- From: "Phil Halton" <philhalt@xxxxxxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Tuesday, April 03, 2007 9:30 AM
Subject: [ddots-l] Re: Auxiliary sends & track outputs


Most excellent! This one clarification is what I needed. And, thanks to Luis, I also understand the sends relationship to pre/post fader.

Now, with the fader in question being the track's volume control...

I would like to understand the relationship between the volume slider, trim slider, and the peak meters. If I have it right, a track whose peak output level indicator is -10db with a volume slider value of 0db. Then, cutting or boosting the volume slider into negative or positive DB would decrease or increase the actual peak level around its -10db level. So, the volume db level is not to be confused with the actual peak meter level, but is relative to it--with 0db being the origional recorded level?

Is the Trim slider then, a fine tuning of the volume slider?

Thanks in advance for your help on this


----- Original Message ----- From: "Christopher Bartlett" <bridgeweaver@xxxxxxxxxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Monday, April 02, 2007 11:25 PM
Subject: [ddots-l] Re: Auxiliary sends & track outputs


OK, I am, with much trepidation going to try answering this one with the usual able backstopping from others here.

No, your guess makes sense, and I thought the same thing myself, but the send is not a diversion from the original signal path, but an additional signal path that is added to the original where the paths recombine at the master bus, or however you have your bus outputs set up. This has several results. If the output volume of your track = the send level, the resultant is twice as loud (+6DB? higher) than the track alone. In theory then, a track at -12DB with a send level of -12 DB and no gain modification in the buses would yield a resultant of -6DB total. This is idealized.

Now the confusing part comes in when you consider whether the send is pre or post-fader, and I may actually have some of the preceding wrong. If the send is pre-fader, then the output of the send is independent of the track volume which is the situation I described. If the send is post-fader, then I think the send output is relative to the track volume, so in order to have the double effect I spoke of previously, the send level would be 0DB or equal to the track output.

Someone rescue me, I think I'm muddling toward correctness, but I may have confused the issue worse.

Christopher Bartlett

** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq



** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq


** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq

Other related posts: