BrainModular

I have an audio matrix patch in one rack that I need to send current values for over a data buss, store these values in a preset, and then when the preset is recalled have the values that were stored in the preset manager sent back to the audio matrix. Seems simple enough, right?
Problem is, is that no matter what combination of modules and approaches I try, I get inconsistent accuracy for the stored values being sent from a get/set array to the audio matrix array inlet. Sometimes I need to toggle presets back and forth several times to get the values updating properly, sometimes the data sent to the audio matrix seems to get mixed between two or more presets. I'm thinking I may be encountering a bug of some sort, but maybe there is something I'm missing?

Here is one of many attempts. Yes this patch has a stop and pass sequentially in the same wire, just trying everything I can think of to stop inconsistent values being sent to the matrix. Even the most logical approaches don't seem to work right but I would be very happy if someone could prove me wrong. I have already spent far too much time trying to work out a solution for this. (btw, no problem directly sending get/set array values stored in a preset to the audio matrix so this rules out issues with actually storing and recalling the values)


Here is one that seems a lot simpler, that should also work?

not sure to understand how you use the audio matrix here..seems to be a very specific use
Any chance for a simple example workspace to illustrate your needs...?

ok.. it's 2am here and I'm tired and can't seem to get my example working right but can try again in the morning. In the meantime, I'll upload the example workspace, general idea is that in rack 1, audio matrix routings are made, rack 2 stores and recalls the routings. It's a lot deeper than that and believe it or not it all works, just this one riddle still eludes me..

http://www.sensomusic.com/forums/upload ... preset.wkp

2 things i first see:
the list button module which drive the preset manager is set to saved in preset, this can create confusion.
why do you need the preset manager in another rack..? the process will be more simpler if it you put him in rack 1 and drive it eventually by bus from rack 2, no...?

haha, I can't sleep.. yes the list box is set to saved in preset, but the parent patch is not, that setting should be inherited by all modules within the sub patch, right, except unless explicitly specified within another sub patch within the sub patch that has another preset manager.. ?
About the preset manager in rack 2, I have reasons. It's hard to explain but just to say, rack 2 ultimately has 16 patches x 16 presets and I want to be able to load or unload each of these 16 patches at will with different versions and mix settings without having any dependencies from rack 1. rack 1 is intended only for "slave" routing purposes from my audio interface.
I'm not so worried about why the example I uploaded isn't working quite right as I am about how to properly relay data from the audio matrixes to the get/set array to store as presets within the preset manager and send back to the audio routing matrix via preset recall without weird feedback issues, which is what seems to be happening.

Ok.. well my whole reasoning for keeping the matrix audio routing patch separate and using two copies sending audio to 32 main patches (16+16 on two racks) in my workspace was to keep resource use to a minimum, but the patch is less hungry than I thought, 32 copies uses only 225MB as shown in the task manager. What's another 225 MB when my workspace template is already using 2.6GB before any VST's or presets :rolleyes: . Gotta love 64 bit!

Wish I could have sorted out this problem, seems it should be simple enough but at this point it is probably faster to repatch my workspace with the routing Matrixes put in the main patches. Thanks for the help tho. Apparently I'm taking this setup out for a live performance next weekend and I have till Tuesday eve to prep! hahahaaa... see how that goes. Might have bit off a bit more than I can chew

not sure to understood all of your hopes but i tried this :
in this example
You can easily store matrix settings, preview there and load on by pressing GET button.
Hope it can help you

carefull. i noticed a bug on the matrix. Only the cell activated by the mouse are send by the cell out.
It mean if you recall a mem and modify it only the cells modifiy are stored. It's a problem. Need to speak about senso team.

Thanks! I will try that method!

ok tell me