saving .axmd from within live - thispatcher seems to only work in max

    Apr 18 2014 | 10:05 pm
    here's a simple example - when editing in max - clicking write saves the patch just fine. When you close and the patch goes back into Live, clicking write has no effect. Is the normal and is there another way to save the axmd file automatically from the patch itself (without having to manually save the patch by clicking on the disk icon)

    • Jun 11 2014 | 8:04 pm
      I am also trying to figure this out,,, Anybody?
    • Jun 23 2014 | 9:05 pm
      I never go this to work - maybe [thispatcher] in maxforlive doesn't support the 'write' message
    • Jul 29 2014 | 11:31 am
      little bump on this - maybe the cycling74 chaps can chime in. This example will save when editing in Max but not when Ableton - any ideas? thanks!
    • Sep 02 2014 | 7:08 pm
      Still bumping up against this - it would be very handy to be able to save the axmd file from within ableton... - any ideas on this one?
    • Sep 02 2014 | 7:34 pm
      what are you trying to achieve with this?
      Off the top of my head though, I can't see how this could work... the code for creating amxd files is part of Max - when you're running a device inside Live, that portion of the Max system isn't loaded, only when you start up the editor...
      not sure why you would want to rewrite your amxd file though anyway?
    • Sep 02 2014 | 8:04 pm
      @Lee - thanks for the reply. The patch learns OSC commands on the fly creates new [live.numbox] objects so you can automate them. However, to save this to the patch, you have to open the patch in max - the "write" message to [thispatcher] doesn't work while in ableton, possibly the reasons you suspect! Just wondering if there was a workaround.
    • Sep 02 2014 | 9:44 pm
      if you're just wanting to save settings then you should look into the pattr system which allows you to save and restore data - you can save this data either with an instance of your m4l device, or separately, e.g. in a file. you can then reload the data at device startup to recreate your state...
      or am i missing something?
    • Sep 02 2014 | 10:05 pm
      @lee - thanks for lending some headpspace to this. The issue is that these parameters are generated dynamically while in Live. So the pattr system wouldn't really help. The way the patch works now - the artist can add on the fly any osc command they want and instantly be able to automate that in a clip (along with many other parameters previously added). Not sure how the pattr system could help with that - but i could be missing something...
    • Sep 03 2014 | 8:16 am
      what is the input from the artist?
    • Sep 03 2014 | 11:35 am
      the artist inputs very little - the patch reads commands mirrored by the OSC app. When the artist finds one they want to automate, they push the button and the command attached to a live.numbox is created like in the example patch above. Then they can simply automate the new parameter in a clip.
    • Sep 03 2014 | 12:36 pm
      ok, so if I click on the '"OSC/Test/Param $1" param1n param1' msg, it creates a new object as you say. so, if this was stored using pattr and reread at startup, you would just issue the same command and therefore recreate the object...
    • Sep 03 2014 | 3:04 pm
      that would be good idea indeed. But alas, it doesn't work. I think the problem is ableton only sees parameters available for automation when the device is initialized. Since these objects are created afterwards - they don't appear as automatable parameters. If you run the patch as you suggested, then open in max, then save and go back to ableton, it works because they now exist upon initialization. But that is really back to square one. thanks for the idea though!
    • Sep 03 2014 | 3:14 pm
      hmmm, see what you mean... in that case you could create a number of controls at startup and hide them all, unhiding them one by one as they are assigned?
    • Nov 24 2014 | 11:31 am
      As @Lee correctly noted, you can't save your device from within the Max for Live runtime environment, only from the editor. If you want to save changes made to your device via scripting as part of a device preset, this is possible with a little work. See for one variation on the theme.
      Best, Jeremy