is there a way to fetch selected track or device to set it up so that a TDAbleton comp is sync with the “mouse” focus in Ableton?
im building it using a m4l device communicating via osc but this seems to be redundant with TDA. not sure why the current track, device,chain,param cannot be passed over from within TDAbleton.
On the abletonValueListener, there is a Follow Selection Parameter that should get you the info you need. If it doesn’t do what you need, let me know. I built the feature anticipating this need but I haven’t had any real feedback on it.
oh thank you! Not sure how I missed that whole COMP. I looked at all of the others looking for it haha.
Chains mode doesn’t seem to follow on my side, but setting the comp to parameter (or device) will find the chain anyway.
From there, how would you proceed to have it so the first 16 parameters of the selected device are available, bi-directionally between TD and Live?
I mostly want it for macros and my controller has 16 encoders, but i figured it could just auto map to the first 16 params. I checked TDA_Mapper and TDA_Rack but I don’t want to have to set it up, I just want to avoid using the mouse when designing stuff in Live. (I know some controllers can do this without going through TD but that controller does other stuff within TD anyway so I figured I’d build on top of what I already use)
My current solution is to transfer the track/device/chain/device.. mapping over to 16 abletonParameter COMP via a replicator and interact with it this way. It works but I’m always looking to learn and optimize.
I saw the ext.TDAbletonCompBaseExt.onOutParChange(par) so I’m guessing there’s a way hack together a single abletonParameter that would handle all 16 values but I haven’t dug far enough to figure it out.
Thanks.
Yeah if that is working for you that might be the best way. It’s not functionality that’s built in, and I don’t think there’s a better pathway at the moment to connect generically to selected parameters.
Thanks! Yeah it works atm, not sure if I’ll face a limit in terms of how many params I can animate at once but that will do for now.
I’m not sure what the use cases or advantages are for TDA_Mapper and TDA_Rack however, aren’t they similar except they require more setup/more devices and limit bi-directionality?
TDA_Mapper and TDA_Rack are significantly faster than abletonParameter because they use OSC instead of the Remote Script. I’m not sure how I’d set them up for a case where they need to hit any device that is selected.
thanks, it’s good to know.