Mattijs

I thought I might just drop the question: does anyone know a way to ignore a specific parameter in a plugconfig program? I need one pp to remain unmodified when a user recalls a preset.

ignore-parameter-in-preset

we had something like this on the old yahoogroup

http://launch.groups.yahoo.com/group/pluggo/)

one solution could be that you disconnect certain

parameters from/to the pp objects (controlled an 

if they are disconnected, they remain untouched after

changing the preset or loading one from disk.

we had something like this on the old yahoogroup
(http://launch.groups.yahoo.com/group/pluggo/)

one solution could be that you disconnect certain
parameters from/to the pp objects (controlled an 
additional pp parameter.)

if they are disconnected, they remain untouched after
changing the preset or loading one from disk.


I needed to set the pp from Logics environment (kindof object oriented approach where there are various instances of the plugin that need some parameters depending on the track they are inserted in).

Wak's idea brought me to my final solution:

Quote: mattijs@samplemadness.nl wrote on Fri, 21 July 2006 03:06

----------------------------------------------------

> I needed to set the pp from Logics environment (kindof object oriented approach where there are various instances of the plugin that need some parameters depending on the track they are inserted in).

> Wak's idea brought me to my final solution:

> #P newobj 46 31 86 196617 pp 2 Player 1 16;

> #P number 10 31 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #N pp 1 DetectPresetChange hidden fixed;

> #P newobj 136 69 179 196617 pp 1 DetectPresetChange hidden fixed;

there is one other approach for zthings like that 

it is - of course - possible to send the message

Quote: mattijs@samplemadness.nl wrote on Fri, 21 July 2006 03:06
----------------------------------------------------
> Thanks Roman and Wak,
>
> I needed to set the pp from Logics environment (kindof object oriented approach where there are various instances of the plugin that need some parameters depending on the track they are inserted in).
>
> Wak's idea brought me to my final solution:
>
> #P newex 46 50 40 196617 t b 1 i;
> #P newex 114 69 21 196617 t 0;
> #P newex 61 69 47 196617 gate 1 1;
> #N pp 2 Player 1 16;
> #P newobj 46 31 86 196617 pp 2 Player 1 16;
> #P number 10 31 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #N pp 1 DetectPresetChange hidden fixed;
> #P newobj 136 69 179 196617 pp 1 DetectPresetChange hidden fixed;
> #P connect 1 0 2 0;
> #P connect 2 0 5 0;
> #P connect 0 0 4 0;
> #P connect 4 0 3 0;
> #P connect 3 0 1 0;
> #P connect 5 2 3 1;
> #P connect 5 1 3 0;
> #P connect 5 0 1 0;
>
> This works!

there is one other approach for zthings like that 
which we all forgot in the past.

it is - of course - possible to send the message
"enable 0" to a [pp] object.

there is one other approach for things like that 

there is one other approach for things like that 
which we all forgot in the past.

Perhaps this is only in version 4.6? 
What would it do?

okay it seem i need to explain better whats up.

first of all, it is "disable" and not "enable".

(remember? rule number one: do not trust 110)

then i should have added that i have only seen it 

in someone else?s patch and not yet tried it.

because it does not do anything locally (numbers still 

pass through in max) my assumption is that it only

disabled from listening to the host programs VST 

first of all, it is "disable" and not "enable".
disable works.

then i should have added that i have only seen it 
in someone else?s patch and not yet tried it.

because it does not do anything locally (numbers still 
pass through in max) my assumption is that it only
disabled from listening to the host programs VST 
parameter data.

Ignore parameter in preset