Julien Bayle

http://forum.designthemedia.com/files/file/5-find-your-way

When I'm designing patch, I like to link this or that parameter to a live.remote~ or live.object object in my patch.

Unfortunately, when you use it natively, you have to know the index of each parameters (I wrote index, not ID)

Example: you want to link this gorgeous LFO rate. OK. You have to use a live.path etc. BUT, what is the index of this parameter ? ? ? ? you can write the path easily like that "live_set tracks t devices d parameters p" but ... WHAT IS p ?

p can be found by trial & error but it is bad.

This device is designed to find that for you.

It is a kind of "index learning mode" device.

When I'm designing patch, I like to link this or that parameter to a live.remote~ or live.object object in my patch.
Unfortunately, when you use it natively, you have to know the index of each parameters (I wrote index, not ID)
Example: you want to link this gorgeous LFO rate. OK. You have to use a live.path etc. BUT, what is the index of this parameter ? ? ? ? you can write the path easily like that "live_set tracks t devices d parameters p" but ... WHAT IS p ?
p can be found by trial & error but it is bad.

This device is designed to find that for you.
It is a kind of "index learning mode" device.

my-last-free-utility-device-find-your-way-1-0

I wonder if using the index of parameters makes still sense considering the new features of M4L, in particular the 'selected_parameter' feature.

using selected_parameter solves a lot of issue.

but the purpose of this device is "only" to find the path of "something" while patching.

a lot of my student loved it (that makes me happy :)

using selected_parameter solves a lot of issue.
but the purpose of this device is "only" to find the path of "something" while patching.
nothing more. nothing less.

a lot of my student loved it (that makes me happy :)


my last (free) utility device: Find Your Way 1.0