autofilter sidechain bug
Posted: Wed Sep 02, 2009 6:05 pm
ive found a nice one.
use a short kick to trigger the autofilters sidechain to get rid of a bassline's low frequencies by highpass filter while the kick lasts.
this is basically done by sidechain compression but the bad then the whole signal is ducked, not only low frequencies.
so this method is less redneck disco i mean better to not confuse the bassline with the kick, but still hear the bassline (the basslines upper(250+) frequencies).
i discovered there is a short click at the beginning, and it shouldnt be there, maybe it could be solved by a 10ms lookahead as in the sidechain compressor anyway (and then would be welcome!).
but the even weird thing is when i route the kick signal to a return track or onto another simple audio track then selecting "sends only" routing on the kick channel and mute the route channel.... then it mutes the 2 same kick but still can trigger the sidechain. this is normal.
but when it comes to choose to what one should trigger: the route or the original, then the characteristics of the filter changes! the weird click at the beginning still present but has two different types!
shouldnt it be the same if the exact same signal on both channel, and at equal volumes?
i would field it as a bug. i dont know its a routing bug or just the autofilter.
but definite is.
here is a sample of this (a small zip project created in live 7.0.15 using operator: a single thin kick and a single subbass)
thanks for checking
http://rapidshare.com/files/274791188/a ... roject.zip
use a short kick to trigger the autofilters sidechain to get rid of a bassline's low frequencies by highpass filter while the kick lasts.
this is basically done by sidechain compression but the bad then the whole signal is ducked, not only low frequencies.
so this method is less redneck disco i mean better to not confuse the bassline with the kick, but still hear the bassline (the basslines upper(250+) frequencies).
i discovered there is a short click at the beginning, and it shouldnt be there, maybe it could be solved by a 10ms lookahead as in the sidechain compressor anyway (and then would be welcome!).
but the even weird thing is when i route the kick signal to a return track or onto another simple audio track then selecting "sends only" routing on the kick channel and mute the route channel.... then it mutes the 2 same kick but still can trigger the sidechain. this is normal.
but when it comes to choose to what one should trigger: the route or the original, then the characteristics of the filter changes! the weird click at the beginning still present but has two different types!
shouldnt it be the same if the exact same signal on both channel, and at equal volumes?
i would field it as a bug. i dont know its a routing bug or just the autofilter.
but definite is.
here is a sample of this (a small zip project created in live 7.0.15 using operator: a single thin kick and a single subbass)
thanks for checking
http://rapidshare.com/files/274791188/a ... roject.zip