How can the LongName of a M4L DeviceParameter be accessed in the LOM?


    Jun 15 2020 | 9:24 am
    The Live Object Model for DeviceParameter only seems to allow access to the ShortName as property. How could one distinguish between different parameters with the same ShortName, then? (You can imagine, in a complex device there can be many "Gain" parameters...)

    • Jun 15 2020 | 2:51 pm
      maybe just give different short names?
    • Jun 16 2020 | 7:56 am
      Well, the short name is the one visible in the UI, it can be short because its precise meaning is clear from the context (panel) around it. It MUST be short because UI space is scarce. The LongName, usually linked to the scripting name, is the one supposed to identify the parameter uniquely in a device. A feature request it is, then.
    • Jun 16 2020 | 11:44 am
      But how about automation? If you have 2 "Gain" parameters on different panels each mapped to an LFO both will show the same target name "Gain" and it's not clear to which panel each LFO belongs. So you need different short names.
    • Sep 14 2020 | 8:31 pm
      Hi Broc, coming back to this, for recorded automation in tracks it is a wee bit better: - the lanes show the device name and the parameter's short name, - but the pop-up menu to choose the parameter shows the long name! - the Info View also shows the long name.
      So in addition to LOM access to the long name, Live should use the long names consistently everywhere a device parameter can be chosen, and display them if space permits.
    • Oct 19 2020 | 10:24 am
      @diemo schwarz @broc LOM features are determined by Ableton, so these requests are best submitted to Ableton support.