MTurboReverb preset making action, let's make the ultimate reverb! ;)

[Sam-U]

The only 2 turbo things about it are the CPU meter going up and me opening another reverb
300 bucks are better invested in something that actually sounds good instead of a quantity of presets.

[nichttuntun]

The only 2 turbo things about it are the CPU meter going up and me opening another reverb
300 bucks are better invested in something that actually sounds good instead of a quantity of presets.

In my opinion you have absolutely no clue about MTR. Melda does 50% sales every year.

Your answer implies MTR doesn't sound good. Yes you got no clue about it and probably never used it in depths. It's obvious you don't know and don't own it. So please don't hitchhike a thread unless you got something constructive to say.

It would be nice

[Sam-U]

I think you have been falling more for the "ultimate reverb" marketing than me and your 50% sales statement shows that perfectly. I know there are reverbs I can load and they fit immediately. MTR is none of them. Too much tweaking still needed, despite there being "heavily inspired" presets. And I don't know what's turbo about creating own reverb algos, but that just another technical gimmick imo. Anyways, once you learned what opinions are, I can start taking you serious

[Tagirijus]

The only 2 turbo things about it are the CPU meter going up and me opening another reverb
300 bucks are better invested in something that actually sounds good instead of a quantity of presets.

That's strange, since I experienced it vice versa: MTR seems one of the most CPU friendly reverbs I used so far. Tbh, I am a bit "back" to Valhalla Room and Valhalla Plate as my more to-go verbs by now, since they for sure have less controls (thus more intuitive, to be honest), save your CPU a bit more while just still sounding incredible. Yet I still find that MTR can be incredible in general (well at least already with its concept after all ... I mean ... having your own reverb algorithms, hehe!? ). Almost every other reverb I tested so far besides these two factions (Melda and Valhalla) used always way more CPU. Except convolution reverbs, which I do not count, since they are not algorithmic.

Some more words regarding MTR and other verbs: I can totally understand, if people do not like MTR, since it maybe even "too many" options to people, who do also not like to go through hundreds of devices; not even speaking of the edit screen! I can totally understand it; most of the time people might just want something more out of the box and less complex, maybe? Still: speaking out of theroy MTR is the most versatile reverb with all the possibilities.

Back to your quote, Sam: Maybe there are some devices in MTR, which are rather CPU intense. Which ones did you use, Sam? I am just curious!

Regarding "Turbo": that's just a term Meldaproduction introduced to some kind of new range of plugins, which are intended to be even more versatile than before ("before" speaking of the other tools by Melda; not like "every other plugin out there". Don't get me wrong here. To me many companies totally have their eligibility, for sure!).


@nichttuntun
Do you have any presets to share? It sounds like you are really into MTR and for sure have spend some time with it? Maybe it could inspire me and others here?


Edit: Wow .. this whole auto-tagging in KVR just went totally nuts ... lol

[Sam-U]

The only 2 turbo things about it are the CPU meter going up and me opening another reverb
300 bucks are better invested in something that actually sounds good instead of a quantity of presets.

That's strange, since I experienced it vice versa: MTR seems one of the most CPU friendly reverbs I used so far. Tbh, I am a bit "back" to Valhalla Room and Valhalla Plate as my more to-go verbs by now, since they for sure have less controls (thus more intuitive, to be honest), save your CPU a bit more while just still sounding incredible. Yet I still find that MTR can be incredible in general (well at least already with its concept after all ... I mean ... having your own reverb algorithms, hehe!? ). Almost every other reverb I tested so far besides these two factions (Melda and Valhalla) used always way more CPU. Except convolution reverbs, which I do not count, since they are not algorithmic.

One reverb I'd compare it with as it can easily reproduce a wide range of environments, is the Fabfilter ProR. Almost all MTR devices/presets use at least 2-3x more CPU than it. I think there was one or two which had practically 0% CPU but, well sounded like that too Probably some experimental stuff.
The ArtsAcoustic reverb is already quite heavy and on par with the MTR CPU usage but sounds waaaaaay better imo and has the experimental/unrealistic options too.
Something I noticed too is the CPU usage going up the longer a reverb tail is in MTR. I havn't seen that with others either.
One reverb taking even more CPU is the Zynaptiq Adaptiverb, but that actually is legitimate as it does produce some magic reverb I think MTR had a preset like that too but these were on a much different level. Which is okay as one plugin has been designed for it and the other has these fancy things as gimmicks.
Let's just say, if I had money left I'd spend it on other reverbs, even if they are just single purpose.

[nichttuntun]

Hi. That's exactly my impression too. I'm using every plugin in a mix context and never save presets or do them beforehand. Only use session save state

I mainly use MTR as an ER designer for individual instruments or groups to give them a space in the mix. Then I dial effects into that space. DOg course I also use the LR of MTR. Opening up the ER-LR relation and get a beautiful reverb tale I to a carefully set ER pocket it's always a wow effect.

MTR makes literally space for every possible situation and every instrument. If you can't get it with this...

Sorry no presets. I never save anything as I want to be flexible every new situation. Also that's one main fun aspect for me when mixing. Creating. I never was a preset guy. But we can exchange some experience of you like.

Cheers

The only 2 turbo things about it are the CPU meter going up and me opening another reverb
300 bucks are better invested in something that actually sounds good instead of a quantity of presets.

That's strange, since I experienced it vice versa: MTR seems one of the most CPU friendly reverbs I used so far. Tbh, I am a bit "back" to Valhalla Room and Valhalla Plate as my more to-go verbs by now, since they for sure have less controls (thus more intuitive, to be honest), save your CPU a bit more while just still sounding incredible. Yet I still find that MTR can be incredible in general (well at least already with its concept after all ... I mean ... having your own reverb algorithms, hehe!? ). Almost every other reverb I tested so far besides these two factions (Melda and Valhalla) used always way more CPU. Except convolution reverbs, which I do not count, since they are not algorithmic.

Some more words regarding MTR and other verbs: I can totally understand, if people do not like MTR, since it maybe even "too many" options to people, who do also not like to go through hundreds of devices; not even speaking of the edit screen! I can totally understand it; most of the time people might just want something more out of the box and less complex, maybe? Still: speaking out of theroy MTR is the most versatile reverb with all the possibilities.

Back to your quote, Sam: Maybe there are some devices in MTR, which are rather CPU intense. Which ones did you use, Sam? I am just curious!

Regarding "Turbo": that's just a term Meldaproduction introduced to some kind of new range of plugins, which are intended to be even more versatile than before ("before" speaking of the other tools by Melda; not like "every other plugin out there". Don't get me wrong here. To me many companies totally have their eligibility, for sure!).


@nichttuntun
Do you have any presets to share? It sounds like you are really into MTR and for sure have spend some time with it? Maybe it could inspire me and others here?


Edit: Wow .. this whole auto-tagging in KVR just went totally nuts ... lol

[Tagirijus]

One reverb I'd compare it with as it can easily reproduce a wide range of environments, is the Fabfilter ProR.

As far as I remember the last time I tested ProR, it used a lot CPU here, strange (i9 9900K here by the way). Unfortunately I cannot remember 100% and also the demo policy isn't the best with Fabfilter, since demos can run out and no further testing is possible, unfortunately, without getting a new demo period argh! I'd like to, though, since I am really curious, haha.

I never save anything as I want to be flexible every new situation. Also that's one main fun aspect for me when mixing. Creating. I never was a preset guy.

Oh okay. This sounds quite uneconomic to me, in a way. When I have client projects, it would be inefficient at least to always "invent the wheel new" and spend to much time for something, which should be ready already to use (e.g. reverb algos or so). ... I did create a to-go device back then which I used a lot and which I could set up to most needs. If I had to code a new reverb algo everytime I just want to have reverb for a specific mix, it would drive me crazy and eat up so much time.

But we can exchange some experience of you like.

Well here it was, like I already wrote above: I took a device found very versatile, modified it, added other algos and set up a bank switch to be able to chose from different algos, had the damping, size, ... well and almost all neede other parameters for the device and had this "preset" as a to-gi device back then. Mainly I liked the standard rd algo module, which was the main algo as Melda once stated (I guess it's the one in MCharmVerb as well) and then I made the seed magic thing to came up with good seeds and setting in the algo designer and saved them as banks (besides all the other options like damping, size, er etc.).

[E_Anderson]

LiquidSonics Cinematic Rooms smokes MTurboReverb. No contest sonically.

To whatever degree you feel you can put it into words, I'm curious how you find that to be so. Part of what has me interested in CRP, besides its sound, which I'll get into in a moment, is the ability to position sounds in space differently from R4/Nimbus which I already own, as their ER sections appear to be different. The best way for me to find out how, before demoing CRP, will be to read the manual. But sonically, I've heard in it and heard it described that CR seems to "meld with the source audio" in such a way that the dry signal is slightly changed, spatialized, so that the source material is not so much placed in a space but becomes part of the space. I believe 2cAudio is doing something similar in Breeze/Precedence though I doubt Breeze being "on/off" comes close to the level of control over this kind of thing (Precedence, I'm not so sure and need some more time with [bless infinite demos])

I think it's important to acknowledge that you're certainly getting a more ""complete"" package with CRP, given that you're paying for the algorithms and the ability to adjust them for a huge variety of purposes, but I double-quote "complete" because it sort of depends on your definition. For me, the infinite-rabbit-hole nature of MTR especially with regard to the ERs is also a complete product; it just depends on whether paying for the flexibility rather than the flat-out polished algorithms of another reverb is more up your alley (or whether you enjoy the sound of the pre-existing algorithms built into MTR)

Anyway, will be interested to hear your opinion on CR and if you have any audio examples to share that informed your opinion, or if it was from demoing (would you mind describing what that process was like for you, how much you explored MTR/whether it was a workflow thing?). Both reverbs are so flexible and powerful, I really have a hard time noticing clear differences, so that it is so decided for you makes me wonder about what you're hearing that I may be missing or whether we just have different taste (or if my monitoring sucks that much!) And if you don't mind indulging me a bit, if you know - how do you find CRP compares to Nimbus/R4?

[Erisian]

The only 2 turbo things about it are the CPU meter going up and me opening another reverb
300 bucks are better invested in something that actually sounds good instead of a quantity of presets.

300 bucks? For a reverb????? You're kidding aren't you? Is that how much it is? Sorry for all the questions, but I'm gobsmacked!!! Who on earth wants to pay that much for a reverb? I don't care if it makes me a cup of fresh coffee while I listen to the tail, I'm not going to pay that for a reverb even if I become a millionaire.

[simmo75]

For me, it’s about the sound and CRP sounds incredible, works really well with ambisonic projects as well as stereo.
To my ears, MTR sounds really thin and metallic. Each to there own and taste is subjective.

Demo the two, do the comparison yourself, and be prepared to part with your money for CRP

[E_Anderson]

For me, it’s about the sound and CRP sounds incredible, works really well with ambisonic projects as well as stereo.
To my ears, MTR sounds really thin and metallic. Each to there own and taste is subjective.

Demo the two, do the comparison yourself, and be prepared to part with your money for CRP

I wouldn't be surprised. I've been preparing my wallet for the past 2 months, it's only been the past couple of days I've actually given MTurboReverb the time of day. MCharmVerb sounded to me like you described, but hearing some of the work by Daniel Dettwiler/Simon Stockhausen/Chandler Guitar/Flashbulb, I was caught a little off-guard by how good MTR actually sounded, and admittedly I'm a bit of a nut for sound design and plugin depth. The demo will be very enlightening - assuming I'm even competent enough to make any realizations, that is.

Between 2c/Pro-R/Valhalla demos, me owning R4/Nimbus, and trialing MTR, CRP and 7H together, it's gonna be one hell of a shootout

300 bucks? For a reverb????? You're kidding aren't you? Is that how much it is? Sorry for all the questions, but I'm gobsmacked!!! Who on earth wants to pay that much for a reverb? I don't care if it makes me a cup of fresh coffee while I listen to the tail, I'm not going to pay that for a reverb even if I become a millionaire.

Meanwhile Bricasti M7 retailing for $3950 USD

Also MTR goes on sale for half or more off periodically. Or you can buy used, but... Other products being discussed in this thread are often over $100; for instance, Cinematic Rooms which we're discussing presently to some degree: $400. Of course it also goes on sale for half-price during Black Friday. Blackhole for $200, but twice-ish? per year sales for $50.

Valhalla is somewhat unique with regard to price and no one is saying you have to buy any of this, it's only if you want what it gives you. For me, with depth like MTurboReverb provides... I could be persuaded.

On the off chance you're actually wanting to spend money on a reverb right now, but not much, you might look at the Plugin Boutique sale (again) of Nimbus/R4, really good reverbs for sub-Valhalla prices (reverbs which people were up until these sales started, actually paying $200-300 for, because they really are good reverbs)

[Kumal]

The only 2 turbo things about it are the CPU meter going up and me opening another reverb
300 bucks are better invested in something that actually sounds good instead of a quantity of presets.

300 bucks? For a reverb????? You're kidding aren't you? Is that how much it is? Sorry for all the questions, but I'm gobsmacked!!! Who on earth wants to pay that much for a reverb? I don't care if it makes me a cup of fresh coffee while I listen to the tail, I'm not going to pay that for a reverb even if I become a millionaire.

Even 350$.

I have to say I don't see creating your own reverb algos as a advantage. If I spent much money I want the plugin to do the work, else I'd buy Reaktor or Plug'n'Script and that's it. But that seems a Meldaproduction thing: first you needed to build your own UI, now the processing And I agree to what has been said, I don't think it sounds that great out of the box. While other plugins for less money, with less options, already can work wonders with just a default preset. And as with the other "turbo" plugins, there is a price to pay for the abstraction. May it be performance wise or UI wise.

Also MTR goes on sale for half or more off periodically.

Which has the same negative effect as with waves or Plugin Alliance: knowing they're not worth more than half of the money and you somehow being ripped off at full price. At least it feels like that. Don't know why devs are doing this. But then I look at the Meldaproduction page and see a paid free bundle or pages full of same type effects and know it's more about quantity and getting something at all out to the customers. Makes me sad sometimes.

[E_Anderson]

If I spent much money I want the plugin to do the work, else I'd buy Reaktor or Plug'n'Script and that's it.
...[re: half-off]Which has the same negative effect as with waves or Plugin Alliance: knowing they're not worth more than half of the money and you somehow being ripped off at full price. At least it feels like that.

I'd appreciate seeing more consistent, and low prices for Melda software, for sure, because for me it just means an inconvenience of waiting for a sale/a second-hand deal or pestering their support for a discount, because yeah, I'm also not paying $300 for MTR, and I'm also not paying $400 for CRP. There are a few arguments to be made otherwise, like a greater number of products meaning a greater number of sales opportunities, or how Exponential Audio reverbs are practically being given away after being bought by Izotope, but I'd hate to see anyone paying anywhere close to retail for most Waves/PA plugins.

I'll push back on the Reaktor bit - I see where you're coming from, and I agree that Melda probably seems to have less of a focus on providing the finished algorithms set to the tastes of the plugin developer+the artists and engineers they worked with and more of a focus on ultimate flexibility - but I really hear some good things in what comes out of the box with MTR, and there are some really talented artists and engineers who swear by just what's coming out of the box. Plus, just designing the interface Melda provides for manipulating ERs would probably take a long time in Reaktor, and they manage to make algorithmic programming, as far as I know, pretty easy. At least, typing-wise So we'll see how this demoing turns out. It may be that the people I heard using MTR with such great sound coming from it could just be experienced reverb programmers? Given the cast I mentioned above, they'd certainly be the demographic to best make use of it, but I can say that the sounds they were achieving did sound great. Definitely not just metallic or thin, and I can certainly program such an unpleasant sound out of basically any top-end reverb.

I'm with you on simplicity - it'd be nice to see fewer "Reverbs" in MTR, but that appears to just be part of how it works. Some of what's in there is probably on the same level already as some of the top-end Relab/LiquidSonics stuff, the fact that you have to sift through 100 Reverbs to get to them is a bit annoying, but it comes with the territory. Even Valhalla is a bit bothersome with its number of algorithms to explore, which is why Nimbus/R4 (and hopefully CRP) are a breath of fresh air with only 4 distinct algorithms to choose from and then all of the parameters offering predictable but flexible quality.

[E_Anderson]

Jesus, folks. Please excuse the long-windedness. It doesn't seem like that much when I'm typing it out, but then I see it sticking out on the page like a proud 6-inch nose. Brevity is a skill

[CrystalWizard]

No worries, super long posts that aren't nonsense is refreshing.