It should be possible to define mappings from one plugin's control
parameters to another plugin's. This would have to be done by the
user. At most there would be a parametric linear or logarithmic
function involved fo map the values, in addition to mapping the
controller numbers or NRPNs. Are
On Mon, Dec 21, 2015 at 6:46 PM, robert bristow-johnson <
r...@audioimagination.com> wrote:
>
> regarding Pro Tools (which i do not own and haven't worked with since 2002
> when i was at Wave Mechanics, now called SoundToys), please take a look at
> this blog:
>
>
thank you to Nigel, Thomas, Bjorn, and Steffan.
essentially you're telling me there is no existing standard of control
number assignment or of scaling and offset of that control.
regarding MIDI 1.0 (which is what goes into MIDI files), i had noticed
that there were some "predefined
> so then, in your session, you mix some kinda nice sound, save all of the
> sliders in PT automation and then ask "What would this sound like if I used
> iZ instead of McDSP?", can you or can you not apply that automation to
> corresponding parameters of the other plugin? i thought that you
This paper on the Audio Effects Ontology extension shows a possible direction
towards unified parameters for a given class of effects (see, e.g.: sec 4.3
Effect
Parameters)http://ismir2013.ismir.net/wp-content/uploads/2013/09/41_Paper.pdf
Disclaimer: I work in the same research group as the
On 21.12.15 03:48 , Bjorn Roche wrote:
> Generally speaking, a program like ProTools (the "host app") will open a
> plugin, and ask for a list of parameters. The plugin will respond with
> something like "These are my parameters and they have the following
> basic properties (id, display name,
Robert,
> i just would have thought that by now, 30+ years later,
> that a common practice would have evolved and something would have been
> published (and i could not find anything).
It's the same situation with, for example, DMX512. 30 years later, and
there's NO consensus on these things.
