sidechaining
-
robinmeier
- Posts: 7
- Joined: Thu Sep 10, 2009 3:13 pm
sidechaining
is there a way to get the signal from track (B) into a track (A) without arming track (A) for recording.
I'd like to do some sidechaining inside a max device.
I'd like to do some sidechaining inside a max device.
-
Gregory Taylor
- Posts: 268
- Joined: Tue Sep 01, 2009 3:11 pm
Re: sidechaining
The opportunity to sidechain is going to be a 1.x feature,
as has been discussed before.
as has been discussed before.
-
andrewbenson
- Posts: 55
- Joined: Tue Sep 01, 2009 4:42 pm
Re: sidechaining
In the meantime, a clever individual could probably make use of live.remote~ to send amplitude-following data to other devices.
AB
AB
Re: sidechaining
Yeah, I've got a patch that does this. The channel is noisy, however.
Re: sidechaining
why can't you do sidechains ? I don't understand...
here are some examples
http://www.max4live.info/content/m4l-sh ... -parameter
here are some examples
http://www.max4live.info/content/m4l-sh ... -parameter

Re: sidechaining
If you depend upon high frequencies/wide bandwidth, you're not going to be happy with this technique. For example, if you are detecting transients, make sure to do it in the sending track rather than in the receiver.
So having real audio sidechains will be a welcome future feature.
I personally do a lot of cross-synthesis, which I cannot do using the automation channel.
So having real audio sidechains will be a welcome future feature.
I personally do a lot of cross-synthesis, which I cannot do using the automation channel.
Re: sidechaining
ztutz wrote:If you depend upon high frequencies/wide bandwidth, you're not going to be happy with this technique. For example, if you are detecting transients, make sure to do it in the sending track rather than in the receiver.
So having real audio sidechains will be a welcome future feature.
I personally do a lot of cross-synthesis, which I cannot do using the automation channel.
sorry if I'm slow...but..
what's the difference between the signal at the sending end and the signal at the receiving end ?
why should it be any different...?

Re: sidechaining
Now THAT is a question for the Ableton guys!
I'd love to know the answer as well, but i suspect that it has to do with priority queues and schedulers.
You'll notice that this uses a lot of CPU, yes? More than just adding another audio stream would use. Also, if you put a very simple signal through and look at it on a scope (or just listen) you'll notice that the fidelity is pretty low. To me, these are indicators that the modulation signal is being massaged and routed somewhere in the codebase. If you do the same experiment with an audio signal, you'll get results that are much less CPU intensive and much higher fidelity.
Of course, I've not seen the codebase and these are just guesses.
Great to see more tutorials, by the way. What you are doing with these signals works well!
I'd love to know the answer as well, but i suspect that it has to do with priority queues and schedulers.
You'll notice that this uses a lot of CPU, yes? More than just adding another audio stream would use. Also, if you put a very simple signal through and look at it on a scope (or just listen) you'll notice that the fidelity is pretty low. To me, these are indicators that the modulation signal is being massaged and routed somewhere in the codebase. If you do the same experiment with an audio signal, you'll get results that are much less CPU intensive and much higher fidelity.
Of course, I've not seen the codebase and these are just guesses.
Great to see more tutorials, by the way. What you are doing with these signals works well!
Re: sidechaining
hehe ... that's not my tutorial... it's 'technogod''s...ztutz wrote:Now THAT is a question for the Ableton guys!
I'd love to know the answer as well, but i suspect that it has to do with priority queues and schedulers.
You'll notice that this uses a lot of CPU, yes? More than just adding another audio stream would use. Also, if you put a very simple signal through and look at it on a scope (or just listen) you'll notice that the fidelity is pretty low. To me, these are indicators that the modulation signal is being massaged and routed somewhere in the codebase. If you do the same experiment with an audio signal, you'll get results that are much less CPU intensive and much higher fidelity.
Of course, I've not seen the codebase and these are just guesses.
Great to see more tutorials, by the way. What you are doing with these signals works well!
but I've done something pretty similar......
an an envelope following filter...
(but it uses the incoming audio signal..)
so... you're saying there is degradation in the received signal ?!
that's bad..
and cpu hungry...that's bad as well...
could it be related to the exponent parameter in the receiveing end ?
I mean in order to sidechain properly you'd have to use a logarithmic scale for modulation of volume...or frequencies ..no ?
again.. I'm sorry if I'm misunderstanding everything ..pretty new to this.

Re: sidechaining
This is kind of a little off topic, but semi-related... In Max it used to be that their were two threads... The high priority and the low priority threads. The High priority stuff was enabled by clicking on Overdrive, otherwise the threads were equal priority. You could modify the priority of messages in the thread with defer and deferlow. In the original implementation, Javascript files would always be low (No way of changing that, that i know of). There were various other messages that would be low or high. I would like to know how things work within Max For Live. I think this is very important when designing apps. If it is the same or we are considering everything is just overdrive than that's fine. I believe there was talk of that. I just want to verify.
Websites:
Max For Live Community site:
http://www.max4live.info
http://www.noisemakers.info
Controllers: Lemur, Ohm 64, Monome, APC40, Launchpad
Daw: Live 8 Suite
Audio Interfaces: Apogee Ensemble & Duet
Monitors: JBL LSR 4300
Max For Live Community site:
http://www.max4live.info
http://www.noisemakers.info
Controllers: Lemur, Ohm 64, Monome, APC40, Launchpad
Daw: Live 8 Suite
Audio Interfaces: Apogee Ensemble & Duet
Monitors: JBL LSR 4300
Re: sidechaining
Actually that tutorial is from some guy at Dubstop in NY. I am showcasing other people's work on my site. I don't want to take credit for something i did not do.3dot... wrote:ztutz wrote:Now THAT is a question for the Ableton guys!
hehe ... that's not my tutorial... it's 'technogod''s...
Websites:
Max For Live Community site:
http://www.max4live.info
http://www.noisemakers.info
Controllers: Lemur, Ohm 64, Monome, APC40, Launchpad
Daw: Live 8 Suite
Audio Interfaces: Apogee Ensemble & Duet
Monitors: JBL LSR 4300
Max For Live Community site:
http://www.max4live.info
http://www.noisemakers.info
Controllers: Lemur, Ohm 64, Monome, APC40, Launchpad
Daw: Live 8 Suite
Audio Interfaces: Apogee Ensemble & Duet
Monitors: JBL LSR 4300