authorizing Max 8?
hello,
editing a M4L device with Live 10 opens Max 8 with the little green ruban "trial not started - saving disabled". But when I try to authorize it and click on "buy now", it directs to "buy Max 7" since Max 8 is not available yet.
I am a little confused, is there a way to authorize the version of Max 8 that comes with Live 10 so I can save patches? or use Live 10 with Max 7?
thanks
Florent
Hello, Florent.
Are you starting Max 8 via the edit button and seeing the banner and unable to save?
That's not what happens on my system, so I'm wondering if you could let me know what platform/OS, etc. you've got - that would be of help.
The new version of Max for Live, which is included in Live 10 Suite, uses Max 8 for its framework, but it is not the standalone Max 8 application. The version of Max that comes bundled with Live is optimized for use with Max for Live, but it is not the full Max 8 application, and is not intended to be used outside of the context of Live 10.
thanks Max, I'm using macOS 10.12.6 and yes I'm clicking on the edit button to start Max
Thanks for the information. I'll look into the matter.
thanks!
looks like it's been fixed; I am now able to save the amxd files and I don't have the green banner anymore
thanks!
Hello,
I ran into the same problem. Any Updates on this issue?
Ditto, I am currently unable to edit Gen patches while in M4L.
I can of course open up standalone Max 7 and edit the gen patch, but obviously that's not ideal.
The version of Max that is bundled with Live 10 is not meant to be used as an application outside of the context of Live 10. One of the places where you will encounter problems involves doing things like editing gen~ patches. You are unable to edit those patches because there is no Max 8 authorization at this time (all authorization of the MFL editor is handled by Live).
Until such time as there is a separate Max 8 authorization, you’ll need to use Max 7 to edit gen~. As you point out, those edits will run perfectly well in the Live 10/Max 8 environment.
1. I think it is really important to solve the gen~ problem. As I understand it: Can only be solved if a new Live version and new Max version is released at the same time (current versions were not) and the Live user buys also the new Max full version immediately. Typical loose-loose situation. I am also using gen~ patches (inkl. editing not just running) in Live (Max 7/Live 9) and I expect that this problem will prevent also many other users from switching to higher versions of Live and Max.
2. I am still suspicious, if it was the right decision, to compile Max directly into Live. It was obviously developer driven (stability, performance) but has consequences for licensing, compatibility, ...On my system, stability of Live 9/Max 7 is ok as well as performance. And also developers will get problems with duplicate/redundant Live 10/Max 8 source codes: New features (Max 8.1, 8.2, ...) or bugfixes have to be synchronized or compatibility issues will occur otherwise. Seems to be like "I stopped smoking, but I prefer to drink more now".
haha
it seems to me that opening/editing/saving the devices from Max7 works much better anyways
baby Max8 is still an infant
I got an idea: Would it be possible to have both: 1. Existing Interface to Max as well as 2. the built-in version additionally? You already have the interface technology. Just keep it as an option for the Live 10.1 release. Then users can decide by themselves what to use. If a user needs performance or stability for a M4L patch: Use the built-in version, if a user has no stability/performance problems but has an older (or newer e.g. Live 10 + Max 9 if Max 9 will be released before Live 11) Max full-version or wants to edit gen~ patches inside Live: Use the existing interface version for a M4L device.
I expect that this can be done easily by the Cycling 74/Ableton developers because you already have the interface. And a well designed interface is always a benefit for keeping a good software design. There would be some migration work: How to transfer M4L-patches from Live 9 to Live 10.
I have the same problem. It's really weird, Ableton says it comes with Max version even if without some capabilities, but then you can't authorize it