via fffff.at: "The 2nd edition of the SPEED SHOW presents again a wide selection of pop.net.art pieces and addresses various developments of performance related but still screen based art works. Most interaction and communication on the web bears it’s very own performance character. One could say Facebook is a huge mass performance piece. net.art in it’s classic form could be considered a performance by interactivity as well. In recent years artists from different fields work increasingly in a mix of performances and digital interventions. In some cases the screen itself, the beholder of the pixel is subject to fluctuations. In other works the performance is acted out by a hysterical mass or just by the code."

Thursday, 8th of July 2010, 19:00 – 22:00 h // Kaukas Handy Shop, Äussere Mariahilferstr. 178, Vienna (Map)

"Hit an Internet-cafe, rent all computers they have and run a show on them for one night. All art works of the participating artists need to be on-line (not necessarily public) and are shown in a typical browser with standard plug-ins. Performance and life pieces may also use pre-installed communication programs (instant messaging, VOIP, video chat etc). Custom software (except browser add-ons) or off-line files are not permitted. Any creative physical modification to Internet cafe itself is not allowed. The show is public and takes place during normal opening hours of the Internet cafe/shop. All visitors are welcome to join the opening, enjoy the art (and to check their email.)"

Participating artists will be:

- Margarete Jahrmann & Renate Christian

- JODI

- JK Keller

- Greg Leuch

- Michael Marcovici

- Will Moffat & Peter Burns

- monochrom

- Evan Roth

- Sakrowski

- Gordan Savicic

- Michael Schieben

- Georg Schütz

- Chris Sugrue

- Philipp Teister & Kim Asendorf

- UBERMORGEN.COM

- Jamie Wilkinson

• 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]

What is a monome? "a reconfigurable grid of backlit keypads which connects to a computer. interaction between the keys and lights is determined by the application running on the computer. there is no hard-wired functionality."

(see more videos of the monome on vimeo)

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

2 new Player Widgets are available. With the new "Artwork" and "Mini" Players, this makes a total of 3 available Player Widgets for SoundCloud.

While the Artwork Player is a great way to showcase album art in your SoundCloud tracks, the Minimal Player is great for embedding where there is not much space available. All in all, the two new Widget options are giving you more options on how to feature your tracks without having the usual SoundCloud look, that is the same on all sites using it (except color adaptions, which were possible before).

Stats have been totally revamped: Who, What, When, Which and Where can be found out for your Tracks now - but - depending on your account type. Full Stats are only available for Business PRO users, while the other accounts have different detail levels. The difference from the Premium SOLO to the full stats seem to be, that embedded, linked or posted tracks are not statistically tracked.

The sharing was also reworked, here's the quote from the official sendout: "Much asked for - here it is: private track sharing via secret link. Simply upload a track or set, generate a private link for it, then quickly share via email or IM. Plus with newly the added privacy options, you can now control if you want people to comment or your tracks or not, hide the stats around your track and make comments only visible to yourself. Perfect for when you're doing promo or need to keep the number of recipients private."

Finally, there are 2 Desktop uploading apps available as of today: "Scup and CloudPost are two nice little apps that let you upload your tracks and sets to SoundCloud right from your desktop". And "one more thing": the iPhone App for SoundCloud which can be downloaded for €0,79 or $0,99. Detailed reviews of all the apps right after I tested them.

Cheers and happy uploading.

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.