API help, how to get parameter names into umenu from the device to the left
Im trying to make a mfl device that automatically reads the available parameter names in the device located to the left of it in Live effect chain.
Is this possible, is this very diffcult to achieve
you’ll need to create a path to the parameter itself, this is easy with the live api, you may need to permanently name the pat eg tracks 0 devices 0 parameters 1 (0 is the the device on off)….
Send this to a live.object and send that a get name into the left outlet, this could then be sent to a prepend set object and out to a textedit object…
It is relatively simple i think, the challenge comes when you want to make the patch less static and available to be put into every track at will… I’d have to look into how a device would read it’s own id?
As soon as i’ve finished my patch i’ll post it up, it’s taken me a day or two to get one parameter going but the rest is a copy and paste affair so shouldn’t take me too long….
Great, im looking forward to reverse engineer the patch.
Im actually strugling with giving the lfo patch from the maxforlive sneakpeak article repleacable arguments, my modified patch fails in showing the the parameter names in the umenu :(
this will give you the path to the next device in row
From there you can easily scan for all parameters in that device
----------begin_max5_patcher---------- 729.3oc0XssiaBCE7YxWgEpOzpRQ3aboO01ei1UqHfaha4RTvYa5tZ+2K1F5 R2BDVRVqPjBPNvAOLLmwGmGVYYut7HqxF7QvWAVVOrxxRERFvp42V14wGSxh qTWlcNqpJdCy1QeNA6nPEeWrXKHieG61Jl.H1Gm7yJfGHkcGOgUAfsITbHmW jwDp6FpIXcxIa4EatcOKQnQCzyyMDivQAN.rWfKIDFfb.PeOWO4NWOvMMYyS UHnb8O9.wuy3TdPzNPvlneurPTDmyTI74873LvWJyRaSRmg326XZPXa+2AQl YE+d0If0XPF8wUqjabdcoNu1Dx3ErjxCEprHuT9zG5FEDDFPc.HTnKIBin9N .JQxmTu94SH4JlOKX+pFi+GclUFmtNtXSuJN3vLDJHPREDMgPUxrv9okvfKK snfqInlZQlqTtMStAiPJxANF4Ph5mbvyUy3z70D0hUGVWI3hCBF3MuXOKLRY NgHJVJHZTmJ5xqxZOaC63NPGN5ScN9oCmo5B4q2AQiJuf8SbzyUd8ZHyFfHe OX1ZK8NbjKcXJBGcY0Vb4TNFSd81uU+IUt492cYEXvHsqdDdLAFFufDXC4is gIFzmGcZhh3q74Ii4fgQKOGLAXMHafhuInezS+g7Fc9OzEd9OcuLZsyktRbz VREa4U2p6Bcl5n.EeEN5DgP3BrESYeT0mP97NyJL8bcPn2XRI5BkZNiVLilP Gl3EPCl5QYt8YGod9Qz1s8wB9CPCdMQSJyyY5EKZa24IPcuTKl7YK7WgGY7+ 8wpp7v9jVtpc0OfmfTJqdV4hXAurnyEIKq6bQa4oorhtvKmmtqr1OqADfa5k jmJlHvIfI4JSLHlnS.RxlMLHjd1vM.MY3WczqOLgilBlnl+cG7T5IyJwk8.d RdxrzDbJNAlspiLE0jO9pybR9u+0Qwcc3g6aTLIal+jEcTyCoSJvQl0GXBPB cNVS0+3wU+w7.h69 -----------end_max5_patcher-----------
does this also work for devices in return tracks? How do you get access to the return tracks, as they are not numbered from 0 to …?
@JKO Thanks, but it does not write the parameters into the umenu.
Would there be an easy way to filter and reorganize the list of parameters from a Live device, so when I load the Operator device, I only get the 10,15 parameters I usually modulate, and also maybe have them organized so the most used parameters appear first in the list
well, with the umenu it seems doable somehow … but what about the live.menu? I mean, this is about MaxForLive, right? :)
is that doable?
(normal Max? js?)
Sure, its maxforlive, but umenu is not an ui element that is likely you want to modulate, and then I cant see no reason not to use max ui elements.
thanks for your thoughts.
Well, IMHO look and feels means something to some computer users ….
and the candy-Max5 umenu is not really fitting the GUI aesthetics of Live ….
ok, this is no technical problem, but …. well, at least to be it is a kind of embarrassment :) whatever that is worth ;)