Sharing objects OK?
I just finished downloading 5, and am about to install it.
Which got me wondering. I read that many or most 3rd party externals should work with 5, but does that mean I can just set the Max paths to the same exact paths in my 4 install as my 5 install? Sharing the library.
Any danger in doing this?
I realize I’ll have to copy or move any I installed into the cycling externals directory in 4’s install…but should be ok, no?
Sounds like a good idea. Plus a nice way to get a fresh clean slate to start from.
Don K schrieb:
> but does that mean I can just set the Max paths to the same exact
> paths in my 4 install as my 5 install? Sharing the library.
> Any danger in doing this?
You could, but I wouldn’t. As the new format requires another extension
What I do now, is copying all my St.ools into a seperate folder in the
Max 5 search path. That allows me to keep the Max 4.6.3 install
completely intact and independent. I’d erase all old versions as soon I
made a Max 5 version of one of my abhaXions… I leave all which I don’t
touch in Max 4 format. That way I get an idea what might be obsolete in
the meantime. (There are some patches I keep for compatibilities sake,
but I would never use them in new abhaXions…)
I would keep the old version alive till a new Max 5 compatible pluggo
will arrive. Also some patches do use 3rd party UI elements which have
to be rewritten, which will take some time…
But now I head of to learn all the new stuff, I’ll keep you posted about
new St.ools (version 5?)
One of the biggest enhancements seems to be transparency, I can create
customised UI elements which simply had not been possible before.
Someone might even have written something in the Max documentation you’re all no doubt searching with every question you may have. In this case, have a look for "old and new versions" and see what happens.
Forums > MaxMSP