|
Dry/Wet & SendFx
|
View this Thread in Original format
| Phantasme |
u have a wav sample of the track for your synth named synth.wav with no effect, it's DRY.
U open your sequencer. You create two identical audio track with synth.wav.
One is dry and the other is inserted with fx.
This is scenario(1).
Scenario(2) is u create only one audio track with your synth.wav and you are using send fx.
what are the differencies between scenario(1) and scenario(2) ? |
|
|
| Pimp_fu |
Lets look at scenario one first. Obviously both tracks are going to end up in the same place, i.e., your master strip on the mixer. The effect of having two identical tracks dropped on top of each other is going to cause a signal spike, without adjusting the relative volumes of each track, this will cause clipping, and/or sit so far up front in the mix that the other elements seem way further back. You CAN set things up this way and sculpt both signals to get them to sit down in the mix, however, this is pretty time consuming. At best, this method is going to result in an unneccesarily high demand on your CPU.
With Scenario two, what you're doing is, in effect, the same thing as before, but by a vastly different process. Instead of having two tracks at identical volumes, think of the dry track as being at 100% volume, and the wet track being at 0%. With scenario 1, as you turned up the volume of the wet track, you have to turn the dry track down to avoid clipping. With scenario 2, the volume of the wet track doesn't have the same impact on the level of the dry. On a more basic level, with scenario 2, you only have to adjust the send level of the wet signal, as the dry signal will essentially remain unchanged. Fewer knobs to fiddle with. In addition, this creates a lighter load on the CPU.
There are undoubtedly thousands of other reasons and explanations for usings sends, but to go into explaining even the more common would take all night. If you want a more info, email me and I'll see what I can do.
-Pimp-
[email protected] |
|
|
|
|
