IK Multimedia this week is shipping both their SampleTank virtual instrument and iRig hardware MIDI interface for iPhone, iPad, and iPod touch. It’s not the first software instrument for iThings, but it is arguably the first appearance of a major, conventional computer soft synth in mobile form. MIDI interfaces, likewise, would require a comparison of some competing gear, but it’s the combination of the two in IK’s demo video that I think might give someone pause.

Music making tech has since the 1980s often involved some kind of computer. You might buy that computer in a piece of hardware that looks like a keyboard, or you might run software on a general-purpose computer. What has happened with Apple’s mobile devices is a third category. Observations:

1. Here’s a computer that’s a lot easier to fit on your music stand than a laptop is.
2. Here’s a demo that’s stunningly unchanged from what you might have done 20 years ago. (You’re even using the same hard-wired interface you were using 20+ years ago.)
3. This same instrument is more flexible and more powerful – though more challenging and time-consuming in setup – on a conventional computer. Of course, you may own both.

IK’s offerings:
SampleTank for iPhone / iPod touch
iRig MIDI interface, with Core MIDI compatibility for maximal application compatibility (including, incidentally, a recent update to Bjørk’s apps – more on that soon)

Side notes:

As for point 3, yes, a number of iOS developers are working now on routing MIDI between applications. It’s an interesting idea, but you have greater horsepower to run multiple applications simultaneously on, say, a MacBook Air than on an iPad 2, and I’m concerned that the mechanism for inter-app communication on iOS is not officially sanctioned by Apple. (I think those developers may be hoping that a critical mass of applications will protect them in the future, and there, they may be right.)

Another reality: all the fundamental technologies on which Apple are building, particularly the embedded platforms, are readily available. Challenging Apple in the consumer space is a massive challenge, as illustrated by the spectacular failure of some very awful – and some fairly nice – tablet entries in the last year or so. But building upon the same low-heat, low-power, low-cost, small-size boards could be something we see others do. (That’s a topic for another post, but worth considering while marveling at how much more convenient the form factor here is relative to a big, hinged laptop.)

It’s an interesting time – perhaps. The software isn’t really anything new. But convenience an make a small thing a big deal.

Over 25 years later, portions of MIDI introduced early on in the spec remain relevant. And if you want to connect your MIDI-equipped gear to Apple’s iPod touch, iPhone, and iPad mobiles, you will soon have an array of choices.

In iOS 4.2, best known for leveling the playing field between Apple’s handhelds and tablet, you’ll get full-blown MIDI support. It was clear in leaked details from earlier releases that Apple’s Core MIDI framework was finding new life on the mobile OS, but not directly what that would mean for hardware. Now, the hardware picture is clear. The Core MIDI framework appears to support two avenues for MIDI:

1. WiFi MIDI, via Apple’s own (apparently unique) wireless implementation, which should allow communication with other Apple handhelds and Macs, but likely not other devices. (WiFi is a common standard, but the way MIDI is transmitted over it is not necessarily so. That said, I believe the protocol for communication itself is based on documented implementation guidelines – not standards, but at least something someone else could conceivably implement.)

2. USB MIDI support for class-compliant devices, using the iPad Camera Connection Kit’s USB adapter.

More on the details – and other options and features outside just what Apple is giving you:

There’s one significant caveat to USB connections: the Camera Connection doesn’t carry a lot of current, so devices may require an external power source. So far, with multiple hardware adapters, and Apple’s own support for class-compliant audio, there could be a significant surge of hardware use with the iPad. But I haven’t yet seen indications these possibilities have taken the world by storm, even among Apple hardware devotees, perhaps because of the added bulk of the accessories themselves. (See more below.) That’s not to rule it out – I still think it’s pretty cool – but we’ll have to see how it’s received out there and how it works.

Interestingly, word of MIDI adapters has spread rapidly through the general tech press – outlets not normally excited by the vision of a 5-pin MIDI DIN connector. Developer Mike Keller, writing for PC World, has an especially ironic headline:

The Coolest New Feature in iOS 4.2 (That No One’s Talking About!)

So, why isn’t anyone talking about this? Apple’s NDA, which still covers 4.2, is one reason. (If anyone wants to have an existential talk with me about whether I should sign an Apple developer agreement and thus effectively gag myself as a writer, I’m game.) Another is that my sources tell me there aren’t yet code samples for the MIDI features. It could be fun to play with, though – especially with tools like libpd in development, bringing that popular free patching environment to the platform. And the good news is – this is public information – Core MIDI on iOS from the developer perspective should work just as it does on Mac OS. So huge kudos to Apple for high-quality implementation of a de facto standard for musicians.

The big news to me is that power requirements may prevent the use of some of the more compact devices out there — anyone want to test, for instance, the M-Audio Uno? Either way, it appears there may remain some call for specialized devices. Update: no worries! Reader reports suggest that at least the M-Audio Uno works fine, and that should mean other 1×1 devices are okay. (They don’t draw much power.) So, connect one of those suckers into the iPad, and you have a viable alternative to the MIDI Mobilizer. (Bonus: developers won’t have to set up an agreement with a separate hardware maker – for iPad, though you still need the MIDI Mobilizer on iPhone and iPod touch, since as readers note, they don’t support the Camera Connection Kit.)

So, aside from what’s coming in iOS 4.2, what are your options for getting MIDI in and out of Apple’s mobiles – or other mobiles, for that matter? Glad you asked.

iConnectMIDI

2 MIDI in (5-pin DIN)
2 MIDI out (5-pin DIN)
Full 2.1A 5V USB power – enough to charge your iPad
Comes with an interface cable
2-4ms iOS app latency

The iConnectMIDI box is the most serious solution out there, especially with dualing ports. And lest you think it’s rendered irrelevant by the coming features in iOS 4.2, think again. Its dedicated connector cable and power specs should make it more useful with iPad than a stock class-compliant device. Buried in the specs document, too, is this gem: “iOS Core MIDI framework support, if and when allowed, is expected to further decrease latency for iOS applications.”

So it may get more useful, not less, with the 4.2 release.

Availability: Not yet. Stay tuned for NAMM.

Cost: Not known. I’m guessing $999/EUR1299. Kidding.

Development: Partner SDK, “as required” by Apple. That means there’s a test and verification process that you have to go through with iConnectMIDI and then you can submit to Apple and go through it again with them. I’m hoping that gets nixed with 4.2, but there’s absolutely no word soon (not even if you break NDA).

Line 6 MIDI Mobilizer

1x in MIDI DIN, 1x out MIDI DIN (via 5-foot breakout cables – they use a 2.5mm connector on their actual box)
Specialized hardware adapter
Includes a free app for recording, exchanging via email and WiFi
iPhone, iPod touch, iPad (a nice handheld option on the former two)
Already supported by a handful of apps, including Line 6′s own MIDI Surface
Developer program open to anyone; see above

Availability: Now
Cost: US$70 street

The MIDI Mobilizer has the advantage of being relatively portable, though as some readers have pointed out, it still adds some bulk to Apple’s svelte handhelds. It’s also costly given what computer users are accustomed to paying for similar interfaces. But once you’ve got it, it’s a powerful, handheld tool. The big question mark has been app support, so watch, again, to see if what we get via 4.2 is standard support in place of individually reviewing apps.

See also SonicState’s review:

WiFi MIDI, OSC, etc.

Readers gripe that the big problem with MIDI adapters is that they kill the portability of the device, thus, erm, defeating the purpose. After all, for $200 these days you can get a netbook and add a $30 MIDI adapter with a lot less fuss, if you want a more portable MIDI rig.

That makes wireless Internet look more appealing, not only on iOS, but potentially other mobiles, too – like Android or even game gadgets.

One example:

DSMI, the DS Music Interface, is free software that has been ported to iOS and enables wireless MIDI communication not just with the Mac, but Windows and Linux, too. (I’ll be interested to see if new implementations of the WiFi MIDI used in 4.2 for those platforms can do the same.)

And that’s to say nothing of various wireless OSC implementations, enabling cool apps like the one we saw earlier this week. If you don’t mind a computer as a go-between, that’s another solution for MIDI right now:

Bluetooth? (on Android?)

What about Bluetooth? Recent conversations I’ve had with engineers on the phone suggest that latency and jitter should no longer be a problem with modern chipsets. That could make Bluetooth an ideal way to enable both mobile platforms and hardware wirelessly.

Just one problem — iOS’ restrictions on device pairing appear to rule out the use of this technique on Apple platforms.

Android is another question; I’ve already seen a couple of proof of concept tests that suggest that this would work really well on Android.

Here’s hoping eventually Apple allows something similar, even via Core MIDI. In the meantime, it could be worth trying on Android. That’d open the possibility of cross-platform mobile-friendly apps that used WiFi and cables on iOS and WiFi and Bluetooth on Android.

Who Cares?

So, why bother keeping track of this? I think there are a few scenarios that get interesting with these devices:

• Mobile music: Get away from your desktop computer and its distractions and work in any environment. (Hey, even the original Nintendo Game Boy can be adapted to MIDI I/O.)
• Alternative sequencers: Since touch control has often been relatively lacking on desktops – and laptop form factors in particular don’t lend themselves to touch in their standard hinged form factor – touch-based software on a system like the iPad (and soon, other tablets) benefits from these approaches.
• Mobile interfacing with gear: Imagine you’re in a studio full of vintage synths and want to record something, without finding a place to balance your laptop.

There’s also just the simple fact that an iPhone, an Android phone or tablet, and an iPad are all computers. Part of what we’re seeing really is reinventing the wheel – in a good way. We’re getting the standards for interoperability and actual music making we’d expect on any computing device.

Stay tuned for when the 4.2 NDA is lifted (and we have the 4.2.1 NDA to contend with instead). And for discussing non-NDA platforms, or iOS once its NDA is lifted, I hope you’ll join us in these groups on Noisepages:
Next-gen Mobile Music + Visual Dev Hack Group
Pd Everywhere

Meanwhile, if you want to see MIDI on traditional computers, a couple of us have found that the good old-fashioned MIDI multi-port hub has some utility, for reasons I’ll explain soon. And yes, you can still buy them – check out the M-Audio MIDISPORT 4×4. So, no, I’m not only about the mobile stuff.

Looking for all the world like a high-end audiophile stereo radio receiver as much as pro audio equipment, the shiny, new Symphony I/O has arrived from Apogee. It’s a top-of-the-range audio interface designed for low latency, high-quality digital-to-analog conversion, and quality clocking, as well as flexible input and output, coming from a company known in the category. With Pro Tools HD support, it’s also a rival to Avid’s own audio interfaces, while also working with all major Mac DAWs – even Ableton Live. You’re talking an investment of a few grand here, depending on configuration, so this isn’t likely to appeal to every bedroom producer. But pricing, starting at US$3690 with the I/O modules, also isn’t astronomical.

Another big highlight: Ethernet and USB releases planned for later in the fall mean the Symphony I/O is a viable alternative for mobile, laptop-based users, not just PCI as on Avid’s Pro Tools HD interfaces. That makes the Symphony interesting as a solution for the road. (The Symphony also works as a standalone converter, not just as an interface.)

Your best bet – check out the full specs from Apogee.
Symphony I/O

I’m mostly ignorant of high-end audio boxes; I can speculate about them a bit as I would pro baseball. I can, say, however, that the trend in converter quality has absolutely been to greater quality for dramatically lower price. It’s also notable that configuring and using converters is much easier than it used to be. The Symphony I/O makes it easy to switch DAWs (though sadly only on Mac, not other OSes), and even plans 64-bit kernel support on Mac OS later this fall. It’s a far cry from the days in the 90s when you’d spend a couple of days mucking about with Mac classic drivers and expansion chassis just to get a Power Mac to do any audio recording at all. (I’m unfortunately more knowledgeable about that than I care to be; I’d like to leave that in the 90s with memories of the Lewinsky scandal.)

What I can offer is the first-hand thoughts of a very biased – but also very interesting – source. Kevin Vanwulpen is one of the engineers at Apogee, responsible for firmware, software, and digital engineering. He was excited enough about his baby that he wrote me an extended explanation of why it’s cool and why it matters. Note that this is not an official PR line (I’m sure PR’s not going to be terribly happy to see it – blame me, not Kevin, guys). And it should be taken with a grain of salt; this device is basically family to Kevin. But taken as such, I do enjoy hearing engineers talk about their creations, so here’s what Kevin has to say.

Executive summary of the highlights from Kevin:

• The converters sound a lot better.
• “Modes” for working with a variety of DAWs makes switching Logic, Live, and Pro Tools far easier. (That’s not news for your basic audio interface, but it’s new to interfaces of this class.)
• Analog fans, this is DC capable. Route control voltage to your heart’s content.

the proverbial cat is out of the bag: SymphonyI/O is online. As usual, I won’t bore you with the stuff you might as well read on our website …but I do want to highlight some other points about the product you may find of interest, which is one of the things I love about your blog.

Also note this was not written by marketing but by myself and thus there is some of my bias/opinion/whatever in there.
Ok here it goes, in random order:

a. The sound….yes I am sure marketing covers that, but I am sure it will take a little while before people ‘get it’.
I do not have ‘golden ears’ (but some who do agree)…I truly can not tell doing a blind test whether I am listening to the analog source or AD-DA. Don’t get me wrong the previous generation was great…but well this is truly a major step up, which I am excited about (I am not in the business of designing the same thing in a new jacket…and neither are some others here, including Lucas our analog wizard)

b. I am excited about the Modes (marketing called it Audio Interface Mode). I personally compare it to multi-booting a computer (such as bootcamp and many others)
In the past Apogee’s products often got complicated very fast, because they are used in very different contexts and we had a hard time squeezing features and trying to make them make sense to everyone. In the end of the day if you’re using Logic you don’t care about ProTools HD specific features and vice versa for example.
Symphony I/O can be restarted in a mode of the users choice and allowed us to keep the box make total sense and easy to use…for the context it’s living in at that moment. Rather than all contexts all at once

I personally will use it with Symphony64 at home…but it’s nice to (down the road) hook it USB to a laptop as that’s plenty in most cases (for me at least) when on the go, which I am not all that often anyhow.

c. As you know I am personally an Analog-synth and modular (eurorack) geek…until now us poor CV-needy souls had to more or less pick between the DC-capable MOTU with it’s crappy sound (for some reason with modulars that is sooo obvious) or better sound quality. I am talking about use with Expert Sleepers’ Silent Way (which I use) or MOTU’s Volta.

Well this thing’s DA’s are DC capable…yay.

But not only that they have an amazing sense of zero (forgot what Lucas calls it, he calls it true-zero or something)…but in short the zero offset is not comparable to the other stuff out there. The legs are veeery symmetrical which does mean you absolutely without worry can use it to get double the voltage swing (and thus octave range)

Second it’s extreeeemely temperature stable, which is clearly important in that situation. I have not ‘measured’ it versus a MOTU but in my experience once tuned I have not had issues (which i do with MOTU as my rig happens to be near the AC airflow in my relatively small appartment where there are physical constraints where I cna put my modular)
I actually last week got an Expert Sleepers ES-1 with DB25 to use with this puppy. I pre-ordered my personal SymphonyIO. I like my Ensemble and all I use right now, but well this is a good notch up.

Obviously it can go out quite hot (+24dBu) so you get a nice large range to play.

d. We do see this not just as a product but more so as a project or platform or whatever you call it.
That does imply we decided to not ship it all at once….yes it doesn’t do everything under the sun today and for those people they can hold of. Likewise for many it is everything they wished for.
Likewise the box is very modular in design in many aspects which will allow us to adapt and allow people to invest in this without the stuff that is valuable obsoleting as fast as technology in general does.
Personally I like the Hasselblad analogy where they had an impossible time selling such expensive digital cameras…untill they figured out to make the digital part a slide-in part that gets updated whenever new stuff comes out and evolves with digital camera technology…but the body/optics and all that stay.

Don’t get me wrong there are many great aspects to this box, but well I know you know how to read and can go through our website and all that…the above is sort of my own input and highlight of less obvious stuff that I find cool about it.

If you’re an Apogee user or in the market for this kind of device, I’d love to hear your thoughts on this offering and how it stacks up to the competition. And what do you think of the staggered release schedule as far as features, which starts now but extends through 2010?

What do most musicians really need out of an audio interface? The answer to that question can vary wildly, but for a whole lot of people, it’s as simple as wanting to get an instrument and/or vocals in, and a basic, high-quality stereo mix out. That’s it.

That’s part of why Apogee’s new compact ONE audio interface could be a huge hit on the Mac. Let’s reduce its specs to the basics:

• It lets you plug in a mic, with a preamp and phantom power
• It lets you plug in an instrument (high impedance — so think your guitar or bass)
• It has an internal condenser mic, so you can record on the go even if you don’t have a mic handy
• It has a stereo output for headphones or powered monitors
• It has a nice big, shiny knob and lights for levels.
• It’s really small.

Apogee’s converters are some of the most respected in the business. If this is up to their usual quality, that could make this a really special box – as a basic audio interface or an addition to your gig bag. This interface does 44.1/48kHz, 24-bit.

And it plugs in via USB with USB power support, so if you got one of Apple’s FireWire-less MacBooks — before the recent refresh returned FireWire — you can actually use this.

There is some bad news. This is really a single-input box; you can’t even use the instrument in and the mic in (even the internal mic) at the same time. That seems an odd choice, as it wipes out a whole bunch of singer-songwriters. The output, likewise, is unbalanced and out of a single 1/8″ jack, which isn’t always what you want out gigging. And the ONE, pretty as it looks, has some stiff competition in the affordable USB market. On the other hand, if these specs do fit what you need, the ONE’s stablemate Duet had fantastic quality and uncommonly plug-and-play operation and Mac OS integration, making this really appealing for the Mac crowd.

And you’ve got to love that optional mic stand mount and design. It’s also really, really small – 4″ W x 6.3″ L x 1.5″. Apogee says “pocket-sized” which is a stretch unless they mean overalls or someone’s metric conversion is off, but it is nonetheless very portable.

Now, Apogee, if we could just get a ONE AND A HALF for people who like this but want balanced 1/4″ outs and two simultaneous ins instead of one… (Yeah, I know, you can’t please everyone.)

The ONE ships in late July.

http://www.apogeedigital.com/one

Thanks to Kevin Vanwulpen for the tip!

Digital technology has made music oddly invisible, virtualized somewhere inside a screen – but it also allows music to be mapped more literally to the physical world than ever before. Some of these experiments may even be silly, but they suggest a lot of possibilities.

From Poland, BeatMachine is a project that sequences beats in a step sequencer using discarded beer bottle caps. Would-be Internet haters, I suggest you count the number of beer bottle caps on the table, and start drinking that number while watching. I guarantee eventually it’ll seem like a brilliant idea.

Make sure you keep watching to the clever-looking software they’ve evidently developed for the task.

http://mw.boo.pl/beatmachine/

If this seems familiar, it was in fact inspired by the Bubblegum Sequencer featured here previously, and its rival I Eat Beats. Through the power of the Internet, iterating and improving ideas isn’t just something you do for yourself alone – it’s something you can share with others. That’s the idea behind our own tangible interface hackday coming up on Saturday:

http://hackday.noisepages.com

Thanks to Artur Nowak for the tip. I know we have a number of readers in Poland, so is there anyone who could help with a quick translation?

(Oh, and Poland, by the way – my book was actually translated into your language!)

Is your MacBook Pro a rightie?

Something’s going on with the one or two left-hand USB ports on all MacBook Pros. I’ve heard some issues with hard disks, and now some problems with audio. (Controllers are evidently just fine.) The solution: use the right-hand USB port for audio instead.

Updated: Reader Adam suggests that this is probably due to a difference in power delivered to the respective ports. USB audio requires more power, and so odds are you’re under-delivering on the left-hand ports. I’m inclined to think that this is exactly what’s going on – unless someone knows something else. (Easy way to test: try plugging in the power adapter. Note that this can be an issue with FireWire, too.)

In fact, even if for some reason M-Audio has found another reason behind this, Andy Ihnatko noted the issue with different USB ports and power variation way back in 2008. It affects non-Pro MacBooks, and I expect likely many PCs, too.

The MacBook. All USB Ports Are Not Equal [Wired Gadget Lab]

M-Audio (now Avid) has gone as far as to tell its customers officially to avoid the use of that port for audio entirely. Native Instruments forum users have evidently had similar discussions. Via matt_bot on Twitter:

The use of USB Audio Devices on the Left-Hand USB Port Is Not Recommended.  This applies to ALL MacBook Pro Models (Core Duo and Core 2 Duo).

•    The 15" MacBook Pro models have 1 USB port on the left side, and one USB port on the right side.
•    The 17" MacBook Pro models have 2 USB ports on the left side, and one USB port on the right side.

Due to the current USB configuration of the 15" MacBook Pro under OS X, use of USB audio devices is supported on the right-hand USB port only.  Use of such devices on the left-hand USB port(s) is not advised because it may cause audio interrupts and/or dropped samples.  However, the use of an iLok on the left-hand port has been qualified and is fully supported.

Due to the current USB configuration of the 17" MacBook Pro under OS X, use of USB audio devices is only supported on the right-hand USB port, and the left-hand USB port farthest from the screen.  Use of such devices on the left-hand USB port closest to the screen is not advised because it may cause audio interrupts and/or dropped samples.  However, the use of an iLok on the left-hand port has been qualified and is fully supported.

These USB port recommendations are specific to USB Audio devices only (such as the FastTrack USB or Audiophile USB).  USB Keyboard and Control Surface products do not have a recommended USB port at this time.

MacBook Pro recommended USB port(s)

That’s got to be a tough technical advisory to issue, like having to tell your users they should turn around in their chair three times counter-clockwise and shout “Mimmymabby” before recording. But I’ve heard indications that devices other than M-Audio’s are seeing symptoms, so I’m inclined to believe there may be something to this.

Now, before you use this to assume this means FireWire is better than USB or PCs are better than Macs or veganism is better for your love life or the end times are upon us, the whole point is what’s causing the issue and why. (Correction: I’m satisfied enough with Adam – and Andy Ihnatko’s – explanation above that I think there’s not much mystery here! So quit with conspiracy folks and trashing vendors you don’t like, folks. Technology doesn’t need superstition; it needs users hungry to know what’s actually going on.)

Of course, that raises a question: why are some USB ports not entirely up to spec on power? My hope would be that USB is USB and you don’t have power variations between ports, but then, I live in a fantasy world of naive hope. (Can anyone comment on PC laptops and power on different ports? I imagine some would have exactly the same issue.)

One theory for the power discrepancy: John von Seggern claims via Twitter that the issue could be the iSight video camera, which does indeed use the USB video bus. (I would think it shouldn’t draw power when switched off, but perhaps that has caused some other change in the configuration.)

Further, we have reports that not only the iSight, but also Bluetooth and other power-consuming peripherals are on the same bus, as well. (That means turning off Bluetooth might be a good idea if you don’t already.) And we have at least one PC with the same issue. This will definitely be something to research with computers, as it’d be pretty desirable to get machines that, erm, don’t do this to their USB ports.

And someone’s having the opposite port work or not work? Now I’m really confused. (I guess we could simplify all of this to say if you’re having problems with USB audio, try either connecting your AC adapter or switching USB ports.)

Amidst all of the USB audio hating, I have to say, it is possible to get good performance out of USB audio interfaces. On the other hand, removing FireWire from MacBooks seems again like a poor choice.

Ever feel like you’ve found the seam dividing past and future?

The past: restrictive UI frameworks requiring pages and pages of code to produce dated-look 2D displays. Proprietary software with rigid interfaces. Input bottlenecked through the x and y coordinates of a single mouse pointer.

The future: UIs whipped together graphically or with a few lines of code. 3D mixed with 2D. Open-source, friendly frameworks. Creating your own interface or drawing upon a community of creative software makers. Input that uses multitouch for gestures, collaborative input, manipulation of 2D and 3D space, and … well, just a lot more fun.

There’s no need to wait around for the future. Creative software inventors are building it for themselves. Here are two of the most promising multitouch interface projects I’ve seen in my inbox.

In no time at all, you’ll be painting a cow! (Okay, more on that in a moment…)

Make Max Multitouch

Max Multitouch Framework by composer Mathieu Chamagne makes turning your Max patch into a multitouch interface a breeze. When I first reviewed the Lemur, I was frustrated by the hardware-style abstraction between your software and the interface. Why was I having to go through Max patches painstakingly assigning Lemur controls to Max controls – why not just make the Max controls appear on the multitouch screen? Well, that’s exactly what you get with MMF. Using a set of Max abstractions, all you have to do is build your Presentation Mode style UI and add in the MMF ingredients – it automagically becomes touchable on a variety of displays.

It’s not hard to imagine how great this could be for musicians, especially those who have already been building original sonic creations in Max/MSP. Best of all, you don’t need an expensive, non-portable table with a projector inside, either – commodity hardware works just fine right now.

Requirements :

- cycling’74 Max5 (version 5.0.6 required)
- any multitouch interface that sends TUIO messages.

MMF has been tested and works fine with : Stantum SMK-15.4 multitouch screen, HP XT2 tablet pc (windows7 + W2TUIO), Demand Evolution + home made multitouch screen + Reactivision / Tbeta , …

MMF (Max Multitouch Framework) @ Mathieu Chamagne’s Site

Hmmm… apps that send (cough) TUIO, eh? Ah, yes, but that’s why you need companies like Apple to tell you what qualifies as useful in an iPhone app. You see, without Apple’s app review team and their superior wisdom, I might wrongfully assume this sort of app would be something I’d want. Now I know better – thanks! (Sorry, couldn’t resist.)

Back to the on-topic discussion, this does demonstrate a real advantage of Max: it has its UI absolutely nailed, and the open-source alternative Pd is woefully behind. It also demonstrates that the beauty of Presentation Mode is, by abstracting the UI from the underlying guts, you can consider alternative interfaces. We should see that in Max for Live, as well.

Pd is fantastic in other ways, but if there’s anyone out there who fancies writing a lightweight new front-end, it could use it – perhaps in Python. Which brings us to the next item.

pymt demo reel from Thomas Hansen on Vimeo.

PyMT: Juicy Multitouch, Just a Few Lines o’ Code

PyMT is a glimpse of what future development could look like. While Microsoft putzes around with their Windows-only Surface, PyMT makes multitouch platform agnostic, open, and easy. That frees up artists to dream up creative new ways of applying this interface to expressive musical and visual creations (among others). Instead of reinventing the wheel as far as plumbing, you can focus on the reason for using devices in the first place – your art.

PyMT is profoundly portable, using Python and OpenGL to deliver windowing and multimedia features across platforms. Documentation and code are both under heavy development, but there are already some friendly-looking resources. This is almost enough to shake me from my loyalty to Java, though, in fairness, you can do some of the same things with Java and other tools. What’s most important is that there are libraries that are providing standards, like TUIO, and implementations in cross-platform languages that can be easily developed.

There’s good reason to be bullish on the future of this tech. And if you want to see it happen, don’t wait – you can get involved in the project directly.

PyMT at Google Code

PyMT Project Page

David Merrill, working with Jeevan Kalanithi and (for the audio engine) Josh Kopin, wowed audiences at the TED conference with his Siftables interactive blocks. These strike me as what the Audiocubes have tried, sometimes unsuccessfully, to be — physical objects that react to the proximity of other objects, allowing you to manipulate music and media by moving around tangible blocks. Siftables are gifted with multiple expressive controls (tilt helping them break the plane of the surface), and intelligent screens that make them more adaptable and provide more visual feedback.

The music sequencer is very cool, though I think it’s actually the Scrabble-like game that may be the winner among the demos. But while TED celebrates all things cool and futuristic for their easily-digestible novelty, sometimes I think the most important design achievements are as significant in their shortcomings as their successes. Siftables raises some important questions. Sure, you can now use two hands, as opposed to the single mouse pointer. But do those same tangible blocks actually limit the kinds of interactions you can have, even compared to a traditional UI? Does it sound any different/ And note that — a little bit of tilting aside — the interface is still essentially two-dimensional. I’m personally really stumped by the question of how you can make a successful three-dimensional controller. Yet three dimensions is how all of us interact with space and movement daily. Maybe it’s the fact that we do so much of this, comprehend movement so richly, and take it for granted, that makes mapping those gestures so challenging.

That’s not a criticism of the project – or a claim that I can do any better. On the contrary, I think it’s important to do this sort of work because it can raise those kinds of questions. We’re gifted as a generation to try out and test these ideas with flexibility that was never before possible — and the intelligence built into these objects shows the potential of that power.

More of Siftables after the jump. And it’s well worth checking out David’s other projects, too – when I last ran into him, he was showing off the totable, Linux-powered Audiopint sound-processing box. Oh, yeah — and he’s the face control for guitar guy!

Siftables Music Sequencer from Jeevan Kalanithi on Vimeo.

Siftables project page

More Merrill Goodness

Before the iPhone, before HP computers and Windows 7 touch features and Apple trackpad gestures, the Jazz Mutant Lemur multi-touch interface was ahead of its time. Today, it’s still unique, in that it’s one of the few commercially-available devices to support OpenSoundControl, it’s a luxuriously-large multi-touch screen, and it has exceptional precision and low latency with its tracking. Of course, it has also been subject to two primary complaints: one, that the software options for creating onscreen interfaces is two simple, and two, that it costs too much.

Well, the Lemur and its more conventional DAW-controlling Dexter sibling address each of those. The Lemur has gotten a significant software upgrade, and both have gotten a steep price cut.

First, Lemur V2 is the biggest set of improvements since the Lemur’s unveiling. New in the upgraded firmware:

• Tabs for containers
• Breakpoint object for envelopes
• Alias controllers to save memory and (your) time
• Control the mouse cursor or keyboard shortcuts directly (that’s actually a huge deal right there)
• Pinch, rotate, trace gestures
• Pop-up menu object
• New JazzEditor, scripting powers, and instant Ableton Live reactivity – yep, doing stuff even the new Akai APC can’t.

The only bad news is, even with price drops, these devices aren’t cheap, though arguably they can make up for that with longevity. The Dexter has undergone a permanent price drop to a much more competitive US$1519. The Lemur has temporarily dropped to US$1769 for a 60-day promotion. No official word yet on what happens after that offer expires mid-March; stay tuned.

I do think this makes a pretty significant adjustment on value. I’m a big fan of the iPhone/iPod touch apps, but the input area is extremely small; there’s no real comparison.

Lemur V2
Jazz Mutant

And even if you decide not to get a Lemur yourself or can’t afford them, they remain a compelling example of what’s possible in the future of music hardware – and how powerful OSC can be. Look for a hands-on with Lemur V2 and more on OSC in other applications (many completely free) over the coming months.

To close out, here’s a nice, if simple, video demo of a Max/MSP step sequencer controller with the Lemur. What’s lovely about this is that it shows how building both software and hardware interface from the ground up can really give you control over how you’re playing. (Meaning, even if you hate this, you can go create something for youself that’s exactly what you love.)

this is a sequencer i programmed in max using the lemur as a control interface. it sends midi info to whatever program you use. i also forgot to mention that each track can have independent timings, so varitions can span longer than just 1 bar of music.

lemur users can download it off the jazzmutant website. user name – Andrew Graham

Got Lemur creations of your own? We’d love to see them. (I really appreciated seeing the amazing work Bryant Place was doing with LemurV2 and Ableton Live while I was out in LA.)

Today is set to be an orgy of computer music-y, Abletronic, drum machine-loaded, Max-patching news, so let’s throw one out to the guitarists. IK Multimedia has two new announcements today that are actually quite cool. The StealthPedal is a Wah pedal that’s actually an audio interface, sort of like a James Bond pen that’s also a gun. And IK also landed the only official Fender-endorsed software amp emulation.

Here’s a quick look at the specs. By the way, I’ve consulted everyone I know (especially as I’m not a guitarist), and basically what we’ve come up with is that a whole bunch of the guitar emulations out there (Apple, IK, NI, and Waves) are pretty damned good. Apple recently upgraded their own guitar emulations, meaning even what you get in GarageBand ‘09 is a big leap forward (and I have it on good authority that they sound terrific). NI has a guitar announcement coming later today, too. I’d choose based on taste, basically; each has a unique personality.

AmpliTube Fender

• 12 Fender guitar amps (Twin Reverb, ‘59 Bassman LTD, Super-Sonic, Metalhead)
• 12 matching cabinets
• 9 microphones
• 6 stomp effects, 6 rack effects (tape echo, Fender reverb, fuzz/wah, triangle flanger, wah, the works)
• Digital tuner, stomp pedal board, amp head, cabinet plus mic, rack effects. (Here’s one point of differentiation: NI, for instance, has more toys here; IK plays it a little more conventionally; that’s a matter of taste.)
• SpeedTrainer, RiffWorks T4 recording included
• “Certified” by Fender
• US$229.99 for the full set, or get the LE (4 amps, 5 cabinets, 2 stomp, 2 mic, 2 rack FX) with the StealthPlug USB audio interface for US$139.99
• Available late February

It’s a pretty stunning deal if you’re a Fender fan.

http://www.amplitube.com/fender

Stealth Pedal

• Looks like a wah pedal – same form factor
• Works as a controller (it’s basically an assignable expression pedal)
• Comes with a double foot switch, and you can optionally add a second expression pedal via a foot input
• Also a USB audio interface (24-bit, 44.1/48)
• “Low-noise” input stage
• Headphone out, volume control, LEDs for use as a tuner or level indicator
• ASIO PC, Core Audio Mac drivers
• Software bundle
• US$269.99
• Available late April

This looks just incredibly functional for someone wanting something compact. There have been controller/audio interface bundles before from IK, NI, and others, but this you can throw easily in your case.

http://www.stealthpedal.com