Send and Receive on different Ableton tracks won't work
Well, I swear I made it work in the past but for a little while, for some reason I cannot have a send and receive work on two different patches located in two different Ableton tracks. Why? Is it maybe related to upgrading to Live 11?
For what it worths I'm trying to use one audio track signal to ring mod another audio track signal, obvious solution was to use "send~" with one channel's audio so I'm able to use it on a patch in a different audio track without losing that track's audio. Maybe there is another way? Basically I'd like to use different Audio source within live, in one single patch, and have them separate, not mixed... A lot of infos and questions, I know! I hope some of it find an answer. Thanks a lot :)
"I'd use internal Ableton Live routing to send audio to another track" yes but then I can't do what I want (one audio track ring modulating another one).
https://cycling74.com/articles/audio-routings-a-new-system-for-multi-channel-routing-in-ableton-live
https://maxforlive.com/library/device/5830/audio-routes
great, thanks!
actually better than great Mahnaz, really awesome stuff
ha ha ha
:-)
you can use send (non audio) for audio too, that is probably what you remember.
I actually made it work again, using two audio tracks, the only different thing I did is that I put the two tracks (the one with send and the one with receive) next to each other and didn't group them...not sure if that's any reason why it worked...
you can use send (non audio) for audio too, that is probably what you remember.
How so? Sending audio signals between m4L patches doesn't work for me using regular s and r objects.
I don't think Audio Routes has useable strategies either for me because I'm trying to send multiple audio signals for DSP purposes between patches.
To give a simple example I would like to be able to use exactly the same noise~ signal from one m4L patch in another one.
Is this possible?
that can be, that those do not work in a live devices context, no idea.
strange enough that [plugsend~] also does not work in live devices, while it is - unlike all the other pluggo objects - still included with max 8.x.
while i am a big fan of sending audio between plug-ins, it can be dangerous strategy and can easily lock up your session when you do something wrong (like creating loops)
in ancient times when you could make VST and protools plug-ins with max, such thigns were also highly dependable on the host programs and had properties and issues in every program.
the recent changes in live and third party options like "audio routes" are still not the real thing, like it used to be in pluggo, or like it is in max. maybe you have the chance to use max instead of live?
p.s.:
now i forgot the most important thing.
regarding [noise~] ... i believe that activating the "classic" mode will make multiple instances of noise~ output the same signal, because that is how older versions of noise~ were working.
noise~ is and was the only object which does that and it can indeed be useful.
Thanks for your reply Roman.
Well, I couldn't verify this working either, using sah~'s (with the same phasor~) or snapshot~'s after two instances of noise~ in classic mode, the outputs were different.
I'm not so familiar with working with audio rate operations, I might be using the wrong logic here.
Would the noise need to be sampled within gen~ instead to achieve synchronised sampling?
Does this make sense for the purpose of generating random modulation signals for multiple instances of a granular engine, the goal being that the mod signals are exactly the same?
Maybe I'd better move this to max, indeed.
oh, if "classic" really only refers to seed modes, then sorry for giving you false hope.
in the max 8 referecence it is not explained what it does, in the max7 reference it is not even mentioned (and probably did not yet exist)
to fully check signal content for congruency you would use [-~ ] (difference)
of course: wherever signals are not indispensable, messages are preferred, so avoid snapshot~/sig~ conversion where you can.