Iron Stack Released — A Breathing Wall-Gain Machine

[kbudrin]

I've recorded a new demo comparing the Community and Full versions of Iron Stack.

This comparison focuses on one specific feature: the cabinet model.

The Community Edition uses a static cabinet response, while the Full version includes a dynamic cabinet model that reacts to signal energy and load.

The demo gradually increases both MASS and POWER, starting from a light crunch, moving into more extreme settings, and finally returning to a cleaner sound with a large amount of MASS applied.

At lower settings the difference is subtle, but as the amount of low-frequency energy increases, the two cabinet approaches begin to diverge quite noticeably.

The goal here isn't to showcase a particular tone, but to demonstrate what happens when a cabinet model is pushed into situations where a traditional static response may struggle.

Demo:


Iron Stack Community Edition:
https://budrinlabs.com/ironstack

As always, feedback is welcome. I'm particularly interested in whether you hear a meaningful difference between the static and dynamic cabinet approaches, and if so, where it becomes noticeable.

[pekbro]

Thanks for preparing the demo, will give it a try soon.

[JerGoertz]

I'm no guitar player, but I've always loved distortion, and this thing sounds alive & organic in the demo's.

Nice work!

[El°HYM]

Interesting project, while still not really getting the main difference between AmpLab & Iron Stack.

[kbudrin]

Interesting project, while still not really getting the main difference between AmpLab & Iron Stack.

That's a fair question.

The short version is:

AmpLab tries to reproduce the behaviour and limitations of real-world guitar amplifiers.

Iron Stack explores what happens if some of those historical limitations are relaxed while keeping the system physically responsive and dynamic.

For example, many traditional high-gain designs aggressively control low frequencies before distortion stages because too much bass tends to destabilize the entire signal chain. Iron Stack takes a different approach and tries to preserve more of that energy, then manages the consequences dynamically instead of simply filtering it away.

As a result, AmpLab is generally closer to familiar amp architectures, while Iron Stack is more of an experiment in alternative amplifier behaviour.

In practice, AmpLab asks:
"What does this amp do?"

Iron Stack asks:
"What else could an amp do?"

[kbudrin]

To expand on that a bit:

AmpLab and Iron Stack actually come from the same underlying idea, but they pursue different goals.

AmpLab is primarily an attempt to reproduce the behaviour of real amplifiers. Not necessarily specific products or exact circuit clones, but the kinds of physical constraints, interactions and compromises that shaped real-world guitar amp designs over the years.

Iron Stack starts from a different question:

"What if some of those constraints could be relaxed without abandoning the underlying physics altogether?"

Many amplifier architectures evolved around practical limitations: limited headroom, speaker behaviour, low-frequency stability, stage interaction, and so on. Iron Stack is an experiment in exploring alternative solutions to some of those problems. In some cases, solutions that would be extremely difficult, impractical, or outright impossible to implement in traditional hardware.

The important part is that it isn't intended to be a "magic box" where arbitrary DSP tricks are used to force a result. The goal is still to maintain a physically plausible, dynamic system whose behaviour emerges from the model itself.

So if AmpLab is about exploring real amplifier behaviour, Iron Stack is about exploring alternative amplifier behaviour that might have existed if designers had access to a different set of constraints.