As Max for Live has matured, this tool for extending the functionality of Ableton Live has played host to a growing wave of brilliant custom tools – enough so that it can be hard to keep track. This month saw a few that deserve special mention. In particular, two tools help make MIDI mapping and automation recording easier in Live, and point the way for what the host itself could implement in a future update. (Live 9, we’re looking at you.) And in a very different vein, from Max for Live regular Protofuse, we see an intriguing alternative approach to sequencing.

Clip Automation does something simple: it patches a limitation in Live itself, by allowing you to record mapped automation controls directly in the Session View clips. (As the developer puts it, it grabs your “knob-twisting craziness in Session View.”) The work of Tête De Son (Jul), it’s an elegant enough solution that I hope the Abletons take note.

Clip Automation

Mapulator goes even further, re-conceiving how mapping in general works in Ableton – that is, how Live processes a change in an input (like a knob) with a change in a parameter (like a filter cutoff). Live does allow you to set minimum and maximum mappings, and reverse direction of those mappings. But the interpolation between the two is linear. Mapulator allows you to ramp in curves or even up and down again.

There’s more: you can also control multiple parameters, each at different rates. And that can be a gateway into custom devices, all implemented in control mappings. BentoSan writes:

For example, if you wanted to create a delay effect that morphs into a phaser, then cuts out and finally morphs into a reverb with an awesome freeze effect, you would be able to do this with just a single knob…

Again, this seems to me not just a clever Max for Live hack, but an illustration of how Ableton itself might work all the time, in that it’s a usable and general solution to a need many users have. Sometimes the itch Max for Live patchers scratch is an itch other people have, too.

Lots of additional detail and the full download on the excellent DJ TechTools:
Mapulator: An Advanced MIDI Mapping Tool for Ableton

Protoclidean We’ve seen Euclidean rhythms many times before, but this takes the notion of these evenly-spaced rhythmic devices to a novel sequencer. Developed by Julien Bayle, aka artist Protofuse, the Max for Live device is also a nice use of JavaScript in Max patching. See it in action in the video above. There are custom display options for added visual feedback, and whereas we’ve seen Euclidean notions in use commonly with percussion, the notion here is melodic gestures. Additional features:

• Eight channels
• Independent pitch, velocity, and offset controls
• Scale mapping
• For percussion, map to General MIDI drum maps (Eep – darn you, English, we’re using the word “map” a lot!)
• Randomization
• MIDI thru, transport sync, more…

More information:
http://designthemedia.com/theprotoclidean

Also, if you’re looking for more goodness to feed your Live rig, Ableton has added a new section to their own site called Library. You can find specific Max for Live content in that area, as well:
http://www.ableton.com/library
http://www.ableton.com/library/tags/mfl/

This is in addition to the community-hosted, community-run, not-officially-Ableton Max for Live library, which is the broadest resource online for Max for Live downloads:
http://maxforlive.com/library/

Truly generative musical scores in games have been few and far between, and “music games” has traditionally meant arcade-style rhythm games in which you repeat phrases or whole songs as accurately as possible. Pugs Luv Beats breaks those molds. Part of a vanguard of new gaming creations that generate dynamic music on the fly, it marries grid-based sequencing and resource-gathering gaming, as music making and gameplay blur together. The interactively-produced music could itself become a new way of delivering a musical signature with sound packs.

And beneath it all lurks a free and open source library, libpd – the embeddable version of tried-and-true free graphical music environment Pure Data. (That library is now on GitHub, and vastly updated, by the way, and we’re expecting a book soon from the library’s principle author Peter Brinkmann.)

Oh, yeah, and don’t forget about some seriously addictive gameplay and adorable pugs. I’m suddenly not concerned about the 15 hours Europe-to-North-America travel I’m doing tomorrow.

Here’s what the gameplay looks like, since it’s much easier to see:

Pugs Luv Beats was just approved on the iTunes App Store for iPhone and iPad.

Co-creator Yann Seznec (The Amazing Rolo) is a terrific musician; I just caught up with him in Edinburgh and Berlin and watched him play a homebrewed pig gut instrument with Matthew Herbert for the performance piece “One Pig,” on tour at Berghain. Working with Pd allowed Yann to focus on those musical impulses and not just engineering, and to let him try things he otherwise would never have imagined on a mobile title. So I asked Yann to walk us through how the project was built. He responded with an exhaustively-detailed examination of the evolution of this title, right down to the Pd patches. (Click through for high-res versions.) If your New Year’s Resolution is doing something with patching, you might want to hang onto these answers. Here’s Yann:

The origins of Pugs Luv Beats date back about two years. After making [musical iPhone game] Mujik, Jon (Jonathan Brodsky, aka jonbro) and I were trying to think of other approaches to music mobile app design, and we started thinking more and more about games. Music games, as a whole, are an oddly passive and traditionalist experience – you play along with a premade track, and you are judged on your accuracy and flair (which is strangely reminiscent of music conservatory mindset…). Obviously there are exceptions (RjDj’s Dimensions, Elektroplankton, etc.), but there you go.

Particularly interesting to me was the idea that game mechanics are often very similar to compositional techniques. So for example, when Sonic runs at a normal speed he collects rings at one rate. However when he powers up and goes super fast, he collects rings at a much higher rate. This could be compared to introducing a melody and then speeding it up – and when there are two players, doing this with two melodies. Instant fugue!

We started looking at how we could make a music game where the music and the game elements were fully intertwined and augmented by each other. So Jon prototyped a space shooter drum machine. It was awesome.

To make a (very very very long and boring) story short, our idea and prototype landed us some funding from Channel 4 and Creative Scotland to work on games that focus on musical creativity and composition.

For various reasons, we decided to put aside the space shooter drum machine for a while, and start from scratch. After going through several full prototyping iterations we eventually settled on a core game mechanic that turned out to be in many ways similar to a Tenori-on [Yamaha grid instrument]/Boiingg-style [monome hardware patch] music generation system – in our final prototype, you controlled a series of little dots that moved around the screen, creating loops. This is super fun from a musical perspective because it’s easy and rewarding within a few seconds, and when you have several loops going it can gain some pretty serious rhythmic and melodic depth.

The key from there for us was turning this into a game. We had been using free Internet graphics packs up until then (we hadn’t hired our artist Sean yet) which featured a ladybug, so we had been referring to the main characters as ‘bugs’. During some discussion one of us accidentally said ‘pugs’, and the game idea was born. We constructed a story about pugs and their love for beets (like the vegetables) which create beats (ha!), and how their love turned into greed and got out of control, destroying their world. The game, therefore, is about helping the pugs rebuild their lost civilization by guiding them to create beats. You grow your galaxy by collecting beats, which you do most efficiently when you dress your pugs up in costumes. What’s not to like?

To get to the part that I imagine CDM readers are most interested in, the app development was done by Jon using openFrameworks, [lightweight language] Lua, our own game engine called Blud, and the audio is all done in Pure Data using libpd (through ofxPd). In hindsight we started using libpd really late in the game, just at the very end of the prototyping stage, which was rather silly. Our adoption of libpd basically made our dev cycle about a million times more efficient. My background is as a musician and sound designer, and I have very little coding knowledge. I do, however, have lots of knowledge of Max/MSP, so picking up Pure Data was pretty easy. This allowed Jon to completely pass off all the audio processing (not to mention aesthetic sound design choices) to me, saving him loads of time, giving me direct control over the sound, and letting me test and prototype different approaches to audio within an environment that I knew would be recreated in the game. Also, as Jon mentioned to me recently, by using PD we are able to take advantage of 20 years of audio DSP research and development. Pretty amazing.

How it all works:

The entire audio engine is contained within this patch. Pardon the messiness.

The simplest part of the patch is the “sounds” section, which is used to playback simple sound effects, for the most part linked with interface actions in the game. I did this by creating a very simple patch which plays a sound when it receives a bang. Which sound it plays is dictated by the argument (in this case, the sound of discovering a new capsule). The process for adding a new sound, then, is as simple as adding the sound file to the /assets/sounds/ folder, and making a new instance of “sounds.pd” and naming it the same as the new sound. Jon, in the project code, created a list called “sounds” which is sent into Pure Data. When that list contains “capsule”, a bang is sent into that subpatch, and the sound is played.

A more complex version of what could be done with this type of data is seen in the voice of Mr Puggles, who helps you learn how to play the game. Mr Puggles pops on and off the screen to guide you through the first few worlds, and when he does he send Pure Data a “puggleShow” and “puggleHide” signal. I wanted to give Puggles a funny synthesizer voice that was different every time – dead simple in PD. To do that, I take the puggleShow bang and use it to trigger five more bangs, spaced out over a second. Each of these bangs triggers a random number which is translated into a MIDI note. This note controls the pitch of two oscillators (a sine and a sawtooth), one of which is slightly modified to make them slightly different pitches. These are played through a short volume envelope and a filter which is also controlled by a random number generator. Result? Hilarious beeping boopy Mr Puggles voice, all coming from one bang.

Every time a player buys or selects a planet, a short list is sent to Pure Data comprised of the planet BPM and a random number seed. The BPM is used to calculate delay times and such, and the random number seed is used to create a sort of musical identity for the planet. This is done by choosing a “beat library” and a musical mode.

The mode is created by building a lookup table that chooses the notes from a chromatic scale that would be used in a particular mode. For example, a major scale (ionian mode) uses notes 1, 3, 5, 6, 8, 10, and 12. Each melodic sound library I used is comprised of a full chromatic octave, and the notes that are played on any given planet are controlled by this table. This ensures not only that all of the different sound libraries being played on a planet will be in the same key, but also that a planet will have a strong melodic identity.

The sound libraries in the game are all controlled by the pugs on the planets. As they run around, each time they land they will trigger a sound. The type of sound is dependent on what terrain they are on – thus, if they run through the snow they play a toy piano, if they run through lava a distorted guitar, etc. There are two states of playing the sound, one if the player deliberately tells the pug to go to that tile, and the second if the pug is traveling over that tile to get somewhere else. It’s super easy to do that kind of thing in Pd; just set up two different ‘play sound’ envelopes, maybe a little extra delay or reverb, and you’re done!

The final piece of the puzzle for making the pugs running around into music is to make each tile be a different note. The terrain of each planet is created by making a sort of height map, where different heights correspond with different terrain types (grass, water, snow, etc). This also means that each tile has a unique number between 0 and 1. When the player buys or selects a planet, a giant random number table is generated in Pure Data which creates a number between 1 and 13 for each possible value between 0 and 1. That value is what is used to pick the note of the mode. This somewhat convoluted approach again lets us make sure that each planet will have a unique, but fully reproducible, musical character.

The actual playing of the sounds is probably the messiest part of the patch structure. Purists look away now.

I wanted to make sure this part of the patch was as flexible as possible, so I ended up using the soundfiler and tabread~ objects, rather than tabplay~, which is great in practice though does look rather uncouth. Additionally, I had some limitations imposed upon the structure of the patch – namely, I had to keep the number of tables down as much as possible, to save on memory. So each sound bank has two voice polyphony – there are many sound banks, and the beats and sound effects aren’t counted in this, so that limitation is not really heard in the final product at all. It did mean I had to work out a decent voice allocation system though!

I think my memory issues were probably my only problem with using PD in this project – though only indirectly. As I mentioned, they were hardly a problem artistically, however it took me a while to get used to the idea that not everything I patched on a computer would work on an iPhone. Similarly, I had to be very careful about things like relative volumes. In a generative music game like Pugs Luv Beats, the player could quite easily send 15 pugs running around making sound, which mounts up pretty quickly. It means that all of the patches and sound need to be designed to withstand lots of triggering without distorting. None of these things are problems, really, all they require is regular testing on devices and simulators – something that every mobile developer is already used to.

That’s the Pure Data audio engine in a nutshell. The end result is a flexible and powerful audio engine that sounds really great and is fully integrated into Pugs Luv Beats. The game is a great combination of music, silliness, and strategy – there’s a bit of something in there for everyone. You can definitely just play with the game to make beats, or you can try and collect all of the costumes, or you can try and make the most efficient planet ever. You can also explore the galaxies being made by your Game Center friends, to hear what they’re up to.

The background story:

And, just for fun, a silly promo featuring real pugs. Anyone traumatized by the sight of Pd patches, these should relax you.

More information at the developer site:
http://luckyframe.co.uk/pugsluvbeats/game.html

Global availability of music may not have silenced the usual gripes about musical quality and diversity, even if they should. But the Web is providing a place for people to share music with other music-making enthusiasts, sharing the craft of constructing it with the relish of chefs talking over drinks at the end of a long day.

Anyway, that’s my excuse for mentioning fellow blogger, music software developer and musician Chris Randall, again. I’ve been thoroughly enjoying the meticulously-concocted sounds of his new micronaut EP, Particulate. Ticking away leisurely, with thick alphaSyntauri pads set against cool, understated metrical rhythms, it’s the as though the machines themselves are enjoying a calm weekend afternoon.

On the Analog Industries blog, more description

Chris admits something I’ve been hearing increasingly in whispers among producers from a wide variety of genres – he’s getting away from the DAW. The dominant computer software model, even in more restrained incarnations like Ableton Live, still involves an overwhelming set of tools and sequencing apparatus that can get you away from, you know, actually playing your machines like instruments. Instead, Chris uses “good old-fashioned playing,” and gating from analog outputs from an Apple IIe-based sequencer. It’s nothing new (quite literally so, as the gear is from the 80s), but it’s a discipline to which I hear many producers return again and again. (I got to read them talking about it in the 80s and 90s, too, as I edited old Keyboard stories for an upcoming book – sometimes you have to turn the sequencers off and focus on really playing the machines. Think that bit in Star Wars with the flight computer.)

The gear:
Roland CMU-800R + Apple IIe (kids, ask your parents)

alphaSyntauri, also based on the Apple II

Korg 770, which has the best vintagesynth.com description ever: “Aside from being very old, there isn’t much else to say about the 770.” Assuming I take care of myself and survive to be a senior, this is I hope what I can someday make my epitaph.

Korg MS20, about which much could be said

Euro-Rack modular

Korg Monotribe

iPad running Curtis (granular app) + Alesis iO Dock

Lexicon M300 (now-discontinued hardware reverb), and ValhallaRoom and Chris’ own Eos, as reverb

I love the polish of the EP, but it’s also revealing to watch Chris tinker with his rack of gear, as in this more recent image:

By the way, for my part, I’m also enjoying not sequencing materials. If you don’t want to go to tape, you can take the same approach in any software. Hanging out with King Britt in his studio, he tracked live playing and CV-gated sequences into Ableton Live; I’ve taken to using Propellerhead Reason (formerly Record) for the same purpose. (Hint: that absence of MIDI output? It’s not a bug, it’s a feature.)

All of this is relevant, as there’s a big Synth Meet tomorrow in Los Angeles put on by those connoisseurs of analog, the blog (and sometimes-artists’-collective TRASH_AUDIO. And certainly the idea of investing in all this shiny is, eventually, to actually make something resembling music with it. Chris, look forward to seeing you tomorrow.

Also, fans of alphaSyntauri — I’ve been watching this growing, open group on Facebook devoted to that instrument:
The Alpha Syntauri Group

They point to a big load of documentation someone has collected.

Now I’m nervous, because typically when I ramble on about something like this, commenters get angry. It’s a Friday. Don’t hurt me. Go listen, and if you don’t like it, it’s a Big, Wide Internet. In fact, go make something.

The tablet – or at least the iPad – is beginning to look like a terrific accessory for lovers of MIDI and hardware. With its compact form factor, it coexists nicely with your MIDI gear and lets you focus on sequencing, perhaps moving to the traditional computer to finish up your track, mixing, and the like.

And it’s spawning MIDI sequencer apps that imaginatively explore ideas for how to create sequencing, all with an immediate touchable interface.

The latest entry: Genome MIDI Sequencer claims to be the “first true pattern-based MIDI sequencer for iPad.” The word “true” might be debateable, but it looks thoroughly full-featured, with clock sync, MIDI import / export (ideal for working with your desktop Mac or PC), and other must-have portable sequencing features:

• Hard-line MIDI support: Core MIDI, Camera Connection Kit, Line 6 Mobilizer Mk I and Mk II compatibility
• Wireless MIDI: Network MIDI support (works with Mac and, via other support, Linux and Windows)
• MIDI Clock: Start, stop / send, receive
• Lots o’ messages: Note On, Note Off, Pitch Bend, Aftertouch, Channel Pressure and CC’s
• Pattern-based; pattern changes occur on bar boundaries so song stays in sync Ed., oh, come on, where’s the fun in that?
• 16 simultaneous tracks, unlimited patterns

There’s also an on-screen keyboard interface (in case you don’t have a MIDI keyboard handy), song and live modes, incoming CC and note recording, and undo/redo for “most” actions.

Having the multichannel capability alone is a must for people with big studios.

Developer Dave Wallin says he’s been working on this for some time. An experienced dev with tools like bleep!BOX and bleep!Synth under his belt for iOS (as well as Additive and Zero Vector for desktop), he’s got a good perspective on the bigger picture.

Since Dave is a user as well as a developer (as is often the case with music tech), I asked him to tell us a bit more about the app, his thoughts on development, and how you might use this.

He even has some good thoughts, in case you’re wondering, about how this compares with and fits in with desktop studios.

CDM: This looks to me to be the most full-featured MIDI sequencer we’ve seen yet, more than just a pattern or step sequencer (though I like those sorts of things, too). That said, what other applications do you like in terms of MIDI control?

Dave: There are a couple other apps that look close in terms of functionality like Step Poly Arp, Polychord and Brainwave Sequencer. The first two are more focused on ‘performance’ imo with Brainwave being the closer. I wanted to provide some of the functionality you’d expect from a desktop sequencing app but redesign the core interface around touch and just make it simple and fun to use. My inspirations for how the piano roll works are 50% monome / [Yamaha] Tenori-on (in terms of a familiar grid and easy one-tap note entry) and 50% iPad paint application (in terms of using gestures to navigate). It also takes some inspiration from [Nintendo] Game Boy tracking apps in that I keep the octave / bar navigation locked to a grid. GMS isn’t locked into 16 step patterns and you can adjust the grid and bar length more freely than some other apps.

Ed.: Of course, at iPad app prices, you can easily pick up all the apps above, and they all have some appeal – yes, I know it’s time for another iPad app round-up. A MIDI-specific one could be fun; I’ll work on it! -PK

How are you using this in your studio – what gear are you using?

Right now I am using it with my [Access] Virus b (desktop [synth]) and a drum machine primarily. It’s great with the Virus since it can do up to 16 parts and I can save these setups and easily recall them later without having to worry about program changes or anything like that. The drum machine saves me from having to waste Virus parts on drums. With just those two pieces of gear and not much else I can make some pretty decent sounding songs. My current work flow is to jam around a bit with Genome and the gear and when I come up with something good, record some loops or tracks it and bring it over to the desktop for additional processing and arrangement. My actual studio doesn’t even have a computer in it at the moment – it’s in a totally seperate room.

At what point do you imagine people would use the iPad sequencer versus, say, the sequencer on their desktop machine?

What I have learned from my own experience and from talking to other people is that the iPad is not a total replacement for the desktop or even for a laptop, unless you’re doing some very minimal stuff. The iPad is more of a convenience and leisure device at this point. I have limited time to relax and if I can spend 30 minutes chilling on the couch, making a tune on my iPad, it’s a win for me. It doesn’t have to be a whole song – it could be some musical ideas, sounds or loops that I end up using later on the desktop or in another app.

With Genome, I think the big wins are portability and ease of use. If I want to jam with a friend, I can throw my iPad in a bag and bring it with me. Sometimes I don’t want to have to deal with all the overhead that comes with a desktop sequencing application like hardware setup, configuring plugin directories, or GUI’s that are packed to the brim with controls. GMS is very easy to plug in and get started within a few seconds.

I’m curious about your reaction to the Open Music App Collaboration Manifesto posted recently. [See Synthtopia coverage.] Any of these issues relevant to your work? What would you like to see in terms of inter-app integration?

I actually just posted some thoughts on this to their Google Group this morning. My response is here:

http://groups.google.com/group/open-music-app-collaboration/browse_thread/thread/75cdd385048fa3ce

Communicating with other apps on the same device is something that I think Genome will be very good for (after some minor updates). Right now, not a lot of apps support Network MIDI, let alone regular CoreMIDI. How well this works will depend on a lot of factors and we’ll just have to wait and see how extensively it’s adopted, both by developers and by users. I could imagine an ecosystem where you can string a bunch of apps together and make songs. The first step right now is to come up with a spec for developers to implement and maybe a way to certify that apps have implemented it properly. If done well, I think there could be some good cross-promotion opportunities to entice developers to do it and it could catch on, much like with Audio Copy did.

Had you evaluated Android at all, or other platforms?

Some work is being done to port libNUI [C++ framework] (which I use for all my apps currently) to Android, however it seems the state of MIDI on Android is nowhere near what it is on iOS. If some well known hardware makers make an accessory or if a good SDK becomes available, I would definitely look into it. GMS is being ported to a Mac desktop app and will be available in the Mac App Store at some point. The desktop version will be almost identical, except for some changes made to adapt it to work with a mouse, instead of multitouch. I think a simple, cheap MIDI sequencer will be attractive to some people and the amount of time to port it is minimal for me.

Ed.: Hopefully more to say about the state of Android MIDI soon; while wired accessories may not be as convenient, wireless MIDI, especially via Bluetooth, holds some promise. I can certainly make a good argument *against* a developer immediately rushing to support Android, but it remains something we’re watching. I also hear these computer things can do MIDI. -PK

US$12.99 in the iTunes App Store, for iPad (iOS 4.2+)

http://www.whitenoiseaudio.com/apps/genome-midi-sequencer/

http://www.whitenoiseaudio.com/

Numerology is a sophisticated Mac modular step sequencer, capable of brewing patterns from simple to elaborate using combinations of note-making building blocks. It’s also a powerful host, opening up signal routing and modulation to AU plug-ins.

Version 3.1, released this week, may be a “point” release, but its two additions are significant. First, it’ll run as a VST plug-in in any host, which adds direct MIDI routing from plug-in to host. (Somewhere, plug-in developers are nodding, knowingly – AU may be more commonly associated with the Mac, but VST can be a better choice even for Mac users.)

Second, as you can see in the video, you get some tasty new real-time pattern recording modules. Out of the box, they’ll run easily with Novation’s inexpensive Launchpad controller, though you could adapt them to other controllers, too, if you wished. Check out the video to see it all coming together.

Description:

Numerology’s updated Launchpad mapping with realtime pattern recording into the DrumSeq, PolyNote and MonoNote sequencers. The laptop is running Ableton Live with three instances of the Numerology VST, as well as Camel Audio Alchemy for synth lead and NI Massive on pads. The drum sounds are from Numerology’s DrumKit module with a patch designed by Jason Wolf of Tripl3Tone.

All of this is yours in two editions:
Standard (US$129)
Pro (US$199) with multi-output support for hosted Audio Units, OSC support, custom scale quantization, and advanced modules

http://www.five12.com

Thanks to developer James Coker – and glad I can prod him to release videos with these software updates.

In our monster MeeBlip round-up the other day, I mentioned the stunning enclosure Michael Roebbeling made for his DIY synth kit. But that’s not all Michael has built. He’s also created a lovely, simple step sequencer with Arduino. It’s a beautiful combination of all open-source hardware, MeeBlip and Arduino. Surprisingly, it’s his first try at all of this:

After my first successful experience in electronics, building the MeeBlip, I was hooked. So I decided to buy an Arduino and dive a bit deeper. My first project was a rudimentary sequencer to work together with my MeeBlip. It took me 3 days to figure out the schematiks and code the program.

With projects like Arduino taking out some of the headaches of getting started, this is further proof that understanding computation allows you to do anything, from hardware to software, on any platform.

Michael’s project represents a simple, afternoon project, but the Arduino can also become the basis of more sophisticated gear – and some more complex groove-making. I’ll look at some of those options here, like Steve Cooley’s beatseqr, here making some grooves with an iPad running Korg’s iMS-20 soft synth and Reason running on the MacBook Pro.

There are plenty of Arduino step sequencer projects – it’s a nice project to try – but what I especially like is that Michael’s design is really minimal, meaning it could be a good starting point for your own project. He provides full code and (via a terrific prototyping tool called Fritzing), easy-to-read, colorful schematics.

If you’ve never done this before, some basic knowledge of how to read the parts, an Arduino, and some copy-and-paste skill is all you need to get going. I’m going to set aside some time to build one myself.

SimplenZAR [Blog post documentation at Carvin' Calamari]

But while we’re on the topic – and since having step sequencers around is a terrific tool for making musical patterns with all your music gear – let’s take a quick look at what else is out there.

littlescale is a must-read for musical Arduino makings, so a good first stop. He’s got his full list of projects, including a microtonal step sequencer, seen below.

http://arduino.milkcrate.com.au/

Johan Larsby has a terrific project, complete with screen, with loads of details and source. You can build the whole thing for under $50 in parts, and his page is also a useful set of references to working with MIDI, physical controls, and the display.

Arduino Step Sequencer… ASS. Fine. Funny enough. But you lose out on bonus points for not making it a recursive acronym.

Mr Speaker goes through the process of how to construct MIDI step sequencers on Arduino in a blog post, as well.

That’s not a complete list, but now onto some fancier projects…

Steve Cooley’s beatseqr, created with Derek Scott, evolves from simple hardware “sketch” into full-blown, feature-packed sequencer, but it’s still got an Arduino (Mega) at its heart. Accordingly, Steve talks through the behind-the-scenes tech details on the Arduino forum.

And, oh yeah, it goes great with Reason. (That in turn means this and an older laptop could be a nice little groove station set up in a studio, to keep your machines out of the closet of retirement.)

Beatseqr v3 — arduino mega based step sequencer [Arduino Forum]

Official site: http://www.beatseqr.com/

And I would be remiss if I didn’t mention the awesome MiniCommand by Ruin & Wesen. It doesn’t in fact have an Arduino board inside, but it does use the Arduino development environment for a custom MIDI firmware framework called MIDI-CTRL. Say wha? Basically, you can use Arduino-style syntax to reprogram this little box to perform whatever MIDI magic you wish. It’s utterly insane, and perhaps a little overlooked because it’s generally associated with the Machinedrum. I’m not going to say any more now, as I know Wesen is getting some time off to work on it, and I hope to talk more about this project over the coming months.

http://ruinwesen.com/products

Result: Euclid pattern generators. (I’m working on some code that does something similar, with visualization; stay tuned while I … um, finish it, in fact.)

So there you go. If it seems overwhelming, just remember, take it one step at a time – and start with the first step. (Sorry, couldn’t resist.)

As I said, the place to begin is doing something like what Michael did – and you can hook up his project in a few minutes.

If you give this a try, let us know! Sounds like a fun weekend project.

The modular MIDI step sequencer for Mac, Numerology 3, gets a big update today, adding humanization, generative patterns, and an enhanced UI and functionality. That makes this a more powerful laboratory than ever for creating new musical patterns. There’s also now a budget “Standard” edition and more advanced “Pro” version, AU support for use as a plug-in with some impressive scheduling accuracy and low-latency MIDI support, and lots of new modules.

The basic idea of Numerology is to turn your Mac into a set of modules for assembling musical patterns, and now you can either make Numerology a (very powerful) host, or a plug-in in your DAW of choice. New in version 3:

• “Generate” and “Evolve” features use generative algorithms for creating and transforming patterns. You can even use them in real-time for ongoing mutations to patterns.
• OSC (OpenSoundControl) support in Pro
• Pro-only features: Route multi-output AUs, monophonic audio, custom scale quantization, and advanced sequencer tools like CV to audio for use with outboard analog synths
• Enhanced filters, envelopes, and modulation in the synth and drum kit modules
• New audio effects: tempo-synced delays, multi-mode filtering
• Better preset storage, now with a centralized Stack Library and per-module preset storage
• Included library of modules to get you started, complete with full examples and templates
• New 222-page manual

Five12′s James Coker is I think one of the more creative independent music developers out there; I really love what he’s doing with this tool. At a time when there aren’t a whole lot of new ideas about how to work in music production, Numerology is a really unique take, and worth considering for that reason.

Numerology AU already works in Ableton, Logic, and MOTU DP, with more hosts coming soon. That makes this now a must-have addition to any Mac music setup, period – it’s looking insanely powerful.

Intro pricing is available through January 9; upgrades from US$34 and full releases for $119-184. (The Pro version doesn’t cost much more, so that may be a no-brainer for most Numerology fans.)

http://five12.com/

Brian Eno should be proud. Generative sequencing – making lovely, shimmering music mapped to pleasant-sounding modes – is totally in this season.

At top, exhibit A: Aura Flux, a new iOS ambient music generator. Priced at US$1.99, it nonetheless packs some 48 different instruments, ambient sounds, four keys, save/load capability, and multitasking support. Sequences are arrayed into editable nodes: touch and explore, or tweak specific settings like pulse speed and decay, trigger rates, and pitch to get the results you want.

Generative music has a key advantage for mobile devices, too: it doesn’t take up as much space. In the case of Aura Flux, the whole thing fits in 8 MB.

Apart from the lovely-sounding tunes, what you get is, notably, also more rhythmically complex than in more traditional sequencers, owing to the open-ended manipulation of nodes across the two-dimensional surface. That’s a prime difference between Aura Flux and some of the similar sounds that came out of Yamaha’s Tenori-On; with the exception of a mode or two, Toshio Iwai’s design was intentionally grid-focused, for more minimal, symmetrical rhythms.

Aura 2: Flux @ iTunes
Developer site

In another take on alternative sequencers, our friend Ted Hayes has presented a new video of his Neurohedron. Rather than array steps across a series of rows, as sequencers have done since the days of the Moog Modular (or earlier), steps follow the faces of a dodecahedron, allowing non-linear progression through tones. Ted showed this project at our own Handmade Music in August, as a couple of us accompanied him on piano, as well as on the In/Out Festival. The patch is Pd/Pure Data.

In a way, you can think of the looped step sequencer as a circle — it progresses from the last step back to the first step. In this case, you take that one-dimensional loop and allow it to branch in two dimensions around the faces of the dodecahedron. People are definitely awed by the sculptural aspect of this when they see it in person. Let us know if you have specific questions for Ted and I’ll see if he’ll answer them for us.

http://www.geekdown.com/t3db0t/
New video via Synthtopia

Neurohedron: Overview from Tedb0t on Vimeo.

For centuries, music has had scores as visual representation. Now it has visual interfaces in software, too. I know from our in-progress platform survey that most of you don’t own an iPad. (At the moment, I’m with you.) But that makes me doubly hopeful that what we get in music software design in general is a renewed interest in visual culture and interface design.

Loopseque is a new, US$4.99 circular-sequencing music app, and it conveys what happens when you really build an interface entirely around touch. It’s also a gorgeous example of why doing a good job of documenting your software can help convey its significance. (The photos this crew has assembled are beautiful. And why not? We have plenty of photos fetishizing analog gear. It’s about time software got its turn. Ask a photography stylist why it’s important some time.)

Even in its first release, Loopseque looks like a usable app. It’s a 32-step circle sequencer at its heart (note how efficient the circle is versus the rectangle). In the demo video seen here, this is kept pretty simple, but each of the four “channels” can have 9 wheels. (There’s an expandable “matrix” of wheels in which you can swap between them, in addition to the simple 4-channel swapping you see in the video.) The first release comes with a variety of sound sets for different genres.

The developers are a group of musicians and artists whose past work goes well beyond apps, into, they say, everything from events to ceramics to Yorkshire terrier breeding.

It’s actually the coming versions that I think may be most useful musically; an upcoming release promises user sample sets and track recording, so you can really make this your own. (They also tease something called “master classes.”)

For now, you can save and manage projects, mute and enable channels, and play around with the variety of included sample sets. And… does anyone else hear the words “Death Star Approaching” when you look at this interface, or is that just me?

I have a fascination with circles; I’ve personally even played around with various circular sequencer prototypes as Processing sketches, including a couple that looked a bit like this. So I was very interested to see how this team solved some of those design problems, and how they felt about circular sequencing in general. Loopseque replies to CDM:

Many genres of electronic music are based on loops, repeating sequences of sounds. The basic idea behind Loopseque is to visualize loops with circles, because a circle perfectly reflects the repeating structure of loop music. After we realized this simple thing, we spent many months experimenting with form and code.

Soon we realized that this visualization opens up really powerful perception of music patterns, and enables immensely deep connection between the musician and the structure of the music. In fact, this simple interface makes it so easy to create rhythm patterns that you can do real-time while music plays and that gives you many abilities for improvisation.

Another concept behind Loopseque is the ability to quickly change between patterns, which is implemented with innovative interface that we call “Wheel Matrix”. It’s also easy: First you prepare several patterns for each instrument and then, in Wheel Matrix mode, you can switch quickly between them.

Wheel Matrix opens up another new dimension for improvisation, because patterns are changed immediately, and that gives you an ability to combine different parts of patterns in many ways. And of course, you can change patterns on different channels simultaneously, since Loopseque is a very multi-touch friendly app!

I will say – back to the fact that this isn’t just about the iPad – there are a couple of lessons here. With more touch platforms approaching from various vendors, designing around touch is essential. And if you are creating new software, going to the time to document it is more than good PR. It’s a way to reflect on the aesthetic of the object you’ve created. For the same reason that a piano or violin is a beautiful object, sometimes in ways that aren’t directly acoustical, why shouldn’t we make the visual representation of our music evocative?

http://loopseque.com/
iTunes link

All images courtesy Casual Underground.

Like well-stocked studios of hardware, software has become personal, idiosyncratic, and stuffed with functionality. Computer producers are passionate as always about what works. And that has made FL Studio a kind of subculture all its own. Image-Line has a unique way of encouraging loyalty: while the company still peddles new add-ons to its existing customer base, the expansive functionality of the FL Studio program and all its major instruments and effects are included in lifetime free upgrades. FL Studio is a program you buy once that keeps getting better, without the usual upgrade purchase treadmill.

So, when we talk about everything that’s new in FL Studio 9, or FL Studio 9.1, released last week, those improvements are free to existing users.

You can read my review of FL Studio 9 for Keyboard Magazine:

It’s a strange thing that the word “toy” has come to have negative connotations in music tech. Apparently, we want our music tools to be big and powerful, like a chainsaw, ideally emitting manly gasoline fumes. But when we talk about music, we use the word “play.” FL Studio is nothing if not a toybox. But it’s a toybox in the best sense.

FL Studio 9 Review

FL Studio 9 introduces a number of improvements, including a Riff Machine (pictured above), which can dynamically generate musical ideas if you’re stuck for inspiration. Perhaps more importantly, the upgrade also delivers more intelligent routing and MIDI control, and a really gorgeous vocoder. (Yes, Reason, Live, and FL Studio now all have vocoders; what’s interesting to me is that they’re each quite different, true to the personalities of the three developers.)

FL Studio 9.1 adds still more, as you can see in the video above. There’s a brand-new drum modeling engine called Drumpad, which should couple perfectly with FL’s sequencing features. (It’d even go nicely with that aforementioned Riff Machine, for some complex, generative patterns. Ah, I think I know what I’m doing with my Saturday night now.) There’s also a real-time convolution plug-in, which sounds like a fun feature to abuse.

There are lots of additional videos on the FL forum, though true to form, I find this isn’t necessarily how everyone uses the program:

FL Studio Guru

Tips for Getting Started, with Jim Aikin

Jim Aikin has long been one of my favorite writers in this field; you can find his work in Electronic Musician, Keyboard, and others, including the lesser-known but superb Virtual Instruments. But, since working with him as the technical editor – slash – life coach on my book, I’ve also gotten to enjoy Jim’s emails, which are frequently themselves packed with knowledge, musical ideas, and perspective. Jim is a cellist, and as someone with a classical and compositional background myself, I appreciate that slant on things. (It’s certainly not what people typically associate with FL Studio.)

FL Studio is a deep tool – deeper than I think a lot of people appreciate. But it’s not always clear where to begin. Jim shares his own take on how to get started with the tool, creatively.

He writes:

My #1 tip would be this: Assign every Generator to its own mixer channel. (And name the mixer channels, so as to avoid confusion.) Then automate your levels by right-clicking the mixer faders and creating automation clips. (After selecting the part of the song where you want the gain change, of course.) The reason to do it this way is because then you can use the volume knob next to the Generator itself for _global_ changes in the level of that instrument. You never have to mess with re-editing tons of automation data in order to make a global gain change from one end of the song to the other.

Here’s another tip, which I learned by posting a message on an FL forum: By default, FL does not patch your mod wheel moves or aftertouch through to the 3rd-party Generators (softsynths). If you’ve selected a patch that uses mod wheel or aftertouch and you actually want to play an expressive line, this is annoying. But there’s an easy fix: Open the instrument’s edit window and select Browse Parameters from the menu in the upper left corner of the window. This opens the Browser, with a complete list of parameters. Scroll down. At the bottom of the list you’ll find all 128 MIDI CC’s, and also aftertouch. (The MIDI CC list does not appear with built-in plug-ins such as Sytrus and Slayer.) Right-click on the knob icon beside the mod wheel, select Link To Controller, and wiggle the wheel. Now the plug-in will respond the way you want it to.

Here’s another one: You can create your own quantization templates. Record a bar of regular 16th notes (or whatever) to a piano-roll, edit it to taste, Open up the piano-roll window’s File menu, and choose Save Score As. Save it in FL Studio > Data > Patches > Scores > Quantization. Now here’s the bonus tip: There’s already a long list in that folder. So that you won’t have to scroll down to find one of yours every time you want to use one, start your file names with an underscore (such as _Shuffle16th_32.fsc). They will appear at the top of the file dialog when you access it from the Quantize box.

And another: Learn the QWERTY key equivalents. When you hover the mouse over a tool button, the key command equivalent is shown as a dark gray (almost invisible) letter at the right end of the info bar, under the word HELP. I’m constantly switching back and forth from Select (E) to Draw (P). Then there’s the scroll lock key (important) and the fact that left Alt is not the same as right Alt.

Jim also shares a bit of how he uses FL in his own workflow:

I clone patterns a lot. But then, I’m a composer, not a loopin’ beatbox guy, if you see what I mean. I lay down a pattern that I like, and then I start to think, “Hmm … I need an extra hi-hat hit on the last beat in every other bar.” So I clone the pattern, delete the hi-hats from version 1 and everything else from version 2, then I put the hi-hat pattern in its own lane in the Playlist and clone it so I can alternate Hat #1 with Hat #2 in the Playlist. That would be a simple example.

The “Jump to next empty” command in the step sequencer is also indispensable, I find. When you’re in song mode and want to record something new, you almost always need to use that command before recording.

The grouping function in the step sequencer is nice. I usually group all of the percussion channels together, just to get them out of the way visually.

After adding a generator, go to the Channel Settings box and give it its own mixer channel routing (“FX”). This is a good habit to get into. With multi-channel VST plug-ins, the MIDI Out generator is absolutely essential — if you can’t figure out how to make this work, let me know, as it’s a little twisty.

Be sure to check out Slicex. It’s a killer plug-in for any type of sampled beat loop. A number of other plug-ins … just go down the Generators list and try them all. Beepmap is cool (it’s a postage-stamp-sized version of [visual/image-based synthesis tool] Metasynth), Slayer rocks, the Drumsynth is stupidly good for analog percussion, Wave Traveller is great for programming scratches, and you can do some fun stuff with the Speech Synthesizer as well. Oh, and SynthMaker … a complete programmable synth, under the hood. Some of the synths that ship with it aren’t that inspired, but SynthMaker is capable of doing many of the kinds of patches that Reaktor does.

The live mode features are not as extensive as those in Live, but they’re usable, I think. Check ‘em out.

And have fun — FL, in my experience, seems to make music fun again.

FL users, got tips we missed?

Has anyone created something with the included version of SynthMaker they’d like to share?

Other questions?

Let us know. And yes, we’ll keep calling it Fruity Loops.