saving .axmd from within live – thispatcher seems to only work in max
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)
----------begin_max5_patcher---------- 605.3ocyV98aZCCDG+4j+JrbeMaJNgFBa6kU0WPZaR64IzjIw.WUhMxwgRWU +ee9GIPXPifz1s8.WjOae9q+3y93QeO7bwVVEF8AzOPddO564YcYb30z1CWR 2lUPqrCCyY2KleGNv0khsUYcqVAUqoprULYae75RQspforSLpwqyk5g0L2ph wA5enYMcuPvUbZosS7mk.s.cinHuMl1k.3K+ojkobAHZT56CCPShM1jQFKQ6 YWDgbarzh9co3NqRE7K6pPB0SYmhAdqfIMNqnaZk5UeyH1C1pH7GMlq9twx3 4NOnYl49juuwDbljsjUUQWxNBs2KAE6zPk7rP8kCTGJic.M4z.85KAnQCfIY hxRFWcDS9D5lZnHG8fnVh95zamhXKVn2AH8gxNVU.bVlnlq5l+cH.CGLkljr GRoWarQS5.oExkysKvNVzAaitn7vWQrcKaCjwPaXREjo2iEPInv8RlUPdNi2 MY6XV0ClBsoOiceHoGc6rWNM4eEmrYTJA5KvFFdHINnoJZAj0CXhs4OjXh4y X6iWjyNAZbWEmIJDxVZGGXLiLVsgzMfcYH4uDCWHEkuoTrIwxdKL8xfXx+QP 7YppVB4fFW3W42tbOvSHQlOiF2WIyn25qf8ryA9EV0CLO0O6EhkXGUB6iJjg REavrEl9i+zkUNF+GhpJc8sr1sWSEWzdIkypT.mp.AuyXROXL6e.uUc4PEcd AytcBO4Q14pFxYnlnApFGpnqWqqVU0DRqPz4O24tqlDXaBbWSadAVpqw0Nd2 .nR8IsReLWKcYCaSSv9l04I+eqjRN5K -----------end_max5_patcher-----------
I am also trying to figure this out,,, Anybody?
I never go this to work – maybe [thispatcher] in maxforlive doesn’t support the ‘write’ message
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!
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?
- This reply was modified 12 months by Lee.
@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.
----------begin_max5_patcher---------- 931.3ocyXt0aZCCE.9Y3WgUZejQsiCIgs8PWWeoR6p1dasZJjXJtJwFkXXsq p+2muj.gURfPgTDB6FGi8474yM2G61wZD+dRlE3sfeA5z4wtc5nGRMPm7m6X kDbeXbPldZVLxe3itypm4UyCRYAID8a3Yg7Yhh2HH2KzCOKZZFgEAh4gAwS3 YBfGDBKl1XNSjQ+qdEP18g4CylkPYwDgdOQ4CNMPDNgxt82ojPgQlwC7k+Ff MFq5PXO8Sv9PvM4+HZjQ3Fc2aP9k20Ex8GRoAwVK2XoRTryP0fO0sqpo2VBn DRVVvsjmwgrvT5TAHjyXRwGbJF.AFjAVPCyVKdXJwndVVKziJ.0zThjth.Ak ydNWP9PUWQyhEaE7ZWMdcvC0KimY0bglEsB750T7hNf30FfzLd2Q6VCIjAKN CL1f90BI2i.HY7gUXJlNmzWtexkCbdtyrjc6e6QWjlJ1nWj8H1yUuL5MDX6f qE0NsApWMd3BRKQq4S0nrWouMxVbywCGLn+.Y6PUakQCwMEONGRKw7IBNWME vonRli3CuObN270tv1dCq0tx90zE9Zqu9iOd1OIYhy9VPZPhDUWaAlp9SDKu u03ks1cz1t97BvWS+vIzLs7SRq2Sb8jA1XOPaGCYP5NWm5HSM0i.tfGGsd5T brjELuPCN4KJcXEcEX8NUyIeW0Jq+xLB3l8no3eRoBRSs0fM1VqfnZaMrAnt qGnC1IftKlag7jDYdtmwj2CtXFMNB7.eVJ3yWc4U.x3wp3axCkErJlJqQgOi IJq4UPowo2NRWJZisDG5tzBLOv1v0iMmcBav8H1tjLmFR.yIoBp7ZBx5RRnB q5IyDZTDgUFB6NqLAv7LcnZqfaXabIhp3j1hRvAeRV21ZwCZOX3fMEYg00p4 YpwpBKGuMX4.tRDDSCq.LkztPdLOs3r.qpND6nZkMH0VuuY33TdxAlh4FSZ2 O+5fn6QLDqHsZBMhV5x9uvbll.74U063Um2mcqEppFMmxpLqGUET+l8IVvFp TeIVu37d5UUmX5+9uAokK03qhpLY9svBkt35D.7BgKRVfJkouFX4IIO9.K0f kQvKPSDMKXTLIp5CsFIO1aRdbZW4AtI4wqckGzljG21Sdr2B932dhiywk33d bINdGWhCba7svsm7rEhS6EIbvA7rxj1HX5TYk6Y4KoVPj4RuyTKhaO8iTl4Q c9NqTY89Ey2LgfTY5OgL22rTS1q68cs5p1mm59O.RNrsiB -----------end_max5_patcher-----------
- This reply was modified 12 months by DRKOSS.
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?
@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…
what is the input from the artist?
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.
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…
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!
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?
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 https://cycling74.com/forums/topic/saving-thispatcher-generated-object-pattr/ for one variation on the theme.
Forums > Max For Live