prko

I would like to control 'sample selector' of an instance of Sampler and 'chain selector' of an instrument rack in Live through M4L.

Firstly, I must know the path of the sample selector. Thus I read the LOM document (

https://docs.cycling74.com/max7/vignettes/live_object_model),

I also think the following method will not work properly, because we have live.remote~, but we do not have live.remote.

live.path -> live.remote~ -> track 5 -> sampler -> sample selector

I would like to control 'sample selector' of an instance of Sampler and 'chain selector' of an instrument rack in Live through M4L.
Is it possible? 

Firstly, I must know the path of the sample selector. Thus I read the LOM document (https://docs.cycling74.com/max7/vignettes/live_object_model), but I could not understand it.

I also think the following method will not work properly, because we have live.remote~, but we do not have live.remote.
live.path -> live.remote~ -> track 5 -> sampler -> sample selector

how-to-control-sample-selector-and-chain-sekector-in-live-through-m4l

I have tried to patch with live.object but have no success.

Yeah there's a solution. You probably just didn't have the right path.

You can also use live.remote~, but I used live.objects for this demonstration.

Why do think that it wouldn't work with live.remote~? and why would we need a non audio version?

Yeah there's a solution. You probably just didn't have the right path.
You can also use live.remote~, but I used live.objects for this demonstration.
Why do think that it wouldn't work with live.remote~? and why would we need a non audio version?


I thought live.remote~ controls audio signals, but "sample selector" and "chain selector" have just 128 values.

I think live.control is a proper object for it...

Thank you very much!
I thought live.remote~ controls audio signals, but "sample selector" and "chain selector" have just 128 values.
I think live.control is a proper object for it...
I will try it later.

You're misunderstanding live.remote~. You use audio signals to control a parameter that is assigned to live.remote~. If you use an lfo (or any continuous source of data) to control a live.object, it will flood the undo history. Which is bad.

how to control 'sample selector' and 'chain sekector' in Live through M4L