Changes to concurrency model in Max 7?
Nov 16 2014 | 4:32 pm
I've been a Max user since version 1.0, back when I had a steam-powered Mac-Minus, and this is one of the most wow releases ever. Congratulations!
I asked this question on the non-dev list last night and was directed here, though I have a little more information.
First, the Max 6 dev kit works perfectly with Max 7 - for my project. Indeed, I moved to using the git submodule version (as opposed to requiring people to separately download the Max 6 SDK) and it worked perfectly first time.
But I have a report from a very reliable user that my external crashes in a few minutes on Max 7 (but worked on Max 6). Well, in interesting news I can't reproduce this at all - my external stayed up for hours and didn't run into any anomalies.
I understand this is nothing for the reader to go on and I'm not desperate and I still have a lot of arrows left in my quiver, but I am curious - was there are a major change to the concurrency model? Is there perhaps a little better documentation about "the best way to do it"?
(If you are interested, you can see what I'm doing here - I get a real time update, prepare a list of atoms, call critical_enter(0);, emit the list of atoms, and call critical_exit(0);.)