MeldaProduction

dmbaer · Post by **dmbaer** » Mon Feb 13, 2017 10:38 pm

Is the MTurboReverb timeframe becoming clear? Is there an ETA for release date, and if so, what is the final date by which our presets must be sent in?

MeldaProduction · Post by **MeldaProduction** » Wed Feb 15, 2017 12:27 pm

Nothing has been settled yet. But I'd like to do a huge thing - release V11 + MDrummer V7 + MTurboReverb at the same moment. Betas will be probably available sooner. But it's a big deal, just finishing MTurboReverb will be a tremendous amount of work, and I'll probably move the deadline once more

. Then next week starts another recording action for MDrummer, after the years... Then the V11 active presets... it will be brutal

.

Alphacodex · Post by **Alphacodex** » Wed Feb 15, 2017 1:14 pm

Rest assured that we love your work and do value your tireless effort!!
Thank you a lot!
Codex

VariKusBrainZ · Post by **VariKusBrainZ** » Wed Feb 15, 2017 1:19 pm

He can't be human !!!

Nicolaibob · Post by **Nicolaibob** » Wed Feb 15, 2017 2:50 pm

Sounds like it is gong to be an early christmas this year

Can't wait!

dmbaer · Post by **dmbaer** » Wed Feb 15, 2017 9:21 pm

MeldaProduction wrote:Nothing has been settled yet. But I'd like to do a huge thing - release V11 + MDrummer V7 + MTurboReverb at the same moment. Betas will be probably available sooner. But it's a big deal, just finishing MTurboReverb will be a tremendous amount of work, and I'll probably move the deadline once more . Then next week starts another recording action for MDrummer, after the years... Then the V11 active presets... it will be brutal .

Fair enough. I will push my SoundBytes Magazine article back from March to May in that case. Do do please keep us all posted however about anticipated release schedule. I don't want to send a preset submission in too soon or I may have to revise it when another pre-beta version of MTurboReverb gets released.

MeldaProduction · Post by **MeldaProduction** » Thu Feb 16, 2017 10:20 am

Will do! Thank you folks!

Batty · Post by **Batty** » Fri Feb 17, 2017 1:57 am

One question about MTurboReverb/MConvo/MReverb...
...is or will it be possible to curb the reverb or halls, to stop them with a secondary function, if they start to get inaudible in a mix, or if I want them to not pollute the following portion of a song, even if it normally has a much longer decay phase, and so, that it doesn't sound like a cut?
Like: if the delay/reverb is in the middle of it's long decay phase, I'd like switch to a much faster decay to shorten the unnecessary part.

How'd I do this, if possible already?
Will there be a function in MTurboReverb to conviently do this the easy way?
Mostly in Halls/Delays I have the problem that the first 3 halls are audible and the rest of the 15 halls are only there to pollute the song, even after the key has changed.
Maybe there is a kind of a curve that exposes the first three halls only and kills the rest in about 2 more halls and then it stays silent. The first three must stay loud enough. I hope I could explain, what I mean.

MeldaProduction · Post by **MeldaProduction** » Fri Feb 17, 2017 1:38 pm

Hmmm, I'm a little lost - isn't that exactly the job for automation dry/wet?

steve2KVR · Post by **steve2KVR** » Fri Feb 17, 2017 1:47 pm

...yup, automating dry/wet externally from the daw would work, tedious, very tedious, but it could/would work...however, MTR could/would be able to "know internally" when the nth "hall" occurred and have no further output...hth.../s~

vectorwarrior · Post by **vectorwarrior** » Fri Feb 17, 2017 3:12 pm

You could do this with mxxx, once Turbo reverb is added to it.

Send the output of the entire mix back to the track you want the reverb on, but send it to the side chain (easy to do in Reaper, unsure about other Daws). Put Turbo reverb in mxxx on the track. Send the side chain (the full mix) to mxxx's feedback generator 1, maybe using a utility module coming off the side chain to send to feedback 1, then another utility after it to mute the signal to silence. Then set up a follower module in mxxx, set it to receive from feedback 1 and set it to control whatever you want in Turbo reverb, probably wet dry of individual reflection generators, you can even set it to bypass reflection modules when their level is at silence, to reduce CPU usage.

The only issue I can think of is some Daws don't allow you to send signals upstream (to avoid internal feedback), so sending the whole mix might be problematic. An alternative is to put every other track in a bus, and send that bus' output to the reverb track (which is not in that bus) mxxx's side chain. The advantage is that the reverb track's amplitude won't contribute to the signal that adjusts the reverb, the downside to this approach is that you can really only do it once in a mix as you've separated the signals up.

Batty · Post by **Batty** » Fri Feb 17, 2017 6:37 pm

Well, yep - automation is good. But can it speed up as well?

This would be an addition, that no hall/reverb has so far, as far as I know.
But I wished I had it for easily forming the tail response of a hall/reverb over time.
Also a time dilation effect would be cool, to let a reverb snarl or slow down...
(like in this graphic)

MeldaProduction · Post by **MeldaProduction** » Mon Feb 20, 2017 2:07 pm

Well, there's a problem - it cannot be done

. Or at least not in an easy way. Basically the algorithm defines the way the signal is decaying. In most cases it is purely exponential (looks linear in dB scale, e.g. in the analysis), some nested algorithms such as an[an[a]] can decay differently. One can then use coefficients to for example interpolate between the 2. It's also a common technique to use mutliple LRs, each with a different decay time (and even shape) to form more complex decay curves.

MeldaProduction

KVR Audio

Last Call for Presets (MTurboReverb)?