Say you’re an up-and-coming crew with a turntable and some mics. You’ve got a gig this Friday at the middle school gym (the janitor has been bribed appropriately) and the boys on the corner have been passing out your flyers to all the lovely ladies. Everything’s set, except you heard that Kool Herc is coming to battle. Herc and his mighty sound system schooled you last go-round, so you know you need something fresh to rock the bodies proper. Your DIY solution? The 55-gallon drum sound system.

Step 1: Get yourself two steel 55-gallon barrels and two 15-inch subwoofer cones.

(Kool Herc shown for scale)

Step 2: Have one of your buddies who works at the auto shop around the corner cut a hole in the bottom of each barrel. Drill some holes to mount the speaker facing out from the bottom of the barrel.

Step 3: Face the can towards the floor and have your buddy weld some 6-inch pieces of pipe on to boost it up a bit. Hook up your dad’s hi-fi stereo amp, plug in your mixer, and turn it up as loud as it will go (10 block radius). Get those bodies movin’.

Big thanks to DJ Mister P-Body and the book Yes Yes Y’All: The Experience Music Project Oral History of Hip-Hop’s First Decade. This idea comes from a story told by Tony Tone and DJ Baron about their early experiences as an MC/DJ duo.

Ed.: Now I can add this to my regrets about school, along with not taking shop to hone my welding skills — seriously, that should be mandatory. (Yeah, like I needed that extra AP. Dumb.) But I’m curious: have any of our readers tried this? Any tips to share? Perhaps we need a DIY speaker summit to try as many amplification and transduction options as possible — complete with welding lessons, natch. -PK

Laptop musicians are feeling out of sync — literally. But we can work together to help the situation.

Computer music making can be an isolating experience. But when users try to use their eminently-mobile tools to play together in the same room, they often find that the technology resists. MIDI, as a serial protocol, isn’t designed for networked environments. Software interfaces are designed to be visible to only one user. Sharing between users rarely figures into designs. Input points are made to be single-user only.

And most importantly, just getting a couple of computers to sync can be a Herculean task — one that seems to have gotten worse with advanced computer software rather than better. In short, for all the technology we have today, we’ve actually regressed from the state of interoperability 20 years ago.

I’ve been hearing more and more frustration over sync, as people begin to collaborate with multiple computers as they would with a small ensemble of instruments. Ableton Live is the most frequent example, but it’s only one case – and I suspect part of the fault is that people are more likely to try to sync multiple copies of Live. When I spoke to Depeche Mode’s Martin Gore in the spring for Keyboard, Martin complained that they had trouble syncing his Apple Logic sessions with other band members using Pro Tools and Ableton. This weekend in Los Angeles at the DubSpot sessions, Glitch Mob’s Justin Boreta talked about the issues that group has had with multiple copies of Live.

Synchronization is, by definition, a tough thing to do. But musical engineering is replete with challenges; it’s no longer acceptable to simply say “live with it” and walk away. It seems we need both better shared knowledge about what sync is how to make it work, and better engineering solutions on the software and protocols side to support the way users want to work. And yes, we need a new sync standard that goes beyond what’s presently available in MIDI alone.

Focusing this discussion, I just got an essay in my inbox that I think focuses the issue. I will try to speak to Ableton’s engineers about the matter, but this isn’t really about Ableton alone, so I’m posting it here first. We could use more data about how you’re working with various software and hardware, what techniques you’ve developed, and what frustrations you’ve had. We have a wide community here of users and developers (and a whole lot of you are both).

Mark Kunoff writes:

I’m writing to you today about an issue which I believe has been a sore spot for many Ableton Live users – *reliable* syncing of two or more computers – particularly for those of us who are attempting to sync for the purposes of *live performance*.

My musical partner Patrick Petro and I (together we perform as “Othership”) have been struggling with this issue for several years now. At present time, we have a decent solution using midi time code. Initially we attempted to use Midi “clock” but our friend Steve Duda (partner of Deadmau5 in BSOD) informed us, “using Midi clock is as reliable as syncing to a boat motor.” He informed us that in BSOD, he and Deamau5 have reliable sync between their 2 laptops using MTC, although the main drawback is the inability to fluctuate tempo – you must run at a consistent tempo the whole time. (You may be aware of this already, but Steve is the person responsible for ‘Molar’ the incredible step and loop sequencer for the Monome, was a programmer for Devine Machine and has worked for many renown artists in the music industry such as Trent Reznor. We are very fortunate to benefit from his consultation!)

Currently we are both using Macbooks and syncing via Ethernet with Audio File Engineering’s “Backline” app to generate MTC. This method has been about 95% reliable, but after reading an article on Ableton Tweets (http://abletontweets.com/post/126300941/why-midi-sync-over-ip-may-not-be-a-good-idea and our response – http://abletontweets.com/post/224247258/midi-sync-in-ableton-live-why-so-complicated) we are going to acquire a dedicated external device to generate MTC such as a Motu Timepiece.

I feel strongly that Ableton has not addressed these issues sufficiently and could do a better job of educating their user base as to the challenges that face performers in achieving reliable sync. I’m not expecting a walk in the park, but as of yet Ableton has not provided comprehensive documentation regarding these issues and places most of the responsibility on users to figure it out for themselves. We are (and have been) perfectly willing to educate ourselves but for the most part this issue remains elusive to the majority of Ableton Live users.

The Ableton Live forum posts regarding sync are fraught with dissension and are excruciating to read to say the least. I feel I’m empathetic to the complexities of programming audio applications, but in my estimation Ableton tech support’s explanations toward this issue have been mostly open ended. Many users report these issues only to report back that Ableton’s tech support doesn’t respond. I have experienced this as well. Certainly there are enough customers who want a better solution.

I feel it’s time to launch a concerted effort to organize users and demand that Ableton addresses this issue once and for all. Perhaps this solution wouldn’t even involve midi at all. Ideally this would be an open protocol such as OSC, but I wouldn’t be opposed to a proprietary solution – just as long as there is a reliable one.

The main purpose of this correspondence is seek your and CDM’s assistance in sponsoring an effort to encourage Ableton to address this issue once and for all. I feel CDM could be quite helpful in garnering leverage toward this effort (a simple blog post, or ideally a dedicated section) to organize users and to demand better sync ability between two (or even multiple) laptops running Live – even from unlike computer manufacturers. I’m sure you know artists with valuable expertise in this area.

Even if the issues regarding sync via midi are insurmountable, there have to be CDM readers who have developed reliable methods of two or more persons performing with Ableton Live and it would be great to have one centralized portal where discussions of working methods can be discovered.

Thank you for your time.

Again, my personal intention is not to single out Ableton — I’ve heard similar complaints about other scenarios, and moreover, I think the “open-ended” tech support response occurs when there isn’t an easy solution. Tech support alone often can’t deal with something as multi-faceted as sync, so it’s time to engage other users in this, as well.

I’ve also spoken to Owen Vallis and other folks about how sync could be executed more effectively over network protocols, and specifically how the time stamp feature in OpenSoundControl might be used in conjunction with MIDI clock messages.

To kick things off, let’s comment here, but I’m also setting up a special Noisepages group for users to share experiences and tips:

Sync or Swim Group [noisepages]

(Incidentally, CDM contributor Matt Ganucheau is joining me Saturday at a WordPress developer intensive here in New York, so we’ll be picking up development techniques to work on the Noisepages community, too.)

Jump in, say hello, and let’s talk about how we can make sync work in real-life musical situations.

I’ll also be talking to more artists and developers about their experiences and suggestions, and will pass along your feedback, so expect a report back. In the meantime:

1. Are you routinely trying to sync multiple musicians?
2. What software (and hardware) tools do you use?
3. What have been some frustrations?
4. What techniques have worked, or what have you learned you might want to pass along to other users at various skill levels?

Novation’s Launchpad, its affordable (<$200) "grid" controller, may have a big Ableton logo on it. But underneath, it's just a MIDI controller. Bi-colored LEDs, containing a red and green element for red, green, and amber output (amber = red+green), can be triggered using simple MIDI note and control messages. That means, whether you're looking forward to Max for Live or you're sequencing in a tracker or writing Processing sketches, you can use the Launchpad just like any other MIDI controller.

One of the things I thought was a major demerit for Akai was the fact that they failed to ship a MIDI implementation for the Akai APC40. MIDI implementations are the charts of MIDI messages we've had since the very first MIDI devices came out in the 80s. They're usually printed in the back pages of the manual, and even the cheapest gear has often had one.

Score: Novation 1, Akai 0. Novation has done the MIDI documentation, and then some. Its MIDI “Programmers Reference” is out even before the official Launchpad ship date. And rather than just doing a MIDI chart and assuming people know how to read it, they’ve taken the care to fully explain the way MIDI messages work, how to calculate the right messages, and how to really use this. Experts will have all the information they need, but newcomers will also find they can spend a little time and learn how to do what they want.

Launchpad Support with Downloads (see Programmer’s Reference at the bottom)
Via: Novation released Launchpad Programming Guide, and Protocol [Nezoomie's Zen Wave Blog - great read]

It’s listed as “for Max/MSP programmers,” but anyone using MIDI will want to have a look; that’s obviously relevant to far more than just Max. (In fact, there’s not a single mention of anything specific to Max in the document.)

What might people do with stuff like this? Well, as of just four hours ago, Matt DiFonzo lets us know he’s written a simple monome emulator. It’s even got a clever name:

nonome – monome emulator for Novation Launchpad

There’s some bad news mixed with the good. Even with something as simple as a grid of buttons, MIDI isn’t as friendly as it could be. I still would like to have a MIDI editor for the Launchpad so you can reassign buttons if you like — that’s a feature, incidentally, available on rival Ohm and Block hardware from Livid Instruments. Also, the documentation reveals that Launchpad uses “a low-speed version of USB,” which runs at a maximum of 400 messages per second, thus taking 200 milliseconds to update a Launchpad’s LEDs. (There are some workarounds, but they’re … more work. Clarification: Once you double up messages, though, you can get this to a more acceptable gap, and that’s for updating all the LEDs, not the latency of input messages.)

Also, here’s a hint to Novation: use a Creative Commons license for that document. That way, your users will be free to document even more ingenious solutions and friendly guides. You win, and your users win. For instance, I have the illustration here, which I should be able to do for purposes of reporting on this story. But can I write my own how-to guide using your guide? Why not make it explicit to encourage me to do so? (They list the PDF as “proprietary,” though there’s no explicit license, and I think they just mean “proprietary” as in “what we’ve done on our hardware.”)

That’s a difference between open hardware and closed hardware, but I don’t even want to belabor the point — CC licenses are something a commercial company like Novation could easily use. In fact, if anyone at Novation or Ableton would like to talk to me about why I think it’s a good idea, I’d like to extend an open invitation. I’m no legal expert, but I can explain what it means to me as a user and developer, and connect you with some of the right people at Creative Commons and the CC-using community.

But those gripes aside, kudos to Novation for getting this documentation out here. I think it’s really good news for people experimenting with grid controllers. And we’ll be looking at how all of these tools, hardware and software, fit together, and how open source development can make them more powerful.

Patchers and coders and hackers: if you’re interested in working on interoperability between all this stuff, let us know.

Once upon a time, people made things from electronics. Boys, girls, laypeople made stuff. My Dad actually tinkered with Theremins growing up and subscribed to Popular Mechanics. Now, in an age of hyper-specialization, too many people assume that making sounds with geeky-looking, handmade electronics should be left to the pros. But give people some instruction and let them make some noise, and you might be surprised how eager people are to try something out. Noise making, it seems, is some sort of primeval human instinct.

So, it comes as little surprise that the wizards of Austin got lots of people into the act of electronic sonification. Led by Dr. Bleep, Eric Archer, and 8ms, they’ve kicked off the Texas iteration of Handmade Music Night, and send us the video to prove it.

There’s no reason you have to be left out of the fun, though – you can handmade some loud noises at home. Eric Archer has expanded the site for his freebie Mini Sound Rockers, the kit he used to get folks started at Handmade Music Austin:

http://ericarcher.net/devices/mini-space-rockers/

Check out the video below to see them in action. And I think we should definitely have, in addition to the schematics, a step-by-step tutorial. The gang in Austin also promises some ready-to-buy kits coming soon, so stay tuned.

More on the Handmade Music series around the world:
http://handmademusic.noisepages.com/

And for another video of the Mini Space Rockers circuit, here’s a terrific creation from Switzerland, as suggested by Eric in comments:

The work is by datenkrieger75, using both Eric’s circuit and a hacked Gakken SX-150 bassline.

The Covert Seq – Creating patterns and Presets from Bjorn Vayner on Vimeo.

The Covert Operators and Bjorn Vayner have become my favorite go-to source for wild Ableton Live hacks. And even before the release of Max for Live, Bjorn has built some terrific, simple step-sequencers using Live’s Racks feature. That’s just the Racks feature – no Max patches or hidden features anywhere to be found. Sure, I suppose the clip view itself can be seen as a kind of step sequencer, but this gives you a unique way of generating sequences.

If you just want to begin playing with step sequencing in Live, Bjorn has a new download, aptly called The Covert Sequencer, as seen in the video at top. It’s free, it’s fun, it celebrates the 5th Anniversary of Covert Ops and the 10th of Ableton Live (good grief!), and it’s all voodoo built with dummy clips and MIDI effects.

Full post, downloads, and video tutorials:
The Covert Seq [The Covert Operators]

If you want to try your hand at the ninja skills behind all of this, Bjorn posted a screencast back in August revealing his secrets:

Making a Step Sequencer in Ableton Live. from Bjorn Vayner on Vimeo.

And if you like this sort of thing, definitely don’t miss The Covert Operators’ exclusive creation for CDM, making elaborate use of the racks and slicing features of Live 7 and later:

Exclusive: Free Ableton Live Slicing Pack by Covert Operators

Slice of Winter from Bjorn Vayner on Vimeo.

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.

four tiny drum machines from ALH84001 on Vimeo.

Cybernetics is poised to make a comeback. The theory is, everything from electronic circuits to plants and animals can be understood in terms of feedback loops, as organisms – mechanical or organic – respond to input from their surroundings. The father of modern cybernetics, MIT mathematician Norbert Weiner, was inspired by working on the guidance systems of missiles. His writing was picked up Louis and Bebe Barron, informing their organism-like sonic circuits, as used in the film Forbidden Planet. The word cybernetic itself comes from Plato. Plato was talking about human self-governance. But designed with cybernetic ideas in mind, technology, too, becomes self-governing and autonomous – and the sonic circuits, too.

Young designers like Eric Archer are to me the newest continuation of work like the Barrons’. Inside his lab, Eric and others are creating hardware that behaves like intelligent life. In the video at top, four tiny drum machines, equipped with insect-like brains and reflexes, network together wirelessly over infrared, responding to light by way of photocells. These tiny devices form a colonial consciousness.

Eric may be a mad scientist, but he isn’t keeping his work secret or proprietary. He’s sharing the tools, sharing his methods, and with a whole growing crew of sonic DIYers in Austin, Texas, inviting anyone to join the revolution under the banner of the Handmade Music series. (More on the upcoming event shortly.) If you’re not from Texas, a lot of this documentation is also appearing online.

Here are more of the creations, plus the simple but powerful circuit that makes it all happen.

And yes, there’s a lot of potential to wireless IR sync.

The drums have names:

Drum Machines (Eric Archer)
ASR mk I “pops”: two analog damped sine oscillators with photocell pitch control, 16 presets
ASR mk II “snappy”: analog white noise, photocell controlled filter, envelope + VCA, 16 presets
ASR mk III “twiki”: photocell tuned analog osc, photocell tuned LPF, envelope + VCA, programmable
ASR mk IV “boomer”: analog damped sine oscillator, long decay, photocell pitch envelope, programmable

But drum machines are just the beginning of what could eventually be wirelessly synced. First up, this autonomous bassline generator, created by 4ms Pedals

The Autonomous Bassline Generator creates deterministic bassline patterns in a sci-fi retro sound by generating melodies on the fly, based on a knob. It’s just an AVR (attiny44) chip doing all the work, plus an opamp to act as the filter (photocell). The blue button is Tap Tempo, or if you hold it down for 1 second, it syncs up to the pulses on the IR receiver (this lets you beat-sync multiple Andromeda Space Rocker modules). The red button lets you edit a single note in the melody. Pulse-width modulation is currently pre-set to a certain envelope, but that will become user-controllable soon!

Part of the “Andromeda Space Rockers” series of modules, see www.ericarcher.net for drum modules.

The 6-pin header board dangling to the right is an ISP header. Totally hackable!

“Ah,” you say. “But I have computers and things. I don’t just want a bunch of little drum machines running around my studio like so many electronic beetles while I furiously tap my tap tempo in Ableton. Can’t I sync thing up?”

Yes. Yes, you can. There’s already a MIDI-to-IR prototype in the works.

Four analog drum machines are synchronized with a desktop computer running Logic. Logic is playing a loop with TR808 samples. MIDI timecode from Logic is converted to IR Sync with a PIC microcontroller. The PIC flashes an infrared LED, providing wireless clock to a chain of analog drum modules. Each drum module has an onboard sequencer, analog sound generator, and IR Sync repeater. At the end of the video, the tempo is increased to almost 3000 BPM. In a separate test, the system played OK at 1000 BPM. Of course this tempo is ridiculous but it is a nice “torture test” of Nathan’s PIC code.

PIC stuff: Nathan Wooster
drum machines: Eric Archer

Our friends at Bleep Labs also have projects in the works.

Eric and 4ms have contributed the circuits at the heart of this.

This simple circuit handles infrared clock networking. (Click for the full circuit.) I’m assuming you know how to read this; we may have to put together an actual how-to tutorial for those new to electronics, too.

And 4ms has a version for interfacing with microcontrollers.

The Barrons would be proud.

For more on the Handmade Music series as it spreads around the planet, visit http://handmademusic.noisepages.com.

Seeing a tracker interface for the first time can be intimidating. But dive in a bit deeper, and you’ll discover what’s actually a very efficient interface for programming in musical sequences and working with samples. With just ten days left in the Renoise – Indamixx music production contest, there’s still time to get up and running using even the demo version of Renoise (into which you can import samples). And this could be a great excuse to learn a new tool.

Dac, who’s a big part of support and community for Renoise, has put together a nice tutorial showing off the workflow in the tool. It’s nothing all that unusual: bring in samples, assemble patterns, make music. Some of the voice over is hard to hear, but this is a good start. Now, I still like reading and writing better than video just in terms of how I learn, so I may try to work on a written version for the end of the week; feel free to shout encouragement.

For more Renoise inspiration, forum regular djnick sends along a PsyTrance video made in Renoise – so, yes, you can make PsyTrance with a tracker, too, if you like. He samples Peter Jennings talking about ecstasy. Yeah, whatever – as if you can make Peter Jennings any more trippy. Watching Jennings is the ultimate natural high.

And here’s the original jerk beat tutorial. (Hey, who are you calling a jerk beat? Sorry, that just can’t sound not strange when I hear that phrase…)

Enjoy. Got specific requests for how-to’s, other tips or tutorials you’ve found useful, or questions you’d like answered? Do let us know.

It’s simply stunning some of the terrific instrument and effect plug-ins available that are now free and open source – yes, free as in freedom, not just freeware. I had commented in the past something along the lines of, “boy, wouldn’t it be great if this now meant, say, a Linux port?” and then went on the business of my daily life, which tends not to include re-compiling plug-ins. But now, the folks of JUCETICE have been busy doing just that, serving up delicious instrument and effect goodness, running native on Linux.

Translation: fire up that netbook and make some music.

Following up on our tutorial on Ardour and netbook-optimized music competition with Renoise and Indamixx, here’s what you need to get rolling.

With Linux growing in popularity on netbooks – and an option like the pre-configured Indamixx solution saving you the work of optimizing and configuring it – it’s suddenly no longer a stretch to imagine yourself a Linux music user. Of course, what you don’t want is to wind up without the arsenal of plug-ins to which we’ve all become accustomed. There are various ways of hosting Windows VSTs under Linux as though they were native plug-ins; check out dssi-vst (which also enables 32-bit VSTs from Windows under 64-bit Linux hosts), in conjunction with WINE. That should probably be the subject of a separate tutorial. (Ardour 3 also promises Windows VST support.)

But here, let’s have a look at native Linux plug-ins. JUCETICE has some beautiful creations of their own – an elegant, 32-voice polyphonic drum synthesizer and a TB-303 clone – plus some familiar favorites ported from Windows, like the ingenious DiscoDSP sampler created by the late, great Arguru.

Here, we’ll use the native Linux version of a commercial host, energyXT. energyXT is proprietary, but it costs just EUR59, has a free demo to check out before you purchase, and – if you do like it – is really different than any of its competitors.

Patrick Shirkey of 64studio, the music-centric Linux distro, walks us through the steps necessary to get the JUCETICE plug-ins going under energyXT on Linux – all native, no WINE or Windows anywhere.

I’ll be doing this myself on my Indamixx test unit, and will let you know how that goes.

Developer note: yes, you should definitely check out the JUCE framework, which makes developing cross-platform C++ easy, efficient, and modern, and is free for open-source projects.

Patrick explains:

1. Download the jucetice linuxvst plugin : http://www.anticore.org/jucetice/?page_id=7

2. Make a folder called “plugins” in the home directory

3. Save or move the plugins to that folder and extract the plugins.

4. Open energyXT and add the “plugins” folder to the “Plugins” folder list. Choose File > Setup:

Select the “Browser” tab and set it to the “Plugins” section.

Now select the “plugins” folder and add it to the list of known folders.

[Here’s what it looks like in the path structure.]

5. To add the plugin to a project double click on the “Plugins” section on the left panel of the main window to show all the plugins and right click on the plugin you want to use. Click “Add as Send” from the popup menu.

6. Finally, open the “Window” menu and choose the plugin from the list to display the user interface and adjust the settings.

Ed.: Definitely let us know if this is helpful to you; we’ll have some more comprehensive, big-picture tutorials on this stuff soon – but in the meantime, I’m definitely checking out these instruments!

The tracker is back. Piano rolls and fake multitrack tape turn out not to be the only way to conceptualize how music is put together in digital form. And Renoise is a terrific way to learn a ground-up approach to production, because you get the quick workflow of the tracker without having to sacrifice so many of the “comforts of home” we’re used to in modern DAWs. So we’re pleased to have our Renoise + Indamixx contest going, not only for existing users, but newcomers, too.

Renoise users have one way of evangelizing why they love their tool, which is to show off, as seen in the excellent video above. But what if you’re new to Renoise, or new to trackers in general, and want to experiment? You don’t even need to make a cash investment: you can start to experiment with a relatively full-featured demo version on Mac, Windows, and Linux. The time investment is the likely barrier. So I asked Montreal-based Dac Chartrand of Renoise, who is also the man who keeps tabs on the community, to share his tips. Here’s what he suggests:

1) XRNS files are source code. Find one you like, load it up, press the spacebar and start clicking around. Renoise will happily chug along as you explore each and every facet of the sequencer. When you get bored of clicking, try remixing. Move some notes around, press the escape key and jam on the QWERTY keyboard. Anyone familiar with trackers will tell you that this is how it’s always been done, this is how it always should be, file sharing since the days of Amiga. PRO TIP: Tutorials and Demo Songs are in the Help menu.

2) YouTube is your friend. Go there, type Renoise, watch and learn. Enthusiastic users show off their tunes, some even make "Do It Yourself" tutorials for good measure.

3) Download the "Pattern Command Quick Reference Card" PDF file. This DIY reference was created by a user in the Renoise forums. It’s a cool print out that folds up and sits pretty  on your desk. Pattern Commands are special columns to the right of notes; lets you take sample manipulation to the next level.

PDF: http://paulmerchant.com/downloads/RenoiseReferenceCard2.pdf

4) If you don’t know trackers, then forget everything you learned about other DAW workflows. You must unlearn what you know in order to be a jedi master. For example, other sequencers  have a very strong relation between track and instrument. In Renoise, instruments go anywhere,  tracks are what you make of them. Other sequencers have a timeline, Renoise has patterns that you chain together to make a song. A newbie mistake is to try to make one gigantic pattern.  Instead, make several smaller patterns and sequence them.

5) Documentation. Yup, it’s thee copout tip. But seriously, there are tons of documentation on the Renoise website. Not reading them is kind of stupid.  When all else fails, browse the forums or see if anyone in IRC chat can help.

DOCS: http://tutorials.renoise.com/
FORUMS: http://www.renoise.com/board/
IRC: http://www.renoise.com/community/chat/

Thanks, Dac! Now, I’ll also be working on some stuff for CDM soon, as well, but this should get you going in the meantime.

Must-Have Renoise Utility

Bantai at Renoise also shares (via comments) an excellent tool for sharing your work in Renoise, compressing files, and – aprospos of Dac’s suggestion – inspecting existing XRNS files.

Another tip: you can get the filesize of your song down by up to a factor 10 if you use lossy compressed samples instead of the default 32-bit stereo FLAC file format. I reckon a small filesize wins you bonus points in a tweaker’s compo.

Since Renoise songs are basically ZIP files containing song data and samples, it’s almost trivial to run the extracted contents of the song through OggDrop or a similar application and zip it up again.

It can be easier: I have written a Java tool that takes the work out of your hands and compresses your Renoise XRNS song automatically:

XRNIRipper

(Java geeks, he also writes me: “I’m using vorbis-java lib from xiph.org and a modified version of jFLAC to support Renoise’s custom 32-bit FLACs. There are also several libs included to convert sample and bit rates. Curiously enough, I couldn’t find any other Java apps that encode files to Ogg Vorbis.”)

More Videos, Tips?

It’s a couple of years old and based on an earlier version, but I especially liked this tutorial for demonstrating what the workflow is about:

And if you Renoise-using readers have tips, or if you find a YouTube video you think is especially awesome, please do share. I’ll get back to working on my basic guide.