Agreed, it does not seem to be a clean approach to hardcode IR into a processor. OTOH, some plugins might offer specific settings and that would mean that these settings had to be outsourced to some other plugin. Specifically, I have Flo’s IR collection/summary ( http://flos-audio-plugins.eu/index.php ) in mind. Wouldn’t it make more sense to have these settings in one place? (Sounds like a rhetoric question … but it isn’t.)

Yes, that’s what they are … a collection of impulse responses, with some interface around them. The options represent (if I understand correctly) just individual IR files. I am just afraid that there would be lots of scrolling if the user had to select a file from a list.

I know they’re brand new (just announced a few weeks ago), and I have used the redwire IRs and they’re really great. I’m excited about the flo plugins because they are basically just an IR manager for these extensive sets of IRs. In theory I think they would be GREAT on MOD. And really, I don’t see how they could mess it up since its really the IRs making the sounds. I’ll have to give them a whirl. I’ll post back here if I get a chance to demo them soon.

I have not used them much, but toyed around with them. Florian did not make them… he used freely available IRs and built and interface around them. But yes, I like them quite a lot! There are just soooo many combinations to try out… which is why the interface is handy.

Want to give them a listen, too? Install audacity, $mkdir /usr/bin/plug-ins/ , extract the downloaded file there, enable in the audacious menu. I was surprised how easy it was.

There is some choice regarding IR-based reverbs, but we need to support file management on the units first.
With the Duo X being able to used as composite usb device, this opens the door for it.
Something to expect next year

Newbie here, I have a question regarding this. When switching from one patch/pedalboard to another, can I get spillover to the next patch? How long is the latency when changing from one patch/pedalboard to the next?

We cut the audio when switching pedalboards, as a way to make them load faster (there is no need to keep doing processing while removing plugins, if everything is about to be removed and replaced with a new set).
The “latency” (better worded as load time) will depend on the plugins you use in each pedalboard. For example, if you use one of the Fluid plugins (they are soundfonts in plugin format), it will take longer to load compared to mda synths because the Fluid stuff has to load the entire soundfont from disk.

We introduced “pedalboard snapshots” (previously labelled as pedalboard presets) as a way to allow gapless, much faster changes, of the pedalboard sound.

this might not be too user friendly, but personally I’ve been using a framework created by @Jarno to load my custom IR’s, it requires you to compile the impulses into the plugin (I do this with audacity’s sample data export for instance and paste them in the IRdata.h file)

Again with file handling in place, this will be made way easier, just wanted to mention it ain’t impossible at the moment if you want to put a bit of effort into it