|
apply filter
|
View this Thread in Original format
| vercetti101 |
how could i apply a filter to all my track for one beat. like on turntabes and a mixer with alow pass filter, on the decks i would cut filter in, turn it left (all bassy) and then right (sharp high) to full frequency - music blasting out fully.
im on FL7 and i think it could be something like putting fruity filter in the master on the mixer but how can i get it just to come in for one beat, possibly tweak it, then turn it off and cut in the music again? :conf: :conf:
how would u guys go about it? ta. |
|
|
| cryophonik |
| Just automate the cutoff frequency on the filter and have it drop down to the desired frequency for that one beat, then return to fully open. That's how I would do it in Sonar, P5, or Cubase at least - I assume FLS lets you automate plugin parameters. |
|
|
| hasbone |
filter on master
automate cutoff or mix level. :) |
|
|
| Elec |
| In case you don't know how to automate, right click on the filter's frequency knob and click "create automation clip" and then draw your line in the playlist where desired. |
|
|
| Mr Kre8 |
Anyone ever get automation clicks when bypassing and enabling delays and filters in Reason(3)? Even when the unit in question is at an entirely dry setting (and therefore doesn't/shouldn't effect the mix/instrument in the slightest.) It's a right pain. I find it happens even more with delay than filters.
EDIT
If so, does anyone have any ways to circumvent this problem? The only solution I have found is either by killing the gain entirely on the track in question (which is often not practical) or by keeping the effect enabled and using dry settings until the effect is required.
As a side question, does anyone know if bypassing or drying out any effects actually aid in CPU strain reduction (within Reason)? I *think* bypassing does this but am not entirely sure.
Sorry for the thread hijack but I believe this question has been answered and don't think this warrants a new thread. |
|
|
| Mr.Mystery |
| quote: | Originally posted by Mr Kre8
Anyone ever get automation clicks when bypassing and enabling delays and filters in Reason(3)? Even when the unit in question is at an entirely dry setting (and therefore doesn't/shouldn't effect the mix/instrument in the slightest.) It's a right pain. I find it happens even more with delay than filters.
|
Can't remember that ever happening to me. |
|
|
| MrJiveBoJingles |
| quote: | Originally posted by Mr Kre8
Anyone ever get automation clicks when bypassing and enabling delays and filters in Reason(3)? Even when the unit in question is at an entirely dry setting (and therefore doesn't/shouldn't effect the mix/instrument in the slightest.) It's a right pain. I find it happens even more with delay than filters.
EDIT
If so, does anyone have any ways to circumvent this problem? The only solution I have found is either by killing the gain entirely on the track in question (which is often not practical) or by keeping the effect enabled and using dry settings until the effect is required. |
I've had this happen. I just keep it enabled and automate the wet / dry. You could also use two separate mixer channels, one for a completely wet signal, the other for a completely dry one, and automate the volumes on those. That would certainly solve your problem. |
|
|
| derail |
Yes, I got clicks when turning Reason effects on and off while a song was playing. I just used workarounds, as other people have already mentioned.
It's interesting...I'm working in Cubase now, but I still don't automate any effect's on/off switches...even though there may be no problems with doing that now... |
|
|
|
|
