Forums > MaxMSP

OSX Snow Leopard…

August 4, 2009 | 9:50 am

hello all,

this is primarily aimed at the cycling ’74 crew as this will apply to them.
i did put a post on some months ago, but only one other person answered with my same question, wondering about snow leopard and the compatibility between max 5 and snow leopard.

but with the up-coming release of snow leopard for os x, will max 5 be able to work in it?
will it be possible to get the upgrade of snow leopard without the worry that max 5 won’t work until an update is installed?

this does need to looked at, as snow leopard is round the corner. and more than likely most people will get it, when it is released in september. even i am on a mailing list to tell me when it is released, and will get a cheap upgrade for it as well.

i do hope at least someone with an answer can help, because this would become a serious matter if it doesn’t work…


August 4, 2009 | 8:17 pm

Snow Leopard is not yet available, members of the ADC have signed some NDA, so I wouldn’t count for an official answer. Unofficially, Snow Leopard could be considered as a minor upgrade (just look at the price of the upgrade), so there’s not much to worry about for the compatibility of the current Max version.


August 5, 2009 | 3:01 pm

I personally am quite concerned myself about the plans for Jitter (2.0?) and Quicktime X which is supposed to be a very different monster from the previous qts, and considering the history of what each major update has done (I’m currently smashing my head against the table with the qt7/spigot~ work around) there’s cause to be nervous. I have faith in the Cycling crew but it still gives me the cold sweats to think about what new challenges Apple may have in store.


August 5, 2009 | 5:45 pm

@cap
i do agree with this. even though people are saying it is just a simple update etc. what about the big updates to things like quicktime?
this would have to have some sort of bad implication to jitter in some way

i would really hate that if people do update, it wont be for another few months until a max update was available for snow leopard.

maybe i am thinking way too much into it, or maybe not enough. but the fact is, that this is still an update of operating system that could render most of your programs useless until a update for a program is created.

anyhow, enough about the future. let’s make some music now Smile


August 5, 2009 | 8:08 pm

the whole world still has headache from the
HI Toolbox implosion and some are already
wondering about quicktime X.

thats too early, guys!

Smile

-110


August 5, 2009 | 9:26 pm

Well, can’t let worrying about tomorrow prevent life in the now, but I don’t think I’m totally off base here.

It’s not like I’m asking the crew at cycling to pat me on the back and tell me it’ll all be okay, but I think it’s fair to say this is a concern for some people and that any news on the matter would be appreciated. I’m looking to purchase new computers in the fall and would hate to have this be a serious issue should Snow Leopard come pre-installed.



efe
August 6, 2009 | 4:31 am

What about openCL(the top priority of this update)?, does it have any perspectives of use inside msp?


August 24, 2009 | 5:22 pm

Bumping this thread again – now that we have a firm release date of Friday, can the devs give us some more insight on max 5 compatibility? I’d be happy with a "Yes, it runs fine, but we haven’t gotten around to taking advantage of OpenCL or Grand Central in any meaningful way yet"

Personally I don’t care if jitter works or not, but I’m sure a lot of people do, and that seems to be one of the more likely troublemaker candidates , due to quicktime X.

And, are there any benefits to using openCL in some way in max? I know it’s possible to do some weird magic with jit.gl.slab and use the graphics card to process some things that way. What about Grand Central? AFAIK, Max runs in only 2 threads, and poly~ instances spread themselves across processors relatively well without Grand Central.

So: Does Max 5 work at all with Snow Leopard? Are there any speed improvements for Max 5 by upgrading? Does it blend?


August 24, 2009 | 8:38 pm

music and computers… will it ever get change?



Nat
August 25, 2009 | 4:05 am

Been running Snow Leopard for a week with Max and so far I see no issues… Jitter and the Quicktime objects are working fine.
I wouldn’t worry.


August 27, 2009 | 12:43 am

Thanks a lot for sharing your experience. I was worried, too. Anyway, at least Jitter should do since QT7 is still part in 10.6 to allow downward capability. There are still too many Apps dependent on that version.


August 29, 2009 | 4:15 pm

Came across this in the compatibility list yet the forums don’t seem to be mentioning this. Any I blind or is this actually even a problem? Can anyone add or comment about this? Or am I just late to the party?

http://snowleopard.wikidot.com/


August 29, 2009 | 4:59 pm

It was me who added Max 5 to the list and I based my assertion on Nat’s post. Would be nice to hear a statement by cycling.

NOTE: AS FAR IS I GOT IT YOU HAVE THE OPTION TO INSTALL/LEAVE QUICKTIME 7 WITH SNOW LEOPARD. I GUESS THIS IS CRUCIAL FOR THE JITTER/QT OBJECTS IN MAX TO WORK.


August 30, 2009 | 11:22 am

what about "Snow-Soundflower" ?

http://d0cut0uch.no-ip.info/index.php/audio/tutorials/26-sf


August 30, 2009 | 12:35 pm

aye soundflower for SL would be good. i dont use it much at all now, but it helps to have it working good just incase. i more just use re-wire and other such things.

i ordered my copy on the launch date. so by next week should have it in my hands, and really get down and dirty.

i was even wondering about ableton live and max updates. whether they would be needed, or would it plainly just be an install and play your tits off.

i am surprised that none of the cycling crew have answered any questions on this matter, as they do read and filter on the forum.

would be nice to check out the capabilities of openCL and even quicktime x. lets hope they all work fine with max 5.

i am going to mail the support on this issue. because more than likely, people, like me, have ordered the new snow leopard. i am not so much worried if things dont work for a few weeks for a new update, i dont use max enough on a professional scale (more ableton suite 8 for that). but more so that what if an update does not come for ages, you know.

aye, new updates can be a pain Smile



Nat
August 30, 2009 | 4:41 pm

If you need soundflower,

You can install it via Airfoil http://rogueamoeba.com/airfoil/
It works great, I suspect there is an issue with the SounfFlower installer, not soundflower by itself.



Anonymous
August 31, 2009 | 1:18 am
lewis g. edwards wrote on Sun, 30 August 2009 06:35
aye soundflower for SL would be good. i dont use it much at all now, but it helps to have it working good just incase. i more just use re-wire and other such things.

i ordered my copy on the launch date. so by next week should have it in my hands, and really get down and dirty.

i was even wondering about ableton live and max updates. whether they would be needed, or would it plainly just be an install and play your tits off.

i am surprised that none of the cycling crew have answered any questions on this matter, as they do read and filter on the forum.

would be nice to check out the capabilities of openCL and even quicktime x. lets hope they all work fine with max 5.

i am going to mail the support on this issue. because more than likely, people, like me, have ordered the new snow leopard. i am not so much worried if things dont work for a few weeks for a new update, i dont use max enough on a professional scale (more ableton suite 8 for that). but more so that what if an update does not come for ages, you know.

aye, new updates can be a pain Smile

Abltone have released a statement on the forum here:

http://forum.ableton.com/viewtopic.php?f=1&t=122995

Abletons main statement "5. Does Ableton recommend upgrading to Mac OS X 10.6? If your main concern is stability, we don’t recommend upgrading to 10.6 until compatibility for Live and all of your third-party software and hardware products has been assured by the responsible companies."

Personally usually I jump at these upgrades but I’m going to leave this one a bit as my system with Ableton Live and Max/Msp is super stable at the moment and I have work to do


August 31, 2009 | 8:20 am

aye, i am the same when it comes to updates etc. i like getting new software and the like. expand my machine, make it cleaner blah blah blah

but this, oooh, is not good at all. i too use ableton suite 8 for work, and it is stable as is it right now. although i do need to clear vst/au plugins that are duff and drag my machine [same with max externals]. now up to too many plug ins to choose from. something like 200-250 now, very silly indeed. but freeware plug in hunting can become an addiction some days Smile

right, this has hit the nail in the coffin now. i wont update my system at all until a stable update for ableton and max has come out.
i ordered my snow leopard disk on the friday release. but when it arrives, i will just stuff it in my ‘to-do-when-the-time-is-right’ file Smile

thanks for that most useful of info tom. helps.

aye, updates, we want them, but we have to be careful, dang…


September 6, 2009 | 3:56 am

I have a patcher that’s crashing under OSX 10.6 when I load a soundfile into sfplay~. It looks to be some kind of thread completion routine.

Thread 27 Crashed:
0 libSystem.B.dylib 0x90b303c3 asl_close + 26
1 com.apple.SystemConfiguration 0x90c7b5e0 __SCThreadSpecificDataFinalize + 39
2 libSystem.B.dylib 0x90b01a27 _pthread_tsd_cleanup + 88
3 libSystem.B.dylib 0x90b0163a _pthread_exit + 154
4 libSystem.B.dylib 0x90af8e66 thread_start + 34


September 6, 2009 | 1:45 pm

Hi all,

I thought I’d give snow leopard a go… I can’t get Max to even startup…..

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.cycling74.MaxMSP 0x00298a81 juce::ATSFontHelper::getPathAndKerning(wchar_t, wchar_t, juce::Path*, float&, float*, float*, unsigned long*) + 311
1 com.cycling74.MaxMSP 0x002985a1 juce::Typeface::findAndAddSystemGlyph(wchar_t) + 585
2 com.cycling74.MaxMSP 0x002f2eb1 juce::Typeface::getGlyph(wchar_t) + 125
3 com.cycling74.MaxMSP 0x002ee205 juce::GlyphArrangement::addCurtailedLineOfText(juce::Font const&, juce::String const&, float, float, float, bool) + 227
4 com.cycling74.MaxMSP 0x002ee372 juce::GlyphArrangement::addLineOfText(juce::Font const&, juce::String const&, float, float) + 62
5 com.cycling74.MaxMSP 0x002ef552 juce::GlyphArrangement::addJustifiedText(juce::Font const&, juce::String const&, float, float, float, juce::Justification const&) + 70
6 com.cycling74.MaxMSP 0x001338ac jtextlayout_set + 618
7 com.cycling74.MaxMSP 0x00133b3b jfont_text_measure_wrapped + 141
8 com.cycling74.MaxMSP 0x001b9f7a textfield_getlayoutinfo(_textfield*, long, double*, double*, long*, double*, double*) + 488
9 com.cycling74.MaxMSP 0x000ad05b object_method + 901
10 com.cycling74.MaxMSP 0×00117021 jbox_reline(_jbox*, symbol*, long) + 175
11 com.cycling74.MaxMSP 0x001192c0 jbox_new + 3344
12 com.cycling74.MaxAPI 0x034ca6d2 jbox_new + 50
13 com.cycling74.message 0x177fdb6c jmessage_new + 98
14 com.cycling74.MaxMSP 0×00018983 typedmess_fun + 1973
15 com.cycling74.MaxMSP 0x000ad37f object_new_typed_flags + 435
16 com.cycling74.MaxMSP 0x000ad3f8 object_new_typed + 46
17 com.cycling74.MaxMSP 0x0015d908 jpatcher_newobject + 358
18 com.cycling74.MaxMSP 0x0015dd9e jpatcher_pastefromdictionary + 286
19 com.cycling74.MaxMSP 0x0016a22d jpatcher_fromdictionary + 1471
20 com.cycling74.MaxMSP 0x0016a491 jpatcher_new + 593
21 com.cycling74.MaxMSP 0×00018983 typedmess_fun + 1973
22 com.cycling74.MaxMSP 0x000ad3ba object_new_typed_flags + 494
23 com.cycling74.MaxMSP 0x000ad3f8 object_new_typed + 46
24 com.cycling74.MaxMSP 0x0000d879 jpatcher_load_fromdictionary(char*, short, object*, short, atom*) + 437
25 com.cycling74.MaxMSP 0x0000d9f8 jpatcher_load_frombuffer(char*, short, char const*, long, short, atom*) + 310
26 com.cycling74.MaxMSP 0x0000dc37 jpatcher_load(char*, short, short, atom*) + 373
27 com.cycling74.MaxMSP 0x0000debd lowload_type + 589
28 com.cycling74.MaxMSP 0x0000e829 primload_type + 105
29 com.cycling74.MaxMSP 0x0000e85f startupfile + 33
30 com.cycling74.MaxMSP 0x0002626c startup_load + 284
31 com.cycling74.MaxMSP 0x0000fd3a max_startup + 370
32 com.cycling74.MaxMSP 0x001c9889 MaxApplication::initialise(juce::String const&) + 23
33 com.cycling74.MaxMSP 0x002a30b3 juce::JUCEApplication::main(juce::String&, juce::JUCEApplication*) + 533
34 com.cycling74.MaxMSP 0x002a31d5 juce::JUCEApplication::main(int, char**, juce::JUCEApplication*) + 125
35 com.cycling74.MaxMSP 0x001c994a main + 76
36 com.cycling74.MaxMSP 0×00002592 _start + 216
37 com.cycling74.MaxMSP 0x000024b9 start + 41

I’m guessing it is in some way related to juce on my laptop
Does anyone have any clues, or shall I just revert back to 10.5.7 for a while?

Thanks,
Leigh


September 7, 2009 | 5:28 am

Perhaps it’s just me, but ‘AU DLS Synth 1′ doesn’t seem to work as a noteout device since updating.


September 7, 2009 | 6:51 am

Just to check, has everyone who is posting issues tried reinstalling Max after updating to Snow Leopard? Are other users able to confirm that these are consistent bugs?


September 7, 2009 | 7:41 am

hi,

what about max 4.6.x ?

does anyone tested it ? can somebody try and post a reply please ?

thanks

g


September 7, 2009 | 9:52 am

just this second got my snow leopard disk through the post.

but, like i said, i am going to wait until an update, or confirmation has been given to give the go ahead that max 5, and also ableton live will work on snow leopard with no flaws.

ooh, i want to try the new features…


September 7, 2009 | 1:38 pm

AU DLS Synth does not work!!!
Same for me also…


September 7, 2009 | 2:26 pm

The AU DLS Synth problem is a known issue and has been fixed for the next incremental. So far that’s pretty much the only one identified problem.


September 7, 2009 | 6:39 pm
cap10subtext wrote on Mon, 07 September 2009 07:51
Just to check, has everyone who is posting issues tried reinstalling Max after updating to Snow Leopard? Are other users able to confirm that these are consistent bugs?

Initially my crash was without a clean install.
I just reinstalled max 5.0.7 and the problem persists, though the the crashed thread is slightly different:

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0×0000000000000026
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.cycling74.MaxMSP 0x00298a81 juce::ATSFontHelper::getPathAndKerning(wchar_t, wchar_t, juce::Path*, float&, float*, float*, unsigned long*) + 311
1 com.cycling74.MaxMSP 0×00298449 juce::Typeface::findAndAddSystemGlyph(wchar_t) + 241
2 com.cycling74.MaxMSP 0x002f2eb1 juce::Typeface::getGlyph(wchar_t) + 125
3 com.cycling74.MaxMSP 0x002ee205 juce::GlyphArrangement::addCurtailedLineOfText(juce::Font const&, juce::String const&, float, float, float, bool) + 227
4 com.cycling74.MaxMSP 0x002ee372 juce::GlyphArrangement::addLineOfText(juce::Font const&, juce::String const&, float, float) + 62
5 com.cycling74.MaxMSP 0x002efa8c juce::GlyphArrangement::addFittedText(juce::Font const&, juce::String const&, float, float, float, float, juce::Justification const&, int, float) + 438
6 com.cycling74.MaxMSP 0x002e7bbe juce::Graphics::drawFittedText(juce::String const&, int, int, int, int, juce::Justification const&, int, float) const + 210
7 com.cycling74.MaxMSP 0x00187ef4 MaxLookAndFeel::drawTableHeaderColumn(juce::Graphics&, juce::String const&, int, int, int, bool, bool, int) + 578
8 com.cycling74.MaxMSP 0x0036223f juce::TableHeaderComponent::paint(juce::Graphics&) + 411
9 com.cycling74.MaxMSP 0x002bf1bc juce::Component::paintEntireComponent(juce::Graphics&) + 684
10 com.cycling74.MaxMSP 0x002bf355 juce::Component::paintEntireComponent(juce::Graphics&) + 1093
11 com.cycling74.MaxMSP 0x002bf355 juce::Component::paintEntireComponent(juce::Graphics&) + 1093
12 com.cycling74.MaxMSP 0x002bf355 juce::Component::paintEntireComponent(juce::Graphics&) + 1093
13 com.cycling74.MaxMSP 0x002bf355 juce::Component::paintEntireComponent(juce::Graphics&) + 1093
14 com.cycling74.MaxMSP 0x001a42a2 PatcherLayerComponent::paintEntireComponent(juce::Graphics&) + 80
15 com.cycling74.MaxMSP 0x002bf355 juce::Component::paintEntireComponent(juce::Graphics&) + 1093
16 com.cycling74.MaxMSP 0x002bf355 juce::Component::paintEntireComponent(juce::Graphics&) + 1093
17 com.cycling74.MaxMSP 0x002bf355 juce::Component::paintEntireComponent(juce::Graphics&) + 1093
18 com.cycling74.MaxMSP 0x002bf355 juce::Component::paintEntireComponent(juce::Graphics&) + 1093
19 com.cycling74.MaxMSP 0x002bf355 juce::Component::paintEntireComponent(juce::Graphics&) + 1093
20 com.cycling74.MaxMSP 0x002bf355 juce::Component::paintEntireComponent(juce::Graphics&) + 1093
21 com.cycling74.MaxMSP 0x002bf355 juce::Component::paintEntireComponent(juce::Graphics&) + 1093
22 com.cycling74.MaxMSP 0x003570bc juce::ComponentPeer::handlePaint(juce::LowLevelGraphicsContext&) + 48
23 com.cycling74.MaxMSP 0x002a1ed8 juce::HIViewComponentPeer::RepaintManager::paint(CGContext*, int, int, int, int) + 862
24 com.cycling74.MaxMSP 0x002a23dd juce::HIViewComponentPeer::hiViewDraw(OpaqueEventRef*) + 619
25 com.cycling74.MaxMSP 0x002a25d1 juce::HIViewComponentPeer::hiViewEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 425
26 com.apple.HIToolbox 0x940c4129 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1567
27 com.apple.HIToolbox 0x940c33f0 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 411
28 com.apple.HIToolbox 0x940c324f SendEventToEventTargetWithOptions + 58
29 com.apple.HIToolbox 0x940eb15d HIView::SendDraw(short, OpaqueGrafPtr*, __HIShape const*, CGContext*) + 475
30 com.apple.HIToolbox 0x940eaab1 HIView::RecursiveDrawComposited(__HIShape const*, unsigned long, HIView*, CGContext*, unsigned char, float) + 713
31 com.apple.HIToolbox 0x940ead24 HIView::RecursiveDrawComposited(__HIShape const*, unsigned long, HIView*, CGContext*, unsigned char, float) + 1340
32 com.apple.HIToolbox 0x940ead24 HIView::RecursiveDrawComposited(__HIShape const*, unsigned long, HIView*, CGContext*, unsigned char, float) + 1340
33 com.apple.HIToolbox 0x940e9ad7 HIView::DrawComposited(short, OpaqueGrafPtr*, __HIShape const*, unsigned long, HIView*, CGContext*) + 873
34 com.apple.HIToolbox 0x940e971d HIView::Draw(short, OpaqueGrafPtr*, unsigned long) + 83
35 com.apple.HIToolbox 0x940e966d HIView::Render(unsigned long, CGContext*) + 45
36 com.apple.HIToolbox 0x940e8faf WindowData::PrepareForVisibility() + 145
37 com.apple.HIToolbox 0x940e8589 _ShowHideWindows + 286
38 com.apple.HIToolbox 0x9414b07d ShowWindow + 79
39 com.cycling74.MaxMSP 0x002a0109 juce::HIViewComponentPeer::setVisible(bool) + 77
40 com.cycling74.MaxMSP 0x002be49d juce::Component::setVisible(bool) + 297
41 com.cycling74.MaxMSP 0×00181448 MaxTopLevelWindow::makeVisible() + 152
42 com.cycling74.MaxMSP 0x000ad05b object_method + 901
43 com.cycling74.MaxMSP 0x001ac86c patcherview_dovisible(_patcherview*, long) + 70
44 com.cycling74.MaxMSP 0x001ac9fd patcherview_makefrontmost(_patcherview*) + 25
45 com.cycling74.MaxMSP 0x001ad59e patcherview_patchernotify(_patcherview*, symbol*, short, atom*) + 270
46 com.cycling74.MaxMSP 0x000aa396 object_method_typedfun + 134
47 com.cycling74.MaxMSP 0x000aa44f object_method_typed + 127
48 com.cycling74.MaxMSP 0x0015fd5d jpatcher_call_object_method_typed(object*, _method_typed_data*) + 47
49 com.cycling74.MaxMSP 0x0005501e linklist_funall + 68
50 com.cycling74.MaxMSP 0x00160bf5 jpatcher_dopatchernotify + 63
51 com.cycling74.MaxMSP 0x0002d2f9 defer + 97
52 com.cycling74.MaxMSP 0x0015ff29 jpatcher_patchernotify + 83
53 com.cycling74.MaxMSP 0x0016002e jpatcher_vis_imp + 168
54 com.cycling74.MaxMSP 0x0016006f jpatcher_vis + 25
55 com.cycling74.MaxMSP 0x000ad05b object_method + 901
56 com.cycling74.MaxMSP 0x0014aac5 jmaxwindow_show + 149
57 com.cycling74.MaxMSP 0x0000fd13 max_startup + 331
58 com.cycling74.MaxMSP 0x001c9889 MaxApplication::initialise(juce::String const&) + 23
59 com.cycling74.MaxMSP 0x002a30b3 juce::JUCEApplication::main(juce::String&, juce::JUCEApplication*) + 533
60 com.cycling74.MaxMSP 0x002a31d5 juce::JUCEApplication::main(int, char**, juce::JUCEApplication*) + 125
61 com.cycling74.MaxMSP 0x001c994a main + 76
62 com.cycling74.MaxMSP 0×00002592 _start + 216
63 com.cycling74.MaxMSP 0x000024b9 start + 41

Regards
Leigh


September 7, 2009 | 7:24 pm

Just to recant…

I’m not able to reproduce the crash cited above. sfplay~ appears to work normally, now.

regards,
Chris



efe
September 10, 2009 | 12:29 pm

I have been running 10.6 for one week now and Max seems to work without any problem. The only issue that i am experiencing is that sometimes, when i want to load the program, the application wouldn’t launch. Even if i try several times, i need to restart the system. I am not quite sure why this behavior is happening.
A second situation that I found is that some externals(in particular pitch~) would’t load either. I needed to use the program maintenance to restore my permission. I don’t understand why this is happening. Maybe it is just my computer…
Emmanuel


September 16, 2009 | 8:26 pm

Anybody having experience with 4.6 in Snow Leopard? I am really dependant on 4.6 to work flawless!


September 17, 2009 | 3:07 am

Uninstalled max 5 completely. Reinstalled with no problems. Haven’t had any issues yet.



waj
September 17, 2009 | 12:58 pm

quote:
what about max 4.6.x ?

just a quick test with Extras>Audiotester:
works.

quote:
Perhaps it’s just me, but ‘AU DLS Synth 1′ doesn’t seem to work as a noteout device since updating.

works also fine.

Max 4.6.3
Os 10.6.1


September 17, 2009 | 1:13 pm

Max 5.0.8 fixes the AU DLS Synth issue under Snow Leopard.


September 28, 2009 | 10:26 am

I detected really weird bug…

Conditions:

1. OS X Snow leopard 10.6.1, MacBook Pro 3.1, Core2duo 2.4, GeForce 8600M GT 256mb.
2. Max5 build 40079
3. Patch with jit.gl.render and jit.gl.slab, I used for test patch from "Jitter Movie Optimization Methods", http://abstrakt.vade.info/?p=147, exactly "5 – GPU UYVY" in folder "Multichannel Playback". My modification is only "fullscreen 1" message for jit.window.
4. No movies loaded, only thing I did – turned on "metro".
4. When patcher window is nearby left window border, it’s OK, fps is about 33, when moving it about 40 pixels to right, fps is dropping down to 1-5.

There is screenshots with details in attachment.


September 28, 2009 | 10:46 am

Another funny thing, is a fact, that render FPS is limited to 33.3333, and it’s not depending on metro speed or CPU usage.


October 8, 2009 | 8:22 am

Up. And reaction?


October 23, 2009 | 12:54 pm

I have the same problem when using a second display.
If I sent a fullscreen message to jit.window my framerate drops from 30 to 2 !
My screen size on the Macbook Pro is 1440 x 900 and I found out that I could make a workaround by sending pos 1441 0 and size 1680 1050 to jit.window without any drop in framerate.
But it would be nice if the fullscreen message worked normally again. Maybe its the snow covered leopard freezing ?


November 9, 2009 | 8:07 am

Hey, somebody working on this problem or I must downgrade to 10.5 ?


November 13, 2009 | 3:05 pm

max 5 crashes for me on startup; even after fresh installation. 5.0.8 & 5.1b..
4.6 seems to work though Wink
also the runtimes don’t crash.

jan

10.6.2


Viewing 39 posts - 1 through 39 (of 39 total)