MVerb - A Free Open Source Reverb

[wolftune]

Whatever happened to this? It seems nice and I wish it were included in KXStudio.
Martin Eastwood's site seems to be down. I have the .so files from an old download still. Maybe it could be packaged in KXStudio?

[wolftune]

the linux version it's kinda broken, and 32bit only afaik.
I could port it into the distrho project, but we already have pretty good reverbs so I don't see the point.

which reverbs do you think are best? And have you listened to this one and compared it to others? I remember liking it messing around on my Mac years ago. If it sounds different from other reverbs (and good), then I'd like to see it in distrho, but if there's others that are really similar (and also similar enough or better in terms of flexibility and CPU use), then forget it. I liked its simple interface anyway. Reverbs can be pretty quirky so the differences can be interesting.

Anyway, I simply haven't fully explored all the plugins in KXStudio yet…

[wolftune]

wonderful!

[wolftune]

Looks like Jeff beat you to it:
viewtopic.php?f=24&t=10716

You could just package his port in KXStudio or maybe there's something you'd want to do to adapt it (I'm assuming / hoping that he knew about the updates you linked to, Jeff did mention updates in his post)

Cheers

[wolftune]

Looks like Jeff beat you to it:
viewtopic.php?f=24&t=10716

You could just package his port in KXStudio or maybe there's something you'd want to do to adapt it (I'm assuming / hoping that he knew about the updates you linked to, Jeff did mention updates in his post)

Cheers

Nevermind, Jeff did not use the updated code, and he included no GUI. So maybe it still makes sense to port separately.

[j_e_f_f_g]

The "updated" code is functionally the same as martin's original code, except with a 4 input version. I don't see the point. Loading up 2 instances of my optimized version would be more efficient and versatile.

[wolftune]

The "updated" code is functionally the same as martin's original code, except with a 4 input version. I don't see the point. Loading up 2 instances of my optimized version would be more efficient and versatile.

Ok, if that's it, I don't care. falkTX seemed interested enough in the update that it seemed to make him change his mind about doing a port, so I thought it was something more remarkable.

So falkTX: do whatever you think makes sense, but packaging some port of this in KXStudio makes sense, if just Jeff's port as is! Thanks