ValhallaRoom 1.5.1 Released. New Electric Blue GUI

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS
ValhallaRoom

Post

Next week, I'll be working on the ValhallaRoom 1.1.0 update. My current plans:

- Port VRoom over to OSX VST64 (this will be a pretty quick port)
- Fix mono->stereo bypass issue in RTAS
- New reverb mode: LV-426. I have this running here, but I want to tweak it a little bit before I get people beta testing it. As the name implies, this one is spacey. I tried a few ideas for super small rooms, but none of them sounded better than the existing VRoom reverb modes for this role.

Are there any more little pesky bugs I should deal with while I'm working with the code?

Sean Costello

Post

valhallasound wrote:New reverb mode: LV-426. I have this running here, but I want to tweak it a little bit before I get people beta testing it. As the name implies, this one is spacey. I tried a few ideas for super small rooms, but none of them sounded better than the existing VRoom reverb modes for this role.
:o Droooling....

Post

valhallasound wrote:Next week, I'll be working on the ValhallaRoom 1.1.0 update. My current plans:

- Port VRoom over to OSX VST64 (this will be a pretty quick port)
- Fix mono->stereo bypass issue in RTAS
- New reverb mode: LV-426. I have this running here, but I want to tweak it a little bit before I get people beta testing it. As the name implies, this one is spacey. I tried a few ideas for super small rooms, but none of them sounded better than the existing VRoom reverb modes for this role.

Are there any more little pesky bugs I should deal with while I'm working with the code?
No bugs here :), but I miss one essential feature: A low cut filter - please. ;)

Post

valhallasound wrote:Are there any more little pesky bugs I should deal with while I'm working with the code?

Sean Costello
No bugs with VRoom... but maybe some more presets for VShimmer? :)

Post

Rat 41 wrote:
valhallasound wrote:Next week, I'll be working on the ValhallaRoom 1.1.0 update. My current plans:

- Port VRoom over to OSX VST64 (this will be a pretty quick port)
- Fix mono->stereo bypass issue in RTAS
- New reverb mode: LV-426. I have this running here, but I want to tweak it a little bit before I get people beta testing it. As the name implies, this one is spacey. I tried a few ideas for super small rooms, but none of them sounded better than the existing VRoom reverb modes for this role.

Are there any more little pesky bugs I should deal with while I'm working with the code?
No bugs, but imo one essential feature: A low cut filter - please. ;)
I had originally planned to add a LowCut parameter to the upcoming release. However, it turns out that this would create some technical issues for some VRoom users.

In the past, I had thought that you can't add parameters to a plugin post-release, as this could create issues with saved DAW projects. However, another plugin developer recently let me know that you can append new parameters to the end of your parameter list without any issues.

ValhallaÜberMod was the guinea pig as far as adding parameters to a released plugin. Version 1.0.1 added the WARP InputPan parameter. I tested the new parameter in saved projects on various DAWs, and had beta testers work with the new parameter for over a month. Everything seemed good, so I released the plugin.

Unfortunately, there is one DAW that apparently can't handle adding new parameters to an existing plugin: Reaper. It turns out that Reaper will put a MUTE parameter at the end of your parameter list. So the new Input Pan parameter ended up muting the plugin in saved projects for one of my users. I'm surprised that I haven't received more reports of this issue, but it might be the case that there aren't many people using ÜberMod in Reaper right now.

However, there are a LOT of Reaper users that own ValhallaRoom. If I added a LowCut parameter, this would break the existing Reaper projects for these users. Since ValhallaRoom has been out for almost a year (the anniversary is coming up on the 23rd of March), odds are good that adding a parameter would affect far more Reaper users than the ÜberMod change did.

So, no LowCut parameter. Which is sad, as I had the GUI tweaks already planned to accommodate the new slider. I would recommend using ValhallaRoom on a send, in series with an EQ plugin, in order to get a thinned out low end.

Sean Costello

Post

In general it is a very good idea to keep an EQ after ValhallaRoom as it doesn't contain one. Almost all other reverbs have some kind of EQ section (hardware and software) for good reasons.

I've had to remind a few ValhallaRoom users of this. They just didn't know you could "add" plugins after the reverb send. So, it's worth mentioning again:

You can, and probably should, add or at least try a few different plugins after valhalla room (or in the case of a de-esser, before valhalla room). Most common ones are EQ, saturation of some kind (subtle!) and an expander/gate (with this you can shape the tail to fit the song instead of reducing the size or decay of valhalla room).

Cheers!
bManic
"Wisdom is wisdom, regardless of the idiot who said it." -an idiot

"They don't ban hate speech; they ban speech they hate." -an oracle

Post

valhallasound wrote:Unfortunately, there is one DAW that apparently can't handle adding new parameters to an existing plugin: Reaper.
If it's the only DAW it's more of a shortcoming of Reaper then than anything else, isn't it? Maybe Cockos should fix this instead of making a developer refrain to improve his plug-in. ;)
I would recommend using ValhallaRoom on a send, in series with an EQ plugin, in order to get a thinned out low end.
I'm afraid that's completely against my workflow.
So, no LowCut parameter. Which is sad...
Indeed! :( I hope this isn't your last word...

Post

And if the proposed new version had a different ID? That would mean that existing projects would still open with the current version, and the user could then instantiate the new version and (presumably?) copy/paste presets from the old into the new?
Anyways, adding to the "drool" about the OS X VST 64-bit :)
I did get a life,once...but it was faulty, so I sent it back.

Post

I, too, would like to see a low-cut filter. Not essential, but it would sure be convenient.

Maybe it should be a new plugin. Call it ValhallaRoom+. Append a handful of dummy parameters ("Reserved1", "Reserved2", etc.) to prevent future obsolescence under Reaper. The only downside is Reaper users might have to have two versions installed side-by-side. That's not uncommon (I have 3 versions of Kontakt installed, 3 versions of Ozone, 3 versions of Dimension Pro).

Post

Just to make my earlier point very clear: I'm not adding any additional sliders to ValhallaRoom. I'm also not creating a parallel version with new controls. The goal of this release is fixing a few bugs, creating a 64 bit VST build for OSX, and adding a new reverb mode. It needs to be seamlessly compatible with previous versions.

Sean Costello

Post

Could add a mute to not break REAPER and then a low cut :hihi:

[e - didn't see the post above before posting, so, uh.. :oops:]
Last edited by xh3rv on Sat Mar 17, 2012 5:18 pm, edited 1 time in total.

Post

valhallasound wrote:Just to make my earlier point very clear: I'm not adding any additional sliders to ValhallaRoom. I'm also not creating a parallel version with new controls. The goal of this release is fixing a few bugs, creating a 64 bit VST build for OSX, and adding a new reverb mode. It needs to be seamlessly compatible with previous versions.

Sean Costello
Personally, I'm totally good with that :tu:

Post

Re: LV-426, there are rumors about a possible future Peter Weyland acquisition of classified Valhalla DSP technology.

http://www.weylandindustries.com/

Post

Good grief.

just tried Room for the first time.

demo'd it for approximately 3 minutes. then bought it.

total no-brainer.

just amazing. :shock:

Post

antithesist wrote:Re: LV-426, there are rumors about a possible future Peter Weyland acquisition of classified Valhalla DSP technology.

http://www.weylandindustries.com/
That. Is. AWESOME.

I must have had Prometheus on the brain when I first named the Nostromo/Narcissus reverb modes. The LV-426 reverb mode was named back when I developed Sulaco back in November, although I don't think that the actual reverb mode is that similar to what I was calling LV-426 back then. The current LV-426 is closer to Nostromo/Narcissus in some ways, but with much more echo density, and more extensive modulation. So the name is appropriate. Sulaco is a totally different architecture than Nostromo/Narcissus/LV-426.

Anyway, the new Prometheus trailers are very cool. I'm trying to figure out if the planet in that trailer is actually LV-426.

Sean Costello

Post Reply

Return to “Effects”