Want to make a splash among the aficionados of digital sound? Releasing a software instrument emulating a broad collection of vintage digital synthesis chips from game and computer systems seems to do the trick. See my look at that software, and just as importantly, the chips that inspired it.

Within days of the release of Plogue’s Chipsounds, we have a couple of fair reviews of the new tool. Already got Chipsounds? Plogue’s David Viens has released screencasts showing you how to use it. Curious about other ways to explore vintage 8-bit sound? We’ve got that, too, in samples, hardware, and even SuperCollider code.

Reviews are in

Torley has an extensive video review – amazing stuff for something just days old – shown above. Gisle Martens Meyers has a review, too, on the blog Ugress. One complaint is that the plug-in is multi-timbral, rather than requiring different instances. In turn, automation is in the form of MIDI Control Changes, not parameters, since parameter automation really doesn’t deal with multi-timbral plug-ins. But all in all, you can get a lot from both reviews, plus a look at how the software works. There’s also a sense of where the software could go in future updates.

Plogue Chipsounds makes chiptune & video game sounds easy [Torley Lives]
Chipsounds Plugin Chip Sounds [Ugress]

The discussion of Chipsounds has also brought other efforts to resurrect vintage, 8-bit sounds.

Get Your Chip Fix

This is by no means comprehensive, but here are a few of the best goodies readers have pointed out in the last few days:

Free Samples: Little Scale, aka Sebastian Tomczak, has been busy. He’s added sample packs of his own, including a Friday release of the Commodore 64 SID. Add that to Sega Master System, Mega Drive, speech chip, and Atari POKEY and TIA. These are just samples, so rather than being a turn-key solution as Chipsounds is, they’re more of a construction set – though that could make them useful in other scenarios.

C64 SID Sample Pack [little-scale]

Go Hardware! And, in turn, if hardware fires you up more than software or samples, Sebastian has done some lovely work connecting the actual chips to MIDI interfaces.

And here’s the documentation on how to do it with the free and open hardware Arduino platform

Other hardware solutions:
A DIY TI SN76477N-based Voice Module, comprehensively documented (a heck of a lot fancier than the Arduino stuff I wanted to play around with)

SuperCollider Code: For SuperCollider fans, Fredrik Olofsson (aka RedFrik) has built emulations of vintage chips in the object-oriented sound coding language. That’s a doubly delicious thing: aside from allowing you to make 8-bit sounds in the free tool, looking at his emulations is a great way to discover more of what you can do with SuperCollider. You can continue in code the kind of elegant, minimal synthesis design work the early creators of the original chips did in hardware. (Thanks, Howard S and Morgan Packard for the tip!)

SC Code [and a lot of other great SC code there, too... bookmarked, downloaded.]

Video walkthroughs

I know quite a few readers did pick up Chipsounds, so you’ll be pleased to know – in case you missed this – that there are some video demos that walk you through how the tool works. This also gives a better idea of how the software itself functions, since I got distracted waxing rhapsodic about the chips!

As my piano teacher used to say to me, “that should keep you off the streets.”

Enjoy.

Call it the 8-bit preservation society. Chipsounds is now available. It’s a new programmable soft synth, filled with custom oscillators and samples of famous and obscure vintage chips, accompanied by an EP of free chip tracks. Far from a threat to fans of hardware, I think this release is a major achievement for fans of digital sounds.

Oh yeah, and if you’ve been feeling burnt out on chip music in general, firing up some of the sound of some of these more obscure chips could well change your mind. If you like sound, there’s something here for you.

Chip music, championed by a supportive network of artists and fans, has unquestionably made the big time. But for those who value the unique sounds of a variety of vintage 8-bit chips, there is still cause for concern. Even though they’re digital circuits, the unique design of various chips won’t last forever. Some chips are simply disappearing, while others cease to work. At the same time, while the sound of the Nintendo game system has become ubiquitous, lots of other unusual chips don’t get heard. Software emulation and sample packs so far have been pretty shallow. Emulators tend not to model all the nuances of different chips, and samples are really only expressive if they’re presented in the context of something that’s fully programmable and playable.

Enter Chipsounds. Creator David Viens told us about the Chipsounds project back in January:
Authentic Chipmusic Soft Synth Emulation: Plogue Chipsounds Scoop from NAMM

It’s available today, with an introductory price of US$75 ($95 thereafter).

chipsounds @ Plogue [Product Page]

Something like Chipsounds could have been just an attempt to cash in on “what the kids are playing.” But David’s work is more like an epic love poem to the sounds of chips themselves, not only as a reminder of game music but as a unique sound source. And the passionate chip music community got in on the act, as well, with notable artists contributing to the product’s development and in fine form on the EP.

But forget about that for a second. What matters is that chipsounds is an exhaustive, exhaustively programmable set of sounds that almost no eBay budget could ever amass. It takes some unique sounds and allows you to warp them into arrangements and performance configurations not possible with hardware. And it might well make you explore hardware in a new way all over again.

For your listening pleasure, here is the full, free EP with downloadable tracks to set the mood. It’s all been made with Chipsounds by some terrific artists, including David Viens himself, and covers a range of genres and techniques.

Why Chipsounds

David has a really lovely intro in the manual for the tool. He’s got a story like many of us I expect have.

My father bought a Commodore VIC-20 for me and my brother when I was around nine. After a few days with it, I guess he knew I had found my calling. There is not a year that passes without me reminding him how bringing that computer home some cold autumn night changed my life.

But this isn’t just nostalgia. David also notes that some of the limitations imposed by earlier 8-bit hardware caused artists and musicians to invent new techniques that were later lost. These methods can now be rediscovered and coexist with new processes only possible with newer tech. What Chipsounds represents is an expanded “sonic palette,” not just the literal representation of the hardware included. And for those willing to dig into programming the sampling instrument itself, that palette can be even wider and more personal.

David did a whole lot of work on research and experimentation to make this work, but also drew upon the massive community online. Here’s a look at the chips included.

The Instruments

David did extensive research, testing, sampling, and A/B sound programming for the project. Just going through the chips is a nice history lesson – and could be a good introduction for those interested in working with hardware, too. You can check out extensive technical details on the hardware at the chipsounds blog.

SID (6581) and (8580) It’s the mother of all sound chips, and deserves the top space in this list. The SID was the legendary Commodore 64 chip, sampled in this collection at 96KHz. The 8580 I think doesn’t get nearly enough credit, so it’s nice to see both so you can hear the oddities of each.

RP2A03 (NTSC) and RP2A07 (PAL) and RP2A0X (unlimited): This is the big one – the chip in Nintendo’s NES and Famicom. It’s not actually a dedicated audio IC, but a clone of the 6502 CPU, but it still has some unique features and sounds.

DMG-CPU, SGB and DMG(unlimited) The classic: Nintendo’s own sound generator for its Game Boy handheld. Confession time: I’ve heard this chip so much that I’m starting to long for other things. But again, because the Chipsounds collection lets you create hybrid instruments in different ranges, there’s nothing stopping you from inserting DMG sounds where you wouldn’t expect. (And while functioning Game Boys are everywhere and run a variety of amazing homebrewed sequencing software, some of these other chips aren’t as accessible or portable.)

AY-3-8910 (various clocks sources), YM2149 (2Mhz): General Instruments’ sound chip was one of the great sound chips of the 8-bit gaming and computing age, found in the Intellivision, Vectrex, Atari ST, and Sinclair ZX, among many others. That means it’s critical not only to gaming fans, but also fans of the sounds in early tracking musicians, particularly on the Atari ST. It’s even got its own Wikipedia article.

D1867G The classic Casio VL-1 makes a surprise cameo in this collection. Result: you have the opportunity to imagine your own music console that combines the sounds of the VL-Tone with the IBM PCjr, and that’s a beautiful thing. The VL-1 may be the odd man out in this collection, but then, it also exemplifies the lo-fi digital sound of the 80s – and with the ARIA sampling engine, you can warp it to do things it has never done before.

P8244 (NTSC), P8245 (PAL) This is one of the rarer (or at least more unexpected) entries in the collection, the sound chip that drove the Magnavox Odyssey2. Intel’s Video Display Controller used this chip to make both graphics and sound (hmmm… could Chipgraphics be next?) For extreme nerding out, check out David’s full post on working with this chip. Unlike the other entries here, the VDC doesn’t have much documentation online for these kinds of applications.

POKEY (various clock configuration) Atari’s Doug Neubauer created sound capabilities for this chip, used in Atari’s 8-bit computers as well as many arcade games. (The POKEY actually handled not only audio, but keyboard, pots, timing, serial… Arduino fans, take note.) Which arcade games? Try Tempest, Gravitar, Gauntlet and Crystal Castles, for starters.

TIA (NTSC), TIA (PAL) and TIA (unlimited) Another combined graphics and sound chip, the Television Interface Adapter was the sonic soul of the Atari 2600. The variations here in Chipsounds give you a lot of choices, including the awesome “polynomial counters” which create different kinds of distortion. Using keyswitching, you can choose among these sounds live, ideal for keyboardists. And David has even included the sounds the TIA makes when the cartridge was improperly inserted.

SN76489(AN) (various clocks) Here’s my personal favorite: the classic Texas Instruments sound chip was dead-simple (three square wave generators and one white noise generator), but elegant, efficient, and unique in sound. The BBC Micro, IBM PCjr, and ColecoVision game system all used its sounds. I can still hear the echoes of Subroc in my sleep. (Yeah, okay, I was a bit jealous of my friends who had Apple IIs and NES instead of the more oddball PCjr and Coleco I had, but now I’m older and appreciate them more.)

Side note: David was nice enough to share some of his SN chips, so I’m working on building them into standalone hardware and will share the results.

UVI 2637(NTSC) and 2637(PAL): Now we get into the chips you probably haven’t heard. Signetics made this chip for the Arcadia 2001 console developed by Emerson (yeah, the electronics company) in the heady year of 1982, before the meltdown that would purge the home gaming market. That console was widely cloned, under names like the Interton, Leisure Vision, and MPT-03.

VIC-I : 6560 (NTSC) 6561(PAL) in various configuration Here’s another oddball chip: the VIC-I, used in the VIC-20, had 7-bit pitch range, giving you oddly-tuned scales, plus a truly strange noise generator. That strange sound is rarely heard, but leave it to the demoscene to exploit it. From the Chipsounds manual:

In 2003, a brilliant demo writer by the name of Viznut reverse-engineered this side effect, mapping all possible “weird” waveforms that the chip was able to reproduce in a deterministic manner, and put the to good use in his now famous “Robotic Liberation” demo.

Here’s a look at that creation:

The Software

Let’s get something out of the way: I believe in synths. I’m naturally skeptical of samples. If I believed for a second Chipsounds was about plugging in some sampled sounds and hitting a key and waiting, I wouldn’t have posted this article. Fortunately, Plogue’s ARIA sampling-plus-synthesis engine is powerful enough to allow immense programmability and playability. It’s loaded up with programs that model every last detail of these instruments, while also providing the possibility to create your own, unique performance configurations. Samples make up just a portion of the sound, used where appropriate, with lots of custom oscillators and modulators, as well. This is really a full-blown instrument, not just a sample library. (ARIA has previously been sampling-only, but Chipsounds is the first of a line of instruments to use synthesis, as well.)

Standalone, plug-in modes:

As a plug-in, Chipsounds works with VST on Mac and Windows, RTAS (for Pro Tools) on Mac and Windows, and Audio Units on Mac. And of course, in plug-in mode you can automate all your parameters.

In standalone mode, you have additional features: audio file recording, MIDI file playback, and even the ability to render MIDI to audio directly.

Mixing, Multis:

• Load up to eight chips/instruments per instance. (Each of those, in turn, can be made up of combinations of samples.) Maximum polyphony is suggested at about 4-5 voices for artistic reasons, but… rules are made to be broken, right?
• Assignable tuning, polyphony, mix parameters
• Reverb busing
• Key switching, which allows you to change between waveforms immediately using a key on your keyboard
• Snapshots

Sound editing:

Here’s where things get fun – and where you can do things more easily than you could with the original hardware. Even with the ARIA engine alone, you have a virtual studio of tools in which to place your samples.

• Arpeggiator for pitch, velocity: with configurable range, loop modes, gate, sync, etc.
• Wave sequencer: This allows you to sequence lists of pitches on an instrument, allowing tracker-style events inside the software. (Add your own tracker to the mix and – well, things get pretty hectic.)
• Live, high-performance oscilloscope.
• Pitch LFO (currently fixed), pitch and amplitude envelope generators.
• Effects, which currently includes only an ARIA-native port of the lovely Ambience reverb by Magnus Jonsson. (But then, the advantage of having these sounds on your computer is easy access to all your other effects.)

Still Want Hardware?

In order to make the Chipsounds collection, David spent time rigging quick hardware devices allowing the actual chips to be connected to a computer. That could make Chipsounds an affordable gateway drug into building your own standalone hardware with these chips as sound sources, as I hope to do soon with my TI SN’s. To get you started, check out the superb resources on the Midibox wiki:

Midibox SID
Midibox POKEY
MIDIbox AY 3 8912

The SID is the most common of these, but ironically finding working SIDs is getting to be much harder than finding these other unique, lovely chips.

I’m actually really interested in the possibilities of combining hardware with the open-source Arduino platform and creating devices that behave in new ways; stay tuned, and hopefully we can get a group of folks working on that.

One example – our friend little-scale aka Sebastian Tomczak of South Australia – has used the Arduino to connect to the SN chip and create a MIDI-controlled Sega Master System equivalent:
MIDI + Arduino + chip on little-scale’s blog

Add in new MIDI capabilities on the Arduino, and this gets quite interesting.

The Artists

A lovely collection of artists contributed to the EP and to the development of the software, so this is very much a release connected to the community. (David’s own music is on the EP, too.)

The artists:
8Bit Weapon
Computeher
nitro2k01
Chupathingy and on MySpace
James Mireau
XC3N
shrimps

And for more on the making of one of the tracks, GameBoy Genius aka nitro2k01 has documented the work of translating a hardcore chip track from Game Boy to computer, using Renoise. This is a pretty traditional approach to what to do with chip music, but on the other hand, once you’re in the world of Renoise, you could go in other directions, as well.

If you’re interested in anything covered here – the artists, the chips and digital synthesis history, how to use the software, or how to make some of these hardware creations – all of these topics are fair game for CDM. I promise a non-nostalgic (okay, maybe slightly nostalgic), musical approach to these topics.

In the meantime, let us know what you think of the software.

Updated: See http://createdigitalmusic.com/snowleopard for a running report.

Apple’s “Snow Leopard” 10.6 ships Friday, which means it’s time to start compiling information about the new OS flavor. Just don’t upgrade too fast, as always.

Want to push an operating system to the breaking point? Ask a musician. Between the demands of real-time performance and the complex ecosystem of mix-and-match hardware, software, and plug-ins, odds are your local audio geek will break an OS faster than anyone else. Not every operating system upgrade is going to have a big impact on music software, but keep in mind that even subtle changes can cause issues that may interfere with your work.

Of course, all of this means music users should treat any OS update with caution. :

• If you’ve got a critical, primary production machine, your best bet is often simply to wait. Confirm that software works before you upgrade rather than after.
• If you’ve got some time to invest in an upgrade or have more than one machine, be sure to do a full backup and system image so you can revert to the previous, known working OS.
• Best solution: Boot off an external hard drive. Don’t commit to installing internally until you’re sure everything is working. Once you are, go enjoy. (as noted in comments, and yes, I should have said this initially… still, the latest 10.5 build is still the preferred OS for now.)

So, sit back. Enjoy life. Go for a walk on a beach. Recline in your favorite chair with your MacBook running Mac OS X 10.5 Leopard. Isn’t it great? Need to waste time? Plants vs. Zombies is out for Mac.

What? Still want to upgrade?

Fair enough. We’ll be tracking changes to Snow Leopard and which of them may impact audio.

The short version: Snow Leopard introduces only small changes, but if a developer hasn’t been on top of those changes, you could see issues. And as for the 64-bit mode that’s attracting most of the attention, the short answer is, you can’t use it for music yet.

Native Instruments and Plogue have each responded to CDM with information on their software.

Executive Summary

• NI and Plogue have tested their software as functioning on 10.6
• Neither NI nor Plogue recommends you upgrade your OS yet – Plogue uses stronger language to discourage you
• 64-bit support, expanded in Mac OS 10.6, is not yet relevant to music use because nothing (not even from Apple) supports it yet, but don’t worry – you can get more RAM through other methods
• Audio MIDI Setup gets a tune-up, and built-in audio support appears to be improved

Native Instruments

If you’re a Mac user who uses NI products on any version of the operating system, you should stay tuned to this URL:

http://www.native-instruments.com/en/support/compatibility/mac-os-x-compatibility/

NI tells CDM they’ve just updated it today with Snow Leopard information:

Native Instruments has conducted initial compatibility tests with Mac OS X 10.6, which have shown all current NI products to work without any specific issues under standard installations of this operating system.

However, users involved in professional audio production or live performance should be cautious about upgrading to Mac OS X 10.6 until compatibility with third-party audio software and hardware has been widely confirmed by the relevant manufacturers.

Native Instruments is currently conducting further systematic compatibility and performance tests with Snow Leopard, and will provide additional information on this page as it becomes available.

The second paragraph sounds like what I just wrote, huh?

Plogue

Plogue, an independent developer of a variety of software ranging from the awesome modular environment Bidule to sampling engines for Garritan’s orchestra and piano products and an upcoming library of vintage chip sounds have been doing their own work. Privately, I talked with them about some of the work they had to do after Apple rewrote underlying operating system plumbing with Objective-C (from C and Carbon). Here’s their official statement to CDM on Snow Leopard and, in the parallel Windows dimension, Windows 7:

10.6 and W7 each caused only minor modifications to our code base, however these mods are necessary for proper functioning of our products on those platforms. Most of our transition efforts as a company will be of a user support nature.

Any musician foolish enough to jump on new OSes without a hint of caution, inevitably makes me wish for a new kind of Darwin Award prize.

(Emphasis mine. Consider yourself warned.)

Ableton (Unofficial) and a Plug-in Warning

From the Ableton forums, via comments:

It’s currently being tested internally over here, so the current version is not officially compatible yet – on the other hand this does not mean that it doesn’t run.

We will release an update after the tests during the next weeks that will be officially compatible, but we don’t recommend upgrading yet if stability is your main concern.

It’s likely that a few new third party plugin problems will show up due to the changes under the hood in 10.6 and experiences show that the latest 10.5 versions now are the way to go after the gfx performance problems with earlier 10.5 and 10.4 versions.

So, in other words, now is a great time to upgrade to 10.5!

More in the thread here:

Ableton Forums

Now, note, mostly what this extensive discussion reveals is that Snow Leopard is poorly understood, partly thanks to a very successful hype campaign on Apple’s part. (Ahem.)

There are not magical performance and speed improvements found by installing Snow Leopard – or, most likely, any OS. (Would that such things were true.) The presence of a set of multithreading tools, for instance, is specific only to developers for whom that set of tools is useful. Audio software already has finely-tuned multithreading implementations specific to real-time applications, and in the case of something like Ableton Live, it really needs to work across platforms.

If you install a new OS with the expectation that it’ll be “faster,” you’ll almost certainly be disappointed. If you install a new OS hoping you’ll “break things,” then you probably won’t be disappointed. I don’t mean to suggest don’t ever upgrade or live in fear of all software, just that you should imagine that, like redoing the plumbing in your basement, long-term advantages will come, but with significant effort and time.

PreSonus Hardware

See a separate post: at Snow Leopard launch, PreSonus audio interfaces are likely to be entirely incompatible.

About 64-bit (Nothing to see here…)

NI notes that the 10.6 offers significant changes to 64-bit support, including a new 64-bit kernel mode – this being the rough equivalent of the “x64” 64-bit versions of Windows (and Linux) that have been available for some time.

Here’s the bottom line: 64-bit support on Mac OS isn’t yet relevant to audio users, period. It’s not supported by Apple’s own Logic Studio, or any other major host at this time. This is a situation we’ll be watching, as it is something developers appear to be investigating.

But before we get too far into that issue, you should consider why you’re asking about 64-bit in the first place. 64-bit computing offers two potential advantage. First, running processor computation natively at 64 bits offers a marginal improvement. Second – the issue most people care about for music – 64-bit memory addressing offers access to massive amounts of memory, beyond the approximate 4 GB barrier that applies to 32-bit applications.

More memory is a very good thing. But you probably don’t want to sacrifice compatibility just to get it. Fortunately, you don’t need the 64-bit OS to get beyond that 4 GB barrier. On the Mac, some workarounds have extended the practical life of 32-bit memory addressing for music applications – thus avoiding the need to get a 64-bit native version of every driver and every piece of software you want to use.

On Windows and Linux, you can indeed get a number of audio applications (like SONAR on Windows, for instance) that have excellent 64-bit support, and a number of the drivers have followed suit. Even, then, though, many users choose to stick with 32-bit versions in order to have superior compatibility.

Note that processing “64-bit audio” – that is, digital audio represented using 64-bit data – is a completely different issues. A 32-bit processor and 32-bit operating system and 32-bit software can all do 64-bit audio processing. Whether you really need 64 bits for audio production is a whole other can of worms I won’t open here.

Getting More Memory – Without Any 64-bit Snow Leopards

When I spoke to Apple earlier this month, they downplayed the 64-bit issue and pointed out that their own EXS24 sampler in Logic Studio can access additional installed memory just fine with 32-bit – that means if you have Logic 8 or later, Pro or Express, Tiger or Leopard or Snow Leopard, you can use additional RAM. Each EXS24 sampler instance has its own memory space, so you can use as much memory as you want.

Apple even has a support doc on the subject:

Logic Pro/Express 8: How the EXS24 sampler addresses RAM in Logic 8

Last month, we looked at the situation for Native Instruments’ Kontakt. Again, using some of the flexibility of the memory architecture unique to the Mac, they’ve managed to access bigger amounts of RAM even on 32-bit OS.

Kontakt, Battery: Enhanced, More Compatible, 64-bit Memory

Kontakt is able to get up to a whopping 32 GB thanks to something called the Kontakt Memory Server. Again, you can get still more than 32 GB using 64-bit Windows, but for most users, that’s overkill.

All of this is to say, 64-bit is not a reason to upgrade to Snow Leopard for audio work – at least, not yet. Some of the built-in applications (like the Finder and Safari) get performance boosts from 64-bit optimization on 10.6, but none of that is critical to audio and music – and it’s certainly not worth upgrading too soon only to find some compatibility wrinkle we haven’t yet found.

Updates to Audio MIDI Setup

A reader tips us off to some small changes to Apple’s centralized Core Audio settings panel, Audio MIDI Setup. Audio and MIDI are now separated into separate windows, and Audio gets some nice improvements.

Note the per-app settings and adjustments for sample rate, bit depth, and Format. As in previous recent versions of Mac OS, you can also aggregate multiple physical audio interfaces into one – one of a number of reasons we really love Core Audio as a sound system.

The reader also notes that the update seems to improve support for his built-in hardware:

It’s now possible to choose a higher sample rate and resolution for all inputs/outputs on the built-in sound card of my MacBook Pro early ‘08, which is pretty cool. Before there was clearly hearable, annoying digital fragments when playing back any sounds, especially on low volume – all magically gone, i don’t hear anymore noise.

Got More Information?

Help us continue our “More Than You Wanted to Know,” obsessive series of coverage on CDM and tip us off!

Corrections and clarifications are welcome, too – that’s why I enjoy the maleable nature of the Web.

The DJ Booth at Bily Kun where Bidule was first conceived.

Ed.: Music creation is all about the special relationship we have with certain, powerful tools. And one app that gets very little attention is unquestionably the deep but elegant modular patching environment Plogue Bidule. CDM turns to power user Primus Luta to kick off a series on learning this tool, starting with an exclusive interview with Bidule’s creators. And if the interview sounds, at times, more than a little pro-Plogue in bias, make no mistake: this is love. Primus Luta takes it away, as we look forward to his upcoming how-to series. -PK

In the modular future, the Bily Kun will be a leading tourist attraction for Montreal. Patrons will come with laptops tucked under their arms sporting fork bomb t-shirts. The bartenders by then will be used to answering the question only tourists ask with a slight wave of the hand toward seats on the other side of the bar. The tourists will follow that wave to the ultimate destination of their pilgrimage, open their laptop, and broadcast their location to bidulers everywhere, before reenacting some sort of virtual cabling ritual to mark their presence at the conception place of Plogue.

“It all started what seems a long time ago,” Sebastien Beaulieu, Plogue co-founder tells me. “David (Viens of Plogue) was coding a few VST plugins to add new toys to Ross Bencina’s AudioMulch. We would meet up one evening a week to code a few cool bits then head up for beer afterwards at the minimal techno pub in Montreal called Bily Kun, where most of the ideas for the future came into place.”

It was the late 1990’s. Modular audio was just coming out of a clumsy adolescence. Miller Puckette rewrote his then decade old MAX software in a new open source format to create Pd. David Zicarelli founded Cycling ‘74 to continue development of the original MAX codebase beginning with a new audio processing engine – MSP. Ross Bencina released the first of thirty six public beta versions of AudioMulch. It was a developing frontier, still early enough that the horizon couldn’t completely be made out. And while working on what would be the first Plogue product, the VST plugin ReBuilder, what would become the Plogue team started envisioning a horizon they could paint themselves.

“Once we had one completed VST,” Sebastien continues, “we decided we needed some kind of entity to release them. We ditched our temporary name while(1)fork();, used to provide a ‘label’ name for our various IDM/Minimal DJ sets. Found a Quebec anglicism/slang word for ‘plug’, some nice chaps to design our logo, and so Plogue was born.

Plogue Bidule

We did another VST plugin (MixedGrains) and then started on Bidule, which, at the start, was to be an app that would improve on both AudioMulch and MAX/MSP, in terms of providing the user with a smaller learning curve to do more. An application that could both be used as an easy modular application, because of high-level objects, and a more advanced one with low-level objects that, depending on your usage, interest or knowledge, you might never need to even look at to get you going making sounds.”

An ambitious endeavor to say the least, starting from scratch in an attempt to improve on a technology while decreasing the learning curve. All of this with a core team that in the decade since founding would only grow to four members, only three of whom are coders, and of those three only Sebastien spends 100% of his time on Bidule.

“Bidule was coded from the start with portability in mind,” he explains, “so the code is mostly C++ and STL. It uses OpenGL for the patchbay rendering. The ‘graph traversal code’ is optimized for various connection types and feedback paths. XML is used to ‘mirror’ the processing graph for serialization.”

Simple, but quite powerful. Powerful enough to attract the attention of some of the bigger names in audio software, such as Garritan and Sibelius, who came to Plogue looking for licensing opportunities. When asked if this was always a part of the Plogue business plan Sebastien firmly states, “Definitely not, but once the opportunity presented itself we thought of it has a good way to sustain and grow. The ARIA Project is a different case because we are developing that in collaboration, which means it’s something we can also use for our own products. This explains why it was developed as a sample playback/synth hybrid engine rather than a straight sample playback one.”

With a reliable buisiness to business revenue stream one can’t help but wonder what influence that has in the development of Bidule. “Our licensing work does not have much influence on what is Bidule,” Sebastien explains. “Licensing work is usually started from our base components/libraries, some Bidule-borrowed code and our knowledge from doing audio plugins and applications. There are way too many things in Bidule to use that as the basis of a licensable audio engine without ending up with either an awful amount of #ifdef or too much code separation in different files.”

On the business end of things he states, “While the added income enables us to pay ourselves and employees it also takes time to do and that time is taken away from our own projects. There’s no way to know what would have happened if we strictly worked on our stuff, would we be at the same point we are now with a physical office and employees? Would we still be working from home? Or would we have given up on doing much more interesting work for less money and gone back to your typical programmer job full time and code the fun stuff evenings and weekends?”

There’s a constantly growing community of bidulers who are thankful not to have to worry about those possibilities. Congregating in the forums, the community in many ways acts as the additional staff for Plogue. It’s an interesting model, because while bidule is proprietary the communal nature of development is reminiscent of open source. One only need look at the Feature Request section of the forums to realize the high percentage of requests that end up in future releases of the software.

“There are several possible way to use Bidule,” Sebastien explains, “and we obviously cannot think of all of them. That is where the community input is important. We can’t even count the number of times forum posts, discussions and emails have led to new features in Bidule or changed the way we were going to approach a specific feature.” As such, you can find Seb (as he’s known in the community) in the forums regularly logging bugs, discussing problems, and ensuring user needs are met. Three years ago those user needs resulted in an SDK. “The SDK came up as a quick way to add new modules. There are times when users need something totally specific to their use or setup and it doesn’t make sense to add it inside Bidule. With the SDK, anyone having some basic code skills can add their own module.”

The true testament to the power of Bidule are what the users are able to do with it. When asked for example use cases Sebastien replies, “Building a setup for an art gallery installation where control comes from external sources. DSP companies using Bidule for quick prototyping of larger algorithms and systems through building blocks and SDK-built modules. People playing live in all sorts of music styles from experimental to jazz and even faith gatherings!

“Some things have just surprised us to find out that they were even possible with Bidule,” he continues. “For example Bram de Jong made a basic time-stretching algorithm out of basic bidules. Someone else made some noise reduction algorithm out of side effects of Bidule’s FFT algorithms. There’s also what you’re doing, which we found interesting because you’re basically building a complete instrument within Bidule and documenting the process.”

All of this with a software still in beta. Easily surpassing the thirty six beta versions of Audio Mulch and going into its seventh year of public beta, perhaps the Guiness Book of Records should be contacted. When asked whether the 1.0 version of Bidule would see release this year, Sebastian navigates his web browser to a virtual Magic 8 Ball site and types the question. The answer is: Very Doubtful.

“Bidule 1.0,” he explains, “has been a long standing internal debate in here. If you made a list of programmers that can’t let go until it’s perfect, you would find us in the upper portion. Lets just say we especially dislike ‘version 6.x’ applications that crash when you just look at them and the endless cycle of pay the yearly (or so) update fee to get a few bugs fixed.” Strangely enough for active bidulers, 1.0 may not be that important. The communal style of development is perhaps the most valuable part of Bidule. Would that come to an end if it were to come out of beta?

“I don’t see why it would stop because we think it has served us very well so far. More importantly, everyone at Plogue uses Bidule as their main development/test tool for everything else they do (like ARIA and chipsounds for instance). It’s our pen, if you will. With that mindset, as long as Plogue is alive, so will Bidule.”

An Alpha Version of Bidule Running on Linux Circa 2001

If Bidule has any limitations, it is perhaps the lack of a Linux version. When asked what’s keeping the software from being ported to the open OS, Sebastien quickly responds, “A time machine might help!” As it would seem back in 2001 there was an alpha version of Bidule which did run on Linux, development on which has since ceased. “I think our main concern is that we are not yet totally convinced of the viability and welcomeness of closed-source applications to Linux. Pretty much every thing else would fall into the lack of time category (most of our other concerns would probably be answered by research and testing), chasing two major platforms is already a time-consuming task, we’re not yet ready to add a third major one.” That shouldn’t be read as the end of the conversation for Linux users. If there’s anything which cannot be overstated about the Plogue team it is that community demand moves them.

This week Plogue launches the latest public version of Bidule 0.9685. As with all public releases it comes with a three month trial period for users to demo the software. To coincide with this, I’ve been given a space over on CDM’s NoisePages where I will be providing a series of introductory and advanced tutorials in Bidule, using the instruments created for my Heads Project as examples. You can read all about the latest Bidule release and after you’ve downloaded you’re copy make your way through the first tutorial. If you’ve ever wanted to have a look at what Bidule is all about, now is the perfect time.

In the modular present, Plogue Bidule has achieved much of what it set out to do – smaller learning curve, doing more. The modular future is bright.

“Total freedom to experiment, and try ideas fast.”

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

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

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

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

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

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

It’s a bit trippy as you make your way through the opening of this video, which features a spooky song and, awesomely, a hooded man who has replaced his face with a certain hit open source controller. (“Darling, wake up, you’re shouting the names of Max/MSP patches again in your sleep!” / “I was dreaming – and I saw that man again. The man with the Monome for a face! He said – he said there’s something I must do. Where’s my MacBook?”)

Ahem. Get past that bit, and your reward is some deliciously sharp Monome virtuosity from Primus Luta:

For the pilot episode of the PEMF (Personal Electro-Magnetic Field) Sessions I go to work on The Roots "Criminal" Remix called "Break the Law." It’s a more dub than step take on the song featuring a firsthand look at the process of creation using the Heads Instruments. Specifically looking at the nsMpLR, strgs and prcs.

It’s a remix here, but naturally you could apply this to any production technique. It’s amazing how freeing the simple process of mapping musical elements to a grid of buttons can be. That would tend to confirm my suspicion that, somewhere at its soul, the Monome is a HyperMPC – an MPC with a lot more buttons, extended by everything a computer can do.

Tool of choice in this case: the wildly underrated modular patching environment / music host, Plogue Bidule.

Good stuff. If this is just the pilot episode, I can’t wait to see what’s coming. (But does Primus Luta get off the island? And is he one of the final Cylons?)

Primus Luta’s site: http://avanturb.com/

Monome official site (yep, CDM aka me will be heading to welcome them to their new Catskills barn!)

Along similar lines, a New Yorker story this week looks at Monome user Flying Lotus, and “Steven Ellison’s atomization of hip-hop.” What better to work on your atomization than the ultimate minimalist digital grid of pads? (Interestingly, he uses a lowly M-Audio Trigger Finger alongside for more conventional pads. Saying this “brings back the physical gesture of the drum” seems a stretch. I’d say it brings back the physical gesture of the Poke, recalling a time when primitive Man sat around poking his significant other – ah, yes, in fact, that’s a tradition I generally keep alive.)

Previous Monoming on CDM

From Arturia, both the CS-80V and minimoog V are now Universal Binaries. (I’m still waiting on the TimewARP 2600 Mac Intel release from Wayoutware, speaking of emulation.) Okay, that’s not actually the CS-80V plug-in pictured here; it’s Arturia’s image of the original Yamaha keyboard. I hear that doesn’t need an Intel Mac update, incidentally, though a black MacBook would look awfully cute next to one. Old meets new, and whatnot.

From Antares, best known for AutoTune, the AVOX (Antares Vocal Toolkit) has made the leap (along with AutoTune) to Mac Intel, in both native and (Pro Tools) TDM versions.

IK Multimedia’s popular SampleTank has added Intel Mac compatibility, and the upgrade is completely free for v2 users. This release also adds Pro Tools 7 support, better search, better program change support, and other enhancements. (Thanks for making it free, IK; I wish more developers would follow suit!)

My personal pick of the Intel Mac update litter this week that you might have missed, though, is the new 0.93 version of Plogue Bidule:

Plogue Bidule 0.93 update

Plogue is a bit of the underdog in the hosting category, part host, part modular environment a la Max. It’s got a few fans here among CDM readers, though. The new release adds a “split by note” MIDI Splitter. (Erm, not sure why they’re just adding that now, but carry on!) More interesting: AU sidechain effects. For power users who want control over their host, Bidule could be the way to go (it’s also on Windows). I hope this is also the way the Max/MSP interface will go: zoomable, OpenGL-based interface, and pretty patch cords, not to mention true OSC integration (client/server).

Join Universal Binary Watch!

Favorite app or plug-in (no matter how obscure) just made the jump to Universal Binary? Let us know about it.

Favorite app or plug-in (no matter how obscure) holding up your slick, new MacBook? Let us know about it, and we’ll see if we can hunt down some information. (I have ways of making developers talk.)

Head to contact and drop me a line.

[tags]universal, mactel, intel, updates, plug-ins, software, Mac, Arturia, IK-Multimedia, plogue[/tags]