KVR Audio

valhallasound · Post by **valhallasound** » Fri May 27, 2011 11:30 pm

New Tips and Tricks: Getting unrealistic hall sounds out of ValhallaRoom:

http://valhalladsp.wordpress.com/2011/0 ... l-reverbs/

I tossed a few sound examples in there as well, in case any of y'all haven't heard ValhallaRoom.

Sean Costello

mooter · Post by **mooter** » Sat May 28, 2011 12:24 am

Methinks Warbler on a low amount and lfo speed would be nice after that...

fgimian · Post by **fgimian** » Sat May 28, 2011 12:43 pm

Hey Sean, just wanted to say that I'm a big fan of your work. I decided to keep Audio Damage Eos after purchasing it and demoing against ValhallaRoom for the last day. I think they are both awesome and I can easily see myself also buying ValhallaRoom in the near future.

Here are some notes I made while trying out ValhallaRoom for your consideration (I'm on Windows 7 x64 running Cubase 6.02 x32):

- I'm colourblind and the colours used for the selected Reverb Mode and Preset are impossible to see with my eyes
- The CPU usage was a reasonable amount higher than Eos and ArtsAcoustic, although not unreasonable
- In Cubase 6, when the plugin interface is open, you can not minimise the arrange window, the Cubase interface locks up and you have to Alt+Tab out of it and go back to get the app to respond again, any ideas? This also affects closing other windows in Cubase too.
- Have you considered extending the range of the HIGH CUT knob to span all the way up to 20 kHz? Sometimes it's desirable to get those shimmering high frequencies in the reverb tail.

I didn't have these issues with Audio Damage Eos which is why I kept it.

Thanks a lot

samsam · Post by **samsam** » Sat May 28, 2011 12:56 pm

How did you demo Eos?

fgimian · Post by **fgimian** » Sat May 28, 2011 1:14 pm

samsam wrote:How did you demo Eos?

Sorry I was a bit unclear, had to purchase Eos to REALLY try it out which I did this morning. But I've been using the samples up on the Audio Damage site for the last few days to demo Eos and compare what I could do with ValhallaRoom since the reverb settings in the samples closely resembled what I wanted out of my reverb.

Edited my post for clarity.

samsam · Post by **samsam** » Sat May 28, 2011 1:22 pm

Cool, I was just thinking out loud, no hidden meaning intended.

Sean's work is great, own n luv Eos too and Room seems great.

fgimian · Post by **fgimian** » Sat May 28, 2011 1:24 pm

samsam wrote:Cool, I was just thinking out loud, no hidden meaning intended.

Sean's work is great, own n luv Eos too and Room seems great.

No worries

Yeah, it's really hard to go wrong with these 2 reverbs, they both sound gorgeous!! Have you found any pros and cons on either plugin out of interest?

Bronto Scorpio · Post by **Bronto Scorpio** » Sat May 28, 2011 1:30 pm

soundpalace wrote:...Yeah, it's really hard to go wrong with these 2 reverbs, they both sound gorgeous!!...

+1

They are the only 2 reverbs I use (And ValhallaShimmer for Special FX). Until I purchased ValhallaRoom I only used EOS. I still prefer EOS for drum plates sometimes.

Cheers
Dennis

opus_diaboli · Post by **opus_diaboli** » Sat May 28, 2011 1:34 pm

Are there significant differences between Eos and ValhallaRoom?

Mercado_Negro · Post by **Mercado_Negro** » Sat May 28, 2011 1:47 pm

opus_diaboli wrote:Are there significant differences between Eos and ValhallaRoom?

Yes. Let's say Eos is more dense than ValhallaRoom.

valhallasound · Post by **valhallasound** » Sat May 28, 2011 3:31 pm

soundpalace wrote:Hey Sean, just wanted to say that I'm a big fan of your work. I decided to keep Audio Damage Eos after purchasing it and demoing against ValhallaRoom for the last day. I think they are both awesome and I can easily see myself also buying ValhallaRoom in the near future.

Well, thanks for the nice words! And Eos and ValhallaRoom are like my children - I loves them all!

- I'm colourblind and the colours used for the selected Reverb Mode and Preset are impossible to see with my eyes

That is something I will consider in the future. I know there are programs for checking out webpages for usability with various color blindness types, so I will use screenshots of the plugin GUIs to make sure there are no issues. Thanks for bringing this to my attention, and my apologies for having this issue come up.

- The CPU usage was a reasonable amount higher than Eos and ArtsAcoustic, although not unreasonable

The Eos algorithms are complex, but the ValhallaRoom algorithms use more memory, more filters, etc., which requires more cycles. I spent a fair amount of time optimizing the ValhallaRoom code (and Eos, for that matter), but some things can't be optimized away to nothing.

- In Cubase 6, when the plugin interface is open, you can not minimise the arrange window, the Cubase interface locks up and you have to Alt+Tab out of it and go back to get the app to respond again, any ideas? This also affects closing other windows in Cubase too.

Is this on the PC? It sounds like it is linked to some issues with Juce that were recently resolved, so I'll look into this.

- Have you considered extending the range of the HIGH CUT knob to span all the way up to 20 kHz? Sometimes it's desirable to get those shimmering high frequencies in the reverb tail.

This is a good idea. The main issue is that changing the slider range would break all existing presets and projects, as the current 0-1 slider range in VST/RTAS is mapped so that it goes up to 15 kHz. In general, changing slider ranges in an update, or adding parameters, is a bad idea for a plugin developer, as it will break functionality for all users that have saved projects. So the range will have to stay at 15 kHz for now, even though raising it would allow for a bit more sonic variety.

Sean Costello

sauli · Post by **sauli** » Sat May 28, 2011 4:33 pm

Couldn't that be solved by having a hidden legacy parameter which when activated multiplies hi-cut by 0.75 and automatically deactivates when hi cut is edited with gui (but not when changed with host automation).

TitusRaindrops · Post by **TitusRaindrops** » Sat May 28, 2011 4:40 pm

sauli wrote:Couldn't that be solved by having a hidden legacy parameter which when activated multiplies hi-cut by 0.75 and automatically deactivates when hi cut is edited with gui (but not when changed with host automation).

Or a check box, unchecked by default, that extends the range of that fader. As long as it is off by default it doesn't break projects right?

valhallasound · Post by **valhallasound** » Sat May 28, 2011 4:46 pm

TitusRaindrops wrote:
sauli wrote:Couldn't that be solved by having a hidden legacy parameter which when activated multiplies hi-cut by 0.75 and automatically deactivates when hi cut is edited with gui (but not when changed with host automation).
Or a check box, unchecked by default, that extends the range of that fader. As long as it is off by default it doesn't break projects right?

Unfortunately, in order to extend the parameter range, it would have to happen in the audio part of the plugin code, not the GUI. This would entail either extending the maximum range of the slider by default, which would break existing projects, or adding a parameter to change the range of the slider, which would break existing projects.

Sean Costello

Klemperer · Post by **Klemperer** » Sat May 28, 2011 4:47 pm

opus_diaboli wrote:Are there significant differences between Eos and ValhallaRoom?

I once - in Sean's blog - asked about the same question concerning Eos, shimmer and room (which I all own^^ and love). Here in his blog you can read the developer's answer. (just search the answer below "Klemperer")

ValhallaRoom 1.5.1 Released. New Electric Blue GUI