Andrew Burgess

I've just got a novation sl 37 controller the automap feature of the new os V3 doesn't work with my pluggos

the stock c74 pluggos work and so do vlad's daevlplugs ones. anyone else got one of these things?

anyone-using-novation-automap-controller

If your uniqueID is made up of 3 digit numbers the novation automap server can't make a valid AU out of it

I re-did a couple of the auto generated id's manually and now they load fine.

ok, got it figured out.
If your uniqueID is made up of 3 digit numbers the novation automap server can't make a valid AU out of it

I re-did a couple of the auto generated id's manually and now they load fine.


there seems to be a limit on the ascii value the numbers of the uniqueID equate to. I've asked Novation to share this limit with developers. so far it seems (unofficially from my research only) as if you can't use any ascii value above Z (132) I'll post Novations reponse in this thread.

So what you're saying is that (if your unofficial research is 

correct) that for the Novation to recognize the Pluggo, its uniqueid 

must have its individual numbers no greater than 132 (i.e. 132 132 

132 is OK, but 133 133 133 is not, and also 132 132 133 is not?)

At 11:24 AM -0800 3/1/07, Andrew Burgess wrote:

>there seems to be a limit on the ascii value the numbers of the 

>uniqueID equate to. I've asked Novation to share this limit with 

>developers. so far it seems (unofficially from my research only) as 

>if you can't use any ascii value above Z (132) I'll post Novations 

202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X / Major 

So what you're saying is that (if your unofficial research is 
correct) that for the Novation to recognize the Pluggo, its uniqueid 
must have its individual numbers no greater than 132 (i.e. 132 132 
132 is OK, but 133 133 133 is not, and also 132 132 133 is not?)

At 11:24 AM -0800 3/1/07, Andrew Burgess wrote:
>to clarify for those interested....
>
>there seems to be a limit on the ascii value the numbers of the 
>uniqueID equate to. I've asked Novation to share this limit with 
>developers. so far it seems (unofficially from my research only) as 
>if you can't use any ascii value above Z (132) I'll post Novations 
>reponse in this thread.
>--
>Thanks,
>Andrew

-- 
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


actually upon further research it seems to be 127 127 127 is ok but 128 128 128 fails. as does 127 127 128

this is / was an issue for me as I've always just used the auto generated number when I made an instance of plugconfig

Now I'm going to manually edit them I'm using 51 xxx 50 where xxx is 1 - 127 . I suggest that you find a nice set of numbers and just always use those changing only one of them, pluggo AU scan will not allow 2 plugins with the same ID to be made into AU's as it violates the AU val spec and will fail Logic's auval scanner.

actually upon further research it seems to be 127 127 127 is ok but 128 128 128 fails. as does 127 127 128 

this is / was an issue for me as I've always just used  the auto generated number when I made an instance of plugconfig

Now I'm going to manually edit them I'm using 51 xxx 50 where xxx is 1 - 127 . I suggest that you find a nice set of numbers and just always use those changing only one of them, pluggo AU scan will not allow 2 plugins with the same ID to be made into AU's as it violates the AU val spec and will fail Logic's auval scanner. 

On Mar 1, 2007, at 2:34 PM, Andrew Burgess wrote:

> actually upon further research it seems to be 127 127 127 is ok but 

> this is / was an issue for me as I've always just used the auto 

> generated number when I made an instance of plugconfig

> Now I'm going to manually edit them I'm using 51 xxx 50 where xxx 

> is 1 - 127 . I suggest that you find a nice set of numbers and just 

> always use those changing only one of them, pluggo AU scan will not 

> allow 2 plugins with the same ID to be made into AU's as it 

> violates the AU val spec and will fail Logic's auval scanner.

I think you'll be running afoul of Cyling's own plug-in uniqueids if 

> actually upon further research it seems to be 127 127 127 is ok but  
> 128 128 128 fails. as does 127 127 128
>
> this is / was an issue for me as I've always just used  the auto  
> generated number when I made an instance of plugconfig
>
> Now I'm going to manually edit them I'm using 51 xxx 50 where xxx  
> is 1 - 127 . I suggest that you find a nice set of numbers and just  
> always use those changing only one of them, pluggo AU scan will not  
> allow 2 plugins with the same ID to be made into AU's as it  
> violates the AU val spec and will fail Logic's auval scanner.

I think you'll be running afoul of Cyling's own plug-in uniqueids if  
you go with 51, Andrew.  51 is Hipno.

http://www.daevlmakr.com
http://www.2secondfuse.com

>I think you'll be running afoul of Cyling's own plug-in uniqueids if 

I thought Hipno and Cycling's other plugins followed this rule? (from 

"0 0 0 is reserved and cannot be used. 0 followed by two other 

numbers is reserved for use by Cycling '74 and its registered plug-in 

So 51 51 51 would be OK, but not 0 51 51?

>I think you'll be running afoul of Cyling's own plug-in uniqueids if 
>you go with 51, Andrew.  51 is Hipno.

I thought Hipno and Cycling's other plugins followed this rule? (from 
the MSP Reference Manual):

"0 0 0 is reserved and cannot be used. 0 followed by two other 
numbers is reserved for use by Cycling '74 and its registered plug-in 
developers."

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


On Mar 2, 2007, at 9:20 AM, Dan Nigrin wrote:

>> I think you'll be running afoul of Cyling's own plug-in uniqueids 

>> if you go with 51, Andrew. 51 is Hipno.

> I thought Hipno and Cycling's other plugins followed this rule? 

> "0 0 0 is reserved and cannot be used. 0 followed by two other 

> numbers is reserved for use by Cycling '74 and its registered plug- 

> So 51 51 51 would be OK, but not 0 51 51?

I'm basing this off an email Tim Place sent out some while back, 

"So the Chamberverb has a unique id of 49 99 98. Which is ascii for

If you are really observant then you will notice that the last number of

all Pluggo plug-ins is 1, the last number of all Mode plug-ins is 2,

etc. This means that the first number of the uniqueid for Pluggo is 49,

for Mode 50, for Hipno 51, etc. You would be well advised not to use an

ascii code for a digit as the first number of the uniqueid, because we

I might be misinterpreting, but I don't think so. Tim?

Like I've said before: I'm pretty sure plugconfig is voodoo.

>> I think you'll be running afoul of Cyling's own plug-in uniqueids  
>> if you go with 51, Andrew.  51 is Hipno.
>
> I thought Hipno and Cycling's other plugins followed this rule?  
> (from the MSP Reference Manual):
>
> "0 0 0 is reserved and cannot be used. 0 followed by two other  
> numbers is reserved for use by Cycling '74 and its registered plug- 
> in developers."
>
> So 51 51 51 would be OK, but not 0 51 51?

I'm basing this off an email Tim Place sent out some while back,  
either to dev or beta.  The relevant bit:

"So the Chamberverb has a unique id of 49 99 98.  Which is ascii for
'1cb' (backwards this becomes bc1).

If you are really observant then you will notice that the last number of
all Pluggo plug-ins is 1, the last number of all Mode plug-ins is 2,
etc.  This means that the first number of the uniqueid for Pluggo is 49,
for Mode 50, for Hipno 51, etc.  You would be well advised not to use an
ascii code for a digit as the first number of the uniqueid, because we
might use it in the future."

I might be misinterpreting, but I don't think so.  Tim?

do you know how to get it to work with effects? It seems to only do the instruments.

do you know how to get it to work with effects?  It seems to only do the instruments.


crazy, I just got it a couple weeks ago and updated, I guess 3 must have come out after that. Im updating from 2.3 right now and then Ill see if that changes things. Wonderful keyboard right! Works so well with logic and 3 octaves is just enough (2 is too small and 6 is too big, i already have an 88 key for that stuff) fits on my lap and I can work on the couch.. Making all sorts of cool physical modeling patches in max that make use of the aftertouch. Ill upload and link soon. Also made a model of an sh101.

crazy, I just got it a couple weeks ago and updated, I guess 3 must have come out after that.  Im updating from 2.3 right now and then Ill see if that changes things.  Wonderful keyboard right!  Works so well with logic and 3 octaves is just enough (2 is too small and 6 is too big, i already have an 88 key for that stuff) fits on my lap and I can work on the couch.. Making all sorts of cool physical modeling patches in max that make use of the aftertouch.  Ill upload and link soon.  Also made a model of an sh101.

On the topic of the remote 37 sl, Im curious how well your xy pad behaves in max. It seems to work great in all apps but when I use it in max it works great on one axis at a time but if I move on an angle it moves choppy. I called tech support but they were stumped.

On the topic of the remote 37 sl, Im curious how well your xy pad behaves in max.  It seems to work great in all apps but when I use it in max it works great on one axis at a time but if I move on an angle it moves choppy.  I called tech support but they were stumped.

On Mar 2, 2007, at 9:05 PM, Nicholas C. Raftis III wrote:

> On the topic of the remote 37 sl, Im curious how well your xy pad 

> behaves in max. It seems to work great in all apps but when I use 

> it in max it works great on one axis at a time but if I move on an 

> angle it moves choppy. I called tech support but they were stumped.

> -=ili!ili=- www.Axiom-Crux.net -=ili!ili=-

>
> On the topic of the remote 37 sl, Im curious how well your xy pad  
> behaves in max.  It seems to work great in all apps but when I use  
> it in max it works great on one axis at a time but if I move on an  
> angle it moves choppy.  I called tech support but they were stumped.
>
> Thanks :D
> --
> -=ili!ili=-  www.Axiom-Crux.net  -=ili!ili=-


anyone using novation automap controller?