huiwang

With Max 6, I was able to edit an AMXD (launched from within Live) and go about editing it and then just save the AMXD patch itself. Once I'm ready then I'd go and freeze it to package in all the dependants.

However, I noticed with Max 7 and editing an AMXD directly, as soon as I save, Max 7 will automatically perform a freeze. Is there an option to disable this?

max-7-how-do-i-save-an-amxd-and-not-have-it-automatically-freeze

I've just confirmed with c74 support and this behaviour is "by design" when you have open it in Max. If you want the freeze/unfreeze option, you need to open it in Live.

I've ask them to cast my vote if the "freeze/unfreeze" button would be back in a natively opened amxd device in Max.

To me, when you are developing, you want the latest and greatest in the maxpath, not an old 'unaccountable' version of when you saved the device.

I've ask them to cast my vote if the "freeze/unfreeze" button would be back in a natively opened amxd device in Max. 

To me, when you are developing, you want the latest and greatest in the maxpath, not an old 'unaccountable' version of when you saved the device.


yeah i totally agree, even though the AMXD project automatically unfreezes when being editted, i still would prefer, as you said, to grab the latest and greatest in the maxpath

I wonder what was the reason behind this decision. Probably a M4L device and it's dependencies created/edited with Max aren't necessarily within the search path when opening with Live? Automatic freezing would ensure that they always work in Live...

I wonder what was the reason behind this decision. Probably a M4L device and it's dependencies created/edited with Max  aren't necessarily within the search path when opening with Live? Automatic freezing would ensure that they always work in Live...

I don't mind the default behaviour of freezing the AMXD when edited with Max, but it would be nice to have an option to override that behaviour.

Jan is right on that one (c74 told me the same thing), this behavior is 'by default' so it is easier to use it in Live afterwards.

But as a developer, I want to use it in Max (probably a thousand times) and then in the final stage, I want a freezed device for Live.

What's wrong with opening it from inside Live. There it doesn't freeze automatically. Nothing against an option to choose, but editing a M4L directly from Max is to my experience a rare case as all the live stuff (.e. LiveAPI) isn't available anyhow...

Often (especially when JS is involved) a maxforlive patch will crash when trying to open it in Max from live. If you then open it in Max to make the changes you want, it freezes and makes external js files internal - very frustrating.

Often (especially when JS is involved) a maxforlive patch will crash when trying to open it in Max from live.  If you then open it in Max to make the changes you want, it freezes and makes external js files internal - very frustrating.


[Max 7] how do I save an AMXD and not have it automatically freeze?