With Mac OSX Lion 10.7.0, a message was repeatedly showing up in the Console.app, so the logfiles would grow in size - sometimes around 100 MB per minute. This is especially bad for SSD owners. While the issue was reported over 6 Months ago, and Flash Player 11 solved the amount of errors in the console, still the message appears and slows down OSX 10.7 systems.

At least the release of Adobe's Flash Player 11 solved the system freezes - but the Log message still is filling the kernel.log, so any debugging or search for errors is quite hard with that amount of data to read through.

If you are experiencing the same issues, please write your concerns to the Adobe Forums in the existing thread and alternatively also in the Apple Discussion Thread.

Nanofunk reported about this issue in july 2011, and we got over 60.000 unique visits to this post - so this is not a rare case, this is a serious bug with Adobe Flash and Adobe Air. We will post any updates to the situation to this blog, make sure to bookmark our feed.

See also:
* macrumors forum about kernel: IOSurface: buffer allocation size is zero
* nanofunk: Mac OSX Lion 10.7 System Freezes: kernel: IOSurface: buffer allocation size is zero (console message)

[Update] I posted to the Adobe Bugbase with a bug description. Hope they will respond now.

It has not been verified yet, but there are some leaked details, which are of course just rumors:

- 4-inch screen
- Aluminum back
- Capacitive home button
- "Flatter" form factor
- Much faster than current hardware, but poor battery life
- 10-megapixel rear camera
- Siri prototype known as "Assistant", which had been the rumored name for the feature until its introduction

There are quite some good deals on the Apple iPhone 4S on ebay, an introduction of the iPhone 5 would let the price of the "older" models drop significantly (talking about the Osborne Effect)

Affected Models: Macbook Pro models 8,1, 8,2, and 8,3. These include both MacBook Pro (Early 2011) and Macbook Pro (Late 2011).

This update resolves an issue where a MacBook Pro being used with a power adapter may unexpectedly shut down under heavy workload if the battery charge level is near empty.
Your computer's power cord must be connected and plugged into a working power source, or your battery must be at least 25% charged.
When your computer restarts a gray screen will appear with a status bar to indicate the progress of the update.
Your computer's fans will run at full speed during the update but will return to normal speed once the update completes.
Do not disturb or shut off the power on your computer during this update.

The MacBook Pro SMC Firmware Update 1.5 can be downloaded from Apple's support website.

Video: Tsawout Spit – Gh2 Test (driftwood 176mb gop1 hack) from mark wyatt on Vimeo.

There seems to be no day without any surprises with the Panasonic GH2. The latest hot-shit is a hack to get 176Mbps AVCHD Intra up and running on the camera. Right now there's no possibility to record in 25p but there are attempts by vitaly and others, so let's see what the future holds.

What is AVCHD Intra?
"AVCHD Intra is usually recorded to extremely expensive P2 cards on high end cameras and here it is on a consumer camera with an SD card. [...] This is a codec that uses i-frames only unlike consumer AVCHD. Every frame from the sensor is stored. Standard AVCHD is a Long-GOP compression format and works by estimating and guessing at frames in-between ‘real’ images but Intra doesn’t. [...] AVCHD Intra is very good for heavy colour grading, fast action, hand held footage and green screen VFX work. You certainly get a better result from AVCHD Intra on the GH2 than by outputting from any DSLR’s HDMI feed to a external recorder as well." (via eosHD)

How does it compare?
eosHD has a comparison on AVCHD intra 100Mbps vs 24Mbit AVCHD.

And if that's not enough: there is even a 244Mbps AVCHD Intra Hack, as outlined by Driftwood: "It's stable and with good lighting conditions can look amazing."

eosHD recommends: "AVCHD Intra at such high bitrates can be tricky to edit so I recommend transcoding it to ProRes 4-4-4 first."

Fuji president and CEO Shigetaka Komori said they will create a mirrorless, interchangeable lens camera built around a larger sensor with ‘resolution and low noise [that] will surpass the 35mm full size sensor’. If Canon does not come up with the EOS 5D MKIII fast, people will start to switch.
(via DC.watch)

Everyone's talking about the new iPhone 4S that was announced by Apple recently. But is there more to it than improved optics? Even if not, the camera is a huge improvement over the previous model: 1080p video recording, 8 Megapixel photo sensor, f/2.4 aperture.

Behind all the updates, the most interesting is HSDPA support. In countries such as Austria or Japan, where HSDPA is widespread, this is a very welcome hardware upgrade. Still, why is there no HSPA+ support? In cities with a weak broadband coverage (everything above a few MB upstream) - such as Vienna, this is really akward. We still have to fall back to the Samsung Galaxy S2 i9100, which offers HSPA+ among other great features. So the "only" killer feature of the Apple iPhone 4S remains the greatly improved Camera - which is to question, concerning the price of such a gadget. An Amazon Search for the iPhone 4S yields no results, obviously, since the device is said to be available from mid October.

Our recommendations: wait for the iPhone 5 and get some real gear instead.

1) Get a Canon PowerShot S100 for Photo and Video
2) Get a SONIM XP5300 3G FORCE if you need a phone that actually works.

Currently, Ableton Live 8 is $499.00 (new) and $425.00 (used).

The 10.7.1 update is recommended for all users running OS X Lion and includes general operating system fixes that enhance the stability and compatibility of your Mac, including fixes that:

For detailed information on this update, please visit this website: http://support.apple.com/kb/HT4764.

There is not much fixed, at least not for the reported issues such as SSD TRIM support for non-apple SSDs and the well known flash issues.
Still, Seems more stable. There is a seperate update for 10.7.1 Server and another update specific to the latest MacBook Air and Mac mini models, adding a few additional fixes. (via macrumors)

To reproduce the issue:
1) click on "Clear Display" in Console.app
2) go to http://www.adobe.com/software/flash/about/ and the error will show up in the console.

The error must be Flash related. Sometimes, the whole System is unresponsive, freezing everything but the mouse. There is no official response from Adobe or from Apple, so we can only hope and wait. Please check your Console.app for this error and respond to any of the existing discussions.

[Update] the error message also seems to have surfaced in 10.6.4 already, as visible in the Apple Discussion Forums

[Update] installing the Adobe Flash Player 11.0 from Adobe Labs seems to at least minimize the freezes, but still the console messages appear.

[Update] i posted a poll on insanelymac to see which browsers and systems are affected. please also post your results there!

[Update] the new Beta 2 11.0.d1.98 of the flash player is out (thanks JP Hansen)

[Update] The Flash Player 11 is officially released. It seems though, that not all issues are resolved with Mac OSX Lion compatibility.

[Update 23.12.2011] more than 6 months after the issue was reported, (and we have Apple Mac OS X 10.7.2 and 10.7.3 in beta) there is still no update on this issue from Adobe. Please write your concerns to the Adobe Forums in the existing thread to have them fix the issues! Especially for SSD owners this is unacceptable!

Existing Discussions:

* Nanofunk.net discussion thread in the Adobe Flash Player Forums
* Thread in the Apple Support Communities Forum
* Thread on MacRumors Forums regarding Lion Freezes with kernel: IOSurface

[Update] I posted to the Adobe Bugbase with a bug description. Hope they will respond now.

1) No TRIM support out of the box if you are using your own SSD (not Apple's)

This is ridicolous: TRIM only seems to work for Apple buit-in SSDs. There is a tool by groths.org that will do the trick: TRIM Enabler, which works for Lion and for Snow Leopard as well. You might want to consider enabling this feature, since TRIM will make your Solid State Drive last longer, due to less writes to the cells.

2) Mouse scrolling direction got reversed: how to revert

Apple decided to reverse the mouse scolling on 10.7 Lion, meaning you have to scroll your mousewheel up to actually move the on-screen content down. Here is a screenshot from System Preferences, where you can change that "feature" to the way it was before: simply uncheck the box left to "Move content in the direction of finger movement when scrolling or navigating".

3) Disabling the "Resume" feature

The "Resume" Feature in Mac OS X Lion restores the state of the application windows, when re-opening an application. Since I definitely do not need this feature, here is a way to turn it off: just uncheck the left box next to "Restore windows when quitting and re-opening apps" in System Preferences -> General

4) Disabling "Versions" feature in Mac OSX 10.7 Lion

Versions should't be a problem unless you are using Time Machine. MacRumors has a forum post on disabling that features.

5) Other (small) annoyances

Google Chrome does not get moved with an update ( Chrome vanishes with Lion 10.7 Update)

This is also very strange: the Google Chrome Browser did not get moved on my Lion update. I had to re-download Google Chrome.app. At least the Application Support files got moved, so I did not lose any browsing history or bookmarks.

Dropbox needs to be reinstalled: special Lion build

The dropbox right-click features dissappear when updating to Lion. Download the Latest Forum Build of Dropbox that is Lion compatible (1.2.16 at the time of writing this entry)

Other interesting reviews about Mac OSX 10.7 Lion can be found here:

* Time Magazine on OSX Lion: "With OS X Lion, Apple's Macs Enter the iPad Era"
* Engadget: "Apple OS X Lion (10.7) review"

Steps to install OSX Lion:
1. Get the "GM" (Golden Master) of Lion via torrent
2. Get an EFI Boot Loader
3. Get a decent 8GB USB thumb drive and install the Golden Master on there.
4. Install using iBoot.

You can get detailed information on installing Mac OSX Lion 10.7 by reading the geeknizer blog howto.

[UPDATE] tonymacx86 showed how to Install OS X 10.7 Lion on any Supported Intel Core 2 or Core i based PC with xMove + MultiBeast. Furthermore, there is a Mac OSX Lion v10.7.2-HOTiSO that should also boot from any PC. Don't forget that you need to buy Apple Mac OS X Lion from the App Store to legally use it.

After days of trying to figure out what is really the issue, we found that most of the times device drivers or other third party apps are mostly causing the crashes - but also CPU-intensive apps such as games sometimes bring the system down. Solution? Yes, there is one: change your system to a 32bit Kernel.

1) The bootup way (temporary solution, great for testing)

If you just want to test if changing to 32bit changes anything, you can reboot your mac and hold down the "3" and "2" keys as soon as you hit the power button. This boots up your Apple in 32bit mode temporarily. If the system

2) The Terminal Way (see the Apple Support Document for more information)

sudo systemsetup -setkernelbootarchitecture i386

if you need to change your system back to normal for any case, you can enter the following command into Terminal.app:

sudo systemsetup -setkernelbootarchitecture x86_64

Just to make it clear: your applications will still run in 64bit mode, you can make sure this is the case by hitting cmd+i on the application icon and see if "Open in 32-bit mode" is checked. See this article from simplehelp with details and images on 32-bit mode. So why should I care then, you might ask: since drivers and 3rd party apps and extensions that are loaded on startup are most of the time the issue with system freezes and hangs, changing to a 32bit kernel did the trick for us and now we have a stable 2011 MBP quad-core system.

[UPDATE] 10.6.8 seems to work with 64bit kernel much more stable than 10.6.7. Still, to be on the safe side we are using the 32bit kernel and had no freezes yet.

The release notes according to Ableton:

Improvements and feature changes

• Added bank names for Amp instant mapping, which in turn fixes a problem with the Axiom DirectLink control surface.
• Fixed problems with the Mbox2 related to non-integer sample rates.
• Added control surface support for Akai Professional LPD8.
• From now on, betas will ask to check for updates only once a week, and starting a week after first run.
• the "Peek" button on the Axiom Pro now works as a momentary control

Max for Live improvements and feature changes

(Note: Most of these changes require an update to the latest version of Max, which is available from http://cycling74.com/downloads/)

• Devices inside Racks can now be accessed via the Max for Live API
• Return tracks can now be observed via the Max for Live API

Live devices and parameters can now be much more easily mapped to controls in Max devices. Devices can safely be moved within a Live Set without breaking any existing mappings. Also, devices and Sets can be saved and loaded without breaking existing mappings. The following changes make this possible:

• There is now a simple way to observe the selected parameter via the Max for Live API, using "live.path live_set view selected_parameter." This can be used, for example, to build a custom "map mode" to quickly map parameters in your Live Set to controls in a Max device.
• Live objects like tracks, clips or parameters retain their identity (id nn) during operations like move, save/restore, cut/paste, delete/undo, the identity is global and can be communicated via Max's Send and Receive objects.
• live.object, live.observer and live.remote~ are now able to remember their target objects when Live sets or presets are saved and restored or when objects are moved within the Live set.
• Ableton protected samples can now be used in Max for Live device, via the Live.drop object
• fixed a bug where clip slots would lose their id on moving a clip
• fixed navigating and observing control surfaces via the LiveAPI
• Repeatedly calling "goto control_surfaces" on a live.path object was producing a different id each time
• Fixed a crash that occurred when deleting a Rack containing a Max for Live device, where a Remote~ was controlling one of the Macro knobs, and then Undoing the delete action
• Navigating the Live Object Model is about two times faster
• Fixed a crash that occurred when moving tracks that contained automated Max for Live devices
• Fixed a crash that occurred when replacing one Max for Live device with another if certain modulations existed
• If a native Ableton device has parameters that are mapped to a Max for Live device, the mappings will be preserved after hot-swapping the Ableton device
• The Track/Chain Activator and Song Tempo are now accessible via the "selected_parameter" property and their path can be queried
• "live_app" and "live_app view" can now be persistent in the Max for Live API
• Mapping some mixer component on the APC40 (for example) through the Max for Live API wouldn't work without pressing the Pan or Send button on the APC40, which reset the component. This has been fixed.
• "goto live_set tracks 2 devices" in a set with one track produced id -1, which is wrong. Now it produces id 0.
• If the LOM id of the observer is persistent, the property of an observed LOM object is persistent, even if it is dynamically changed using a message.
• Max for Live devices that control the Application objects (e.g. live_app (live_app view)) or which get information about the Live version and document name (e.g. get_major_version (focus_view)) will work when loading the Set, without requiring user interaction.

Bugfixes

• Fixed a problem with nested Macro mappings when the range of a mapped ON/OFF switch, or of a selector switch (such as a filter type switch), is not at default values. In such a case, the right value would be displayed, but the wrong value would be used internally.

Note: with this fix, you will now hear what you see, although this may mean that previously saved Sets that contained the bug may sound different.

• Deleting time in the Arrangment View could delete crossfades in certain cases.
• When using an APC40 and Scratch Live, Scratch Live would sync to the APC but would not initially show the return tracks .
• If the VST plug-ins folder contained shorcuts/aliases to files in another location on disk, the folder would be rescanned each time Live starts. This has been fixed.
• When launching a scene with via Key/MIDI mapping or a control surface such as the APC40 while "Select on Launch" is enabled, the Master track became selected. This would result in the selected device switching to the device on the Master track. Now, launching a scene via remote control behaves the same as when launching with the mouse; the device selection doesn't change.
• Fixed a crash that could occur when clicking the status bar, while it displays "Media files are missing", and just after having adjusted a Macro knob.
• Fixed a crash that occurred when adding an audio clip, scrubbing in the clip detail view, and pressing Undo while the mouse was still down for scrubbing.
• Fixed a crash that could occur when switching between certain audio interfaces on a Mac
• updated Complex Pro libraries to prevent a potential crash
• fixed Transport button behavior for the Akai MPK61 and 88
• fixed a crash that could occur when opening very large Live Sets
• fixed a crash that could occur when a clip referencing a sample was in the clipboard and when pressing the Edit button (in the File Manager or Clip View) to set the sample offline and then on again
• Holding a note while recording a MIDI clip and stopping the transport while the note is held would result in a silent note during play back
• If a clip was in Gate Mode, releasing the trigger key within the launch quantization period would still launch the clip
• Fixed a bug that caused a clip in Gate launch mode to continue playing after clicking another clip for a very short time
• Fixed a bug in how MIDI effect Racks handle latency. Now chains compensate properly against each other

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!

The Offers in Detail:

• Kore 2 + Komplete 6 for 699€
• Komplete 6 Update from any previous version: 74,50€
• Kontakt 4 Update 64,50€
• Traktor Scratch Pro Update , FM8 or Absynth 4 Update from 34,50€
• Guitar Rig Update for 34,50€
• Free Traktor Pro with Audio DJ 8 Soundcard (Free Traktor Duo with Audio DJ 2 or Audio DJ 4)
• Kore 2 Update or Battery 3 Update from 49,50€
• Reaktor 5 Update from 59,50€

I got myself a Kore2+Komplete, an Audio 8 DJ Soundcard and a Traktor Scratch Pro Update. Since I already own Komplete 6, i am selling it (as well as Traktor Pro and tons of other gear) on the Audio Sellout list.

Here are the two graphics of the Native Instruments offers:

• A very short MIDI note at the beginning of a clip would not be audible. [6130]
• Recording via 'Resampling' would not properly compensate latency. [6124]
• Under certain conditions, it would be possible to get 2 Arranger tracks highlighted. [6144]
• Using the Launchpad as control surface and additionally for manual mappings would not always work properly.
• When installing Live Packs which have dependencies to other content, Live would show the corresponding message twice. [6153]
• Using a Rex file could crash Live. [6157]
• 'lock control surface' function would not properly work in user remote scripts. [6064]
• A particular Live set could not be loaded and would lead to a 'Invalid Product ID Error' message. [6165]
• In the Arranger, punch In/Out would delay notes by the 'punch in time' in beats. [6167]
• Using the pads of the Akai MPD18 would not work properly.
• Having a Live set with particular Drum Racks could increase the CPU usage of the main thread, which would result in very slow graphical updates. [6181]
• Installing a new Library from within a second running instance of Live could crash Live. [6171]
• Certain operations like sample crop/reverse/replace would remove the tempo envelope. [6179]
• Using Novation's Launchpad, when switching between Automap and Live control would not work properly.
• Under certain conditions, editing or creating parameter automation would not work properly. [6188]
• Playing a 32-bit audio file immediately after a 16-bit audio file could cause a click in the audio. [6152]
• Moving the last track out of a track group onto a closed group track in the Arranger could crash Live. [6193]
• In the Auto Pan device, switching shape to random would not show the 'Width' knob. [6192]
• Loading a Max device would crash if Pluggo was already active.
• It would not be possible to create a new Project in the File Browser if the root is set to 'Workspace'.
• Fine tuning of macro knobs would not work via key modifier. [6180]
• Starting clips via the Launchpad while changing parameters via mouse could crash Live. [6143]
• Moving the mouse over a certain Sampler preset could crash Live. [6207]
• Loading a Live set containing not yet authorized add-ons could crash Live. [6203]
• Under certain conditions, fade creation would not work properly. [6195]
• An Ableton preset of a third party plug-in would not change the On/Off mapping range. [5652]
• Receiving an invalid parameter index from Max could crash Live.
• Inverting a macro mapping range would not work properly. [6238]
• Under certain conditions, extracting an existing groove from a clip would crash Live. [6235]
• Having a Max device sending many blob changes during saving could crash Live.
• A malformed database file would interrupt user interactions like renaming files, saving presets, recording, etc. [6230]
• Having a particular Live set loaded and searching for media files could crash Live. [6241]
• On Mac OS X, under certain conditions, making Live the foreground window could lead to a crash.
• The context menu of a frozen clip would have enabled audio fades commands. [6253]
• In the Arranger, changing the mixer properties like volume, pan etc. would not show the changed value in the status bar. [3238]
• Having a multi selection of Arranger track and use the 'Show Automation' command would destroy the selection. [6243]
• Choosing a custom VST directory within the preferences would not keep this new directory until the next start of Live if the required rescan leads to a crash. [6190]
• On Mac OS X, duplicating a track with Fab Filter Twin 1+2 could crash Live. [6063]
• The Looper display would use the wrong colour in 'play' mode. [6234]
• Holding SHIFT + Space Bar would make the transport play button flicker. [6227]
• The area to click on an Arranger clip would be too small by a few pixels. [6261]
• Particular Live sets, especially with a lot of transient data, could not be loaded. [6263]
• Pasting 3 unstretched and crossfaded Arranger clips could crash Live [6289]

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

• Updated manuals
• Updated Help Pages

Bugfixes:

• Surface controller support for the Oxygen 3rd generation
• Using the Axiom Pro as controller surface would not work properly with certain effects and instruments
• Under certain conditions, a volume automation would not work properly [6005]
• The mouse handling of certain Sampler parameters would not work properly [5961]

Most of all, 20% off Live 8 and Upgrades, some users even get free Upgrades, and 10 Free Downloadable Live Packs from Various Artists. Sadly for Ableton Suite owners there is no special discount or goodie - but for people owning Live 8 or 7 - or even the Lite versions - now it's a good time to Upgrade! The release for Max for Live was set on the 23rd November 2009 and a new stripped-down Ableton for starters is ready: Live Intro.

Changes from Live 8.0.5 to Live 8.0.8

Improvements:

• Updated manuals
• Updated Help Pages
• Control Surface support for Novation Launchpad
• Several improvements for the AxiomPro Controllers

Bugfixes:

• Using the double/halve tempo buttons of the Looper could introduce an audible offset [5857]
• Playing MIDI could crash Live when multi-core support is enabled [5608]
• If the slot button below a disabled Session clip has been removed, the disabled clip would not respect this and act as stop button [5872]
• In the Arranger, auto scrolling would not work properly when dragging tracks [5865]
• On Mac OS X, open the application menu would not close an open context menu [5768]
• On Mac OS X, using a Remote SL and loading a particular Live set with a Fab Filter Twin 2 would crash Live
• On Mac OS X, the Key stroke handling for AudioUnits using Cocoa views would not work properly
• On Mac OS X 10.6.x, starting Live with a template set that contains audio clips, and with another CoreAudio client running at the same time (e.g. iTunes), would freeze Live. Also, changing sample rates in Live would not work properly
• Replacing a Macro mapping with a Key mapping could crash Live [5913]
• Return track header selection would not work properly [5677]
• On Mac OS X, Audio Units, wrapped by Novation Automap, would not appear in the right folders [5752]
• Setting an MTC start offset to a negative value would not show the value properly [5456]
• Grabbing and moving the left edge of an Arranger loop while the loop start is out of the view would not behave properly [5216]
• In the Arranger, scrolling would not work properly when dragging or moving tracks [5139]
• Under certain conditions, the LFO of the Sampler would not work properly
• Switching banks via remote script would not be indicated in the status bar [5969]
• Switching on track-solo would not work properly in exclusive mode when switching via the APC controller [5838]
• Unsupported multi channel audio files would crash Live [5995]
• When exporting an video file, the resulting video file would grow on each export instead to be replaced [5996]
• On Mac OS X, when typing the name of an existing file, but without the extension, Live would overwrite the existing file without asking for confirmation

Native Instruments Komplete 6

Native Instruments Komplete 6 was announced some days ago. As a proud owner of Komplete 5 i am looking forward for the update. The previous Komplete Version was a total bargain for me, since i got it within the Kompletely INSANE Sale for just 399€. Since the new Komplete will be €499, it is even cheaper for people to get the new version as to upgrade from version 5. (damn, I should have waited. but who cares, I love my FM8)

Key features of NI Komplete 6 are: Kontakt 4, Absynth 5 and Guitar Rig 4 Pro. (See the Native Instruments Page on Komplete 6 for all news regarding version 6). I will post an in-depth review when i received my update.