Hi,

I have a Step sequencer I made using toggle boxes. I store the presets in text files. I actually like this system, but when I switch presets there is a little glitch often times.

Most of the time I use my step sequencer on a Rpi 3, so cpu is a concern. I also use my step sequencer to store drum beats, where many voices might have a hit in the same beat, like a hi hat an a kick drum, or a hi hat and a snare drum.

It has been recommended to me to make a sequencer using an array, and storing presets in tables. But I can't seem to figure out how you can have multiple values in a column in an array or table. Seems like you can only have a monophonic type sequence.

I also can't figure out how to quantize an array or table to a integers. if one percussion instrument is value 1 an another is 2 I really don't want values like 1.5 or 1.2. So how do I quantize values?

If any one has thoughts on this please let me know. Should I be looking at other methods instead of tables and arrays? Or if anyone has an example patch I can look at please post a link.

Thank You.

@seb-harmonik.ar said:

btw, another option is to use the tglgrid external https://github.com/nicklan/tglgrid. You'd have to have a route after the [tglgrid] that routes depending on if you're saving or playing.

That looks interesting, is there a binary available for OSX?
I can't find it on Github or Deken.

tglgrid.zip @dom1817

@nicnut There was an object [iem_pbank_csv] that I used all the time for presets.
It stores and recalls a set number of lines of a set length... and can write them out to files that can be read back in.
So much like the new [text] object.
So I made, following fairly closely an object [pbank]

Moonlib's shared list [slist] was also useful for such things.
Because one can only have one array defined for a specific name I had to have an [slist-master] and an [slist] to use elsewhere.
The original was for symbols.... and I can't remember if mine will work for floats......
Both made using [text].......... stuff.zip
The [iem_pbank_csv-help] is from the original but should apply to [pbank]
David.

@seb-harmonik.ar
THANKS

thanks everyone for your comments. i've sort of been preoccupied by armageddon happening around me here in LA this week. I'm getting back into this sequencer now. @seb-harmonik-ar this 64 step sequencer is beautiful. Im going to try and wrap my head around this more before I comment or ask more questions. Thanks for posting this.

I looked at 64seq patch which is really cool. It looks like is saves the sequencing presets to text files. I realize that there are also arrays involved inside each row.

So, in this method will there still be glitches or not? I was thinking I needed a system that didn't use text files at all, and only saved every preset to a bunch of stored message boxes or arrays. I guess it's possible if the toggle boxes are reading from tables or arrays the glitchyness might not be there. Is that they case or should i continue to try and develop something that doesn't use text files at all?

Thanks, Nick

@nicnut storing the patterns in memory will probably take more ram but definitely less load time when changing patterns
I guess the best way is to use [array define -k] if you don't need to store an infinite # of possible patterns. Here's a version with arrays for up to 64 patterns (64 patterns X 64 steps = 4096 steps for each [array define])

64seq-arrays.zip

In this version, every time you click a toggle it will save that value in the array (so there is no "reloading the current pattern" and all edits are destructive, in order to do reloadable current patterns you might want to have a current-pattern array or position in the global array that you copy the current pattern into, so when you want to reload the pattern you could just re-copy it)

@seb-harmonik.ar ok this looks good. I'm gonna examine this one and let you know what I come up with. Thank you so much for the input and help!

Hey @seb-harmonik.ar and anyone else following this thread.
Just wanted to update you. I found a way way easier way to have a drum sequencer, store beat patterns, etc.

In the else library there is an object called drum.seq. Wow. it just made my life a lot easier. I think its pretty amazing does what I've been trying to figure out here with barely any objects and no text files.

Thank you everyone for the help with this issue!