What you need to do is create an fx bus, insert an effect (reverb for example), and move the coresponding knob up on whatever track you would like to have reverb on.
Although it will be nice to have the option for post fader sends, they are not broken. If you don't do any volume fader automation, you are fine.
They do work as is, but they should be post-fader, as this is what most people familiar with DAWs are going to expect, and I'm reluctant to start making use of them if Intua does release an update that changes them to be post-fader.
Intua either needs to engage the user community a bit more, or get more beta testers. It's bizarre to me that none of their beta testers would bring up the issue of sends being pre-fader, or the existence of the FX bus bug in 2.4.
@thesavage: Alright. There is a fundamental difference between insert effects and send effects.
You use insert effects if you want to change the sound of the *entire* signal - i.e., nothing of the original signal is left, it's all processed by the insert effect. This is typical for compressors, EQs, chorus etc.
Now, a SEND effect is a totally different beast: You use it to *add* something to a signal, but leave the original signal intact. Best examples for this use case are reverbs and delays (echos).
You can do this with inserts as well, but you'll need to insert a reverb (eats lots of CPU as well) into EACH channel where you want reverberation.
So, you take a different approach: You use an AUX bus (BM2 calls this "FX Bus"), and then insert a SINGLE reverb there set to all "wet" (it doesn't leave any of the original signal).
THEN, you can use the SENDS to send a PART of each channel signal that wants reverberation to that FX bus, and depending on the level of the send knob, the reverb bus will get different proportions of each signal and thus different amounts of reverb will be heard for each of those signals from the channels.
It's a hard to grasp concept at first, but the bottom line is: You only need a SINGLE reverb plugin (with single CPU usage) to add reverb to an arbitrary number of sounds/channels.
Makes sense?
(Same goes for Delay (Echo))
Now, the pre/post problem: Intua has made the hilarious mistake and made the sends PRE-fader. That means that the amount of signal sent to the FX bus is *independant* of the channel volume fader. That is not good, because if you make a channel louder, its reverb (for example) will then actually get softer, because the fader doesn't influence the amount of signal going to the FX bus. Likewise, if you lower a channel's level, it will suddenly have too much reverb.
That's why any "normal" <!-- s;-) --><img src="{SMILIES_PATH}/icon_e_wink.gif" alt=";-)" title="Wink" /><!-- s;-) --> mixing console has the FX sends *after* the fader so that if you halve the signal of the channel, the portion of the signal going to the reverb is halved as well.
Would anyone else like to see send knobs on the pads? Post pad volume, of course <!-- s:D --><img src="{SMILIES_PATH}/icon_e_biggrin.gif" alt=":D" title="Very Happy" /><!-- s:D -->
Well, actually, I think that would be the wrong approach. Multiple outputs per Drum Machine, and then assignable output per Pad would probably make more sense (a la NanoStudio). Then you can also use inserts...
But we already have as many multiple outputs as the iOS device allows, via the busses.
I see what you are saying, but its way too complicated. One knob somewhere in the pad edit section with a drop down box to select which fx buss to send to. No?
Comments
Although it will be nice to have the option for post fader sends, they are not broken. If you don't do any volume fader automation, you are fine.
Intua either needs to engage the user community a bit more, or get more beta testers. It's bizarre to me that none of their beta testers would bring up the issue of sends being pre-fader, or the existence of the FX bus bug in 2.4.
what the difference between pre and post fader?
and "volume fader automation" please what do you mean by that, keep seeing it come up?
Sorry for my lack knowledge, but beside being a great app, I have learned a great deal from it and everyone here.
thank you.
You use insert effects if you want to change the sound of the *entire* signal - i.e., nothing of the original signal is left, it's all processed by the insert effect. This is typical for compressors, EQs, chorus etc.
Now, a SEND effect is a totally different beast: You use it to *add* something to a signal, but leave the original signal intact. Best examples for this use case are reverbs and delays (echos).
You can do this with inserts as well, but you'll need to insert a reverb (eats lots of CPU as well) into EACH channel where you want reverberation.
So, you take a different approach: You use an AUX bus (BM2 calls this "FX Bus"), and then insert a SINGLE reverb there set to all "wet" (it doesn't leave any of the original signal).
THEN, you can use the SENDS to send a PART of each channel signal that wants reverberation to that FX bus, and depending on the level of the send knob, the reverb bus will get different proportions of each signal and thus different amounts of reverb will be heard for each of those signals from the channels.
It's a hard to grasp concept at first, but the bottom line is: You only need a SINGLE reverb plugin (with single CPU usage) to add reverb to an arbitrary number of sounds/channels.
Makes sense?
(Same goes for Delay (Echo))
Now, the pre/post problem: Intua has made the hilarious mistake and made the sends PRE-fader. That means that the amount of signal sent to the FX bus is *independant* of the channel volume fader. That is not good, because if you make a channel louder, its reverb (for example) will then actually get softer, because the fader doesn't influence the amount of signal going to the FX bus. Likewise, if you lower a channel's level, it will suddenly have too much reverb.
That's why any "normal" <!-- s;-) --><img src="{SMILIES_PATH}/icon_e_wink.gif" alt=";-)" title="Wink" /><!-- s;-) --> mixing console has the FX sends *after* the fader so that if you halve the signal of the channel, the portion of the signal going to the reverb is halved as well.
Well, actually, I think that would be the wrong approach. Multiple outputs per Drum Machine, and then assignable output per Pad would probably make more sense (a la NanoStudio). Then you can also use inserts...
I see what you are saying, but its way too complicated. One knob somewhere in the pad edit section with a drop down box to select which fx buss to send to. No?
'One knob somewhere in the pad edit section with a drop down box to select which fx buss to send to. No?
That seems better, not sure why there is 4 knobs?