joelsquare

I did a search here, and I know it's been said a dozen times... so I won't mention how badly there needs to be a 'setcolumn' command. Ahem...

Before I reinvent the wheel trying to accomplish this... has anyone made a patch that does that effectively? I need an easy way to take the data I've gathered using GETCOLUMN, and to put it back into the Matrixctl...

I did a search here, and I know it's been said a dozen times... so I won't mention how badly there needs to be a 'setcolumn' command.  Ahem...

Before I reinvent the wheel trying to accomplish this... has anyone made a patch that does that effectively?  I need an easy way to take the data I've gathered using GETCOLUMN, and to put it back into the Matrixctl...

matrixctl-column-set-short-cuts

> I did a search here, and I know it's been said a dozen times... so I

> won't mention how badly there needs to be a 'setcolumn' command.

maybe it didn't happen because its too simple ?

> Before I reinvent the wheel trying to accomplish this... has anyone

> made a patch that does that effectively? I need an easy way to take

> the data I've gathered using GETCOLUMN, and to put it back into the

I just reinvented the wheel, which took less time than writing this 

Still, if you have changing sizes of matrixctrl, a set collumn/setrow 

joelsquare wrote:
> I did a search here, and I know it's been said a dozen times... so I
> won't mention how badly there needs to be a 'setcolumn' command.
> Ahem...

> Before I reinvent the wheel trying to accomplish this... has anyone
> made a patch that does that effectively?  I need an easy way to take
> the data I've gathered using GETCOLUMN, and to put it back into the
> Matrixctl...

I just reinvented the wheel, which took less time than writing this 
mail... ;-)

Still, if you have changing sizes of matrixctrl, a set collumn/setrow 
command could still be helpfull...

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


What's needed so much more than that is for matrix~ itself to accept 

the "setcolumn" and "setrow" messages. Matrixctrl is good for routing 

type situations, but it's not well-suited to open-ended gain 

situations. "Setcolumn" and "setrow" would allow multislider to work 

I have a couple of abstractions that do this (PM.MatrixSetOutlet and 

PM.MatrixSetInlet); e-mail me off-list if interested. Also, I've got 

a version of the "function" object (the graphical envelope tool) that 

works with matrix~, if anyone's interested. (so you can have envelopes 

What's needed so much more than that is for matrix~ itself to accept 
the "setcolumn" and "setrow" messages.  Matrixctrl is good for routing 
type situations, but it's not well-suited to open-ended gain 
situations.  "Setcolumn" and "setrow" would allow multislider to work 
directly with matrix~.

Inevitable plug:
I have a couple of abstractions that do this (PM.MatrixSetOutlet and 
PM.MatrixSetInlet); e-mail me off-list if interested.    Also, I've got 
a version of the "function" object (the graphical envelope tool) that 
works with matrix~, if anyone's interested. (so you can have envelopes 
on individual matrix~ connections...)

I am, send it on list, 'cause I guess I am not the only one....

There are a lot of "common" problems you seem to have a bag of solutions 

for. Even if I have as well solutions, I am always interested in how 

others solve the same problem. Sometimes my solutions are suboptimal... ;-)

The Idea to putting individual envelopes on matrix points is an 

interesting concept for a lot of applications, especially additive 

There are a lot of "common" problems you seem to have a bag of solutions 
for. Even if I have as well solutions, I am always interested in how 
others solve the same problem. Sometimes my solutions are suboptimal... ;-)

The Idea to putting individual envelopes on matrix points is an 
interesting concept for a lot of applications, especially additive 
synthesis...

I'll see if I can modify that to do what I need it to do.

I'm struggling to find a way to save the state of a large matrix - 64 X 128 - SO I've created a small patch that reports and saves to a COLL object, but I've been struggling to get the info back into the matrix.

Matrixctl Column Set Short Cuts