Cycling 74 » Topic: consecutive pp's http://cycling74.com/forums/topic/consecutive-pps/feed Wed, 19 Jun 2013 13:37:48 +0000 http://bbpress.org/?v=2.2.4 http://cycling74.com/forums/topic/consecutive-pps/#post-30772 <![CDATA[consecutive pp's]]> http://cycling74.com/forums/topic/consecutive-pps/#post-30772 Mon, 12 Mar 2007 22:47:57 +0000 Dan Nigrin I currently have a bunch of user-exposed pp’s (for example, say numbers 1-20). I also have a bunch of hidden pp’s (say numbers 21-50). I might need to add more user-exposed pp’s in the future.

I would like automation stored by host programs that use my pluggo to be future proof – with this in mind, would it be better to set up my parameters like this:

1-20 current user-exposed pp’s
21-50 current hidden pp’s
51-? future user-exposed pp’s

OR

1-20 current user-exposed pp’s
21-50 future user-exposed pp’s
51-80 current hidden pp’s

The docs say “Parameter numbers should be consecutive (but they need not be)”. What badness might happen if I choose the second option, and in my current plugin have non-continuous pp’s?

Conversely, what badness might happen in the future, if I choose the first option, and have user-exposed pp’s that are discontinous?

Thanks,
Dan

]]> http://cycling74.com/forums/topic/consecutive-pps/#post-98961 <![CDATA[Re: consecutive pp's]]> http://cycling74.com/forums/topic/consecutive-pps/#post-98961 Mon, 12 Mar 2007 23:51:54 +0000 Timothy Place On Mar 12, 2007, at 5:47 PM, Dan Nigrin wrote:

> The docs say “Parameter numbers should be consecutive (but they
> need not be)”. What badness might happen if I choose the second
> option, and in my current plugin have non-continuous pp’s?
>
> Conversely, what badness might happen in the future, if I choose
> the first option, and have user-exposed pp’s that are discontinous?

The tricky part here is that the “hidden” parameter mechanism is a
suggestion to the host – and it is not binding. Like most things
VST, everything is optional and every plug developer and host does it
differently… So what does this mean?

Well, in Ableton Live (which doesn’t hide hidden parameters) the user
is going to see all of them anyway.

What Pluggo does if the pp numbers are not contiguous is that it adds
a bunch of dummy parameters internally. So follow this scenario:
1. You use non-contiguous pp #s
2. Your users then create sessions with your awesome plug – and save
their sessions
3. You decide to use the pp #s between the ones you were already using
4. Your user loads one of their old sessions

What happens? Well, all of those dummy parameters had written a
value of zero in the session. So when the user loads your new
version, all of your new parameters will be zeroed instead of at some
other intelligent default.

It should all be as clear as mud now, so I’ll let you chose the
compromise that best fits you :-)
Tim

]]> http://cycling74.com/forums/topic/consecutive-pps/#post-98962 <![CDATA[Re: consecutive pp's]]> http://cycling74.com/forums/topic/consecutive-pps/#post-98962 Tue, 13 Mar 2007 01:14:39 +0000 Dan Nigrin >It should all be as clear as mud now, so I’ll let you chose the
>compromise that best fits you :-)
> Tim

Thanks Tim, very useful info.

Dan
–
Dan Nigrin
Defective Records
202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X / Major
Malfunction
http://www.defectiverecords.com

http://www.jackosx.com

]]>