I got to spend yesterday working with the Launchpad; see the video above which I think should help you get a sense of scale and what it looks like. (Also on YouTube) We have additional videos from other sources below.

It’s only been public for less than 24 hours, but as we did with the APC40, I think it’s time for a superguide answering questions about the Novation Launchpad controller.

The Launchpad and the way it works reveals a lot about how controllers work with Ableton Live. You may be surprised to learn a lot of this doesn’t require a special controller and doesn’t require Max for Live – it’s standard Ableton stuff that works with MIDI. (Remember MIDI?) And I think some of these answers could be worth a read if you have interest in hardware control hacking in general.

There have been a lot of questions from myself and readers, so I’ve done my best to get answers. Realize, a lot of this information is developing and is based on my limited understanding, so it’s all subject to change. I’ll update this guide over the next couple of days if I get any corrections.

Side note: What about interoperability? I intend to talk more about OSC and the Live API (and each separately) in coming weeks. I think it’s impossible to judge the full picture of how Live can interoperate with other tools, though, until there’s some more information, so stay tuned on that.

Basic Questions

Q. What do you get with Live 8 Launchpad Edition, the bundled software?

New to Ableton Live, and wondering if you can get anything done with the “lite” Launchpad Edition bundled with the hardware. The short answer is, yes you can. The included edition has restrictions, but it’s still a reasonably capable version if you’re new to Live and want to experiment.

Ableton Live 8 Launchpad Edition vs. Live 8

The Launchpad Edition even comes with 1 GB of Loopmasters loops to get you started.

Most importantly, ReWire support for Master and Slave (Host and Client) is included. That means if you have an existing host and just want to play with Live’s non-linear clip launching features, you can stick with that host, using Live alongside software like Reaper and Reason. You may want to consider upgrading, though, as some cool features like the use of Racks and the ability to slice instruments, plus the “Complex” warp mode, are missing.

Q. What the heck is going on in the crazy Novation video demo? How do I do that myself?

There isn’t any Max patch or other voodoo in the video demo from Novation. It’s all just a standard Ableton Live set, and the fact that the Launchpad responds to MIDI messages as well as sending them (something useful if you’re scripting the Launchpad in software other than Ableton, too).

Matt Derbyshire of Novation put together the video. Matt’s an interesting guy musically when not working for Novation, too – he’s part of a DJ Shadow cover band, for one. He shares with CDM how he went about this:

It’s actually a very simple session.

1) There are four clips only for drums in the drumrack channel

2) Each clip is pre-recorded but EMPTY at 1 bar length

3) These four clips are the first four clips in session mode but for convenience I also learned these to to User 1 mode bottom four left buttons.  Basically setting this up removes the need to rush back to session mode to drop out of record

4) Obviously quantize is on ‘cos my playing ain’t that great.

LED feedback

In User 1 mode the bottom left button turns on/off LED feedback.

The important thing I want from the video is to show that I personally do not think the lack of velocity sensitivity stops drums being played. In fact, to the contrary, I think in creative electronic music it helps to even out the playing.

The still-simpler explanation:

So long as you use the User Mode to play, enable LED feedback, and route MIDI from Live back to the Launchpad, you can get interactive light modes, as seen on the monome and Tenori-On.

Q. Okay, the Launchpad can assign control to continuous values. But it’s got buttons. How do you get eight buttons to replace a fader?

Actually, thanks to an Ableton feature that works with any MIDI controller (not just Novation or Akai), this is quite easy to do. You can assign any range on your controller by holding it down.

From Novation’s Matt Derbyshire:

Step 1: Choose the slider/knob you want (i.e. cross fader)

Step 2: Select USER 1 or 2 mode on launchpad

Step 3: Select MIDI learn mode in Ableton

Step 4: Select the thing you want to control (ie crossfader)

Step 5: Select the range of buttons on launchpad

Note that this also works for playing clips.

Now, obviously, if you control something like a volume fader with a set of buttons, you won’t get continuous values. And unfortunately neither Ableton nor Novation has designed any sort of interpolation between button values (though DIYers could find a way to do that). But I’m kind of finding the angular changes in buttons to be fun to play with. If I want a knob or fader, I’ll use a knob or fader.

Q. What can you do with these User Modes?

There are two User pages. User 1 sends basic note values – minus any velocity sensitivity, just on/off. User 2 sends control changes. User 1 by default will play any active MIDI inputs listening to channel 1. In Ableton Live, User 2 only sends control changes once you’ve mapped it using the MIDI Map, to avoid accidentally triggering notes when trying to control something else. (See also the special behavior with Max for Live below.) Of course, in software other than Live, you’ll set up whatever layout you want.

You can’t rearrange the organization of pitches on User 1 because there’s no real editor for the device; everything is hard-wired. On the other hand, you can always make this adjustment in software, as in a Rack in Live.

Advanced Live Use

Q. How will Max for Live integration work?

Max for Live will use the User 2 page. The good news here is, Max by default will listen only to User 2 while the other modes get routed to Live.

Q. Can you control Devices dynamically using the Launchpad?

No. Unfortunately, while there are pages for mixer settings and a generic way to transmit MIDI control changes, you can’t click a device and have a page on the Launchpad automatically make its eight columns control eight parameters / macros. That’s actually a feature enabled by the simple scripts available for the Korg nano series here on CDM (see my post explaining how this works, follow-up script from reader Raymond).

Of course, because this feature is supported by the Korg with our scripts and it’s very, very compact, the nanoKONTROL and Launchpad could make a great, cheap combo. And if you have Novation’s ReMOTE, Nocturn, and the like, you can alternatively use them – so, for instance, a keyboardist could stick the Launchpad atop a keyboard.

Q. Can you edit MIDI assignments? Is there a MIDI template editor, in other words?

No. All the MIDI assignments are hard-wired. The good news is, everything appears to send MIDI, though I still need to investigate how that works outside Live. The bad news is, as with the APC40, a lot of functionality is organized around Live.

That would be my one potential criticism, which is that we’re moving away from hardware that’s useful everywhere to hardware that’s useful only in one program. But I want more time to see how the Launchpad performs outside Live before I pass judgment on the Launchpad in particular, especially as I don’t even have the final software yet.

I still like editors, though, Novation, if you’re listening.

Q. What if you still have Live 7?

Update – official word: Ableton’s Baptiste Grange tells CDM:

On Nov 1 we’ll release two updates: Live 8.0.7 and Live 7.0.17. These will both support Launchpad.

So, Live 6 and earlier would need to upgrade, but not Live 7.

Hacking

Q. Will we get the full MIDI implementation and protocol for creating custom patches or custom setups with our own software? Will that be true outside of Live, too?

Novation confirms that they plan to release the full MIDI implementation and communication protocol for the Launchpad at launch. That’s something that was missing on the APC40, leaving us all to figure it out ourselves, so I’m looking forward to seeing that documentation. Part of the reason to use MIDI is to have a spec that everyone can read so power users can do what they want.

Q. Can you control the lights using MIDI?

Yep. This should be in the full documentation, too, but here’s a sneak peak. Bjorn from the awesome Covert Operators sent me the velocity assignments, which I’ll be using to hack my Launchpad setup:

Velocity 0 = Off
Velocity 1 = light red
Velocity 2 = medium red
Velocity 3 = full red
Velocity 16 = light green
Velocity 32 = medium green
Velocity 48 = full green
Velocity 17 = light amber
Velocity 34 = medium amber
Velocity 55 = full amber
Velocity 18 = light orange (Lighter > red / darker > amber)
Velocity 35 = medium orange (Lighter > red / darker > amber)
Velocity 31 = full orange (Lighter > red / darker > amber)

The Competition, and the monome

Q. How does this compare to the Akai APC40 / controller XX / the monome as far as Live integration?

The most important point here is that you can easily mix and match. You can even have multiple control surfaces active, operating dynamically, at the same time, as well as multiple MIDI inputs for instruments. Also, most of the features of the Launchpad are available to all controllers. Novation is emphasizing the mix-and-match functionality of the Launchpad. Basically, the feeling is, there is no one control scheme that works for everyone.

The Launchpad is quite similar to the APC40. The clip functions are nearly identical, if in a slightly different (8×8) layout – you get the red onscreen rectangle, the red/green/amber LED indicators, scene launching, the ability to page through clips, and so on.

Basically, the major difference with the APC40 is trading functionality for size and price. The APC40 has the ability to map to Devices automatically, as does Novation’s own ReMOTE series; the Launchpad does not. The APC40 also has encoders, faders, a crossfader, and a number of shortcuts. On the other hand, you can get a lot of the APC40’s functionality in other hardware, meaning the Launchpad can combine nicely with other gear you already have.

One significant edge the Launchpad has over the APC40, though, is that the Launchpad is set up to play drum racks.

The monome is also capable of nearly everything you see the Launchpad doing, with the exception of the clip selection rectangle (though I find that a bit hard to see, personally). In fact, the pages on the Launchpad are clearly inspired (directly or indirectly) by Pages, a GPL-licensed, fully-free, Java-based tool for monome which even appeared in action on David Letterman with Imogen Heap.

You certainly have other options that provide dynamic, automatic control mappings, including the M-Audio Axiom Pro series, the Korg kontrol and nano series, Novation’s ReMOTE line, the Faderfox series, and various others. You can see the built-in scripts available on the Control Surface menu, and anything that supports MIDI can be adapted for additional functionality.

I expect that with the release of Max for Live, scripting custom control for other controllers should be more powerful, even if you don’t have Max for Live installed. Stay tuned in the coming weeks as I’ll be trying to get more complete information on this.

The Live API improvements should be especially benefit the monome project. And remember, the monome isn’t standing still. Because it’s open, it’s conceivable clever users could hack new features.

Q. Can I run monome software on it? OSC?

Yes and – no.

The Launchpad uses MIDI, not OpenSoundControl (OSC). That means you have to translate incoming, sometimes arbitrary MIDI numbers to useful information, and that the Launchpad can’t natively interpret messages in the way the OSC-native monome can. However, as noted in our APC40 hacking superguide, it is possible to use an emulator to translate between MIDI and OSC. That should also be possible with the Launchpad. One challenge is the extra buttons around the grid. I’m going to have to write some Java MIDI code that can map to an arbitrary array of buttons, huh?

Q. Does the Launchpad violate monome’s license and design? How is the monome licensed? How “open” is the Launchpad?

I don’t want to – and cannot – speak for the monome project. However, while the Launchpad is unmistakably similar to the 8×8 grid of pads on the monome, it is not a “clone.” It’s only superficially similar to the monome. Cloning isn’t necessarily healthy for design, but a certain amount of copying can be. Without the spread of keyboard layouts, for instance, we wouldn’t have any of the keyboard instruments we have today – and, indeed, before the standardization on the fortepiano, a lot of keyboard instruments were strange copies of one another. In modern design, the monome is itself indebted to the pad layouts on early drum samplers.

I mention the word “clone” because the Arduinome is an clone of the monome which is distributed non-commercially as a result. It actually duplicates major portions of the design, PCB, and protocol, which is not remotely true of the Launchpad. Because their intention was cloning (for the purpose of ready availability of parts), the creators of the Arduinome consulted with the monome project.

For the record, the monome’s software is released under an open source license, and it uses fully-documented, open protocols, including OSC. The hardware is not technically open source, but it is open to the extent that specifications for the hardware, PCB, and firmware are provided for customization and modification, and the construction of custom housing. You are restricted from using the hardware design to make your own commercial hardware, which means the monome doesn’t fit some more restrictive definitions of what qualifies as open hardware. But it does offer some components that are truly open source, and it affords a great degree of real-world openness for its users.

None of the “openess” of the monome is true of the Launchpad, which operates under more traditional and proprietary models. You can’t easily physically open the Launchpad case (and I expect you’d void your warranty if you did). It uses MIDI, an open protocol, but has a proprietary mechanism for interacting with Ableton Live (at least so far as I can tell). It uses USB, but does not support class-compliant operation – you must install your own drivers, which means you can’t use it with some devices (like Linux netbooks). And the process and operation of the Launchpad are not available or documented. That’s not to discourage the Launchpad, and you still have plenty of power via its MIDI implementation to keep you busy. But that does differentiate it from open hardware like the monome and the newer Livid Ohm64, and it’s worth considering how this difference impacts the ways you want to use the hardware. That issue is much bigger than any one piece of gear, and it’s one I hope we can cover in more depth.

More Videos

MusicRadar did their own hands-on:

Actually, judging by the LEDs, I think they were also working from a prototype and not the final production run. But you will also notice they have an L-shaped USB cord, which I believe is what the final unit will have. (And, heck, that’d be a useful thing to have around here, I may have to pick up some.)

Novation TV also has their own set of videos:

http://www.youtube.com/user/NovationTV

And DJ Tech Tools got a hands-on, too.

What does it mean to truly democratize technology? When is DIY more than just the creation of an object? That’s the question asked by our friend Julià Carboneras, who curated the new Nerdeferences feature of the OFFF digital design conference in Portugal last week. DIY is more than just cool devices, argues Julià: it’s social hacking, too. He brought together myself, Instructables.com founder Eric Wilhelm, and musical inventor and artist Gijs Gieskes (who stole the show, showing some creations live onstage). But there was a bigger picture, too, that I wanted to share.

Julià wrote, in Catalan and English, an introduction to the idea for the conference catalog that I thought was really compelling. OFFF has allowed this text from their catalog to be reprinted here, and Julià has given us a Spanish translation, as well. (Spanish first, English second.)

I’m actually pleased that on CDM we have the chance to talk about radical DIY and open source ideas alongside more traditional commercial projects. In that way, you see design in a larger context. You can see the tools that allow people to be creative alongside one another. And my sense is that people do find ways to build business models and economic independence around notions of open source and DIY, which is vital in the capital-driven world in which we live. What draws together people, whether using commercial tools or building their own, is some desire for real independence instead of dependence, for expression and not just consumption.

I’ll let Julià take it away, though, because the issues he raises goes well beyond the insertion of some of these ideas (and some very nice, loud sounds) into a design conference. I know many of you working in communities and events elsewhere are thinking along similar lines.

(Photos here from the event itself; we expect to have additional video, too, soon. Let me know if you were there in Lisbon!)

NERDFERENCES [ESPAÑOL]

Desde sus inicios la llamada “democratización” de la tecnología ha estado limitada por demasiados factores para poder considerarla genuinamente democrática. A pesar de que realmente la caída de precios ha permitido un acceso más amplio a sofisticados dispositivos digitales, también ha determinado la manera de utilizarlos impuesta por sus fabricantes. Hoy en día, miles de usuarios están rompiendo estas limitaciones a través de la ética del DIY (háztelo tu mismo).

Desde que Reed Ghazala acuñó el término “circuit bending” en los años sesenta para referirse a la modificación de la circuitería de aparatos electrónicos para generar sonido, la influencia del movimiento DIY en la creación contemporánea ha sido obvia, y algunas de sus invenciones y descubrimientos se han convertido en recursos básicos en el arte digital actual, como el software Processing o las superficies de control Monome. Pero no podemos pensar en el circuit bending y en el software de código abierto como meras técnicas o dispositivos. La naturaleza de su propia existencia está fuertemente vinculada a ideologías que se asocian a movimientos sociales y políticos alternativos. Frecuentemente relacionado con el punk y los movimientos anticapitalistas, el DIY es, ante todo, una postura en contra de la producción en masa y las políticas de comercio multinacional. Pero lejos de usar técnicas de confrontación abiertas y directas, su beligerancia se expresa principalmente a través de estrategias de “copia y mejora”: algunos de los dispositivos más famosos que han nacido del DIY tienen sus orígenes en la reformulación o modificación de tecnologías ampliamente conocidas vendidas por multinacionales. En realidad, cuanto más popular es el producto, más atractivo es piratearlo.

A Gijs creation. Photo courtesy OFFF Festival.

Nerdference es un nuevo panel enfocado al DIY digital que se presenta en el festival OFFF: un movimiento social, ideológico y tecnológico bajo el cual pueden encontrarse múltiples formas conceptuales a través de disciplinas como el circuit bending, el software y hardware hacking, el desarrollo en código abierto, superficies de control de fabricación casera, entre otras muchas. Nerdference es una oportunidad única de dar una visibilidad física y una exposición offline a un fenómeno que vive mayoritariamente en internet. La red ha permitido desde el desarrollo de proyectos colaborativos tan grandes y conocidos como Linux a poder compartir con el resto del mundo dispositivos caseros realizados individualmente como hobby. Una red internacional de tecnologías de dormitorio que ha contribuido substancialmente en la evolución de las herramientas digitales usadas ampliamente en la creación con nuevos medios actual.

Nerdference es un amplificador para una generación de artistas con voz propia. Una generación nacida con un portátil bajo el brazo; adolescentes que han aprendido a programar de forma autodidacta y se han convertido en hackers famosos; músicos que elaboran todo un proceso de producción, con suficiente imaginación y conocimientos técnicos como para crear desde sus propios instrumentos hasta sus redes de distribución musical; artistas que desarrollan su propio software y lo distribuyen libremente…

La primera edición de Nerdference en el OFFF Oeiras 09 tiene el honor de presentar a Eric Wilhem, Peter Kirn y Gijs Gieskes.

Eric Wilhem es el fundador de instructables.com, un web de referencia mundial donde todo aquel que quiera puede mostrar sus dispositivos caseros hechos por ellos mismos. Instructables.com es, tal como Wilhem declara, “el web de Muestra y Explica más grande del mundo”, y se ha convertido en la Biblia del DIY. En él se puede encontrar lo más inimaginable: desde como se diseñó y programó la propia web, a como customizar instrumentos musicales o como fabricarse uno mismo el detergente para lavar la ropa. Esta será una oportunidad única para disfrutar del amplio conocimiento de Eric sobre DIY.

Peter Kirn es el nombre que está detrás de createdigitalmusic.com, createdigitalmotion.com y
createdigitalmedia.com. Estos blogs son puntos de encuentro esenciales para artistas, programadores y VJs, y son una guía para conocer las últimas novedades tecnológicas y de DIY. Y por último, pero no menos importante, el artista holandés Gijs Gieskes nos mostrará como lleva el circuit bending al extremo en Nerdference. Aprenderemos como concibe, diseña y construye sus extraordinarios artefactos y software de modificación de navegadores web.

Julià Carboneras

NERDFERENCES [ENGLISH]

Since day one, the so-called “democratization” of technology has been constrained by too many determining factors as to be considered genuinely democratic. Although it’s true that the prices drop has improved a wider access to sophisticated digital devices, it also has determined the way of using them through the limitations set by their manufacturers. Today, thousands of users are breaking these limitations through the DIY (Do It Yourself) ethos.

Since Reed Ghazala coined the term “circuit bending” in the sixties to name the modification of electronic devices internal circuits to generate sound, the influence of the DIY movement in contemporary creation has been obvious, and some of its inventions and discoveries have become basic resources in today’s digital art, like the Processing software and the Monome control surface. But we can’t think of circuit bending or open source software as mere techniques or devices. Their most intimate nature, their existence itself, is strongly connected to an ideology that deals with alternative social and political issues. Often related to punk attitude and anti-capitalist movements, the DIY is, first of all, a stand against mass-production and mainstream trade politics. But far from openly confrontational techniques, its belligerence is mostly expressed through copy-and-improve strategies: some of the most famous devices born in the DIY scene have their origins on the re-formulation or modification of already existing and well-known technologies manufactured and sold by multinationals. Actually, the most popular the product, the most attractive the hacking.

Nerdference is a new panel at OFFF focused on the digital DIY: a social, ideological and technological movement whose multiple formal and conceptual traces can be found on disciplines like circuit bending, software and hardware hacking, open source development and homemade control surfaces, among many others. Nerdference is a unique opportunity to bring physical visibility and offline exposition to a phenomenon mostly living on the Internet. The net has been a determinant platform for the development of so big and well-known community projects as Linux or the worldwide sharing of self-made devices made out by individuals all over the planet. An international bedroom technologies network that has become a substantial issue in the evolution of digital tools massively used in today’s new media creation. Nerdference is an amplifier for a generation of artists with an already own voice. A generation born with a laptop in its hands; teenagers who learned how to program by their own and have become famous hackers; self-taught music producers with enough imagination and technical skills to build up their instruments and create their particular distribution networks; artists that develop original software and give it out to like-minded others.

Nerdference’s first edition at OFFF Oeiras ‘09 proudly features Eric Wilhem, Peter Kirn and Gijs Gieskes.

Documenting process via Instructables. Photo (CC) Anna Fuster / Tartanna.

Erik Wilhelm is the founder of instructables.com, a world reference site where anyone can show his / her self-made devices and applications. instructables.com is, as Wilhelm himself declares, “the world’s biggest show and tell website”, and it has become the bible for the DIY believers. It covers almost every imaginable topic: from designing and programming the site’s pages themselves to customizing musical instruments and creating your own washing powder. This will be a unique opportunity to enjoy Erik’s broad knowledge of the DIY industries.

Peter Kirn is the man behind createdigitalmusic.com, createdigitalmedia.com and createdigitalmotion.com. These blogs are essential meeting points for artists, programmers and Vj’s, and extremely useful guides to check today’s DIY state of the art.

Last but not least, Dutch artist Gijs Gieskes will show his extreme take on circuit bending at Nerdference. We’ll be able to learn how he conceives, designs and constructs his amazing artifacts and web browsers modification software.

Julià Carboneras

More resources:

Instructables.com

Trackmate Tangible Controller: A terrific example of documenting a tangible music interface project via Instructables (which in turn this group linked back to their Sourceforge page, a case of using the right tool for the right job)

Gijs Gieskes

Links from my presentation:

Adobe Rants Produces Unexpected Glitch Art
(proof that having tools that don’t always work perfectly, or that can be pushed past the point at which they function properly, can make them more powerful)

TUIO + reacTIVision: a protocol and open source vision library for touch, tangible interfaces

opensoundcontrol.org: a means of making devices and software more intelligent, more expressive, and more connected in a way that benefits artists and musicians

Save that Old PDA: Run Reware, Play Pd Musical Creations, Android (OFFF, NYC) – a way to harnass open source software to make supposedly “disposable” devices powerful again

handmademusic.noisepages.com: an opportunity to work on this stuff with other people, live, in person – and a call to extend this around the world, beyond Brooklyn, has already resulted in a number of cities in the US, plus London, Berlin, and Porto, Portugal

http://paia.com a source of DIY kits, including solder-free, business-card-sized kits that can be used to teach kids about electronics and sound early

Finally, here’s my presentation via SlideShare, complete with (some) of the embedded videos:

Should sounds be part of a closed format that may not last? What happens if the format and platform that once were trusted by musicians and sound designers ceased to be? That’s the hard lesson learned by users of a popular sampling “standard” – but for once, the news is good.

GigaSampler has been a huge part of the sampling landscape since its introduction a decade ago, and users have massive investments in Giga sound libraries. As I noted over the summer, however, Tascam ceased development on the aging Giga platform, leaving users without an important tool – and some powerful technologies without a home.

Today, news has leaked out that Garritan, developer of some popular sample libraries and (with Plogue) the sophisticated, cross-platform ARIA Engine, has purchased all of the technology assets related to Giga from Tascam (TEAC). That includes GigaStudio, Gigasampler, GVI, Gigapulse, and everything that goes with it.

This is huge news for compatibility, interoperability, and the future evolution of sampling. I spoke with Garritan chief Gary Garritan himself to chat about some of the possibilities.

The most obvious potential benefit is native file compatibility with Giga sample libraries, so that that sound content isn’t stranded in an abandoned, closed format. Gary says native file reading and writing is high on the priority list – which should also be a big coup, I think, for his ARIA platform.

There are some technologies worth saving in Giga, too, though, not just the sample format. Some of the jewels in Giga include the DEF high-quality filtering algorithms, spectral morphing, and convolution capabilities.

“There’s a treasure trove of great technology and we want to make it available to as many musicians as possible,” says Garritan. “We just have our work cut out for us.”

The process of assimilating Giga’s technology is likely to take time, Garritan says:

What this means is that we have this great technology and we can do stuff with it. But we don’t have the original Giga team – and we have two million lines of source code to go through. Some of that code is fifteen years old. I want to examine the code … and I want to consult with the user base, and chart a direction.

There’s potential to merge technologies, so that future versions of ARIA benefit from Giga technology. “We have a really efficient engine ourselves,” says Garritan. “It’ll probably be using the best of both ARIA and Giga.”

Gary emphasized that this process is really open to input: “We need to consult with the user base and ask the users what they want – ask our users what they want.”

We’ve certainly seen how not to acquire technologies in the past. I’ll bet money that someone brings up the acquisition of music software developer Opcode by Gibson, which turned an entire platform into abandonware.

Far from that, what Gary is describing is really the opposite: an opportunity to embrace open standards, and perhaps to even avoid the kind of closed platform Giga originally represented. Ironically, the open source Linux Sampler Project, while its own codebase is entirely open source, relies on the closed Giga format for storing samples.

“On our ARIA Player we use an open source format, SFZ,” says Garritan. “We’re for promoting open standards.” Working with Cakewalk, Plogue, and others, Garritan says he hopes to encourage more openness. SFZ could even become the kind of common format that Giga (and other proprietary formats) have been in the past – only without being the sole domain of one vendor. “I think sampling technologies and formats should be open – they shouldn’t be closed and proprietary.”

This is also, incidentally, good news for Linux. I know there’s talk of SFZ in Linux Sampler, as well. And for those who want a friendlier interface, ARIA already works in WINE, with a native version in the works. Gary says ARIA works beautifully on netbooks. That means you could have a sampler running on the netbook, then do your production in, say, SONAR on your Windows machine at home.

I should clarify that ARIA itself is a proprietary player – and, honestly, I expect commercial developers to continue to develop proprietary technology and use that to sell their wares; it’s a system that works. But on the other hand, with a common, open standard file format, you could benefit from both the commercial-proprietary and open/free ecosystems. For many of us, we might even use both on the same machine. Right now, you have the opposite: a common file format that had been closed and proprietary (and not entirely supported), an open source sampler built on that proprietary format, and limited cross-platform support. It looks to me like we’re moving toward resolving all of those issues.

Composers and sound designers are deeply connected to sound libraries, investing time and money into purchasing or designing libraries, and in using them in their work. Happily, the days in which that investment could be gone forever because a vendor lost interest may finally be coming to a close. As I noted in July, simply open sourcing Giga wasn’t a real option: there’s too much work to do to navigate the code base and modernize the format, and we’d still be stuck with a dated, closed format. So to me, this is about the best thing that could happen: get Giga into knowledgeable hands, and really try to move the best of it into modern, open formats.

That is, open source alone is never a panacea. In this case, you need a commercial developer that can put work into maintaining the technologies, but you also need a common format for commercial and free software developers alike – because, really, it’s what the musicians, composers, and sound designers need.

Because this is sure to be a long process, we’ll be watching as it unfolds. But in the meantime, Gary has posted some FAQs and invites Giga and Garritan users to talk about what they need and want. So, don’t be silent: this is a chance to have someone actually listen and respond, rather than just “wishing” for something to happen.

Northern Sounds Forum [Garritan community]

http://gigastudio.com/ [New Garritan Giga site with press release, FAQ]