Replacing 2Caudio Reverbs

[jens]

Are we there yet?

I certainly hope not - the GUI imo clearly needs a lot of work still...

[Aloysius]

[jens]

Ah, so you asked that with your best Eddie Murphy voice?

[VariKusBrainZ]

^ A demo version is a good indication that it is

[2ca]

yes, getting close. things left to do:

A) Re-design UI for better experience. This is mostly about editing skin's yaml files rather than the code.
well, since UI is completely in a skin (even including shader code) anyone can design their own skin simply by
editing text files. UI/Skin also supports localization

B) Make factory presets. Contributions from users are greatly welcome

C) Do full manual

D) Optimize the dsp code some more (there is a room to make the code 2-3X faster on AVX2/AVX512 enabled CPUs)

E) of course fix various bugs which are still there

anyway this latest version has most of the reverb alg systems working properly now.

Denis,
DEVPROAUDIO
https://devproaudio.com

[pchase]

It's sounding really good. Could you clarify what type of DRM will be implemented in the final product? Thanks

[Aloysius]

iLok please

[2ca]

nothing fancy. just serial code without internet access requirement

[Funkybot's Evil Twin]

Just some feedback, and I mean this to be helpful and constructive for future products, but I gave this a go and it's just "too much" for me. I think I'd be in for a "simple version" but there are a LOT of parameters here. The tabbed GUI with lots of equally sized knobs doesn't help dial back the complexity either IMO. As an end user, this feels like a reverb for tweakers, or one where a bunch of hidden "behind the scenes" parameters were left exposed to end-users. It feels like there are areas where something that could've been one knob, are three or four knobs.

It's fine. Not everything needs to be for me.

But maybe for a next product, to try something different, perhaps target a simpler approach with far fewer controls, no or fewer tabs and do a little more hand-holding for users with the target of getting consistently good sounds quickly. You could make important knobs like Decay and/or Mix larger to emphasize them visually. Or don't do any of that stuff. There are other products that do that too. But as an example: I feel like the Exponential Audio verbs from back and the day, now Equinox from Izotope, is about as complex as I ever want to go in a reverb. I can make those work quickly but they're still very flexible. Valhalla stuff is my jam too and the absolute simplest I'd ever want a reverb to be. So in my head, fewer controls/options than ValhallaVintageVerb is too simple, and more controls than Equinox is too complex. But anything within that range is a nice place to be and kind of the sweet spot.

No one asked, but those are my two cents. Reverside is certainly a very different take on verb than what I'm used to and that in and of itself is kind of cool. But I just can't wrap my head around it and won't ever really sit down to learn it.

[2ca]

Thanks for the feedback. The UI/UX is just a test one, it's really hard to come up with a nice UI for such a complex product at a first run. I might need 2-3 more iterations to find something useful. Also a lib of factory sub-presets which is supposed to help to organize/navigate this complexity is not there yet.

[jens]

Just some feedback, and I mean this to be helpful and constructive for future products, but I gave this a go and it's just "too much" for me. I think I'd be in for a "simple version" but there are a LOT of parameters here. The tabbed GUI with lots of equally sized knobs doesn't help dial back the complexity either IMO. As an end user, this feels like a reverb for tweakers, or one where a bunch of hidden "behind the scenes" parameters were left exposed to end-users. It feels like there are areas where something that could've been one knob, are three or four knobs.

It's fine. Not everything needs to be for me.

But maybe for a next product, to try something different, perhaps target a simpler approach with far fewer controls, no or fewer tabs and do a little more hand-holding for users with the target of getting consistently good sounds quickly. You could make important knobs like Decay and/or Mix larger to emphasize them visually. Or don't do any of that stuff. There are other products that do that too. But as an example: I feel like the Exponential Audio verbs from back and the day, now Equinox from Izotope, is about as complex as I ever want to go in a reverb. I can make those work quickly but they're still very flexible. Valhalla stuff is my jam too and the absolute simplest I'd ever want a reverb to be. So in my head, fewer controls/options than ValhallaVintageVerb is too simple, and more controls than Equinox is too complex. But anything within that range is a nice place to be and kind of the sweet spot.

No one asked, but those are my two cents. Reverside is certainly a very different take on verb than what I'm used to and that in and of itself is kind of cool. But I just can't wrap my head around it and won't ever really sit down to learn it.

Keep in mind that at the moment there is a lot of redundancy, so while Reverside is indeed a very deep plugin, it at first sight appears even more complex than it actually is.

[Funkybot's Evil Twin]

Thanks for the feedback. The UI/UX is just a test one, it's really hard to come up with a nice UI for such a complex product at a first run. I might need 2-3 more iterations to find something useful. Also a lib of factory sub-presets which is supposed to help to organize/navigate this complexity is not there yet.

Thanks for listening and replying!

Maybe consider grouping the most "important" controls in a "Main" or "Easy" tab and make that the default screen? The idea being that most users would never need to dive deeper into the tabs unless they really wanted to.

You could probably limit that just to:

1. Decay
2. Pre-Delay
3. Size
4. Diffusion
5. Density
6. Spread
7. Width
8. ER/LR Blend
9. Low Frequency Decay xOver
10. Low Decay
11. Hi Frequency Decay xOver
12. Hi Decay
13. Mix

...I'd say that's like 95% of what I'd ever use right there and entirely avoids the need for tabbing for me.

[jens]

Thanks for the feedback. The UI/UX is just a test one, it's really hard to come up with a nice UI for such a complex product at a first run. I might need 2-3 more iterations to find something useful. Also a lib of factory sub-presets which is supposed to help to organize/navigate this complexity is not there yet.

Thanks for listening and replying!

Maybe consider grouping the most "important" controls in a "Main" or "Easy" tab and make that the default screen? The idea being that most users would never need to dive deeper into the tabs unless they really wanted to.

You could probably limit that just to:

1. Decay
2. Pre-Delay
3. Size
4. Diffusion
5. Density
6. Spread
7. Width
8. ER/LR Blend
9. Low Frequency xOver
10. Low Decay
11. Hi Frequency xOver
12. Hi Decay
13. Mix

...I'd say that's like 95% of what I'd ever use right there and entirely avoids the need for tabbing for me.

Many of these would have to be macros with Reverside's architecture and thus I'd personally prefer a
macro-page instead, where you basically could roll your own - including presets ideally, so what you wish for could still come true.
(But keep in mind that there could be a number of very different sounding (and behaving) macros with the exact same parameter-set you propose.)

[jalex]

On mac os 15.5 (arm) there is a lot of crackling when changing parameters. Tested in renoise

[bk]

Latest version 095 b370, Win 10, Studio One 5 Pro: I have experienced a number of crashes, typically when instantiating the plugin, but not always. Studio One shows a message that it has created a dump report, which I can't read, but on next start the app asks if I want to disable Reverside before starting. Other times it seems to work fine. When the crash occurs, Studio One is still visible, but I can't open any plugin guis until closing and re-opening Studio One.
This type of crash did not occur for me with the prior version I was using, but I'm not entirely sure which version that was.