cbannis

I have a pet project/patch that is getting way too complicated. In the past I have had a lot of trouble applying oop principles in Max... So I have been avoiding the issue.

Wondering if anyone has an example of an effective framework for a multi-track "track as object" approach. I would like to be able to instantiate a track/buffer and a few local variables. An efficient aux-send would be an nice as well.

I have a pet project/patch that is getting way too complicated.  In the past I have had a lot of trouble applying oop principles in Max...  So I have been avoiding the issue.

Wondering if anyone has an example of an effective framework for a multi-track "track as object" approach.  I would like to be able to instantiate a track/buffer and a few local variables.  An efficient aux-send would be an nice as well.  

muli-track-example

> Wondering if anyone has an example of an effective framework for a

> multi-track "track as object" approach. I would like to be able to

> instantiate a track/buffer and a few local variables. An efficient

I place a track subpatch into a bpatcher, I give it a name like 

"Track[1]" and some parameters. Inside the track subpatcher I have a 

javascript that retrieves the number of the patcher and adjusts my Midi 

controls automatically. That way I just duplicate the track and 

The same applies for mixing consoles. And now I even have a way to get a 

central UI for accessing all mixer channels from a single point...

All that is done with pattr objects for communication. The pattr objects 

create a defined name space, which eases the communication a lot...

I am not sure if the "mynamber" abhaXion is already in the published 

version of my St.ools collection, if not, let me know, I'll put up a new 

version soon... (Its growing day by day... ;-)

cbannis schrieb:
> Wondering if anyone has an example of an effective framework for a
> multi-track "track as object" approach.  I would like to be able to
> instantiate a track/buffer and a few local variables.  An efficient
> aux-send would be an nice as well.

I place a track subpatch into a bpatcher, I give it a name like 
"Track[1]" and some parameters. Inside the track subpatcher I have a 
javascript that retrieves the number of the patcher and adjusts my Midi 
controls automatically. That way I just duplicate the track and 
everything is set already.
The same applies for mixing consoles. And now I even have a way to get a 
central UI for accessing all mixer channels from a single point...
All that is done with pattr objects for communication. The pattr objects 
create a defined name space, which eases the communication a lot...

I am not sure if the "mynamber" abhaXion is already in the published 
version of my St.ools collection, if not, let me know, I'll put up a new 
version soon... (Its growing day by day... ;-)

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


I am now scheming a few great strategies to reduce the redundancy in my UI as well! It had not even occurred to my to do this before your post. Thanks for that.

I am now scheming a few great strategies to reduce the redundancy in my UI as well!  It had not even occurred to my to do this before your post.  Thanks for that.

Muli-track Example