davidestevens

Is there a message that I can send to a plug in in a vst~ to change 

the presets of that plug? Or am I going to have to dump all the 

parameters out to a bunch of number boxes exposed to pattr?

Is there a message that I can send to a plug in in a vst~ to change  
the presets of that plug? Or am I going to have to dump all the  
parameters out to a bunch of number boxes exposed to pattr?

preset-change-to-vst

>Is there a message that I can send to a plug in in a vst~ to change 

>the presets of that plug? Or am I going to have to dump all the 

>parameters out to a bunch of number boxes exposed to pattr?

you can save and recall presets in vst~ - i use it all the time. 

>hi all,
>
>Is there a message that I can send to a plug in in a vst~ to change 
>the presets of that plug? Or am I going to have to dump all the 
>parameters out to a bunch of number boxes exposed to pattr?

  you can save and recall presets in vst~ - i use it all the time. 
VERY useful with NI plug-ins !!!!

kasper
-- 
  Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com

On 19 janv. 07, at 18:50, David Stevens wrote:

> Is there a message that I can send to a plug in in a vst~ to change 

> the presets of that plug? Or am I going to have to dump all the 

> parameters out to a bunch of number boxes exposed to pattr?

You just need to send an integer (see example in the help file).

> hi all,
>
> Is there a message that I can send to a plug in in a vst~ to change  
> the presets of that plug? Or am I going to have to dump all the  
> parameters out to a bunch of number boxes exposed to pattr?

On 19 Jan 2007, at 18:07, Emmanuel Jourdan wrote:

>> Is there a message that I can send to a plug in in a vst~ to 

> You just need to send an integer (see example in the help file).

I want to do this with my Ohmboyz delay plugin, which has 8 preset 

slots. Clicking on a preset button inside the plugin causes the 

controls to smoothly onterpolate from one preset to the next. Sending 

an integer to the vst~ inlet doesn't appear to do this. Nor do the 

resulting control settings look to be the same as when I change 

presets from inside the plug. Perhaps there's a difference between 

program and preset? What I want to do is just select the internal 

>>
>> Is there a message that I can send to a plug in in a vst~ to  
>> change the presets of that plug?
> You just need to send an integer (see example in the help file).
>

I want to do this with my Ohmboyz delay plugin, which has 8 preset  
slots. Clicking on a preset button inside the plugin causes the  
controls to smoothly onterpolate from one preset to the next. Sending  
an integer to the vst~ inlet doesn't appear to do this. Nor do the  
resulting control settings look to be the same as when I change  
presets from inside the plug. Perhaps there's a difference between  
program and preset? What I want to do is just select the internal  
preset numbers.

Ignore my last email - I just checked this with my other Ohmforce 

plugs, and it works as expected, although unfortunately without the 

> On 19 janv. 07, at 18:50, David Stevens wrote:

>> change the presets of that plug? Or am I going to have to dump all 

>> the parameters out to a bunch of number boxes exposed to pattr?

Ignore my last email - I just checked this with my other Ohmforce  
plugs, and it works as expected, although unfortunately without the   
interpolation between presets.

> On 19 janv. 07, at 18:50, David Stevens wrote:
>
>> hi all,
>>
>> Is there a message that I can send to a plug in in a vst~ to  
>> change the presets of that plug? Or am I going to have to dump all  
>> the parameters out to a bunch of number boxes exposed to pattr?
>
> You just need to send an integer (see example in the help file).
>
> Best,
> ej
>
>


>On 19 Jan 2007, at 18:07, Emmanuel Jourdan wrote:

>>>Is there a message that I can send to a plug in in a vst~ to 

>>You just need to send an integer (see example in the help file).

>I want to do this with my Ohmboyz delay plugin, which has 8 preset 

>slots. Clicking on a preset button inside the plugin causes the 

>controls to smoothly onterpolate from one preset to the next. 

>Sending an integer to the vst~ inlet doesn't appear to do this. Nor 

>do the resulting control settings look to be the same as when I 

>change presets from inside the plug. Perhaps there's a difference 

>between program and preset? What I want to do is just select the 

I never found a way to intrepolate (or rather to use the interpolate 

function) with plugins such as OHM Force and GRM Tools - i even 

asked them why and... well, seems you can't

the only way I found is to interpolate in max - dump the state of the 

params and "fade" them into the next preset..

>On 19 Jan 2007, at 18:07, Emmanuel Jourdan wrote:
>
>>>
>>>Is there a message that I can send to a plug in in a vst~ to 
>>>change the presets of that plug?
>>You just need to send an integer (see example in the help file).
>>
>
>Oh yeah! like - duh!
>
>But ...
>
>I want to do this with my Ohmboyz delay plugin, which has 8 preset 
>slots. Clicking on a preset button inside the plugin causes the 
>controls to smoothly onterpolate from one preset to the next. 
>Sending an integer to the vst~ inlet doesn't appear to do this. Nor 
>do the resulting control settings look to be the same as when I 
>change presets from inside the plug. Perhaps there's a difference 
>between program and preset? What I want to do is just select the 
>internal preset numbers.
>

I never found a way to intrepolate (or rather to use the interpolate 
function) with plugins such as OHM Force  and GRM Tools - i even 
asked them why and... well, seems you can't

the only way I found is to interpolate in max - dump the state of the 
params and "fade" them into the next preset..

On 19 Jan 2007, at 19:00, Kasper T Toeplitz wrote:

> I never found a way to intrepolate (or rather to use the 

> interpolate function) with plugins such as OHM Force and GRM Tools 

> - i even asked them why and... well, seems you can't

> the only way I found is to interpolate in max - dump the state of 

> the params and "fade" them into the next preset..

What I'm now thinking of doing is dumping out all the parameters to a 

bunch of named number boxes in a hidden subpatch with pattrstorage. 

The only thing that ' s putting me off with Ohmboyz is that there 

are 121 parameters, which is a heck of a lot of naming of number 

boxes to do! I was looking to see if there's a way of naming them 

using a coll which already has the parameter names in it and some 

sort of set message, but it doesn't look like that's possible. So I 

guess I'll have to do it manually. Still, once it's done, I'll have 

total flexibility with controlling the plugin from Max! And I wanted 

to have routable access to this plugin in another instrument I built 

On 19 Jan 2007, at 19:00, Kasper T Toeplitz wrote:
>
> I never found a way to intrepolate (or rather to use the  
> interpolate function) with plugins such as OHM Force  and GRM Tools  
> - i even asked them why and... well, seems you can't
>
> the only way I found is to interpolate in max - dump the state of  
> the params and "fade" them into the next preset..

What I'm now thinking of doing is dumping out all the parameters to a  
bunch of named number boxes in a hidden subpatch with pattrstorage.  
The only thing that ' s  putting  me off  with Ohmboyz is that there  
are 121 parameters, which is a heck of a lot of naming of number  
boxes to do! I was looking to see if there's a way of naming them  
using a coll which already has the parameter names in it and some  
sort of set message, but it doesn't look like that's possible. So I  
guess I'll have to do it manually. Still, once it's done, I'll have  
total flexibility with controlling the plugin from Max! And I wanted  
to have routable access to this plugin in another instrument I built  
as well, so ...

you don't need to write it all - it's max after all

the following patch (dirty as it is, sorry) lets you store 2 "states" 

of a plug-in (2 presets if you want) - actually a lot more - it 

writes it in a coll, and then you can interpolate between them (0.->

lets you store presets and interpolate between them

hope you'll find it useful (needs Lmult object - part of lobjects)

>>I never found a way to intrepolate (or rather to use the 

>>interpolate function) with plugins such as OHM Force and GRM Tools 

>>- i even asked them why and... well, seems you can't

>>the only way I found is to interpolate in max - dump the state of 

>>the params and "fade" them into the next preset..

>What I'm now thinking of doing is dumping out all the parameters to 

>a bunch of named number boxes in a hidden subpatch with 

>pattrstorage. The only thing that ' s putting me off with Ohmboyz 

>is that there are 121 parameters, which is a heck of a lot of naming 

>of number boxes to do! I was looking to see if there's a way of 

>naming them using a coll which already has the parameter names in it 

>and some sort of set message, but it doesn't look like that's 

>possible. So I guess I'll have to do it manually. Still, once it's 

>done, I'll have total flexibility with controlling the plugin from 

>Max! And I wanted to have routable access to this plugin in another 

the following patch (dirty as it is, sorry) lets you store 2 "states" 
of a plug-in (2 presets if you want) - actually a lot more - it 
writes it in a coll, and then you can interpolate between them (0.->
1.)

>
>>
>>I never found a way to intrepolate (or rather to use the 
>>interpolate function) with plugins such as OHM Force  and GRM Tools 
>>- i even asked them why and... well, seems you can't
>>
>>the only way I found is to interpolate in max - dump the state of 
>>the params and "fade" them into the next preset..
>
>What I'm now thinking of doing is dumping out all the parameters to 
>a bunch of named number boxes in a hidden subpatch with 
>pattrstorage. The only thing that ' s  putting  me off  with Ohmboyz 
>is that there are 121 parameters, which is a heck of a lot of naming 
>of number boxes to do! I was looking to see if there's a way of 
>naming them using a coll which already has the parameter names in it 
>and some sort of set message, but it doesn't look like that's 
>possible. So I guess I'll have to do it manually. Still, once it's 
>done, I'll have total flexibility with controlling the plugin from 
>Max! And I wanted to have routable access to this plugin in another 
>instrument I built as well, so ...
>

> I want to do this with my Ohmboyz delay plugin, which has 8 preset 

> slots. Clicking on a preset button inside the plugin causes the 

> controls to smoothly onterpolate from one preset to the next. Sending 

> an integer to the vst~ inlet doesn't appear to do this.

because those 8 presets are _not regular VST plug-in presets.

they might be identical to the first 8 VST presets of the

ohmforce plug-in, but it is an independent mechanism.

hey if you would put some effort into creating your own

preset morpher in MAx, you could use it with _all plug-ins

there are at least 2 examples people somewhere out there 

made, when i remember right one was an example for the use 

> But ...
>
> I want to do this with my Ohmboyz delay plugin, which has 8 preset  
> slots. Clicking on a preset button inside the plugin causes the  
> controls to smoothly onterpolate from one preset to the next. Sending  
> an integer to the vst~ inlet doesn't appear to do this. 

because those 8 presets are _not regular VST plug-in presets.
they might be identical to the first 8 VST presets of the
ohmforce plug-in, but it is an independent mechanism.

hey if you would put some effort into creating your own
preset morpher in MAx, you could use it with _all plug-ins
andnot only with ohmboys and oddity. :)

there are at least 2 examples people somewhere out there 
made, when i remember right one was an example for the use 
of 3rd party list interpolation objects.

preset change to vst