ValhallaRoom 1.5.1 Released. New Electric Blue GUI

[antithesist]

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

I didn't even know about Prometheus until a couple weeks ago. So, you'd have been way ahead of me there. I got a big kick out of the TED thing and it immediately made me think of Room. I'm really looking forward to the new mode. Valhalla Room is already great and just gets better.

Of course, everyone knows that Acheron (LV-426) is the second of three natural satellites that orbit Calpamos, which is the fifth planet from the star Zeta 2 Reticuli. Actually, I copied that from from an AVP Wiki. I was looking for info about the planet in the trailer and trying not to read possible spoilers. Sadly, I came away less than victorious and encrusted in dried virtual nerd spittle. I guess if the trailer shows the same derelict ship, then that's Acheron?

[bangzero]

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.

hmmm. i've been using ÜberMod quite a bit in Reaper and didn't see this problem. and i can't replicate it now when i try reverting to 1.0.0, saving a fresh project with a couple of instances of ÜberMod, installing 1.0.1, and opening that project. works fine. and, something doesn't make sense about the scenario you describe. this would only be an issue when Reaper is doing its own save/restore of the ÜberMod state with a project, yes? with ÜberMod 1.0.0 there would be N params, and N+1 would be this MUTE param. when loading a project after updating, ÜberMod now reports N+1 parameters. if anything i would expect the old MUTE param saved as N+1 to stomp the new Input Pan param. there wouldn't be anything saved at the new MUTE param position of N+2 to change the MUTE state. if it is muting somehow it would mean Reaper is loading some random value into MUTE. that's a bug i'd like to report. also, what does this MUTE parameter do in Reaper exactly? afaik there isn't any effect mute by that name anyway. does it change the effect "bypass" or "offline" settings? but as i said, those restore ok for me from a project saved with ÜberMod 1.0.0. i'd really like to be clear on this. it seems a real shame if this is holding up useful new features. please let me know more exactly how to reproduce the problem so i can followup with the Cockos folks. tia! /dan

[egbert]

Reaper developers might be prepared to address your issue, Sean. Has in been drawn to their attention? They seem pretty responsive to ideas - from users at least.

[valhallasound]

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.

hmmm. i've been using ÜberMod quite a bit in Reaper and didn't see this problem. and i can't replicate it now when i try reverting to 1.0.0, saving a fresh project with a couple of instances of ÜberMod, installing 1.0.1, and opening that project. works fine. and, something doesn't make sense about the scenario you describe. this would only be an issue when Reaper is doing its own save/restore of the ÜberMod state with a project, yes? with ÜberMod 1.0.0 there would be N params, and N+1 would be this MUTE param. when loading a project after updating, ÜberMod now reports N+1 parameters. if anything i would expect the old MUTE param saved as N+1 to stomp the new Input Pan param. there wouldn't be anything saved at the new MUTE param position of N+2 to change the MUTE state. if it is muting somehow it would mean Reaper is loading some random value into MUTE. that's a bug i'd like to report. also, what does this MUTE parameter do in Reaper exactly? afaik there isn't any effect mute by that name anyway. does it change the effect "bypass" or "offline" settings? but as i said, those restore ok for me from a project saved with ÜberMod 1.0.0. i'd really like to be clear on this. it seems a real shame if this is holding up useful new features. please let me know more exactly how to reproduce the problem so i can followup with the Cockos folks. tia! /dan

I should also add that I've got a new plugin in the works, and don't want to add any new sliders to VRoom right now. This would require a GUI design, and a whole bunch of testing - about 2 weeks of solid work.

The current 1.1.0 update will have the following features:

- OSX VST64 (working nicely in Cubase 6 as I write this)
- Fixed mono->stereo bypass in Pro Tools
- Some optimization. I figured out some buffer allocation techniques with ÜberMod, that I need to fold back into VRoom. I just remembered this tonight. It will take an hour or two to implement tomorrow.
- Correct version numbers when viewed in Finder in OSX (some DAWs get their version number from the same part of the code)
- New reverb mode: LV-426.

A bit about LV-426: The overall sound is like a cross between Nostromo and Narcissus, but with a much higher initial echo density than either of those modes, and a more diffuse randomized modulation. The LATE Bass/High Mult and Bass/High Xover controls are moved to a different part of the algorithm, and can now act as low/high boost and cut controls. This is similar to some older reverb algorithms (Lexicon 224XL Concert Hall, SP2016 Stereo Room). If you want a thinner low end, use the LV-426 mode, set LATE Bass Mult to a value less than 1X, and set the LATE Bass Xover to the desired shelving frequency. This will affect the initial tone as well as the decay, and creates some cool effects.

I haven't reproduced the Reaper bug here, but heard about it from a VRoom customer. Once I have the 1.1.0 update done, I can take a little time and pass on the bug report to the folks at Cockos.

Sean Costello

[xx JPRacer xx]

I should also add that I've got a new plugin in the works

A little bit more info... please

[valhallasound]

I should also add that I've got a new plugin in the works

A little bit more info... please

I'll announce it when it's done. I think people will like it.

Sean Costello

[valhallasound]

Reaper developers might be prepared to address your issue, Sean. Has in been drawn to their attention? They seem pretty responsive to ideas - from users at least.

The Reaper developers are really helpful, in my experience. The thing is, I don't know how deeply this "mute parameter" is embedded within Reaper projects. Plus, I don't know what other hosts have this issue with adding parameters to updated versions. At this point, I'd rather err on the side of caution, and leave the VRoom parameters as is. I will bring the issue up in the Cockos technical forum at some point, just to get their viewpoint on things.

Sean Costello

[Audio~Geek]

Hey Guys
I just posted the latest Home Recording Show podcast. Sean was our excellent guest this week. I reviewed UberMod and we talked at great length about reverbs, dsp, knobs and more.

http://bit.ly/H0Xmkh

[karrikuh]

Hi,

I found an issue with VR (which probably also applies to VÜM, didn't check):

1. Create a track in REAPER with some audio and a VR instance set to a very long reverb time. For better demonstration of the issue, leave a few seconds of silence at the beginning.
2. Start playback until audio starts.
3. Stop playback. The reverb tail will continue (which is fine)
4. Quickly call "render project".
5. The resulting rendered audio will contain the left-over reverb tail from project playback!

I would bet the same issue appears in other hosts too.

I also know how to fix this, at least for VST:
you have to implement the "resume" method which gets called whenever playback starts. Here you should clear all your buffers. I actually stumbled over this issue in the development of my personal delay effect so I could verify that the fix does work!

[valhallasound]

Hi,

I found an issue with VR (which probably also applies to VÜM, didn't check):

1. Create a track in REAPER with some audio and a VR instance set to a very long reverb time. For better demonstration of the issue, leave a few seconds of silence at the beginning.
2. Start playback until audio starts.
3. Stop playback. The reverb tail will continue (which is fine)
4. Quickly call "render project".
5. The resulting rendered audio will contain the left-over reverb tail from project playback!

I would bet the same issue appears in other hosts too.

I also know how to fix this, at least for VST:
you have to implement the "resume" method which gets called whenever playback starts. Here you should clear all your buffers. I actually stumbled over this issue in the development of my personal delay effect so I could verify that the fix does work!

I'll look into this. IIRC, other DAWs do have different behavior around this. If I can find some shared aspects of this issue (i.e. all VST hosts have this behavior), it might be a quick fix. Thanks for the tip on the resume() method.

Sean Costello

[DuX]

Keep up the great work Sean. Your plugins change the landscape of VST plugins IMHO. I'm looking forward to new modes.

However, my obsession of a kind is Uberobsession currently.

Cheers!

[jensa]

I was the guy/criminal reporting about the Mute bug in Reaper to Sean. Feeling I had to do my duty I posted a bug report at the Reaper forums about few hours ago and just got a reply from Justin:

" Thanks for pointing this out! We are working on a fix for this issue, but it might be as far away as 4.30."

The thread is here if you wanna read or try it out for yourselves:

http://forum.cockos.com/showthread.php?t=99917

[valhallasound]

I was the guy/criminal reporting about the Mute bug in Reaper to Sean. Feeling I had to do my duty I posted a bug report at the Reaper forums about few hours ago and just got a reply from Justin:

" Thanks for pointing this out! We are working on a fix for this issue, but it might be as far away as 4.30."

The thread is here if you wanna read or try it out for yourselves:

http://forum.cockos.com/showthread.php?t=99917

Thanks for posting the bug at the Cockos forum! Amazingly fast reply from the crew there.

Sean Costello

[jensa]

I was the guy/criminal reporting about the Mute bug in Reaper to Sean. Feeling I had to do my duty I posted a bug report at the Reaper forums about few hours ago and just got a reply from Justin:

" Thanks for pointing this out! We are working on a fix for this issue, but it might be as far away as 4.30."

The thread is here if you wanna read or try it out for yourselves:

http://forum.cockos.com/showthread.php?t=99917

Thanks for posting the bug at the Cockos forum! Amazingly fast reply from the crew there.

Sean Costello

My pleasure, Sean.

[SuperFly76]

Hey Guys
I just posted the latest Home Recording Show podcast. Sean was our excellent guest this week. I reviewed UberMod and we talked at great length about reverbs, dsp, knobs and more.

http://bit.ly/H0Xmkh

Just finished listening to the show. Great show guys! It was really cool to get to hear from Sean directly in podcast format. Great show.

~ride the electric chicken~