While the new Apple MacBook Pro Machines are really fast desktop-like speed packed monsters, it seems like they also have severe hardware design faults as outlined by zdnet and ifixit. With a geekbench score over 10.000 the new MacBook Pro (early 2011) beats the Mac Pro (Early 2009) Intel Xeon W5590 3.33 GHz (4 cores). All the good talk and benchmarks cannot make up for the current problems Apple users are facing with their brand new machines:

• too much thermal paste seems to raise the CPU temperature
• fans running at 6000rpm+ constantly
• frequent kernel panics or freezes that are maybe related to the new GPU
• heating issues with the whole MBP early 2011 series

Come on Apple, wake up and fix those machine fast, as lots of us could benefit from a stable quad-core laptop solution (talking audio plugs and realtime audio performance).

We can recommend to tell apple to send the replacements before they pick up the faulty machines, so it is easier to transfer the data already on it. (apple care even suggested it this way)

[UPDATE] Gregg Keizer from Computerworld also writes about quality concerns regarding the new Apple Notebooks and there is also a discussion about actual "Overheating" going on in the Apple Forums. Well, I can confirm the issue exists and the current MacBook Pro Models freeze a lot. If it is a hardware, software or firmware issue remains unclear.

[UPDATE] There is a macrumors forum thread discussing that there were issues with the 2010 MBPs as well when they came out. Another thread at macrumors forum tries to sort out if it is a hardware or software issue.
Some people suspect it is related to internal graphics switching, but there really seems to be something going on since also reports on the apple discussion forums are increasing.

[UPDATE] as of 2011/03/14 macrumors suggest in their forum to "go 2010 or wait for ivy bridge". The early 2011 version of the MacBook Pro das 45W TDP vs. last generation's 35w. That's a big increase which automatically makes the whole series go louder and more hot than the 2010 model.

[UPDATE] 2011/03/21: Macrumors posted a story: "2011 MacBook Pros Crashing Under Load?"

[UPDATE] 2011/03/21: Mac OSX 10.6.7 Update was just announced by Apple. Unfortunately, on the two machines we have here, the update does not fix anything related to CPU temperature. Still there are frequent freezes as well.

[UPDATE] 2011/03/22: dailytech confirms that New MacBook Pros Freezing When Stressed, Update Adds More Problems

[UPDATE] 2011/03/28: we received our two replacement MacBook Pros. They don't seem to have any issues and also still did not freeze on us! Also the fans are not spinning like crazy anymore! For all people affected by any of the issues reported above: get your Notebooks replaced! Apple is aware of the issues and replaces faulty hardware (we had to wait for two weeks though).

[UPDATE] 2011/04/23: the current Systems freeze 2-3 times a day. Not all the issues seem to be solved! You should definitely get a late 2010 model, if you need a highly stable system!

[UPDATE] 2011/11/01: Apple replaced one of our 15-inch MBP MC721LL/A machine and the freezes are not appearing anymore. Reports from other users that bought an early 2011 model are positive, so currently the advice would be to get a refurbished Apple MacBook Pro MC721LL/A 15.4-Inch Laptop even before getting a MD318LL/A 15.4-Inch (late 2011) version, not only because of saving some bucks, but also since the Apple MacBook Pro early 2011 performs better in most of the situations compared to the late 2011 version.

Besides the heating issues, there are also reported "intermittent flickering, brief blackouts and other periodic but noticeable flaws" reported in the Apple Discussion Forums. We are getting replacement Machines - let's see if there is any improvement after the first round of shipping!

Instruments, Audio Effects, Midi Effects - but of course, this is not all of the cake. Imagine you can create user-interface elements however you please and also assign MIDI to that interface parts. This brings Ableton Live huge steps forward: the possibility to extend ableton to include a full featured audiovisual prototyping environment and to interface with the world: be it sensors, webservices or other Ableton Live installations.

1. Installation and Setup

Ableton Live Suite 8.1 (1.4GB download size!) and max/msp 5.1. are out in final versions as of today. As a happy Ableton and max/msp owner, the crossgrade was only 79€ for me (including VAT).

Right after Live starts up it has to be authorized, so all the extensions would be usable. After everything is set up, the following popup should be visible:

2. Overview

There are 3 different ways to include Max for Live patches into Ableton.

a) Instruments
Instruments would be a Synthesizer, a Sampler, etc.
Input: MIDI, Output: Audio

b) Audio Effects
Imagine any Audio Effect you can build here - let's say a Reverb for now.
Input: Audio, Output: Audio

c) MIDI Effects
Controlling and modifying the MIDI flow - like arpeggiators, mathematical functions, midi-sequencers, whatever.
Input: MIDI (or controller values), Output: MIDI

Of course, the whole bandwidth of max/msp is much more than only that. With Max for Live, now it is possible to use sensoric interfaces directly with Ableton Live: such as the i-cube, the arduino microcontroller board and so much else (for example the wireless MIDI Glove).

Interfacing to the "outside world" is also quite easy with max/msp: the netsend and netreceive objects let you connect via socket to e.g. a webservice, RSS-feed, whatever.
See also: Max for Live and twitter integration, the shoutcast~ and netsend~ objects for sending your audio stream around.

3. First Steps

In the screenshot above you see where the "Max Instrument" can be found in Ableton Live. In the right corner you can also see the first Instrument example I built: a sine wave oscillator.

a) Example: Sine Wave Oscillator Instrument with Signal Oscilloscope [download the patch]

This is a very basic patch: notein gets the MIDI note played, ddg.mono simplifies monosynth creation by dealing with last-note priority and note-on/note-off pairing, mtof (MIDI to frequency) translates the MIDI note to a frequency which is pushed to the cycle~ object (sine wave generator). The cycle~ then sends its audio-output to plugout~ which gets routed back to Ableton Live. Play the Sine Wave Oscillator as you would play any other instrument in Ableton Live: either via keyboard or via MIDI tracks.

b) Example: Simple Delay [download the patch]

This is also a rather simple patch. The incoming signal is delayed for a specific amount of time using the tapin~ and tapout~ objects. The tapin~ object is a continually updated buffer that stores the most recent signal it has received, and tapout~ accesses that buffer at one or more specific points in the past. The sound is mixed with its delayed version to create a sort of reflection.

What you can see in the screenshot below is how to implement images in patches that get loaded also to Ableton (using the fpic object) and which part is actually displayed in Live: everything below the black line is "invisible".
Test out the patch with the presets and also try to change the tapin~ and tapout~ values (use it as an audio effect on any soundfile. percussion or drums may be the best to hear the difference).

c) Example: 8-Step-MIDI-Repeat [download the patch]

The patch is also really simple: a line object counts from 1 to 9, resetting itself to 1 when it reaches 9 (=8 step), the select object checks for values between 1 and 8 and sends the according bang messages to the lights on top. the lights also trigger the int object, that saves values and outputs them on demand. this int objects are used to save the state of the checkboxes.
everytime an int object outputs a 1 (checkbox=checked), the select object on the right side sends the last notein event to a noteout object, causing the last note to be played again.

The difference between the two above screenshots is: hidden objects. Objects that you don't want to be visible in your Ableton Live surface you can hide with Object -> Hide on Lock (Apple+K).

Patch No.3 repeats your last played note in a step-sequencer style: however you checked your checkboxes, every time the light is active over a checked box, the last note will be played again. Test the 3 different presets and also the freestyle option (entering numbers on your own). Be careful with too low and negative numbers.

3. Conclusion

Max for Live is not only a very huge extension to Ableton Live (as stated above, a lot is possible now, from interfacing with hardware to webservices) but also finally a step in the right direction for the said to be lazy "ableton users": while the mainstream of ableton users use similar effects and instruments, this will change from now on. Instrument-directories such as on maxforlive.com feature lots of already available patches.
Another positive point is since max/msp is there much longer than Ableton Live and there is lots of educational content, tutorials etc. around. This could bring more people to look and learn about DSP and sound engineering als well as the physics behind audio.

Max for Live has still a few bugs - but what is there already is really something! Maybe one has to see it like this: in the end max/msp got a really cool sequencer ;)

4. Ressources

* ableton.com maxforlive product page
* cycling74 product page for max/msp
* maxforlive.com
* cycling74: the edit button has been pressed
* max 5 help and documentation

Technorati Tags: ableton, max msp, live, max for live, sound, review