Digital: disposable, identical, infinitely reproducible. Recordings: static, unchanging.

Or … are they?

Icarus’ Fake Fish Distribution (FFD), a self-described “album in 1000 variations,” generates a one-of-a-kind download for each purchaser. Generative, parametric software takes the composition, by London-based musicians-slash-software engineers Ollie Bown and Sam Britton, and tailors the output so that each file is distinct.

If you’re the 437th purchaser of the limited-run of 1000, in other words, you get a composition that is different from 436 before you and 438 after you. The process breaks two commonly-understood notions about recordings: one, that digital files can’t be released as a “limited edition” in the way a tangible object can, and two, that recordings are identical copies of a fixed, pre-composed structure.

Happily, the music is evocative and adventurous, a meandering path through a soundworld of warm hums and clockwork-like buzzes and rattles, insistent rhythms and jazz-like flourishes of timbre and melody. It’s in turns moody and whimsical. The structure trickles over the surface like water, perfectly suited to the generative outline. At moments – particularly with the echoes of spoken word drifting through cracks in the texture – it recalls the work of Brian Eno. Eno’s shadow is certainly seen here, conceptually; his Generative Music release (and notions of so-called “ambient music” in general) easily predicted today’s generative experiments. But Eno was ahead of his time technically: software and digital distribution – both of files and apps – now makes what was once impractical almost obvious. (See also: Xenakis, whom the composers talk about below.)

You can listen to some samples, though it’s just a taste of the larger musical environment.

Fake Fish Distribution – version 500 sampler by Icarus…

12 GBP buys you your very own MP3 (320 kbps). Details:
http://www.icarus.nu/FFD/

The creators weigh in on the project for Q Magazine:
Guest column – Electronic band Icarus on whether algorithms can be artists?

The conceptual experiment is all-encompassing. Just to prove the file is “yours,” you can even use it to earn royalties – in theory. As David Abravanel, Ableton community/social manager by day and tipster on this story, writes:

“As a sort-of justification for the price, all Fake Fish Distribution owners are entitled to 50% of the royalties should the music on that specific version ever be licensed. A very unlikely outcome, but at least it’s sticking to concept.

I spoke with Ollie and Sam to share a bit about how the mechanism of this musical machine operates. Using Ableton Live and Max for Live, each rendition is “conducted” from threads and variables into a sibling of the others. The pair talk about what that means compositionally, but also how it fits into a larger landscape of music and thought. Of course, you can also go and just experience your own download (first, or exclusively) to let the music wash over you, an experience I also find successful. But if you want to dive into the deep end as far as the theory, here we go.

CDM: How is the generative software put together? What sorts of parameters are manipulated?

Ollie: The basic plan to do the album came before any decision about how to actually realise it, and we initially thought we’d approach the whole thing from a very low level, such as scripting it all in the Beads Java library that has been a pet project of mine for some time. But although we love the creative power of working at a low level, the thought of making an entire album in this way was pretty unappealing. We looked at some of the scripting APIs that are emerging in what you might call the hacker-friendy generation of audio tools like Ardour, Audacity, and Reaper, but these also seemed like a too-convoluted way to go about it.

Even though Max for Live was in hindsight the obvious choice, it wasn’t so obvious at the time, because we weren’t sure how much top-down control it provided. (As a matter of fact, one of the hardest things turned out to be managing the most top-level part of the process: setting up a process that would continuously render out all 1000 versions of each track.) Although it was quite elementary and unstable (at the time), [Max for Live] did everything we wanted to do: control the transport, control clips, device parameters, mix parameters, the tempo … you could even select and manipulate things like MIDI elements, although we didn’t attempt that. 

So we made our tracks as Live project files, as you might do for a live set (i.e., without arranging the tracks on the timeline), then set up a number of parametric controls to manipulate things in the tracks. Many of these were just effects and synth parameters, which we grouped through mappings so that one parameter might turn up the attack on a synth whilst turning down the compression attack in a compensatory way. So the parameter space was quite carefully controlled, a kind of composed object in its own right.

We also separated single tracks out into component parts so that they could be parametrically blended. For example, a kick drum pattern could be spilt into the 1 and 3 beats on the one hand, and a bunch of finer detail patterning on the other, so that you could glide between a slow steady pattern and a fast more syncopated one. So loads of the actual parameterisation of the music could actually be achieved in Live without doing any programming. Likewise, for many of the parts on the track, we made many clip variations, say about 30, such as different loops of a breakbeat. The progression through those clips — quantised in Live, of course — could also be mapped to parameters.

Finally, by parameterising track volumes and using diverse source material in our clips, we could ultimately parameterise the movement through high-level structures in the tracks. So we could do things like have a track start with completely different beginnings but end up in the same place. We did this in Two Mbiras, which is probably the track where we felt most like we were just naturally composing a single piece of music which just happened to be manifest it a multiplicity of forms. In that sense, this was the most successful track. Some of the other tracks involved more of an iterative approach where we didn’t have a clear plan for how to parameterise the track to begin with, but that fits with our natural approach to making tracks. At one point, we wondered if we could just drop a bank of 1000 different sound effects files into an Ableton track, to load as clips. To our glee, Live just crunched for a couple of seconds and then they were there, ready to be parametrically triggered. So each version of the track MD Skillz could end on a different sound effect.

The Max software consisted of a generic parametric music manager and track-specific patches that farmed out parametric control to the elements that we’d defined in Live. The manager device centred around a master “version dial”, a kind of second dimension (along with time), so you could think of the compositional process as one of composing each track in time-version space.

We used Emanuel Jourdan’s ej.function object, which is a powerful JavaScript alternative to the built-in Max breakpoint function object, and wrote some of our own custom function generators and function interpolation tools to interact with it. Using the ej.function object, we composed many alternative timelines to control the parameters, and then used the version dial to interpolate smoothly between these timelines, resulting in a very gentle transition between versions. I.e., version 245 and 246 are going to be imperceptibly different, but version 124 and 875 will be notably different (we quickly broke from our own rule and started to introduce non-smooth number sequences into some of the tracks, so for example in Colour Field two adjacent versions will actually have quite different structures). We spent some time making it well integrated into Live so that once we really got into the compositional process it would work smoothly and be generally applicable to all of the different ideas we wanted to throw at it. That said, it’s a few steps of refinement from being releasable software. 

Pictured: the master controller device, very minimal, just a version dial and a few debug controls. Double clicking on bp_gui leads to the other figure, a multitrack timeline editor, with generative tools for automatically generating timeline data using different probability distributions.

How did you approach this piece compositionally, both in terms of those elements that do get generated, and the musical conception as a whole?

Sam: Since 2005, we had been working a lot in the context of performance, not only as Icarus, but with improvising musicians through our label / collective Not Applicable. This is reflected in the records we put out both as Icarus and individually during that time, which increasingly used generative and algorithmic compositional techniques as structural catalysts for live improvisations. (As Icarus: Carnivalesque, Sylt and All Is For The Best In The Best Of All Possible World. Individually: Rubik Compression Vero, Five Loose Plans, Nowhere, Erase, Chaleur and The Resurfacing Of An Atavistic Trait). Our performance software was made using Max/MSP and Beads and we started by crafting various low level tools that would loop and sequence audio files in various different ways, giving us control parameters that were devised around musical seeds we were interested in exploring.

In many respects, our approach was very similar and partly inspired by Xenakis’ writings in Formalised Music, although the context is obviously very different. These low-level tools were augmented by various hand-crafted MSP processing tools which used generated trajectories and audio analysis as a method of automating the various parameters that effected the sounds themselves, the logic being that an FX unit as a manipulator of sound is in some way loosely coupled to the musical scenario it is contextualised in. In both cases above, the idea was to step back from performance ‘knob twiddling’ by using the computer to simulate specific types of behaviour that would control these processes directly (hence the reason why we have never used controllers in performance).

Our search for different methods of coupling our increasing parameter space led us to develop various higher-level control strategies at Goldsmiths and IRCAM respectively, culminating in autonomous performance systems built in the context of the Live Algorithms for Music Group at Goldsmiths College. The autonomous systems we developed used a battery of different techniques to effect control, from CTRNNs and RBNs to analysis-based sound mosaicing, psychoacoustic mapping and pattern recognition. This work resulted in us being commissioned to put together a suite of pieces for autonomous software in collaboration with improvising musicians Tom Arthurs and Lothar Ohlmeier called “Long Division” for the North Sea Jazz Festival in 2010. The challenge of putting together a 45-minute programme of autonomous music really forced us to think more strategically about how it was possible to structure musical elements within a defined software framework and how they could vary not only within each individual piece, but also from piece to piece.

The most obvious inspiration for how we might do this ultimately came from reflecting on what it is we do when we perform live as Icarus. The experience of working up entirely new live material and touring it without formulating it as specific tracks or compositions proved to be an ideal prototype not only for Long Division, but also ultimately for FFD. Here, in a similar sense to the work of John Cage, large-scale structure and form became a contextually-flexible entity, which meant that for us it became to a far greater extent derived from the idiosyncrasies of the performance software we developed and keyed in by our own specific way of listening out for certain musical structures and responding to them in either a complementary or deliberately obstructive fashion (or perhaps even not at all). Creating these two pieces (‘Long Division’ and ‘All Is For The Best In The Best Of All Possible Worlds’) gave us the conviction that we could devise musical structures that were both detailed enough and robust enough to benefit positively from some level of automated control.

Therefore, when we came to start working on FFD, the main question we had to ask ourselves was; within the music making practices we had already been working with, what were the tolerances for automation within which we were still ultimately in control of and ultimately composing the music we were creating? In the end, the framework we set up was comparatively restrained; the generative aspect of each track was always notated as a performance via a breakpoint function and therefore able to be rationalised by us, the variation between different versions of the same track was done using interpolation and is completely predictable and incremental and finally, the entire space of variation is bounded to 1000 versions, meaning that the trajectories of the variation never extend into some extreme and unrealisable space.

More notes on the album:

Web: http://www.icarus.nu
RSS: feed://www.icarus.nu/wp/feed/

Last.FM: http://www.last.fm/music/Icarus
Discogs: http://www.discogs.com/artist/Icarus+(2)

SoundCloud: http://soundcloud.com/icaruselectronic
Twitter: http://twitter.com/#!/birdy_electric

Myspace: http://www.myspace.com/icaruselectronic
Facebook: http://www.facebook.com/pages/Icarus/132324596558

CREDITS

Music, Software, Scripting – Icarus (Ollie Bown and Sam Britton)
Mastering – Will Worsley, Trouble Studios
Artwork – Harrison Graphic Design

Icarus gratefully thank the following for their support of the FFD project

The PRSF Foundation (UK)
STEIM (Netherlands)
Ableton (Germany)
The University of Sydney (Australia)
Emmanuel Jourdan (France)

Renoise’s scripting interface is something special, allowing people to build anything they imagine in a way that’s directly integrated with this production studio – no add-ons required. But whether or not you yourself want to code, that also means access to the imagination of the Renoise user base. And one of the most impressive shows so far is an ambitious process to duplicate Ableton Live’s mixer and clip launching interface inside Renoise. We first saw that effort at the end of the year, but it’s now about to reach a whole new level.

Now, in fairness, part of why people like me would like to see people use something other than Ableton Live onstage is to see different performance modes on laptops. And this absolutely doesn’t do that – you’ll see that the interface is more or less a clone of Live. (And I’ve been known to be critical of such interface cloning.) But there are two advantages. One is, doing this in a script in another host is a fascinating exercise in learning how to maximize the potential of Renoise’s scripting, one that could lead to other things. The other is, it’s possible that the familiarity of environments that work like the Live Session View could help performers ease into new ways of working with Renoise – without having to make the leap all at once. Renoise itself offers a very different way of working, built on tools of yore – basically, an alternative music-making path in software design entitled trackers. Like being able to go for a burger, fries, and ketchup in a foreign town, the availability of Cells could help those foreign to the tool moonlight between Ableton and Renoise in their work.

If nothing else, it’s something of an engineering triumph that this works at all.

In version 2.0, now in beta, a complete rewrite of the code vastly expands what’s possible with Cells. CDM readers took a lot of interest in this development when we covered it last, so it’s great to see what may be possible as the code matures.

And in some critical respects, Cells now does things in an integrated fashion that aren’t in Ableton Live. Pattern riffs, built on Renoise’s unique instrument paradigm, encapsulate samples and sample mappings together with your patterns. Bi-directional controller support, while eventually grafted atop Ableton (particularly for certain supported controllers), is part of the framework. There’s also integrated network sync support inside the tool, all implemented atop OSC; it’s still in beta, but shows lots of potential. (That’s possible in Ableton using existing MIDI and network tools, but seeing the server inside the tool is impressive.) And these are the kind of areas where it’s hopeful we’ll see new ideas in Ableton and rivals alike – another reason choice is a good thing.

From the forum post, forwarded to CDM by the creator:

Cells! 2.0 is a complete rewrite of Cells! 0.9. This has been based upon further code experimentation and user feedback. However, due to the improved approach and cleaner code, it has been possible to add many more features.

Thanks to Void Pointer (http://soundcloud.com/void-pointer) for kindly supplying the samples used in the demo video.

Realtime ‘Granular’ Timestretch

Cells! 2.0 allows realtime timestretch in a ‘granular style’. This allows full independant control of both tempo and pitch while still keeping playback syncronised to the beat. Granular timestretch applies to samples which have both a beat sync value and autoseek enabled but beat sync is disabled.

Realtime ‘Slice Based’ Timestretch

Similar to the ‘granular’ timestretch, Cells! 2.0 adds support for sliced loops with independant tempo and pitch control. Each slice will be played back at the correct time to maintain the overall tempo of the entire loop. Slice-stretch applies to samples which are sliced. The length of the cell is assigned through the beat-sync value.

Pattern ‘Riff’ Storage and Playback

Cells! 2.0 allows you to quickly save individual pattern tracks as riffs for use live in Cells!. The riffs are stored in compressed format within the instrument itself, so you can quickly and easily save all samples, sample mappings and riffs self-contained within a single XRNI file. Note that any Renoise instrument is be supported. This means you should be able to send note riffs to external instruments or VSTi’s.

Live Jamming Mode

For specific types of samples, Cells! 2.0 allows real-time ‘live jamming’ playback mode. Play your samples directly with either the mouse or a physical controller for improvising over your mixes to add that extra sparkle. Individual slices from sliced loops and plain one-shot samples can be played in ‘live jamming’ mode.

Bidirectional Controller Support

Cells! 2.0 now has its own native controller framework. This allows full bidirectional support for supported hardware controllers. Livid Instruments Ohm64 and Novation Launchpad (beta) are available with the inital release. If you would like further support for any additional controllers, feel free to either send them to me for development or contact me directly to work together and implement support.

MultiFX

Cells! 2.0 incorporates a simple ‘DJ style’ effects processor into the main UI. Effects supported are a low-pass filter, beat repeat, delay and phaser. All effects are controlled through simple common amount and rate controls. All time based effects are syncronised to the beat.

Sample Preparation Tools

Cells! 2.0 incorporates simple methods to quickly create and prepare samples for use. Both the sample editor and the sample list box contain a ‘Cells! menu’ from which the sample can easily assigned to a specific playback mode and length. A ‘sample report’ feature is also available which allows you to quickly identify how the selected sample
will play within Cells! 2.0.

Additionally, Cells! 2.0 allows quick rendering of either entire patterns or specific tracks within patterns from your existing songs. Only the instrument of the first note within the pattern track will be saved. It will automatically assign the correct beat sync values even if the original song is not written at 4 LPB. All rendered samples will be contained within an ‘Unsorted Cells! Renders’ instrument within the song to easily allow saving of all samples to disk. This menu is present in the pattern editor context menu.

Multiplayer Networking (beta)

Cells! 2.0 has built in support for up to four machines to link together over a lan (via OSC) and keep in sync. Make huge mixes across multiple machines or get some friends around and all play together. Setup network connections on the master and ensure Renoise OSC servers are running on all machines.

Minor improvements

- Variable channels from 4 to 16.
- Variable cells per channel from 4 to 16.
- Variable cell height and width (for touch screen usage).
- Automatic sample selection option (for waveform view in the sample editor).
- Safe cueing option to automatically mute cue output if set to the
same as the main audio output.
- Single output mode (splits the audio so master output on one
channel and cue output on the other).
- Slightly tweaked user interface to cater for the additional features.
- Better audio routing (A/B crossfader or crossfader bypass (M))
- Various other optimisations (too many to list)

Downloads

Download the updated 2.0 beta manual here (http://www.box.com/s/evt2vnpb51hzj6kic1zg). The XRNX tool will is attached to [the forum] post. Please ensure you read the manual, most questions will probably be answered within. Cells! 2.0 Beta requires Renoise 2.8 beta 7.

Download and forum post:
http://www.renoise.com/board/index.php?/topic/33947-cells-20-for-renoise-28-beta/

Let us know if you put this to use; we’d love to hear how it works (particularly network-synced jams). And, hey, there’s nothing stopping you from using this alongside a machine running Ableton Live – even on a Linux laptop.

For fans of slicing, dicing, glitching, reversing, and shuffling incoming audio streams, this Max for Live Device is for you. Shuffler 2.0 is the latest in a series of “modular” Max for Live devices from developer Isotonik Studios. Mappable to MIDI, the suite of Devices focuses on simpler tasks in ways that can be combined. There are interactive Follow Actions, for instance — a feature I’ve long argued should be native to Ableton Live — plus tools for more easily mapping MIDI to envelopes. There’s a convenient Looper.

From last week, there’s a module called Smart, capable of mapping some eight macros to one knob.

The entire series is sold as a subscription for 17 quid:
http://isotonikstudios.com/modular/

Check out the Follow actions in the video below.

In a marvel of DIY engineering, one intrepid user of the tracker-made-modern music making environment Renoise has reconstructed the basic elements of the Ableton Live interface. With quantized clip launching on channels and even a crossfader, it’s unmistakably a copy of what Ableton does. I don’t think you’d dump your install of Ableton for this; the whole reason you’d want a feature like this is really if you prefer other elements of Renoise that are different from Live. But as a proof-of-concept, it’s pretty extraordinary. (Ableton users, the ball’s in your court: someone want to make a tracker in Max for Live?)

mxb has more information on the Renoise forum:
Cells! Preview

We love the bleeding edge, but as mxb notes, “this is still at a very early beta stage; if anyone has any suggestions or feature requests, [they should] make them in the thread on Renoise forums.”

All of this is possible because of Renoise’s powerful scripting environment.

The Cells! video above is a bit primitive – mxb says it’s a result of poor screen capture software, which is also responsible for sync disappearing – but you get the idea. mxb has also built a four-oscillator synth called ReSynth, and previously-mentioned sample import.

http://tools.renoise.com/users/mxb [all of mxb's creations]
http://tools.renoise.com/tools/resynth

I tend to tune out when it comes to sample libraries, but here’s one that takes the scripting capabilities of Native Instruments’ Kontakt sampler to extremes. The Grid Machine line developed by Lindon Parker (Channel Robot) and distributed by LoopMasters brings to Kontakt the sort of grid-based, sliced-up sample manipulation we’ve seen in the monome community and in custom tools in environments like Ableton Live and Renoise. Using KSP, the scripting environment in Kontakt, these produce entirely-custom instruments that cut, chop, stutter, reverse, mix, trigger, sub-loop, re-trigger, and modulate. You can change speed, mute, skip, reorder, and play patterns, and even mix between loops.

Even before you get to Kontakt’s effects, this kind of work really challenges the notions of what people imagine a “sampler” or “loop library” to be. And that’s been true of the sample sound design community, generally – they can brew things beyond the expected boundaries of a sample. I could even see this becoming a performance instrument.

Now, for those of us not content to use existing loops, I hope we can somehow convince Lindon to explain how he did the KSP scripting work to make it all happen. Drum ‘n Bass and House libraries are £29.95 each.

Loopmasters: Channel Robot

Some House for those of you who weren’t into the DnB version:

FL Studio, beloved to its users by its original name “Fruity Loops,” has long had a Playlist mode that could be used to assemble simple live performances by jumping to sections of your music.

But a new alpha mode takes this mode far further. It’s still based on the Playlist, but can add clips dynamically – including Audio, Automation, and Pattern. While still in early testing, developer Image-Line has released some information about how triggering works, as well as the video above. And oddly enough, just like the video we saw earlier this week in Renoise, it employs a Novation Launchpad controller. (The impact of the monome on the market is really hard to overstate.)

More details from the developers:

Controllers

Keyboards – There are 12 Clips assignable to each Playlist Track (one octave of a MIDI controller per track)

Launchpad & Mouse – Unlimited Clips assignable to each Playlist track.

Other Pad based Controllers – Limited only by the number of MIDI note assignable pads

At the moment there is basic scripting to define extra pages on the launchpad, you’re able to define actions for buttons, among transport ones, notes & controls.

The CPU load is similar to the project as it would play normally.

Performance Mode [Image Line forums]

It’s not quite an Ableton killer – not yet, anyway, especially as it lacks Ableton’s unique Session View paradigm for working in this way. It’s even a bit short of some of the hacks we’ve seen for Renoise. On the other hand, if you’re an FL fan you should be able to make your performance plenty sophisticated – and since just trigger clips isn’t everything, you might also want to play along with an instrument or sing. And I could see this catching on. It’d be great to see something other than Ableton in live laptop performances. Variety is the spice of life.

Rating: very, very promising.

Previously (this week, no less): More Renoise Step Sequence Goodness: Launchpad + Lauflicht (Other Controllers, Too)

Thanks to Dario Lupo for the tip!

There’s a beautiful immediacy and tactile quality to hardware step sequencers. And there’s all the flexibility, convenience, and power of software.

Solution: combine them.

We’ve been following various custom creations for the music production tool Renoise – the latest being a lovely performance grid, and back in 2009, the beginnings of Launchpad grid sequencing.

You can thank Renoise’s powerful API, which allows its users to modify the way the app works with surprising ease (at least for the hack-inclined), all for free.

The latest is Lauflicht, an 8-, 16-, or 32-step step sequencer for the Novation Launchpad controller (or, alternatively, other controllers like the monome) and Renoise. What’s nice about it is, you can add as many tracks as you want, with whatever samples and instruments you want, but then trigger those steps from hardware. Now, this will appeal of course to those who want these kind of regular rhythms – I’m already anticipating some frustrated responses from our fans of non-duple rhythms and polyrhythms in comments. But if that is what you want, this looks fantastic.

The creator sells the tool for EUR24. How much that means to you is dependent, of course, on the stability of the Greek government. (Sigh.)

Side note: rockin’ domain name.
http://www.stepsequencer.net/

Via BrenMcGuire on CDM comments – thanks!

Lots more videos; check the site for the artist’s own techno tracks:

Writing code for music may still seem a remote notion to the vast majority of even geekier digital musicians, but as exemplified by the language Overtone, it looks very different than coding once did. Whereas sound code was once a type-and-render affair, new coding environments focus on live coding. They use elegant, lightweight modern languages that take up less space. And they can be surprisingly musical, coming remarkably close to just typing “play a c major chord.”

Not to say that you won’t look plenty geeky doing it — but, hey, if you can’t impress slash frighten your friends a little…

Using a brew of powerful free and open source tools, all available via GitHub and running here on the Mac (though any OS will work), contributor Sam Aaron walks through the program at top and demonstrates some musical examples. After the jump, a much longer screencast walks you through how to get up and running with the emacs text editor for live coding.

Key ingredients:
overtone @ github
emacs live coding @ github
supercollider for sound production
clojure, the language, modern dialect of lisp

Features, as described by the creators:

Overtone is a toolkit for creating synthesizers and making music. It provides:

• a Clojure API to the SuperCollider synthesis engine
• a growing library of musical functions (scales, chords, rhythms, arpeggiators, etc.)
• metronome and timing system to support live-coding and sequencing
• plug and play midi device I/O
• simple Open Sound Control (OSC) message handling

Note the MIDI support — code, like many other things on the computer, isn’t very tangible. But you can quickly go to MIDI or OSC for some hands-on control of what you’re making. I have to say, some of this is quite a lot easier and less abstract than what you see in a Max/Pd-style environment. We’re blessed to have such choices in music making. Let us know if you try it out.

More videos and screencasts from this Cambridge-based artist:
Sam Aaron on Vimeo
http://twitter.com/samaaron

CDM’s Matt Ganucheau contributed to this story in San Francisco.

If you just want to fire up Renoise, the modern tracker/music production app, and not worry about the fact that its innards are hackable, you can. But for a reason why you might at least want to explore customization of this music tool, give the video above a look. It starts sleepy and slow … and then, part of the way through, as creator Dac Chartrand starts demoing the tool, something really special happens. (Anyway, that’s what I think. See if you agree.)

Dac explains his work, completed at the recent Montreal Music Hackday:

My Renoise hack was Grid Pie. One of the new trends in our community is the concept of a meta-interface. In essence, programmers use the Lua API to transform Renoise into something else, hide the Renoise window, and work with hardware interfaces connected to their own scripts. Three current examples: MPE, Step Sequencer Lauflicht and Duplex. Grid Pie is “yet another meta interface.” It turns Renoise into a live performance audio recombination machine. Still in alpha, but people were into the demo I gave. I got a lot of handshakes and positive feedback.

It’s an alpha, so your mileage may vary, but I’ll bet this whets some appetites for people who hadn’t yet realized the power of the Renoise API.

http://wiki.musichackday.org/index.php?title=Grid_Pie

MOTU’s MachFive sampler, while perhaps not getting the kind of attention rivals from NI and Steinberg have, has had in its history some compelling features. Those features were in a multi-window interface, though, that not all of us loved – while I can’t find the review, I know when I covered it for Keyboard, I praised powerful editing features like the slicer but lamented the UI.

MachFive’s new UI looks radically different. The tabbed layout and modules and preset browsing all recall NI’s products, but there are new twists, too, like slick, readable waveform views, gorgeous EQ visualizations borrowed from MOTU’s DP DAW, and plenty of shiny. The results look far more usable, which means easier access to new sonic capabilities. And that’s good news, because it’s those features where things get interesting. Just a few highlights:

• Granular stretching and re-pitch sounds, licensed from IRCAM. I’m fairly certain this is the first time I’ve seen the Paris research center as a specific bullet point in product promo, but there are samples that sound terrific.
• New scripting which MOTU touts for modeling things like strumming and fingering on guitars – and lots of other things, too. New sound content will take advantage of the scripting features. And, oh, yeah, if you’re thinking that scripting is available elsewhere, CDM’s nerdier readers will like this: the scripting engine is now in Lua.
• Hybrid synth engine covering wavetable, subtractive, and FM synthesis. Earlier today, readers were talking about disappointment that Omnisphere, the massive sample-based synth, lacked samples. Well, here you go – here’s one strong sample/synth hybrid contender. (Omnisphere’s another animal, but that doesn’t make this any less interesting.)
• Modular effects architecture, convolution reverb mean greater ability to apply effects, from buses to individual oscillators and keygroups.
• Oberheim-style Xpander filter.
• Tons of ready-to-use MIDI scripting.
• Powerful arpeggiator and micro-tuner.

You also get 45 GB of sound content (wowsa), full-screen mode, an updated slicer/looper, and expansion of MachFive’s already-extensive support for third party samples, even including obscure old formats.

I’m intrigued: the intelligent new layer rule interface, the overhauled UI and sound engine, and then extensive micro-tuning and Lua scripting start to make me interested, even with intense competition in this arena. For experimental sound design, there’s some real potential here. Stay tuned.

In the meantime, pictures:

More:
http://www.motu.com/products/software/machfive/

http://www.motu.com/products/software/machfive/technology.html