MeldaProduction

CableChannel · Post by **CableChannel** » Tue Oct 07, 2014 10:13 pm

BTW elassi, is your click/pop bass problem resolved? If not I might look at it tomorrow.

wildcafe · Post by **wildcafe** » Tue Oct 07, 2014 10:15 pm

Oooookay, now I got the idea, thanks guys.

4th possibility: mod 1 contains an lfo that should be faded / delayed.
In mod 2 set "LFO modulation" of mod 1 as target. You can now fade in / delay mod 1 with the envelope of mod 2.

@elassi: I'd prefer Red Bull Whiskey

Btw: I love the learn function of the modulators...

elassi · Post by **elassi** » Tue Oct 07, 2014 10:19 pm

CableChannel wrote:BTW elassi, is your click/pop bass problem resolved? If not I might look at it tomorrow.

The prob is not within the fxp I've uploaded - just for the record.

First I'd like to know if the export works.

I'm a serious Beta-tester.

elassi · Post by **elassi** » Tue Oct 07, 2014 10:24 pm

wildcafe wrote:@elassi: I'd prefer Red Bull Whiskey

Though I admire your pretty rapid consciousness for the depth of MPower's in-built playground I must correct you: I promised beer, not liquor.

Breeze · Post by **Breeze** » Wed Oct 08, 2014 3:17 am

Sorry if I missed this, but is there a way to control envelope times from MIDI velocity that's polyphonic?

MeldaProduction · Post by **MeldaProduction** » Wed Oct 08, 2014 8:45 am

Breeze wrote:Sorry if I missed this, but is there a way to control envelope times from MIDI velocity that's polyphonic?

No I'm afraid, but if you don't care about notes with different velocity arriving at the same moment, then it is possible - simply attach MIDI to the envelope parameters. When you press a key then, the envelope will be changed, the new voice created with that envelope and if another note arrives later, the envelope can change again. It's not very accurate, but it should do the trick.

Breeze · Post by **Breeze** » Wed Oct 08, 2014 12:46 pm

MeldaProduction wrote:No I'm afraid, but if you don't care about notes with different velocity arriving at the same moment, then it is possible - simply attach MIDI to the envelope parameters.

OK, thanks. IMO, this should be considered for a future revision as it's essential for making patches sound organic and feel natural when played. In nature, things behave and sound differently if you hit them softly or hard... just like people.

CableChannel · Post by **CableChannel** » Wed Oct 08, 2014 8:49 pm

When you save a modulator preset, the target parameters are not saved. That's a bug isn't it?
If you save the whole row of modulators as a preset, then the target parameters are included as expected.

MeldaProduction · Post by **MeldaProduction** » Wed Oct 08, 2014 9:55 pm

It's intentional, modulator presets are made so that you can use them in different plugins and with different parameter. They control behaviour, not the target

.

CableChannel · Post by **CableChannel** » Wed Oct 08, 2014 10:21 pm

MeldaProduction wrote:It's intentional, modulator presets are made so that you can use them in different plugins and with different parameter. They control behaviour, not the target .

Hm the thing is, sometimes I have a complex setup of multiple targets, where interval ranges are carefully adjusted to fit with one another etc. and which took quite some time to create. And currently there is no way to save this work, I have to do it all by hand again if I need it again.

I can use a multiparameter to circumvent this, but that's only a workaround, and in fact I lose one of eight multiparams which I could/should better use for user interaction stuff.

I vote for saving the targets with the LFO. I don't see any disadvantage in that. Or maybe you could make preset saving available for the target section separately, then the LFO presets could remain as they are.

Another request: is it possible to include transformation shapes for the midi setup? It would be very cool to have custom transformation shapes when you attach a parameter to velocity, midi CC, etc.
Again, workaround via multiparam is already possible, but these are limited, only eight of them, and I prefer using them as quick controls for the user to fiddle with.

MeldaProduction · Post by **MeldaProduction** » Wed Oct 08, 2014 11:04 pm

Sorry, that won't happen. The whole idea is really to let you easily store/randomize the LFO behaviour, not the target parameters, which are assumed to be different every time, otherwise you could just start with the same preset...

About the MIDI - sorry, I'll deny this too. Mainly because of storage limitations, long technical story

. Simply put, the settings/presets are already too big and this would make them huge. And it's really a very specific feature, it's just not worth it.

wildcafe · Post by **wildcafe** » Thu Oct 09, 2014 8:43 am

elassi wrote:
wildcafe wrote:@elassi: I'd prefer Red Bull Whiskey
Though I admire your pretty rapid consciousness for the depth of MPower's in-built playground I must correct you: I promised beer, not liquor.

Ok then let's go for a beer

- sorry for OT

CableChannel · Post by **CableChannel** » Thu Oct 09, 2014 5:35 pm

Hey Vojtech, did you confirm the voice limit feature? It's really important for pads with long tails. I know of two algorithms for voice stealing, oldest or quietest. Any of those would do, whatever is simpler

CableChannel · Post by **CableChannel** » Thu Oct 09, 2014 6:13 pm

Another (quick I guess) request: filter frequency by note currently allows a negative value of -8 minimum. Unfortunately, -8 just can just (hardly) compensate the regular internal frequency by note which is always active. It would be cool if the configurable frequency by note range is extended to -16 or something like that so one can really get a filter frequency which actually goes down for higher notes. Since the functionality is there and only the range has to be changed I guess this should be possible?

MeldaProduction

KVR Audio

MPowerSynth improvements & feature requests