// I need to

ModernizeUpgrade without breaking it RescueFix what someone else started Build NewTurn an idea into a product Reach More PeopleGet found, get used, include everyone

// Company

Case StudiesExpertiseAbout + CareersResourcesContact Book a call →

Designing Audio Effect Plug-ins in C++ (book review)

A developer's review of Designing Audio Effect Plug-ins in C++: what it teaches about writing VST and AU effects, and how it helped a JUCE audio project.

Art+Logic Jul 3, 20133 min read

From the Art+Logic archive · written in 2013. The tools may have moved on; the thinking still holds.

Image of Book cover for Designing Audio Effect Plugins in C++

I’ve been writing a series of posts here over the last few months discussing the JUCE C++ application framework and how useful it’s been in creating the ‘Scumbler’ looping audio performance application that’s my current nights & weekends project. One of the important requirements that I had for the project was that it be able to use existing VST or AU audio effects plug-ins to process the audio during performance.

Over the years since I graduated with a degree in electronic and computer music, I’ve accumulated a fairly large shelf of books on digital signal processing theory and applications. Earlier this year, Focal Press released what’s the most usable book on writing audio effects plug-ins. It’s very easy to find books for theorists, or for people who already have very heavy math backgrounds explaining the concepts behind DSP; it’s rarer to find resources targeted at interested and motivated practitioners. Anyone coming to this book with a relatively solid background in C++ programming and high-school math (trig and at least pre-calculus) should be able to work through it and come out the other end with an understanding of much of the DSP that’s needed out in the wild.

What’s Included

Any book like this needs to include a chapter on basic digital audio theory, and having read a lot of those chapters over the years, this one should be especially understandable to someone new to the concepts, the author is a professor of music engineering at the [University of Miami](http://maps.google.com/maps?ll=25.721644,-80.279267&spn=0.01,0.01&q=25.721644,-80.279267 (University%20of%20Miami)&t=h “University of Miami”)’s Frost School of Music, and it’s clear that the book has benefited from many semesters of refinement from teaching the material to students there. The book proceeds in a logical fashion from “this is why you can turn sound into numbers and back into sound without losing anything” into the central concept of the math behind digital filters through the major categories of digital filter topologies, delay lines, oscillators, reverbs, and the various ways that parameters can be modulated.

RackAFX

RackAFX

From my point of view, the one thing that really sets this book apart from any of the others I’ve read is that it uses a piece of software developed by the author that jumpstarts your plug-in development. The RackAFX software:

It’s a minor quibble of mine that RackAFX only runs under Windows, but in practice all that means is that I need to start up Parallels Desktop and get Windows 7 running. That’s a good excuse to get a refill of my coffee while the hard drive spins, so everything comes out even in the end on this point.

The RackAFX software and a boatload of additional content not in the book are available at the author’s website: http://www.willpirkle.com/

Even if you already have some experience in this topic, this is an excellent book to have on the shelf.

Disclosure: The author is a friend, and we were both in grad school at U Miami at the same time.

keep going

More to explore in Build New.

All Build New resources →
let's talk

Got a problem like this one?

Tell us what's stuck. A real person replies within one business day.

Talk to our team →

Talk to people who know software, not a sales script.

Your first call is with Aja, our VP of Sales. He'll help make sure you're solving the right problem. Here's what you'll cover together:

  1. What you're trying to accomplish

    The business goal first, then the technology.

  2. Possible approaches

    And the tradeoffs of each, in plain language.

  3. Risks you may not have considered

    Technical and business, before they cost you.

  4. Whether AI changes the math

    What's practical, and what's just hype for your project.

  5. Sensible next steps

    Even if the right next step is not us.

book-a-call.ics

Loading the scheduler…

Open the booking page →

Some problems are easier to explain in writing. Send us a few lines about what you're working on, and we'll reply within one business day. Helpful to include:

  1. What the software does, or should do
  2. What's stuck, or what's worrying you
  3. Any deadline or budget you have in mind
note.md

Loading the form…