joelsquare

SO sorry to bring this up yet again, BUT I'm still hoping that someone can help a brother out...

OK... mega big patch - which has within it 8 matrixctrl objects, each of which is 128 X 64.

This is the final stumbling block on a patch that has taken me months. HOW THE HECK can I save matrixctl states.

The pattrstor won't save info from matrixctl object that are that large.

Preset objects DO save it, but are so flakey, I've never seen them able to recall data prperly, after writing and reloading. Most recently, I've used this method, and it works fine, until I save, quit, and reload, then... nothing. The preset object seems to have presets, but they don't do anything.

I'm desperate here ... this patch is awesome, but unless I can save, it's all for naught...

Could there be anything, anything anything I've over looked?

This is the final stumbling block on a patch that has taken me months.  HOW THE HECK can I save matrixctl states.

Preset objects DO save it, but are so flakey, I've never seen them able to recall data prperly, after writing and reloading.  Most recently, I've used this method, and it works fine, until I save, quit, and reload, then... nothing.  The preset object seems to have presets, but they don't do anything.

matrix-saving

if you have jitter: just save them as jitter matrices.

if you have jitter: just save them as jitter matrices.
else: lots and lots of colls.


On 19 Jun 2006, at 21:35, joelsquare wrote:

> This is the final stumbling block on a patch that has taken me 

> months. HOW THE HECK can I save matrixctl states.

If pattr and presets don't do it: how about iterating the cell values 

(Sorry if that's been suggested before; I've not been paying too much 

nick rothwell -- composition, systems, performance -- 

> This is the final stumbling block on a patch that has taken me  
> months.  HOW THE HECK can I save matrixctl states.

If pattr and presets don't do it: how about iterating the cell values  
to/from a coll?

(Sorry if that's been suggested before; I've not been paying too much  
attention to this thread.)

   nick rothwell -- composition, systems, performance -- http:// 
www.cassiel.com


what if you save it as an actual jitter binary matrix, and use some 

you could do a jit.matrix 1 char 128x64 and store the states with 

what if you save it as an actual jitter binary matrix, and use some  
javascript to iterate through the cells?

you could do a jit.matrix 1 char 128x64 and store the states with  
setcell and recall with getcell maybe?

I don't have Jitter, and for now, I can't justify buying it for one object.

There's no way to just use that one object, is there?

I'm really hoping - naive, perhaps - for a quick solution, akin to PRESET or PATTRSTORAGE. Mostly because there are so many layers to this patch...

I did think about using COLL, but I'm confused as to the most ergonomic way to use it in this case. Again, this is where a 'setcolumn' command would rock my world. Any thoughts as to the best way to convert Matrix settings into COLL-able data, and back again?

I'm really hoping - naive, perhaps - for a quick solution, akin to PRESET or PATTRSTORAGE.  Mostly because there are so many layers to this patch...

I did think about using COLL, but I'm confused as to the most ergonomic way to use it in this case.  Again, this is where a 'setcolumn' command would rock my world.  Any thoughts as to the best way to convert Matrix settings into COLL-able data, and back again?

You can also write a javascript to do the same thing as a coll would

You can also write a javascript to do the same thing as a coll would
but has more intelligence.

It might be worth checking to see if Nick (Rothwell) 's registry 

objects will deal with datasets that large.

It might be worth checking to see if Nick (Rothwell) 's registry  
objects will deal with datasets that large.
Nick?

On 19 Jun 2006, at 22:18, David Stevens wrote:

> It might be worth checking to see if Nick (Rothwell) 's registry 

> objects will deal with datasets that large.

I did think about that - I suspect my code has the same list length 

limitations as other externals (255 atoms?) - but if a solution using 

'coll' looks like working at all, then registry would probably work 

as well - it's implemented against the same API - and might be more 

convenient. (Registry is OS X only, though.)

On the other hand: you could always (*ahem*) use an SQL database:

http://www.loadbang.net/space/Software/net.loadbang-SQL

> It might be worth checking to see if Nick (Rothwell) 's registry  
> objects will deal with datasets that large.

I did think about that - I suspect my code has the same list length  
limitations as other externals (255 atoms?) - but if a solution using  
'coll' looks like working at all, then registry would probably work  
as well - it's implemented against the same API - and might be more  
convenient. (Registry is OS X only, though.)

	http://www.loadbang.net/space/Software/net.loadbang-SQL

If you use long lists , thinks about this

    (   )
  ~ O ~	www.kineticsoundsystem.com
    (   )		

_________________________________________

> Preset objects DO save it, but are so flakey, I've never seen them

> able to recall data prperly, after writing and reloading. Most

> recently, I've used this method, and it works fine, until I save,

> quit, and reload, then... nothing. The preset object seems to have

You should connect the matrixctrl's with the left outlet of preset, that 

will asure you that the content is not scrumbled. As each time you add 

UI elements, the order of preset might be displaced. (I once made a 

little abstarction (still in St.ools) which could help out there, but in 

your case, just save only the matrixctl states and nothing else...)

joelsquare wrote:
> Preset objects DO save it, but are so flakey, I've never seen them
> able to recall data prperly, after writing and reloading.  Most
> recently, I've used this method, and it works fine, until I save,
> quit, and reload, then... nothing.  The preset object seems to have
> presets, but they don't do anything.

You should connect the matrixctrl's with the left outlet of preset, that 
will asure you that the content is not scrumbled. As each time you add 
UI elements, the order of preset might be displaced. (I once made a 
little abstarction (still in St.ools) which could help out there, but in 
your case, just save only the matrixctl states and nothing else...)

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


Thank you so much for contributing... this has been the final headache in a large project. SOME headaches, I like - I love to solve problems, but this headache was getting too big!

I will check some of these solutions out! I really appreciate it. Yacine - I had played with something like this, but I think my MAX/MSP knowledge limited me a bit... your patch looks good, and might just be the solution. How much do I owe you?!

Thank you so much for contributing... this has been the final headache in a large project.  SOME headaches, I like - I love to solve problems, but this headache was getting too big!

I will check some of these solutions out!  I really appreciate it.  Yacine - I had played with something like this, but I think my MAX/MSP knowledge limited me a bit... your patch looks good, and might just be the solution.  How much do I owe you?!

'hope your headaches will leave you for a while!

a bear will fine when we meet someday...
'hope your headaches will leave you for a while!

Matrix Saving