joelsquare

I'm building a patch that uses the Matrixctrl object to as a step sequencer, but I've found a problem that, and I'm wondering if someone has a solution or workaround.

Using autopattr and pattrstorage, I've found that there is a limit to how big a matrix can be and still store data. Smaller matrixctrl's accurately commuincate with autopattr and pattr storage, but larger ones do not.

Any ideas how I can save matrix states in large matrices? To complicate things, the matix appears IN a bpatcher IN another bpatcher - so, it's 2 levels below sea level, if that makes sense. :)

Using autopattr and pattrstorage, I've found that there is a limit to how big a matrix can be and still store data.  Smaller matrixctrl's accurately commuincate with autopattr and pattr storage, but larger ones do not.

Any ideas how I can save matrix states in large matrices?  To complicate things, the matix appears IN a bpatcher IN another bpatcher - so, it's 2 levels below sea level, if that makes sense. :)

saving-matrix-setups-possible-bug-maxs-or-mine

On Apr 24, 2006, at 12:52 PM, joelsquare wrote:

> Any ideas how I can save matrix states in large matrices?

How large are talking about? I've done 10x64 without a problem.

On Apr 24, 2006, at 12:52 PM, joelsquare wrote:
> Any ideas how I can save matrix states in large matrices?

How large are talking about?  I've done 10x64 without a problem.

-----
Nathan Wolek
nw@nathanwolek.com
http://www.nathanwolek.com


Any size which x3 >= 4094 exceeds the current limit of getbytes, which 

is used to allocate memory for pattr. Hopefully, a future version of Max 

or pattr will address this. For the moment, you can't do anything about 

it without breaking the matrixctrl into separate, smaller objects.

Any size which x3 >= 4094 exceeds the current limit of getbytes, which 
is used to allocate memory for pattr. Hopefully, a future version of Max 
or pattr will address this. For the moment, you can't do anything about 
it without breaking the matrixctrl into separate, smaller objects.

I've found that 48 X 28 works, but 49 X 28 doesn't.

48 X 28 gives a string of data in the 'Client Window' in pattrstorage, while 49 X 28 shows nothing in pattrstorage. BUT 49 X 27 does.

48 X 28 gives a string of data in the 'Client Window' in pattrstorage, while 49 X 28 shows nothing in pattrstorage.  BUT 49 X 27 does.

Any thoughs on a clever workaround that won't require me breaking the matrix up?

I had a stupid thought the other day about saving matrices. You 

might try using a base 62 system and store your binary rows in apha- 

numeric symbols. you can get 29 cells worth from 5 characters. 

I had a stupid thought the other day about saving matrices.  You  
might try using a base 62 system and store your binary rows in apha- 
numeric symbols.   you can get 29 cells worth from 5 characters.      
get row would give binary numbers.

On Apr 24, 2006, at 2:05 PM, matthew aidekman wrote:

The problem with "getrow" is the lack of a "setrow" message. Sure 

you can parse it (which I've done), but it would be so much simpler 

On Apr 24, 2006, at 2:05 PM, matthew aidekman wrote:
> get row would give binary numbers.

The problem with "getrow" is the lack of a "setrow" message.  Sure  
you can parse it (which I've done), but it would be so much simpler  
with the proposed partner message.

i have managed to save large matrix (127*96) info using the good old preset object. it was also buried in a bpatcher. i was using it for sequencing as well

I've managed to do it using the preset object BUT...

My matrix is in a bpatcher, IN another bpatcher, so, I'm not sure if there is a solid way to to presets like that? Do you think?

My matrix is in a bpatcher, IN another bpatcher, so, I'm not sure if there is a solid way to to presets like that?  Do you think?

You can probably rig something up using jitter. May be more clinky

than using preset though. Just a thought...

You can probably rig something up using jitter.  May be more clinky
than using preset though.  Just a thought...

i don't know if you've tried this but, look at the bpatcher inspectors and 'embed patch in parent'. that did the trick for me in any case

Saving Matrix Setups - possible bug (MAX's or mine)