I just tried this in Reaper and it is working fine for me. I added MVerb as an fx on an audio channel containing a drum loop and then added a few of Reaper's built in fx and everything worked as expected here. Anything else I should try to reproduce this?V'ger wrote:Thx for the update, this is one nifty verb.
Still hoping it can modified so that it can be used freely in an insert chain, as now it will only through sound to some other plugs after it, others not.
MVerb - A Free Open Source Reverb
-
- KVRian
- Topic Starter
- 995 posts since 25 Apr, 2005
- KVRAF
- 3922 posts since 15 Dec, 2009
I have this bass track made up of several VSTi's but I want some dry and some wet so I stuck Xhip reverb in the middle and it works fine, but replacing that with Mverb there's no sound coming from the synths after that. The chain is like this:
Oatmeal
EVM Ultrasonique
IDJ 3-OSC
Xhip reverb
Ilbit
massTURBOtar
Here is the Reaper FX chain: http://www.box.net/shared/9yg5t9z6dz
Oatmeal
EVM Ultrasonique
IDJ 3-OSC
Xhip reverb
Ilbit
massTURBOtar
Here is the Reaper FX chain: http://www.box.net/shared/9yg5t9z6dz
-
- Banned
- 96 posts since 24 Sep, 2009 from Europe
Bravo!
I love that you did this. I love that you shared the source code because I too have been curious about the dark arts!
I love that you did this. I love that you shared the source code because I too have been curious about the dark arts!
"Hardware versions of software are on the horizon."
-
- Banned
- 96 posts since 24 Sep, 2009 from Europe
this is because effects don't normally pass midi data through. its just not necessary or useful. easier to do routing. plus you get more control over your mix.V'ger wrote:I have this bass track made up of several VSTi's but I want some dry and some wet so I stuck Xhip reverb in the middle and it works fine, but replacing that with Mverb there's no sound coming from the synths after that. The chain is like this:
Oatmeal
EVM Ultrasonique
IDJ 3-OSC
Xhip reverb
Ilbit
massTURBOtar
Here is the Reaper FX chain: http://www.box.net/shared/9yg5t9z6dz
put Ilbit and massTURBOtar on their own track and route the midi to that track.
you just gave us an idea i think...
it would be really cool if mverb was the first reverb that responds to midi!
imagine, midi notes controlling the reverb algorithm in subtle to extreme ways!
"Hardware versions of software are on the horizon."
- KVRAF
- 3922 posts since 15 Dec, 2009
No that's the brilliant thing with Reaper, you can stack whatever you want on one track to keep things simple and configurable. Synth to effect to synth, whatever, and then change the order by dragging them higher or lower.
In rare cases synths won't pass sound through to the next in the chain, as do some effects like MVerb now which is a bit of a shame as it's so kind on the CPU that it can be used on all tracks individually as inserts.
In rare cases synths won't pass sound through to the next in the chain, as do some effects like MVerb now which is a bit of a shame as it's so kind on the CPU that it can be used on all tracks individually as inserts.
-
- Banned
- 96 posts since 24 Sep, 2009 from Europe
agreed.V'ger wrote:No that's the brilliant thing with Reaper, you can stack whatever you want on one track to keep things simple and configurable. Synth to effect to synth, whatever, and then change the order by dragging them higher or lower.
MVerb is an effect, and by definition will pass the audio stream. What's not making it through MVerb is the midi information. The plug needs a midi input and midi output. I won't criticize your creative choice to layer the track that way, but it is widely thought that reverbs are best used as send effects. Also, by stacking 4 synths on one track, you are missing out on a lot of control.V'ger wrote:In rare cases synths won't pass sound through to the next in the chain, as do some effects like MVerb now which is a bit of a shame as it's so kind on the CPU that it can be used on all tracks individually as inserts.
So I recommend for Mr. Eastwood (Caco) to add a midi in and midi out so the other synths will function. For that matter, Mverb could also have a bunch of dummy audio ins and outs so it will pass all audio, even if its coming after a sampler and before another multichannel effect. It doesn't have to use all the channels, but it will be more 'future proof' in terms of your kind of problem.
What do the others think? Is this superfluous?
"Hardware versions of software are on the horizon."
- KVRAF
- 3922 posts since 15 Dec, 2009
Yes of course, midi information, what was I thinking. 
But about reverbs as sends vs inserts, there've been threads to prove people are split on this issue. Put as insert there's that much more control as to where in the chain it is plus automation etc. Having it as send I think has maybe been the norm as the possibility to have inserts on each track were not there. With super low CPU-using and nice sounding verbs like MVerb, using inserts only is possible.
As for stacking synths, configuration is not really suffering as any synth in the chain can be set to a midi controller via Reaper's nice learn function, so all will respond to a single automation lane etc. Certainly much easier than several tracks with one on each and nightmare editing. Of course I prefer a single synth on tracks, but this is a freeware project and stacking can anyway be quite interesting.
But about reverbs as sends vs inserts, there've been threads to prove people are split on this issue. Put as insert there's that much more control as to where in the chain it is plus automation etc. Having it as send I think has maybe been the norm as the possibility to have inserts on each track were not there. With super low CPU-using and nice sounding verbs like MVerb, using inserts only is possible.
As for stacking synths, configuration is not really suffering as any synth in the chain can be set to a midi controller via Reaper's nice learn function, so all will respond to a single automation lane etc. Certainly much easier than several tracks with one on each and nightmare editing. Of course I prefer a single synth on tracks, but this is a freeware project and stacking can anyway be quite interesting.
-
- Banned
- 96 posts since 24 Sep, 2009 from Europe
I wouldn't want to work that way myself, but since it's hard to predict how people will use a plugin I guess they should all pass midi and auxiliary audio channels 3/4 just to be safe for things like passing signals for later effects that use sidechaining.
It could very well be that I am mistaken as to the cause of this nitpick, we'll see I guess.
It could very well be that I am mistaken as to the cause of this nitpick, we'll see I guess.
"Hardware versions of software are on the horizon."
-
- KVRist
- 57 posts since 29 Sep, 2005 from Bergen, Norway
@V'ger: you can right click on in/out settings in the MVerb window in Reaper and go MIDI output/ Merges with MIDI output, and you should be OK 
- KVRAF
- 3922 posts since 15 Dec, 2009
Thx, but can't find that option anywhere? 
-
- KVRist
- 57 posts since 29 Sep, 2005 from Bergen, Norway
Im not very good at explaining, a picture should do a better jobV'ger wrote:Thx, but can't find that option anywhere?

- KVRAF
- 3922 posts since 15 Dec, 2009
Ah there it was.. So well explained.. 
That setting fixed the issue, cheers. Now MVerb can go anywhere in the chain and also others that was blocking too (like Minimonsta).
That setting fixed the issue, cheers. Now MVerb can go anywhere in the chain and also others that was blocking too (like Minimonsta).
-
- Banned
- 96 posts since 24 Sep, 2009 from Europe
does reaper remember the setting, even when you use the plug in a different project?V'ger wrote:Ah there it was.. So well explained..
That setting fixed the issue, cheers. Now MVerb can go anywhere in the chain and also others that was blocking too (like Minimonsta).
"Hardware versions of software are on the horizon."
- KVRAF
- 3922 posts since 15 Dec, 2009
Unfortunately not, so still hoping some kind soul will add the midi output/thru.. 
-
- KVRian
- Topic Starter
- 995 posts since 25 Apr, 2005
Blurk has kindly ported the GUI version of MVerb to OS X VST and AU!! They should also now work on OS X 10.4 upwards. HUGE thanks to you blurk 

For people who installed the GUI-less version of MVerb on OS X please note blurk's installation instructions below
www.martineastwood.com

For people who installed the GUI-less version of MVerb on OS X please note blurk's installation instructions below
Still lacking a Linux version. I thought this would be more likely than OS X as Linux generally seems more aligned with the whole open-source idea and presumably there aren't many reverb VSTs on Linux?? Nobody want to have a go at it???blurk wrote:If you have already installed the GUI-less version of the MVerb AU, this new version of the AU will probably fail AU validation (and possibly crash your host) unless you reboot after installing the new AU. We apologise for this, but don't know of any other reliable work-around. As far as we know, this is due to OS X caching the details about the AU, which includes where to find the UI (so OS X keeps thinking there is no UI until it refreshes its cache, which happens at boot time).
www.martineastwood.com
