Steven Miller

I've never used the MaxMSP scripting features, and am in the process 

of diving in to the relevant tutorials, etc. So far, so good.

At this point, I can't tell if there's a command to script changes of 

arguments to existing objects. For instance, if I wanted to change a 

[ctlin a 7 1] to [ctlin a 10 2] or some such, is there a scripting 

command specifically to change arguments. If not, do I have to delete 

the existing object, create a new one with the desired arguments, 

I've never used the MaxMSP scripting features, and am in the process  
of diving in to the relevant tutorials, etc. So far, so good.

At this point, I can't tell if there's a command to script changes of  
arguments to existing objects. For instance, if I wanted to change a  
[ctlin a 7 1] to [ctlin a 10 2] or some such, is there a scripting  
command specifically to change arguments. If not, do I have to delete  
the existing object, create a new one with the desired arguments,  
then reconnect everything?

----
Steven M. Miller
Professor, Contemporary Music Program
College of Santa Fe

Home 
SFIFEM 
Atrium Sound Space 
OVOS 
CMP 

scripting

Quote: smill wrote on Mon, 26 November 2007 11:44

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

> I've never used the MaxMSP scripting features, and am in the process 

> of diving in to the relevant tutorials, etc. So far, so good.

> At this point, I can't tell if there's a command to script changes of 

> arguments to existing objects. For instance, if I wanted to change a 

> [ctlin a 7 1] to [ctlin a 10 2] or some such, is there a scripting 

> command specifically to change arguments. If not, do I have to delete 

> the existing object, create a new one with the desired arguments, 

AFAIK, objects read their arguments at instantiation, only. So, to really change the arguments, you'd have to destroy and replace the object.

That being said, you could use scripting to send a message to your object. If your object was called "foo" then "script send foo set 64" would set it to controller 64, and "script send foo port b" would set it to port b. These messages go to the thispatcher object. Unfortunately, it looks like ctlin won't take a message to change channel.

Quote: smill wrote on Mon, 26 November 2007 11:44
----------------------------------------------------
> Hi all,
>
> I've never used the MaxMSP scripting features, and am in the process  
> of diving in to the relevant tutorials, etc. So far, so good.
>
> At this point, I can't tell if there's a command to script changes of  
> arguments to existing objects. For instance, if I wanted to change a  
> [ctlin a 7 1] to [ctlin a 10 2] or some such, is there a scripting  
> command specifically to change arguments. If not, do I have to delete  
> the existing object, create a new one with the desired arguments,  
> then reconnect everything?
>
>

AFAIK, objects read their arguments at instantiation, only.  So, to really change the arguments, you'd have to destroy and replace the object.

That being said, you could use scripting to send a message to your object.  If your object was called "foo" then "script send foo set 64" would set it to controller 64, and "script send foo port b" would set it to port b.  These messages go to the thispatcher object.  Unfortunately, it looks like ctlin won't take a message to change channel.

> AFAIK, objects read their arguments at instantiation, only. So, to 

> really change the arguments, you'd have to destroy and replace the 

Yes, this makes sense. I was hoping for something more elegant, but 

> Unfortunately, it looks like ctlin won't take a message to change 

The channel setting is precisely the sticking point I'm trying to get 

around. I'm making a patch to be distributed to various folks, and 

want to have them be able to initialize the MIDI settings before 

running the patch by setting their own port, cc# and channel for each 

of 8 [ctlin] objects. The scripted delete, replace, reconnect 

>
>
> AFAIK, objects read their arguments at instantiation, only.  So, to  
> really change the arguments, you'd have to destroy and replace the  
> object.

Yes, this makes sense. I was hoping for something more elegant, but  
it is what it is.

>
>   Unfortunately, it looks like ctlin won't take a message to change  
> channel.

The channel setting is precisely the sticking point I'm trying to get  
around. I'm making a patch to be distributed to various folks, and  
want to have them be able to initialize the MIDI settings before  
running the patch by setting their own port, cc# and channel for each  
of 8 [ctlin] objects. The scripted delete, replace, reconnect  
strategy is what I'm going with for now.

On 26 nov. 07, at 22:36, Steven Miller wrote:

>> Unfortunately, it looks like ctlin won't take a message to change 

> The channel setting is precisely the sticking point I'm trying to 

> get around. I'm making a patch to be distributed to various folks, 

> and want to have them be able to initialize the MIDI settings before 

> running the patch by setting their own port, cc# and channel for 

> each of 8 [ctlin] objects. The scripted delete, replace, reconnect 

> strategy is what I'm going with for now.

By the way, a couple of == and gate do the trick. Is there any 

specific reason why you wanna use scripting for that matter?

>>  Unfortunately, it looks like ctlin won't take a message to change  
>> channel.
>
> The channel setting is precisely the sticking point I'm trying to  
> get around. I'm making a patch to be distributed to various folks,  
> and want to have them be able to initialize the MIDI settings before  
> running the patch by setting their own port, cc# and channel for  
> each of 8 [ctlin] objects. The scripted delete, replace, reconnect  
> strategy is what I'm going with for now.

By the way, a couple of == and gate do the trick. Is there any  
specific reason why you wanna use scripting for that matter?

On Nov 26, 2007, at 2:48 PM, Emmanuel Jourdan wrote:

> By the way, a couple of == and gate do the trick. Is there any 

> specific reason why you wanna use scripting for that matter?

I already did that route, and it works fine. I just thought that if 

there were a simple way to script it, that might be a more elegant 

solution. A good excuse to finally delve into scripting, perhaps.

>
> By the way, a couple of == and gate do the trick. Is there any  
> specific reason why you wanna use scripting for that matter?
>
>

I already did that route, and it works fine. I just thought that if  
there were a simple way to script it, that might be a more elegant  
solution. A good excuse to finally delve into scripting, perhaps.

> the existing object, create a new one with the desired arguments, then 

There is a script replace message. That will replace an old object with 

a new one without the need of reconnecting. Unfortunately you have to 

specify the complete coordinates though...

You can have a look at some of my abhaXions which use this technique, 

freshly updated on c74/share... (look for ctl.in for example...)

Steven Miller schrieb:
> At this point, I can't tell if there's a command to script changes of 
> arguments to existing objects. For instance, if I wanted to change a 
> [ctlin a 7 1] to [ctlin a 10 2] or some such, is there a scripting 
> command specifically to change arguments. If not, do I have to delete 
> the existing object, create a new one with the desired arguments, then 
> reconnect everything?

There is a script replace message. That will replace an old object with 
a new one without the need of reconnecting. Unfortunately you have to 
specify the complete coordinates though...

You can have a look at some of my abhaXions which use this technique, 
freshly updated on c74/share... (look for ctl.in for example...)

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com

Scripting