Ableton Forum

When I distribute to other users of live, they are saying it is not finding the subpatch for a puly~ object. It works on my machine. What are we meant to do that we did wrong?

You have to freeze your device: https://cycling74.com/docs/max5/vignett ... ezing.html

All is explained. I didnt press that thing. thank you very much.

But now I have an associated question. If I build a Live! instrument for the 64bit version of Live! on a Mac, does it work on 32-bit Mac Live! installations? Or do I need to build two versions?

Also, if someone has both Max 6 and Max7 installed, is there a way of telling it to use either Max 6 or Max 7--or can only one version of Max be activated in Live! at a time?

I already answered you over at The Max forum but I'll leave it here too.

It should work unless there is an external used that is only written for one or the other.

You can only have one version of Max chosen as the editor at a time. It can be changed under the File/Folder preferences in Live.

Thank you stringtapper, you saved me repeating your words. I take it the same is not true for Windows, that is, on Mac, if we build for 64 bit live, it includes the 32bit version; but on Windows we need to make one version with 32-bit max selected, and one version with 64-bit max selected. And I think I can stay with Max 6 distributions for now, so it is only 3 variants to build for Live support.

That sounds right. Two versions for Windows.

ernest, it sounds like you are talking about compiling custom externals written in C.

but i suspect you are not.

if you really are just talking about M4L devices (.amxd), then certainly not - you just make one patch on one platform and it will work flawlessly on windows, osx, 32 & 64. .amxd is just a special type of max patch (actually a version of .maxproj), nothing clever or 'compiled' there.

the only issue is if you use third party externals.

if properly managed, .amxd handles all your dependencies and crossplatform/architecture externals, if required, for you. you are building a max patch (project), not a compiled application. M4L is a runtime of max.

as for max6 / max7, the issues are only visual / ui because of changes cycling have made, not under the hood (unless you use max7-specific features). theoretically devices will 'just work' if made in max6 and opened against max7, although you may have to do some tweaking. but you can forget about max7 for the time being - it is not even officially supported by ableton.

all this is pretty basic stuff and is covered in the documentation. go through all the tutorials for info on managing your file dependencies, freezing, what m4l is, etc.

hth.


by the way, i have no idea where you got this "!" at the end of the word 'Live' from. it is your own strange invention.