Was sounding like the trippy droning ambient middle section of Echoes (Pink Floyd)

Long live David Gilmour

I hereby demand that SiMOD will not be allowed to post audio examples (for his presets) until all platform version are released (so users will be able to use his presets. or, at least, beta testers)


Thank you

LOL - just quickly buy a Mac

If only it was that easy. Apple has upped the exclusivity factor with their new iAudition sales program. Basically you now have to prove that you're not only financially solvent enough to pay 3-5 times market cost, but have to display how uber-hip and shiny your wardrobe is before purchase is authorized. This disqualifies many of us fleece pajama-bottom home recordists. When you are the world's most valuable corporation and the creator of the computer 'for the rest of us', the riff-raff and their dull music must be kept off the shiny side of the street.

At least Performer is soon coming over to the former evil empire OS, so all hope is not lost for us formerly evil cool artists.

After composing for the whole day I needed a break and made this little easter experiment with French Horns and LV-426:
http://soundcloud.com/sampleconstruct/valhalla-horns-lv-426

...turning up the Decay during the last chord (as if you hadn't noticed)

Da Preset:
<ValhallaRoom pluginVersion="1.1.0b1" presetName="Drown them Horns" mix="1" predelay="0.0571999997" decay="0.0900000036" HighCut="0.322818786" earlyLateMix="0.400000006" lateSize="0.620000005" lateCross="1" lateModRate="0.0727272704" lateModDepth="0.319999993" RTBassMultiply="0.600000024" RTXover="0.25959596" RTHighMultiply="0.300000012" RTHighXover="0.387919456" earlySize="0.60490489" earlyCross="0.779999971" earlyModRate="0.230303034" earlyModDepth="0.189999998" earlySend="1" diffusion="0.810000002" type="0.916666687"/>

Seannnnnn

Givasss v1.1 !!!

SiMOD... you remind me of Blake Griffin... AKA "The Humiliator"

Cheers

Well i've noticed a similar problem with Reaper and Usine but in a slightly different application : in live situations when you bypass and unbypass effects.

1. Create a track in REAPER with some audio and a VR instance
2. Stat playback with effect on
3. Bypass the effect
4. Stop the playback
5. Unbypass the effect
> It plays whatever reverb sound it has in its buffer

I think Shimmer, VRoom and Ubermod have this behaviour.
For live work it would be preferable that the plugin always clears its buffers after it has been bypassed to avoid a huge reverb noise each time it is turned on (or maybe this could be an optionnal setting ?)

I'm just jumping at the opportunity here to mention this although i'm not sure it adds anything to what karrikuh already described.
It's really cool if this is fixed with the next release !
Last edited by farfadetfarfelu on Sun Apr 08, 2012 12:25 pm; edited 1 time in total

You mean the NBA player - I'm trying to make a connection to myself...what does he mean?

Yes

He's well known for "walking" over his opponents. you are dunking us in misery with those presets, Sir (as
long as we can't use 'em)

Continue, and you'll be invited to the east vs west game...

WOW, those dunks he does are absoultely f*****g amazing

Yes, he's one powerful young dude (he's 23 !!)

I lough my a$$ off when I see him in action. it's almost ridiculous... he's like a human tsunami

i just tried this with every reverb and delay plugin in my plugin folders, from a variety of plugin companies and freeware creators, and they all exhibit this behavior. Which makes sense, as the "bypass" function simply stops calling the plugin processReplacing() function - it doesn't call a unique bypass function within the plugin. Essentially, when you bypass the effect, the plugin just stops whatever it is doing, and doesn't even have consciousness that it has been stopped.

The workaround in the VST SDK would be to call setBypass(), but this would simply call the processReplacing() function with whatever wet/dry gain code I put in there. This would result in none of the CPU savings of calling the bypass in the DAW, and would probably break the expected behavior for most users.

The best solution to avoid these lingering "buffer" artifacts is to automate wet/dry levels, instead of bypassing effects on the fly. Or, run plugins on a send, and automate the send levels.

Sean Costello

I agree, Sean, it's not a bug, it's a feature! Lingering "buffer" artifacts aren't malingering at all and have creative merit beyond the obvious semi-realtime sub-ambient tarnce gate effect, altho that's fun too. When I die and my horrible unreleased basement tapes are released, I want then to be titled: Lingering Buffer Artifacts - 100 years of VRoom tails.

I'll release them for ya