some more MIDI plugins...

[Miq]

okay I see why it's not working for you...the expression editor is CAPS sensitive, and the internal functions need to be lowercase...also you need a semicolon at the end of each expression. Try this:

Code: Select all

ipart(w/16)*16+ipart(x/8);

Ah, the uppercase was the culprit! I had a semicolon in my function, just forgot to type it in my post. Thanks a lot.

Also download the new version above again....I've added a switch to choose between 0-10v or 0-127v
nF

You bet I did!
Thanks again, soma and nicfit!

[fr4ncesco]

NicFit,
a suggestion/request:
wouldn't be useful to have a kind of CCvalue_converter?

Think of a 128x128 grid of little squares, where the columns represent the input CC values and the rows are the output CC values.
A diagonal line (from left-bottom to top-right) wouldn't change anything, any input CC value would be mapped into the same value for the output.

With the mouse one could draw interesting mapping curves. The only requirement is that each input CC value must me mapped to an output CC value, so only a square per column could be switched on.

An example: say I'm using the modulation wheel to control the cutoff filter (classic application).
At the same time, I would like the resonance to have high values only when the filter is almost closed (15%) and almost fully open (85%), near zero anywhere else.

In this case, it would be enough to draw a "M" shape on the grid (the two peaks at 20 and 108). Hope it makes sense.

What do you think?


ciao
Francesco

[silicon/silicium]

Think of a 128x128 grid of little squares, where the columns represent the input CC values and the rows are the output CC values.

héhé, good luck for making such a matrix in synthedit

[NicFit]

NicFit,
a suggestion/request:
wouldn't be useful to have a kind of CCvalue_converter?

Think of a 128x128 grid of little squares, where the columns represent the input CC values and the rows are the output CC values.
A diagonal line (from left-bottom to top-right) wouldn't change anything, any input CC value would be mapped into the same value for the output.

With the mouse one could draw interesting mapping curves. The only requirement is that each input CC value must me mapped to an output CC value, so only a square per column could be switched on.

An example: say I'm using the modulation wheel to control the cutoff filter (classic application).
At the same time, I would like the resonance to have high values only when the filter is almost closed (15%) and almost fully open (85%), near zero anywhere else.

In this case, it would be enough to draw a "M" shape on the grid (the two peaks at 20 and 108). Hope it makes sense.

What do you think?


ciao
Francesco

....yeah good luck to you getting something like that



Try this.
...double click to add a node, Ctrl+click to delete a node.



nF

[fr4ncesco]

wow, call it express service

yes, the curve with the nodes makes much more sense
will try it later

thanks!


ciao
Francesco

[soma]

nice one brother.

[asseca]

works perfect, thanks !

FR - is it possible to map 1 input-CC to say 4 output-CCs, i.e. 4 curves in 1 plugin. ( each curve a different color ) A user could then make accurate change-over CC-maps...

[NicFit]

works perfect, thanks !

FR - is it possible to map 1 input-CC to say 4 output-CCs, i.e. 4 curves in 1 plugin. ( each curve a different color ) A user could then make accurate change-over CC-maps...

The reason this was realeased so quickly after fr4ncesco requested it, was I only had to pull it out of a "preset morpher" plugin I made about 6 months ago...I only had to pull a couple graphics out of my more recent SE projects and ad save. The preset morpher is just what your talking about, but each control(16) has a seperate(smaller than above) envelope curve(I can't plot more than one per window).

I never released it because you will find that it's not practical to morph preset through CC in most situations the plugins will drop-out/crackle when you slam them with too many controller messages(some plugins are ok, but the ones I was interest in morphing crapped out loud)...


I wanted to develope it further into something like OhmForces MeloHman...but I was discouraged by the performance. ...I'll look into ressurrecting it soon as I get some of my other half finished projects out of the way.


nF

[asseca]

Hi NicFit,

It works perfect as is, no hurry at all...

[soma]

A ohm style preset morpher. Cool. I had a similar idea once but I couldn't get it to work.

[cold c]

I updated the midi plugins page with the various plugs.

Re: the preset morpher, it would be great if the existing preset generator in eXT could be modified for realtime/synchronised use via a note trigger or cc input.

A similar request is already on the FR list.

[soma]

Hey That was my orignal post on the FR list... cool.
I agree that would be the best way to handle preset morphing.
Also on teh subject , a "VST Parameter Dump" function would be invaluable. I'm picturing something like a button on the vst loader you press that sends all the current (or selected) VST parametr values to a clip.You could use this to draw interpolations between dumps or just to restor a preset with out having to worry about saving the preset elsewhere.

A copy/paste preset to envelope type function, I guess. But now we're off topic.

[RChler]

hi...all this stuff is great, nf...

unfortunately, i could not dl it...i get an error message kind of "server down"...have you moved some of the files ??

[RChler]

ah...ok


get 'em here, folks

http://www.asseca-pt.net//nicfit/index.html

[cold c]

a "VST Parameter Dump" function would be invaluable. I'm picturing something like a button on the vst loader you press that sends all the current (or selected) VST parametr values to a clip.You could use this to draw interpolations between dumps or just to restor a preset with out having to worry about saving the preset elsewhere.

I noticed that some plugins (like the Ohmforce effects) already behave in this way in hosts like SX3 that receive their automation from the plugin, so writing one parameter writes many to the host for those effects.

I think some other plugins like pro53 can dump CCs.

Any kind of snapshot feature like this in eXT could either be implemented as you say by converting all the current parameter values to CC and dumping them to an envelope or MIDI track (along with an automatically generated CC map), or alternatively, creating a more direct envelope-to-VST parameter relationship option in eXT and creating an automation point for each parameter value (but still having the ability to copy automation between envelope tracks of different types).