Music Tech Pronunciation Guide

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.

TouchOSC Controller with Template Editing Coming Soon to iPhone, iPod touch

touchosc

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:

Tangible Interface Hackday: Music with Soda Bottles, Floor Toms, More

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).

Video: Novation Automap for iPhone, with Ableton Live

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.

Livid’s Ohm64 Controller: Full of Buttons and Knobs, As Open As You Like

ohm64 

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.

read more