Lions, & lions & lions -oh my!
So tomorrow is the day. Any word from the devs as to whether max plays ok with Lion?
yes … i’d upgrade to lion if I was told there are no issues with max
I’ve been running Lion for about a week now, and have found no problems w/ Max, fwiw.
I have just finished installing Lion on a Mac mini here and playing with Max and MFL.
Here are some first impressions.
Everything seems pretty much fine. MFL is working correctly so far, but please note that Ableton are currently recommending people NOT update.
Our CP is working , including iLok.If you encounter any problems with your authorisation, please do not hesitate to get in touch with support.
Lion does not include Java by default. If you see a message asking you if you want to install the Java runtime, please do.
PLEASE NOTE: this is an entirely preliminary basic walk through., and is not meant at all to be the definitive answer to MaxMSP’s Lion compatibility. Over the next few weeks we shall be doing extremely thorough testing of all of MaxMSP’s feature set in Lion, and if there are any issues, these will be addressed in the forthcoming Max 5.1.9 incremental update.
I updated my post with new info. iLok is working fine for me.
What’s the jitter performance like? I noticed a serious performance hit in Snow Leopard from Leopard (a noticeable few frames of latency in live video) so I’d be thrilled if Lion was at least back to the Leopard speed.
So I noticed a problem today after updating to Lion. Regardless of what input I use (internal mic, Apogee Jam) I get meter-peaking noise. It changes pitch as I change the vector size. I’m also including a link to a movie. Note that you are NOT hearing feedback. This is the audio that comes out of the patch due to corrupt audio input as far as I can tell. Can’t seem to shake this no matter what I try (restarts, reconfiguration, etc.)
----------begin_max5_patcher---------- 274.3ocqR10aCBBEF9Z3WAgqcMHncy8WYoYgBrVVPvHXR2Z59suBpq01YR2G 2.d9Humm2irGBvqc6TdL5QzSH.XOD.RohI.Cw.bMemvv8o1v0pfp8CbVeIaW s1ZTgTs7gjM7fXq1t44VkHzqMikufjgxKKiWOPRArEDzpSB45BWpjVlloa8q 2ULNx91Bu0n5kF+hwwONlUwxGfv3Q1MZF06Rt36MCcdyPqVF4mRphWEkimyX Fx0lgg+Uvxkhe7lmVk3a482DqzqYkN6h2q2X4Fb1WeM4ePZBXi1d46qDjw7S 8p200JFkdXvnSbJU9f1xCZm8rdXS5YqVJU1y240ZYiSaCCHLyij+ShJ9CDcL 3.7STMfze. -----------end_max5_patcher-----------
I don’t have problems with audio here. Try deleting your preferences?
Thanks Andrew – Tried deleting ~/Library/Preferences/com.cycling74.* but that didn’t solve it. Other apps work so I don’t think it’s a global audio setting but I could be wrong. Is there an official un-install script so I can do a fresh re-install or is it just the Max folder? Thanks for any other advice.
EDIT: PRAM reset didn’t help.
Your prefs folder is here:
~/Library/Preferences/Max5 Preferences Folder
trash the whole thing. Then download and install the latest version of Max– it will replace your current install.
If that doesn’t help, send in a note to support at cycling74 dot com
Thanks Dave – no go there as well…also deleted /Library/Preferences/Audio to no avail.
As I mentioned – other apps work – Live, Wave Editor, etc. when it comes to audio input.
Each time (in Max) when I change the input in DSP settings I get noise of a different pitch – classic random data writing to an audio buffer type stuff – just as in the movie posted above. any other thoughts? Will keep trying various things…
EDIT: Creating a new user and launching Max from there causes the same issue. Very strange.
EDIT: Fresh install also does not fix the problem.
I have an issue with suckah object it give me always 0. 0. 0. 1. with max 5.1.5
Yeah I can reproduce the problem with suckah on Lion.
We’ll get on it.
Well this is a bummer – even re-installing Lion still causes it to occur. I’m not sure what to try next. I emailed support. Hopefully Andrew is not support since he’s already here. :-)
Is anyone else having this problem? Thanks!
What hardware are you on, as in, what type of Mac is it?
MBP. 2.2 GHz Intel Core i7. 4GB 1333 MHz DDR3. Note that this worked yesterday before Lion – I use this functionality practically daily. Definitely something in the install messed things up. I just also reinstalled Soundflower, Xcode, Lion and MaxMSP itself. I’m sifting through the console.app and found this – not sure if it is significant or if it happens under non-Lion.
Jul 21 21:01:50 i7mbp [0x0-0x6f06f].com.cycling74.MaxMSP: cmd line -psn_0_454767
Jul 21 21:01:50 i7mbp MaxMSP: CFURLCreateWithString was passed this invalid URL string: '/System/Library/Frameworks/CoreServices.framework' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateWithFileSystemPath or CFURLCreateWithFileSystemPathRelativeToBase should be used instead.
Jul 21 21:01:54 i7mbp [0x0-0x6f06f].com.cycling74.MaxMSP: MaxMSP(1493,0xad1532c0) malloc: *** error for object 0x999a000: pointer being freed was not allocated
Jul 21 21:01:54 i7mbp [0x0-0x6f06f].com.cycling74.MaxMSP: *** set a breakpoint in malloc_error_break to debug
Jul 21 21:01:54 i7mbp [0x0-0x6f06f].com.cycling74.MaxMSP: sqlite version 188.8.131.52
Jul 21 21:01:55 i7mbp MIDIServer: MIDIServer  starting; arch=x86_64
Jul 21 21:01:58 i7mbp MaxMSP: CFURLCreateWithString was passed this invalid URL string: '/System/Library/CoreServices/CommonCocoaPanels.bundle' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateWithFileSystemPath or CFURLCreateWithFileSystemPathRelativeToBase should be used instead.
Jul 21 21:01:58 i7mbp [0x0-0x6f06f].com.cycling74.MaxMSP: Max: starting db update
Jul 21 21:01:58 i7mbp [0x0-0x6f06f].com.cycling74.MaxMSP: Max: unable to open [-psn_0_454767]
Jul 21 21:02:05 i7mbp [0x0-0x6f06f].com.cycling74.MaxMSP: Max: db update complete
Another note – Process coreaudiod by user _coreaudiod is running @ 0% CPU with 3 threads. When I enable audio in MaxMSP and what is in my video starts to occur coreaudiod jumps up to ~9%-11% CPU with 5-9 threads. This is just with adc~ going into meter~ and nothing more. Removing meter~ makes little difference in these numbers.
----------begin_max5_patcher---------- 276.3ociQkrSCCCD8r8WgkOGpRbPkB236.EgbicaGThcT7DQfpx2N0SVJAQA t3k2Lyaw9HmI256sAo3AwSBF6HmwHnH.a7NSVq6KqzApMYsEsseHSFJ45p8c XkEohYinMZr7.31+bqsDGHWc6lUoIhr02G21jRWxWkJJFmALD89subiZh8Ap w2ZrCjH2U40mIr3h5faV7H1INOtj7OCiy95YAmjCs8jakZS4URn5WRX9ZJTY zV9cwUU5OmvrI124cnSWS4S9XKnqtZ1CvdWr77oYhijDf2oFyTm08OdcnAkU f66+7Tph3KexB9t1xIaLZewkbYrADbZD7tuziZQOG.iwRkmbWMXZ7fCGsfnX gA4m3exKKr4u -----------end_max5_patcher-----------
One more thing – not sure if an issue – coreaudiod is Intel 64 bit but Max is simply listed as Intel (not 64 bit) – was coreaudiod 64 bit before Lion? Does that even matter?
Ok Mr Earsmack.
We’ll continue this conversation in support. Thanks for the information.
We can reproduce this issue and are now working on it in engineering.
Thanks Andrew – I look fwd to hearing from them.
i have the same problem!
(Mac Book Pro 2 Ghz Intel Core i7 4 GB 1333 MHz DDR3)
Hello everyone some information about OS X Lion+MAX 5+OpenNI+OSCeleton.
I work on a Mac Mini Core 2 Duo 2.4Ghz 8GB and OS X Lion.
The latest CMake update works perfectly with OS X Lion.
The latest MacPorts update works perfectly with OS X Lion.
The latest OpenNI update works perfectly with OS X Lion.
OpenNI Unstable Build for MacOSX 10.6 Universal x86/x64 (32/64-bit) v184.108.40.206
PrimeSense NITE Unstable Build for MacOSX 10.6 Universal x86/x64 (32/64-bit) v220.127.116.11
Another information for option outputs !THE JOINT ROTATION DATA! you will find here :
OSCeleton uses 26% CPU on my MAC Mini.
update avin2-SensorKinect-2d13967 OK!
I hope this information will help you
I have the same problem. Macbook Air – OSX Lion. Does anyone know how to fix it?
SOLVED: Upgrade to 5.1.9
Forums > MaxMSP