dhjdhjdhj

I haven't had to deal with this since Max 5 --- there used to be a runtime system that could be delivered along with some patchers for people without Max to use.

I believe that with Max8, people are supposed to just download the main program. But if they do that, are they now going to see all the warnings about trial mode, patcher won't be saved and all that stuff that's basically irrelevant if they're just trying to use some patchers that have been distributed?

I haven't had to deal with this since Max 5 --- there used to be a runtime system that could be delivered along with some patchers for people without Max to use.
I believe that with Max8, people are supposed to just download the main program. But if they do that, are they now going to see all the warnings about trial mode, patcher won't be saved and all that stuff that's basically irrelevant if they're just trying to use some patchers that have been distributed?


I haven't had to deal with this since Max 5 --- there used to be a runtime system that could be delivered along with some patchers for peopl

distributing-max-patchers

Maybe You could trimm down own "runtime".

It is just a matter of testing if max with replaced binary 

and removed unneeded stuff and repacked into dmg

In the resources folder are 2 runtime binaries (compressed into runtime.zip), 

one to use with CEF, the other if CEF is not needed.

If one replaces max with renamed runtime binary it runs just like standalone.

In fact that is how I build standalones on Mac,

just drag stuff I need into new .app bundle, and edit rsrc file for own prefs dir.

But I don't use any gatekeeper enabled system, so can't tell if it would

still remain signed and whatever to pass gatekeeper.

Maybe You could trimm down own "runtime".
It is just a matter of testing if max with replaced binary 
and removed unneeded stuff  and repacked into dmg
would survive the gatekeeper.
In the resources folder are 2 runtime binaries (compressed into runtime.zip), 
one to use with CEF, the other if CEF is not needed.
If one replaces max with renamed runtime binary it runs just like standalone.
In fact that is how I build standalones on Mac,
just drag stuff I need into new .app bundle, and edit rsrc file for own prefs dir.

But I don't use any gatekeeper enabled system, so can't tell if it would
still remain signed and whatever to pass gatekeeper.


When you share a patch, the user now needs to install Max on PC or Mac. They can't save modifications to your patch, but that was the case when the runtime was separate, of course.

But they can do more than what was possible with Runtime: they can access Audio Status or some test example patches from the Max menu, for instance. 

More importantly, you can edit a patch to make a quick personalization, which might be useful even if you can't save. That was not possible with the Runtime.

When you share a patch, the user now needs to install Max on PC or Mac. They can't save modifications to your patch, but that was the case when the runtime was separate, of course.
But they can do more than what was possible with Runtime: they can access Audio Status or some test example patches from the Max menu, for instance. 
More importantly, you can edit a patch to make a quick personalization, which might be useful even if you can't save. That was not possible with the Runtime.

i forgot the exact routine, but we recently discussed that you can turn the "demo" into a "runtime" by setting something via patcher inspector, isnt it?

In fact nobody prevents users to start demo period,

and enjoy max for 30 days and eventually buy it at the end.

Maybe that is one argument against providing "runtime"

versions from cycling, beside the fact that now max has so

many more functions inside than in that golden days

when only few externals needed to be bundled into "runtime" version.

I think that most of the forum topics with similar questions

are arrising only because of apple security politics.

I can't remember anybody asking about that ...

In fact nobody prevents users to start demo period,
and enjoy max for 30 days and eventually buy it at the end.
Maybe that is one argument against providing "runtime"
versions from cycling, beside the fact that now max has so
many more functions inside than in that golden days
when only few externals needed to be bundled into "runtime" version.
------
I think that most of the forum topics with similar questions
are arrising only because of apple security politics.
Nobody is missing windows runtime ?
I can't remember anybody asking about that ...


> In fact nobody prevents users to start demo period, and enjoy max for 30 days and eventually buy it at the end.

Yeah, but I'm not in the business of promoting Max! I want to give my users some Patchers and I'd like them to be able to just use them without their being prompted to "try" or "buy" Max.

I had hoped not to have to be distracted dealing with Apple security stuff for Max standalones -- I have do all that crap with our own product already!

> i forgot the exact routine, but we recently discussed that you can turn the "demo" into a "runtime" by setting something via patcher inspector, isnt it?

If you can point me at a reference to this, that would be awesome

> i forgot the exact routine, but we recently discussed that you can turn  the "demo" into a "runtime" by setting something via patcher inspector,  isnt it?

I am afraid such thing does not exist, at least I never heard of it.

And no one would be prompted to buy max untill they try to edit and save the

You can also share mxf files, they can't be edited and so no nags about trial.

on top of build script, than built mxf file

wil have nothing included, just the patch and few

Screen shot 2015-12-12 at 17.13.41.png

I am afraid such thing does not exist, at least I never heard of it.
And no one would be prompted to buy max untill they try to edit and save the
patch.
You can also share mxf files, they can't be edited and so no nags about trial.
if you insert line :
excludeexternals true
on top of build script, than built mxf file
wil have nothing included, just the patch and few
header / primitive checksum lines.


not sure about max 8, but in max 7 you only see the "demo" badge when you unlock the window.

this is not the case in fullscreen mode as well as in nofloat or notitle, and of course you cant even go to edit mode in collectives. there are so many options...


not sure about max 8, but in max 7 you only see the "demo" badge when you unlock the window.

this is not the case in fullscreen mode as well as in nofloat or notitle, and of course you cant even go to edit mode in collectives. there are so many options...



Distributing Max patchers