Create clip - Possible?

    Jan 10 2010 | 12:43 pm
    is there a way to create a (MIDI) clip using M4L (I'm using Javascript)? The API documentation does not seem to list a direct method to do that.
    What I'd like to achive is to trigger, by MIDI, duplicating an existing clip to a new slot. I can indirectly achive that by arming the track, firing an empty clip slot, wait for the has_clip message and then use a new Task object to perform the copy operation.
    This seems like a pretty convoluted way to do this, and it has the downside that the copying operation is defered until after the clip has started recording. Thus, notes that are right at the beginning of the clip are not played in the first iteration of looping the copied clip. It also requires passing a lot of state around when all I really want is create a clip.
    Any help would be appreciated! Thanks! -Hans

    • Jan 10 2010 | 4:22 pm
      At the moment, clip creation isn't supported by the Live Object Model. It's not the first time it's been requested, but your interest is noted.
    • Mar 25 2010 | 3:21 pm
      Sorry for th noise, but this would be really great.. Also deleting clips would be awsome. Moreover is there a possibility to query if a clip is "empty"(edit: which would represent a workaround while creation and deleting is not available)? thanks
    • Mar 25 2010 | 10:20 pm
      Basicly you can't change the contents of clipslots using MFL. Perhaps there are some clever workarounds translating midi to qwerty keyboard macros.
      I haven't tried it out yet, but I guess one could create a Live Looper and send audio material to it using MFL automation. When loading audio output the track can be muted.
      Lately all kinds of Live menu action is sugested in this forum for automation by MFL. There is no first class solution for that builtin in MFL. Is it possible to enhance this behaviour by implementing a SDK Keyboard/Mouse macro device aka the Bome MIDI Translator? ( ) or Novation Automap Pro?
    • Aug 03 2015 | 4:10 am
      Is this still unsupported?
      and if so, why? seems odd that a feature request goes unresolved for 5 years.. function is still in the API reference doc.
    • Aug 03 2015 | 5:23 am
      OT: The OP looks like Kevin Spacey. Just had to point that out. Ok. Thanks for reading.
    • Aug 04 2015 | 12:09 pm
      Had to make this utility to get around the inability to work with unused clip slots. Can it be done?
      Can't get a path on any unused clip slots (id 0) So can't call functions on them to generate new clips using 'call fire' or 'call create_clip' Would love to have this confirmed/denied.
    • Aug 04 2015 | 12:40 pm
      For me the path of an unused (empty) clip slot gives a valid id.