It isn't unstable with the update display option on, it just hesitates ever so slightly, when changing presets.
I suspect the hesitation is caused by the Patcher itself, as it updates the UI. That's why I have a suspicion that the hesitation won't happen, when the Patcher is taken out of the equation.
I haven't tried running the patch without the Patcher, to see if the same thing happens.
I will add a dial to change presets, map it to a CC, and try that.
a|x
Incidentally, where did you find the code to update the sequencer displays?
Is it from one of the Factory objects?
a|x
I had the idea myself but couldnt get it working so sirsicksik told me to look in his supercool sss/filter/paraEQ, to find out how to write the parameters to positions in the array. Very clever object... It took me a little while getting it working, but again, i never really got it working, as you saw...
But one issue with having many presets in one table is saving the individual presets inside the table. Basically most table/write objects overwrites the whole table, so if you have written 3 presets to the table and you want to write 3 more to the same table you cannot do that.... BUT there is a way... The table/write 8 (WITH GREEN INLET) can easily write to only parts of the table. Which means that you would be able to save one preset(4 parameters to the table array{0,1,2,3} and then later on when you want to write the next preset, you write it to {4,5,6,7}...... next preset to {8,9,10,11}... I have made a set up somewhere that does this. If you could use it, I could try to dig it out?
But I dunno how that would work with your system. Are going to test yours now
I see. I have a feeling there's no 'official' way to update the values of parameters from inside an object, so this method may not reliably work in the future.
My table object only writes to the section of the table where the currently-active preset is stored, so you can update any preset at any time. When an update is made, the whole table is automatically saved to SD card. I don't see that as a problem, though, since the object always reflects the values of the whole table, on the SD card.
You can change the value in the string constant object at the top to save a different table, if you want, or disconnect the trigger to the table save object and connect it to a momentary button, and only save the table to SD card when you want to.
a|x
Ok so are testing it now. Seems stable with the preset loading. First preset is always present. But when I dial in the next preset and go unlive and live again, the next preset is lost.
After testing a little bit I found that if i create for example preset 4 and push the update display 2 times( so it is on again) and STAY on preset 4, go unlive and live again the preset is not saved. Actually previously saved preset to that slot will be lost when going live again. It just shows a blank lane... BUT if I go back to preset 1 BEFORE going unlive ALL presets WILL work when going live again..
To sum it up; if you have selected a specific preset when going unlive and live again, the preset will be lost. BUT if you remember to go to preset one before going unlive all presets will be there Does this make sense?
After alittl bit of testing, it seems like if I have made preset 4 and STAY on preset 4, go unlive and live again, preset 4 will be lost. Nothing happens when pushing the update display button..
BUT.... If I go to preset 1 BEFORE going unlive and live again... ALL presets will be there when going live again. This happens even if I disconnects the sequencer from the save object and only connect a button to it.
Can you make anything of that?
Beside that... This is SUPER cool... Really.... This makes track progression a bliss in Axoloti and opens up for serious complex sequences with just a mouse click.. Hell, yuo could even just connect a logic counter and use that to change presets automatically as the track progresses for full automated track.....
Was also just wondering if more than 16 presets is wanted, 32 for example, I could just double the table size, right? instead 32X4 = 128 samples table?
EDIT: the issue mentioned above with presets being deleted only happens sometimes. I tried taking the presets selector OUT of the sequencer object and instead of the radio buttons I used a ctrl/i....
But anyway, once the sequences are saved correctly and you go unlive and live again they work and recall correctly. I guess one solution is just having a patch for writting sequences in and the just use them in patches you need it in.