Max For Live Sneak Peak from max4live on Vimeo.

Suddenly, I have an image of American Ableton hackers patching on their MacBook over Thanksgiving turkey.

After a long, long wait, a public beta of Max for Live is available. The software incorporates the full version of Max/MSP/Jitter – complete with visual output, video processing, and 3D capabilities – with the Live host. Max patches operate with all their usual capabilities as devices inside Live. User interface elements are available to give Max patches conventional Ableton device interfaces, and there are even pre-built elements for useful functions like frequency displays and MIDI patterns. Via the Live API, Max for Live patches are also able to control most elements of the Live interface.

Because of Max’s networking capabilities, Max for Live devices can also be used to route OpenSoundControl data into Live. That isn’t necessarily with the same ease as you might route MIDI, and there’s still no native support in the Live interface, but it is a step forward.

Our friend Michael at max4live.info has been busy documenting the new software. His overview video is at top, and for OSC coverage, see his tutorial [part 1 | part 2].

Updated: Pricing has now been announced.
Max for Live is not included with Live 8 or even (perhaps surprisingly) Live Suite. It will be a US$299 / EUR249 download, available separately, on top of the cost of Live 8 or Live Suite 8. If you already own Max, you’ll have a set of crossgrades available:
1. You own Live. You can add Max for Live for US$99.
2. You don’t own Live, and want just Live. You can get that and Max for Live for US$449.
3. You don’t own Live, and want the whole Suite. Suite plus Max for Live crossgrade, US$699.

Total cost:
Max owners without Live: US$449-699
Live owners without Max: US$299 + cost of the upgrade to Live 8
Max + Live owners: US$99 + cost of the upgrade to Live 8

I think this could arguably be worth the investment, but given the discontinuation of support for developing VST, RTAS, and AU plug-ins in Max – a feature that was formerly free – I expect some resistance. Also, as previously announced, there is no known Max for Live “runtime,” meaning Max patch developers don’t really have a distribution outlet for work made in Max for Live, other than other Max for Live users.

Sign up for the public beta on Ableton’s site, and you’ll be able to grab the downloads (details below). You must be an Ableton Live 8 owner, though you don’t need to own Max 5:
http://www.ableton.com/maxforlive/beta

At the bottom of the page, you’ll have a direct link to download Live 8.1 (the official current build of Live is 8.0.9 otherwise), and a link to Cycling’s site to download Max. (Note: the Max link worked this morning, then promptly disappeared, so it’s possible they’re uploading an updated build is now back up.)

There are full instructions there. I was able to simply click a button and become a beta tester; hopefully you have the same experience. You’ll need to install two pieces of software, both Ableton Live 8.1 on the Live side and Max 5.1.

For the Python-based Live API, and the MIDI and OSC interfaces based on it, this should also come as good news. Live 8.1 should theoretically represent a more stable, feature-complete, fully documented version of the Live API under the hood in Live. That means even without Max for Live, it may be possible to, say, route an OSC input into Live as easily as a MIDI control surface.

If you’d like to join in with other people working on hacking Ableton Live and ask questions, try out our Noisepages group, which should now be functioning properly with a forum, wire, and networking features. More to come with this, with Max for Live, with OSC, with other tools, with… yeah, I’m glad I own a coffee maker.

http://noisepages.com/groups/ableton-hackers

The “space bassoon” Eigenharp seems to have landed from another planet. Today, I’ve got good news: it’s bringing alien gifts with it. By next year, both the software and the high-performance protocol the instrument uses will be open source. Taken together with other advancements in the open source community and with protocols like OSC, that could mean we’re at the vanguard of a golden age for more open, more intelligent, more expressive digital instruments.

Genuinely new music controllers made available commercially don’t come along very often. So this week’s news of a strange but wonderful-looking instrument shaped like a bassoon with customizable key controls turned many heads. With high-resolution, high-frequency data and reliance on the computer for everything from sound generation to mapping the keys to different tunings, the computer connection matters. Eigenharp’s chairman, John Lambert, sets the record straight for CDM on the software, the way it talks to your computer and other gear, and how open the tools and protocol will be.

I’ll be talking more with John next week, but I want to bring you this news now. Part of blogging means that you don’t hold back – you share that first reaction and then learn more. I’m pleased to say I was dead wrong on the Eigenharp. What looked on the spec sheet like MIDI-only communication and proprietary software turns out to be just the opposite. Sometimes, being wrong is great. Here are all the details:

What protocol do the instruments use?

The instruments talk to their base station by a dedicated, high speed, differential, transformer-coupled, error-correcting digital protocol designed (and tested) for use in noisy stage environments by ourselves. The wire used is a 4 core, standard star quad mic cable and can be up to 40M long. The base station then talks to the control software running on the host PC (Mac at the moment) via a dedicated protocol over USB2. In the host system, the native protocol used between agents (our software components) is a network protocol called Eigentalk. This can run over Ethernet wires (with slightly increased latencies due to some smart jitter buffering we do). We will be making this public and freely available (when we open-source our main software) in Febuary next year. There is an open API, to be published at the same time, for our equivalent of AU’s or VST’s, hosted in our software, EigenD. This is rather richer than the AU and VST API’s, for reasons connected with the expressiveness and configure-ability (is that a word?) of our system. A couple of interesting AU vendors are looking at producing native EigenD instruments at the moment, and I think there will be many more in time. We try to avoid MIDI wherever possible as it has so many serious performance limitations.

Had you considered OSC?

We did have a look at OSC but there are a bunch of things that our protocol does that OSC didn’t (not least of which, for example, is clock syncronisation for jitter removal, utterly vital over ethernet for live performance) so we decided to grow our own and release it. Absolutely no reason whatsoever that we can’t interoperate fuly with it though, I suspect that an OSC EigenD Agent will probably come quite soon after the open source release.

Ed.: Actually, with OSC (OpenSoundControl) moving increasingly toward broader input and assimilating other standards, I can easily imagine that a future implementation of OSC could begin to implement these features. More on both protocols in the coming months. -PK

Is it possible to use this as a controller for MIDI hardware? MIDI software?

Yes, EigenD has in and out MIDI gateway programs. The incoming [MIDI] is mainly used for pedalboards at the moment (to control scale, key, tempo, etc.), although there is no reason you couldn’t use a midi keyboard to play notes. We’re using the MIDI out to do a wide variety of things, including playing MIDI sound modules, and controlling video DJ software and lighting systems. There is a huge reduction in effective bandwidth when ‘downsampling’ to MIDI, but for a lot of things it still works very well. And of course, the AU and VST standards (which we fully support) are a kind of MIDI interface.

Is it possible to access its native protocol for custom software / Max-Pd patches and the like?

Well, we’re open sourcing the whole thing early next year, and I think there’ll be a lot of work done to glue all sorts of external stuff in then. Max/MSP has attracted a lot of interest in this area. The whole of EigenD is kind of built for this really. We’re an Open Source company: my main personal desktop is Linux and I have a strong personal commitment to open standards. I offer a number of ‘programming bounties’ for Linux improvements on my personal website at http://johnhenrylambert.com.

Tell us more about open-sourcing the software. What tools did you use to build the software.

It’s written in a mixture of C++ and Python. It’s quite scary code, but very clean and pretty, with little ‘cruft’. I think the open source community are going to have fun with it. Its a big system too, 8 years of R&D in one huge release. I don’t think that there’s been anything quite like this open sourced before in the music world – it is a bit as if Logic or Ableton were GPL’d tomorrow.

Thanks, John! Stay tuned for more details, and let me know if you have specific questions for the creators.

Take a weekend, and make something: that’s the challenge behind the Music Hack Day, which joins a growing phenomenon of events built around collective creation. (CDM held its own tangible interface hackday online, which I definitely hope to follow up soon!) Initiated by Dave Haynes of music sharing service Soundcloud, the Hack Day has already hit London. Many of the events were Web app-based and focused on consumption rather than creation of music, but we also saw a chordal synth plug-in and beer bottle percussion instrument.

The Berlin Hack Day, which wound up earlier today, offers still more projects focused on the creation side of music hacking. Having Ableton and Native Instruments as sponsors likely helped the mood. And as you’d expect from one of the world capitals of creative hacking, Berliners don’t disappoint.

Among the projects: a beautiful, elegant 3D sequencer, a fun bird-and-sky multitouch soundmaker with multitouch trackpad input, and a robotic xylophone controlled by monome. Someone even worked out a way to turn NI’s Maschine into a rhythm game, complete with Street Fighter sounds.

I’ve got some of my favorite projects here, but see also an eyewitness report (in English and Italian) at Audio News Room:
Just back from Music Hack Day Berlin
… and keep your eye on the wiki:
Berlin Hack Submissions

xylobot run by monome from robb on Vimeo.

Monomist Rob Böhnke and Ramsey Arnaoot created one of my favorite hackday projects so far: a monome-controlled robotic xylophone. The ingredients: one monome grid controller, one Java application for step sequencing to the output, one Arduino open source controller board, and one terrific xylophone “robot” made of an array of servos that strike the bars of the instrument. Oh, and some hot glue and wood, of course.

Project details

Debugging

Audio loop

Of course, what’s especially impressive is nailing this in just a weekend – imagine what they could do with more time and iterations.

Proof that musical visualizers don’t always have to be trippy, futuristic, Tron-like 3D landscapes (and that’s me speaking as a fan of such things), Gernot Poetsch instead chose a whimsical environment with clouds and cartoon birds, inspired by the graphic identity of Twitter. (No actual Twitter is involved, meaning you lose the, ahem, unreliable, buggy, unfiltered chat network but keep the cutesy happy sky! Works for me!)

The visuals are built in Quartz Composer, which via OSC transmits messages to synthesis language ChucK for noisemaking. The surprise is, the multitouch input is not a Lemur or an iPhone – it’s the new MacBook touchpad under Snow Leopard!

iLoveAcid is a beautiful-looking nodal sequencer by Jakob Penca which uses wireframe “tracks” to guide music playback through a sequencer, transmitting events to your soundmaker of choice via MIDI or OSC. By using curved timelines and connections, it’s a veritable model railroad of music, in which formations combine to form more complex structures instead of simply stepping across a grid. Despite appearances, it is so far only two-dimensional – but then, the z displacement could easily be assigned to some form of modulation. I’m really eager to see the video of this.

One ingredient: Processing, which makes it easier to write visual code and to connect to Java libraries.

Project Page

The hardware controller for Native Instruments’ Maschine software drum machine has been adapted to other software, like Ableton Live. But this is surely the first time it’s been made into a game. Using Maschine’s MIDI output as a game control and sounds from Street Fighter, MaschineFighter is a simple, Simon-style rhythm game. Unlike Simon, though, there’s a twist – instead of rote patterns generated in advance, you face off against a friend and try to out-rhythm each other, battle style. I think it’s actually a pretty brilliant idea, and could become a new sensation for us electronic music nerds – not to mention, it’ll finally test our rhythm in a way electronic performance often does not. (Correction: It is Mac-only, making use of the PYMIDI Objective-C based library, which, since everything else that starts with “Py” usually means Python – a la jThings that mean Java – I assumed, incorrectly, was built on Python. But anyway, if you like the idea, carry on! And, actually, having a pure Objective-C CoreMIDI interface is also pretty awesome.)

Hoping for a video of this, too.

If you have a project that didn’t make this list, or if you add documentation after the fact, let us know.

It’s still anyone’s guess exactly what fruit parent technology maker Stantum may soon ship, but the JazzMutant Lemur touchscreen is getting a component update soon. Nat Lecaude points to a quiet MySpace post from JazzMutant with the details of a coming manufacturing change.

“…the next batch of Lemur will feature the latest generation of our multi-touch technology: better optical performances, higher precision, greater accuracy and responsiveness. It will be clearer and have brighter colors. We plan on launching the new Lemur in early October, and of course we will keep you updated as we get closer to launch date. We once again thank you for your patience, and look forward to sharing the excitement early October!”

It’s actually quite remarkable to me that JazzMutant remains alone in this market – and with Stantum focused on the mass market, that could be the case in the future, too. The issue is that doing multi-touch well still costs some money. There are basic implementations on computers that are cheaper, but that restricts you to a few computer models, because slapping multitouch overlays on displays remains pricey. So HP can get a few computers to the mass market, but not without cutting some corners and not even on that company’s full range. The iPhone has brilliant multi-touch control, but a mobile form factor makes this much easier.

I’ve got some videos demonstrating what’s possible with the Lemur coming soon, as well as some notes on how the software has evolved since I first saw it in its initial release. Even if you don’t want or can’t afford a Lemur, it’s a fascinating demonstration of interaction design and OSC, with lessons (inspiring and tough alike) for other interfaces.

Photo by Rainer Knobloch for CDM.

Pronunciation of some common music tech terms has been a source of debate. Generally, though, there’s only one right answer. I had hoped to kick off a pronunciation guide yesterday or today, but now I really can’t resist – not with none other than Tegan & Sara getting together to debate the right way to say Moog.

Don’t get me wrong. I love cows, and the sound “moo.” I suggest if you have something you want to name Moo, you should, like your own MooVerb max patch or something. However, here goes, a few of my favorites:

Moog: Rhymes with “brogue” or “rogue,” not the sound a cow makes. Don’t say “Moooooog” unless you want to get funny looks from synth nerds, or if you’re teaching synthesis to livestock in a dairy.

Monome: The community-based, (partly, at least) open-source controller rhymes with “MA gnome,” not the Spanish-sounding “Ma gnome ME.” You should not be able to use it in a couplet with paper mache. Get it? Two syllables. Sure, this pronunciation varies, but the two-syllable version is what the device’s co-creators call it.

OSC: Pronounce the letters of the open communications protocol, as in “O.S.C. / oh ess see”, not “osk” – though that would have been kind of cool. Think, “Rah, rah, rah, Give me an O! Give me an S! Give me a C! What’s that spell? Better than MIDI! Time-based messages, higher resolution, transport-independent high-speed networked communication with auto-discovery, gooooooooooOOOOO O.S.C.!” (People sometimes say this site is geeky. I have no idea what gives them that impression.)

And for now, O.S.C. stands for Open Sound Control, even though in one spot on the JazzMutant website it’s called “Open-Source Control.” Just get ready for this to change – because OSC really isn’t specific to sound, it may need a new name, like Open System Control. (A recent paper suggests dropping the “sound” in the name.)

MIDI: Rhymes with G. Gordon Liddy, or P. Diddy, or Tweetiebird saying “Piddy.” And, actually, it occurs to me I’ve never heard anyone mispronounce this. Fascinating – an acronym that’s actually intuitive. Oh, but “C.C.” stands for “Control Change,” NOT “continuous controllers” — look at the CC specs; most aren’t continuous. There. I got to be anal about something anyway. Updated: consensus is actually that “mee-dee” is a mispronunciation for native-English speakers, but likely makes more since than “mi-dee” in other languages — particularly if you speak French. So, in other words, it’s an acronym, and makes the most sense to pronounce in the natural way you would in your native tongue. (For English speakers, who knows what vowel sound is appropriate given how screwy our language is, but the creators of MIDI all say middy.)

Maschine: Native Instruments’ drum machine software and controller is German-engineered, so say “muh SHEEN uh,” three syllables, as if you grew up in Berlin. Now, granted, Maschine’s own promotional videos — outsourced to the US — anglicize this to “machine” / “muh SHEEN”, but the engineers and product folks who built the thing use the German pronunciation and think you should, too. And, anyway, it sounds cooler, just as I have to admit a currywurst is tastier than a Nathan’s dog.

I’m sure this is only a small selection of potential mispronunciations. Other candidates? We’ll have to release a full pronunciation guide soon.

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.

Most important is the programmability of the Ohm64. You can make your own custom light interactions – or, if you’re not into that sort of programming, count on what may be a growing community of open source musicians and visualists doing it for you.

In fact, Livid is so committed to customization that in addition to the natural, blue, and red finishes, you can order it unfinished and stain or paint it whatever color you like.

The Ohm64 is also priced at just US$599, meaning it doesn’t cost much more than the APC40. And with future OSC support, hardware MIDI support, bus power so you don’t have to carry a dongle, fully programmable visual feedback and assignments, and open source editing software, the APC has some real explaining to do about what its long-term payoff may be.

The editor is currently built in Max/MSP with some interesting possibilities coming up in Max for Live, but I’m also interested in working on some editing and performance tools in fully open source environments. Stay tuned.

Now, mind, this isn’t a review – I’ll get my hands on the Ohm64 next week here in New York, and I’ve only had a brief encounter with the APC. But if I were a betting man, I have to say, the contest here isn’t looking like it’s in the APC’s favor.

Available now.

Livid Ohm64

http://www.lividindustry.com/culture/ blog with more videos

Updated: I should note, one issue is definitely that, in order to maintain bus power, there are some compromises. You don’t get quite as much interaction from the lights as you do on the Akai APC – I do like the APC’s lovely LED rings around its encoders. You can interactively dim the lights on the knobs on the Ohm, though, which would work nearly as well. More once I get my hands on the Ohm, and theoretically, I should have an APC for testing at some point, too, assuming I didn’t just make Akai angry. (Uh…. competition is good. Blogs are all about opinions. Don’t hurt me.)

By the way, if you aren’t convinced and think you can do better, Livid is also distributing the brains of this device – the MIDIDIY – so you can build your own creations. Other such solutions exist, but the MIDIDIY is distinguished in its ability to support a lot more contacts for doing this sort of more complex device.

http://www.lividinstruments.com/hardware_mididiy.php

For that reason, you may be intrigued to see this video of Zen Piano, a demo app for the iPhone and iPod touch. The idea: respond not only to the position of your finger taps, but also to how hard you’re tapping the phone That promises “velocity-sensitive” tapping, which would make touchscreen interfaces more powerful.

Here’s the somewhat overheated description by GreatApps, who say their “patent-pending,” “cutting-edge” technology is the result of “having gone through the research and development phases.”

TapForce^TM has been developed from the ground up to provide a completely intuitive way of interaction for users. It can detect more than a hundred different levels of force, and has an accuracy that has to be seen to be believed. And all this can now be done in software, no hardware modifications are necessary. Hundreds of millions of devices currently on the market can make use of the TapForce^TM technology today.

A whole new range of games and apps has just been made possible.

http://greatapps.co.uk/technologies/

Okay, so what is it doing, exactly?

Most likely, it’s simply reading data from the accelerometer. Hit the device harder, and the accelerometer will respond to more force. That’s actually a fairly clever combination of two sensors – it’s just not the sort of stuff you’d necessarily want to trademark or try to get patented, at least, not if you’re a normal person. (TapForce creators, feel free to explain to us that you’re doing something fancier and I’ll eat my words.)

In fact, part of the reason I suspect that’s how they’re doing this is I’ve been tipped off by a developer who’s already implemented just this. He even uses a piano-style keyboard to show it off.

Sadly, that developer and application is Memo and his MSA Remote application, which was inexplicably blocked from the iTunes store – I think because whoever would have understood the app was on a lunch break or something. See, previously:

MSA Remote for iPhone

Apple Rejects Free iPhone Tool For Artists Because of “Minimal User Functionality”

But as it happens, this is something any mobile device can do that has an accelerometer. I may try something like this on the Android app I’m developing. (No one can reject that, because Google allows any application package to be installed on the device should the user chose to do so. Perish the thought.) Accelerometer data alone is usually not very useful, but combined with touch, it could start to make more sense.

It’s another reason to look forward to MSA Remote, and I do still think that the snafu with Apple will get cleared up at some point. (Unfortunately, what we had on CDM were a lot of rants – perhaps even justified rants – but not necessarily the best way to make the argument to Apple’s store.)