MSF: Use velocity to determine final output AFTER all processing?

[Annabanna]

I have a patch in mind, and the one part I'm not sure of in how to create it has to do with the fact that it has a significant amount of clipping built into the sound and I don't want it to clip differently depending on velocity, but I do want to be able to determine the level via velocity.

If I understand correctly, the default routing would mean that the velocity determines the level of the sampler module (for instance) which would then mean that different velocities hit the clipper (waveshaper) IN THE FX section differently.

That's not what I want in this case. I'm assuming it's easy enough to turn the velocity off for the sampler module (or maybe it's global), but not sure what to look at to see about then rewiring it to have the velocity determine the final output post fx.

[Held]

In case you didn't know this, there's a waveshaper module in the Generator section, so you can do the distortion per voice and then set the volume with a velocity modulator after.

The velocity is a per note property, so there are only per voice modulators available. For the global settings, click "Show advanced settings" above the Global Envelope.

Unfortunately, I don't have an answer to your actual question, and I don't think it's possible. Maybe there's a crazy way using a follower to normalize the volume before the distortion and then set it back to the original value after, but that's way to complicated for my current level of understanding.

[Annabanna]

In case you didn't know this, there's a waveshaper module in the Generator section, so you can do the distortion per voice and then set the volume with a velocity modulator after....

I don't have the plugin in front of me, but if I remember correctly, the issue is that there's no EQ (tilt, so mDynamicEQ) in the generator section. Not just on this patch, but pretty much always I want to clip AFTER any EQ since the whole point of the clipping is peak management, and the EQ can then change the peaks.

I believe the issue was that this then forces me to use the FX section for both the EQ and then the waveshaper. Sounds fine at a constant velocity, but the whole nature of it changes rather than just the level with velocity changes.

[Held]

I don't have the plugin in front of me, but if I remember correctly, the issue is that there's no EQ (tilt, so mDynamicEQ) in the generator section. Not just on this patch, but pretty much always I want to clip AFTER any EQ since the whole point of the clipping is peak management, and the EQ can then change the peaks.

There's dynamicEQ in the generator section No tilt eq, but you can build it with the multi-paremeters if you want.

[Annabanna]

I don't have the plugin in front of me, but if I remember correctly, the issue is that there's no EQ (tilt, so mDynamicEQ) in the generator section. Not just on this patch, but pretty much always I want to clip AFTER any EQ since the whole point of the clipping is peak management, and the EQ can then change the peaks.

There's dynamicEQ in the generator section No tilt eq, but you can build it with the multi-paremeters if you want.

OK, thx. I think that was the reason I was in FX section, but I may have the details mixed up. Will take a look tonight. Not quite picturing how tilt EQ would be built with MP's.

[Held]

OK, thx. I think that was the reason I was in FX section, but I may have the details mixed up. Will take a look tonight. Not quite picturing how tilt EQ would be built with MP's.

If you have the stand-alone version of MDynamicEQ, there's a device that you can study. It's basically two bands (high and low-slope) with the frequency controlled by the same multi-parameter. Then there's a second parameter that controls the gain of both bands, but one is inverted.

How are you getting tilt eq in the FX section?

[Annabanna]

How are you getting tilt eq in the FX section?

DynamicEQ module via slope. Functional in a very basic sense, but I use tilt EQ constantly, and it would be MUCH nicer if there was something that worked like GoodHertz TiltShift where you just tell it the start and end points and how much rise or fall between, and it generates a slope limited to those exact parameters. MUCH more intuitive, MUCH quicker to dial in, and it's that kind of tight control over exactly what is and isn't getting tilted on either end that almost always yields better results.


Perhaps that can be cobbled via MP's that I could use in MSF, MXXX, etc.