The beauty of using touch for controllers is flexibility. Sure, you give up tactile feedback – but you can also quickly make your own layouts, make touch controllers an ideal complement to your existing hardware gear (the stuff with physical knobs and faders and pads).

For that reason, we’re all eagerly anticipating an upcoming version of the awesome OSC-based iPhone/iPod touch controller, TouchOSC.

http://hexler.net/software/touchosc

The included layouts are already fantastic, with rotaries and virtual buttons and multi-faders and toggles and X/Y pads. But custom control would be even better. Creator hexler writes CDM with the latest:

The long-awaited update to TouchOSC that will allow for custom layouts has just been submitted for review to Apple,
so I hope that as soon as next week it will be available as a free update to all users on the App Store.

Together with this release (1.3) there will be a free editor application to visually design and upload layouts to the device. You can take a look at the last beta version I published if you want, there’s both Windows and OS X versions available, but I will also prepare a Linux version as soon as possible, of course without the new version of TouchOSC this is but a preview of things to come:

http://dev.hexler.net/touchosc/touchosc-editor-0.7-osx.zip
http://dev.hexler.net/touchosc/touchosc-editor-0.7-win32.zip
http://dev.hexler.net/touchosc/touchosc-default-layouts.zip

And nicely enough, the editor is built in cross-platform Java, which I think makes a whole lot of sense. (Go Java, Python, etc., rather than getting stuck in hard-to-port platform-specific stuff like Cocoa.)

Thanks, hexler! I don’t have a video of the new features yet, so instead here’s a nice novelty – the beginnings of a creation using the free SuperCollider (which runs OSC natively) in combination with TouchOSC to make a custom step sequencer. Should fuel other ideas, too:

Fritzcrate Project / lusidLearn Early Demo from Michael Schieben on Vimeo.

Knobs and faders can be rigid. Fancy multitouch devices can be expensive. But for the cost of a webcam and some spare materials, you can build computer interfaces with objects around the house, thanks to the power of open source software.

In just one day, a group of artists in the CDM community, from Austria and Germany to New York to Australia, got quite a lot working with tangible interfaces. At top, Michael Schieben and Christophe Stoll experimented with using soda bottles to control software like Future Audio Workshop’s lovely Circle. (Ableton Live works, too – as does any MIDI software.) As Precious Forever, these guys are responsible for some of the best UIs in music software, from FAW to recent Native Instruments designs, so it’s lovely to see them experimenting with this idea.

As you add more people to the mix, you get ideas you might otherwise never have imagined, from a game involving blocks of the Tokyo skyline to an interface built into floor toms.

We also got a lot of real-world data on what works, what needs work, and what causes trouble for beginners, which we’ll be documenting. (Adam and Martin from the Trackmate and reacTIVision projects, respectively, were both tuned in to see progress and provided lots of help – and are also collecting that data to improve their own documentation and libraries.) More commentary on all these side benefits, as well as a discussion with visitors from Argentina on the scene around the world, at Create Digital Motion.

Musical Resources

We also got some really helpful tips for working with the free, powerful, tri-platform synthesis tool SuperCollider:
Charles Martin wrote up an easy SC test script for receiving Trackmate messages (and also had the clever idea of using a floor tom)

And for connecting Trackmate to MIDI and working with Processing, lots of tips are available on Michael Schieben’s noisepages blog:
http://fritzcrate.noisepages.com/

Get Involved

More documentation:
Tangible Interface Hackday: The Projects (So Far)
http://hackday.noisepages.com/

http://trackmate.sourceforge.net/
http://reactivision.sourceforge.net/

So, what’s next? You can join discussion and brainstorming for how to proceed, and how to get in on another hackday (formal or ongoing), even if you missed the first. Stop by the Tangible and Multi-Touch Interface group on noisepages:
Tangible + Multi-Touch noisepages Group

Our noisepages community is still in “alpha” state, but it’s usable – we’ve just fixed avatar uploading, which was the biggest problem. We’ll have more features, functionality, and improvements down the line, as well as more extensive documentation for how to get started. But if you’re a bleeding edge sort of person, join up free and give us some advice on what you’d like out of it.

I look forward to more work on these projects. Stay tuned for more, including some additional documentation (I’m developing some stuff around my own project).

Automap on other devices – and an iPhone as a remote control for your Live set? Our friend Ben Rogerson at MusicRadar have caught up with the chaps at Novation at a London trade show to have a look at Automap for iPhone. This app hasn’t yet hit the App Store yet – Hispasonic and the Ableton Forums got the jump on the story last month. But it looks appealing.

It seems to auto-detect the computer to which it’s connecting – as it should, folks, look up Zeroconf. (implemented on iPhone as “Bonjour”) And you can learn in both directions – so you can interactively choose parameters on the iPhone and decide what you want to control. It also sends MIDI to Live for clip triggering, though you’ll notice that some features on the APC40, like clip status and the ability to move through blocks of clips, aren’t possible here. Because Automap wraps around VST and AU automation parameters, you also get high-resolution control of plug-in parameters.

This should also open up possibilities for other Automap-supported apps, not just Live; I’ll be able to test this once the app comes out. No official word on availability or pricing other than soon and cheap. Before people start complaining about the tiny iPhone screen — yes, absolutely. But there’s a nice blank spot on the Novation controllers on which you could put your iPhone or iPod touch. Think about it: you can add an intelligent multi-touchscreen to your existing hardware, use your conventional gear for physical control, but keep the Apple gadgetry as an additional remote (now fairly cheap with no contract for iPod touch). You can even wander around the room during sound check while still controlling your set.

Update: I should note, as I just got asked on Twitter, most Wi-Fi adapters allow you to create your own Wi-Fi network. So you don’t need Wi-Fi in a venue. You’d just create your own network on your PC or Mac laptop, and connect via that – the iPhone and iPod touch both support connecting to these networks. (Note that not all devices do: the Android-powered TMobile G1, for instance, has a chip that apparently doesn’t support them, and I have an 802.11b/g USB adapter that won’t create them. But mostly, this is an easy matter.)

Cool as this is, and elegant as the work Novation appears to have done, I can’t help but notice this is still something of a kludge. The iPhone communicates natively over TCP/IP with the computer. That’s what this app is using – but then it needs a Rosetta Stone and another set of software on the computer just to untangle the archaic protocols music software uses (plug-in automation, MIDI, and more oddness heaped atop of MIDI). There’s absolutely no reason that music software couldn’t be intelligent enough to support networking protocols so that all software and devices can easily communicate. That wouldn’t put Novation out of business, either – on the contrary, it would allow them to do their jobs and this very app could be more productive. Instead of MIDI CC numbers, imagine if you could refer to clips by scene and position number, or even by clip name. Imagine if the iPhone displayed clip parameters and changed when clips were launched. Imagine no more drivers or software to install: someone who bought Novation hardware with OSC support could bring it to a friend’s place and work on a session without that friend installing Automap software.

(singing) You may say I’m a dreamer, but … (sorry, cough) actually this is all possible right now.

I’m all for solutions that work, and Automap (and M-Audio’s HyperControl) both have great capabilities now. But OpenSoundControl is also something you can implement now (provided hosts like Live will support it), and we’ll be talking more about what it can do over the summer to make it more practical and less abstract.

So, you’ve been looking at that Akai APC40. And it’s appealing. It’s got lots of lights and a huge array of buttons for triggering samples or video or what have you, and plenty of knobs and faders.

Now the APC40 has some serious “indie” competition, though, in the form of Livid’s Ohm64. Let’s compare:

APC40:

• Proprietary connection to Ableton Live
• A proprietary handshake that ensures only a real APC is being used with Live
• Fixed MIDI assignments – no MIDI assignment editor
• MIDI only
• No MIDI out jacks, so you can’t use it with outboard gear
• No bus power
• 40 buttons
• Made in some factory somewhere we’ve never seen

Livid Ohm64:

• Open source editor, partially open source firmware, open source patches to connect to whatever you want
• Custom MIDI assignments, for use with whatever you want
• MIDI for now, but the chipset supports open source solutions for OpenSoundControl (OSC) in the near future – and even DMX (for lighting) is a possibility
• USB and standard MIDI jacks so you can sequence outboard gear
• Bus power
• 64 trigger buttons in a more logical 8×8 array
• “Made in the USA by humans” – with a beautifully-crafted body
• Free Cell DNA video software included

Both the APC and Ohm are class-compliant, so at least neither needs drivers to work over USB for MIDI on Mac, Windows, and Linux.

Sure, the APC is plug-and-play with Live. But just as lots of non-programmers use open source browsers like Firefox, the whole point is that the Ohm could wind up being more plug and play with more tools thanks to its more open approach.

Ed.: Plogue Bidule is an unusual animal: this affordable patching tool resists conventional ways of doing things, down to its hatred of the number “1.0.” But Plogue has an underground following inside the already-underground world of modular patching tools for creative music. I’ve invited Primus Luta, aka David Dobson, to give us insight into this tool – including a new release that will be big news to the people who rely on Plogue to make their productions and live performances tick. -PK

Today if you go over to the Plogue site you will see the announcement for the latest release of Plogue Bidule. In addition to a number of bug fixes, there are some amazing updates in this latest release. On the eye candy side of things, Bidule finally gets a waveform viewer module — the WaveViewer shown in the image above. There’s also a new Audio Buffer module for visualizing waveforms. These are great additions to the Bidule arsenal and also a good indication of more visual goodness to come.

In its ever-growing commitment to fully support OSC [OpenSoundControl], a new tool has been added for monitoring OSC communication. The OSC Monitor behaves like many third-party options, showing not only the OSC messages sent by and to Bidule, but also picking up any additional messages being transmitted, as well. Ed.: A general-purpose monitoring tool sounds like a great idea! A great resource when trying to get multiple OSC-enabled devices or pieces of software communicating with each other.

Perhaps the biggest update of all in this version is the introduction of Multi-Core Processing, supporting up to 8 Cores. Previous versions of Bidule only allowed for processing on two cores, but now the MP Assign command lets you not only utilize up to 8 cores, but also select which processors you’d like to use. As a bonus, there’s also a new DSP Adapter function which allows you to run a limited set of modules at a buffer size of 1 sample.

All an all, it is a very welcome update. As with all publicly-released versions, this one comes with a time-sensitive trial period, so that new users can explore Bidule over the next three months without purchase. Simply make your way to the Plogue site to download this version today. If you’re looking for encouragement, also starting today, I’ve launched the first tutorial in a series which will be utilizing instruments that I’ve developed in Bidule for the Heads Project as examples. The series will be starting from the most basic concepts and progressing toward the more complex over the next months. If you’ve ever wanted to get your feet wet in Bidule now would be the time.

Lastly, I had the extreme pleasure of having a conversation with Sebastien Beaulieu, co-founder and lead Bidule developer over at Plogue. He gave me some great insight into the origins of Bidule, the business and development model of Plogue, and some ideas of what we can expect in the future. You can read the full interview here on CDM.