OS X 10.4.6 breaking all distributed applications made with maxmsp?
It seams that also application made with maxmsp and distributed to users
(applications using objects affected by the change made in 10.4.6)
Developers can afford to download and reinstall a 130MB combo update,
but for end users, it is not acceptable for end users.
Are there some solutions studied at Cycling to modify impacted objects,
so that we can make a new version of our software?
In my case, the current situation makes demo version of one of my
software unusable on 10.4.6, but it’s not serious to ask people to
reinstall an OS update before running a demo.
Broken demo=>no people interested in the software
I think many developpers are in such a situation.
For now, installing the combo update is the best solution.
Quote: firstname.lastname@example.org wrote on Tue, 11 April 2006 09:16
> For now, installing the combo update is the best solution.
unless you also need to operate protools and
altiverb, those also dont run yet in .4.6
What exactly is broken? Is it confined to MSP, or are all Max runtimes affected?
It is specific to MSP objects which make use of the vecLib, which
includes fft-objects and sqrt~.
Running the Combo Installer will fix the problem.
My "Open Tuning" works fine after installing X.4.6 via "Software
No need to install the full combo.
I’ve always been a slow adoptor for just these reasons. Sure, there are
reasons for upgrading your OS, but it’s surprising how often it causes big
Powerbook G3/500 640/40 – Stilll great for audio!
Max/MSP, Live 4, DP4, & various hardware synths