Back To Schedule

An Audio Plugin’s Mid-Life Crisis!

New Features. New Framework. Same Identity?

What does a mid-life crisis look like for an audio plugin?

A successful product has been around for years. Users know it, workflows have formed around it, and expectations define what it should be. But the world keeps moving. Technologies change, new creative possibilities emerge, and the product needs to evolve. So we add a feature, modernise a system, introduce a new framework, revisit an old workflow. Before long, our perfectly stable audio plugin might be having a bit of an existential crisis.

For developers, maturity creates an interesting engineering problem. New capabilities and shared frameworks can extend a product's life, but they also introduce complexity, dependencies, and new assumptions about what that product should become.

Through examples of long-lived audio software and evolving architectures, this talk explores software maturity, feature accumulation, and architectural reinvention, asking where engineering evolution ends and product reinvention begins.

Does staying relevant require becoming something different?

Perhaps audio plugins don't need fewer features or newer frameworks. Perhaps, like the rest of us, they occasionally just need to figure out what they want to be when they grow up.