how would you sequence the preset object?
Hey,
first post here :)
So I've got a patcher with a preset object that I'd like to sequence so I can program at what specific time I want to recall a specific preset. I have fun using a random object so it randomly switches presets but I wish I had more control.
I know I have to send it an int, which is easy, but what would be a good way to write a sequence of int (following the tempo of my patch)?
I am thinking of using a matrixcontrol object using dial mode but it seems like there is a simpler way to do this?
Thanks a lot for your help.
i would use horizontal sliders which display the name of the preset at their side.
yes, you have to build that naming scheme yourself. its center would probably be an umenu object. ;)
that'd work but it's still a non programmable option, isn't it? I am looking for a way to send int in advance, like 1 for x amount of time, then a 7 for x amount of time, then a 4 etc etc. Could be "x amount of time" or with a counter object, something like "when the count is 6 send a 4 to preset, then when the count is 12 send a 3 to preset"...that kind of things...How do I do that?
This sounds like a good time to use [coll]. You can store each preset at the time it should be called in ms, followed by the preset number. Inside [coll] might look like:
%time-as-address, preset-number%
0, 1;
3000, 7;
3500, 2;
...
adding to what Holland wrote above, i did something similar recently, except using [coll]'s number index counted out by a counter, and within [coll] used scripting messages sent to [thispatcher](this way i could script a number box(attached to [pattrstorage], but you could do the same with the [preset] object, anyways)... with scripting name "pre" for the preset number which created 'global' changes to the patch, but also script other remote connections by scripting-name elsewhere for more specific changes to other parameters after the global preset changes)... so inside my 'coll' there was a sequencer script(sequenced out by coll's index-numbers from a [counter] iterated by [metro]) that looked like this:
1, script send pre 1;
22, script send HolSeqRan 0;
24, script send carrfreq 32.7;
25, script send HolSeqRan 1;
28, script send hatsoff 1;
41, script send HolSeqRan 0;
42, script send carrfreq 28.;
43, script send HolSeqRan 1;
44, script send hatsoff 0;
45, script send HolSeqRan 0;
46, script carrfreq 25.;
47, script send HolSeqRan 1;
49, script send pre 2;.........
using [coll] the way Holland suggested allows you to write a sequencer script all in one local list
Thanks guys for your help, sounds very interesting, probably a bit above my skill level at this point...care to share your patch Raja? The counter approach sounds great because I usually use tempo units in my patches (rather than ms).
Anyway thanks again for this, gives me a lot of new perspectives.
i was pretty sure you asked for a suggestion how to organize and layout things. i keep misreading things when i didnt had enough sleep.
music sequencers... are usually based on metro and counter, that is true.
but if you want to schedule things more like in a "theater" or "broadcast station" manner you might also want to look into the [timeline] object.
or, if time does not have to be super exact, you could start from a [clock] object, let it run infinitely and pick out the times you want to trigger something.
care to share your patch Raja?
apologies, i have to think on this(came up with a new synth engine that the sequencer drives, and want to share the synth engine secrets later once i've already put out some music with it...), i'll try to whittle it down to just the sequencer portion and share here within a month - if you have an impending need, let me know perhaps i can find some time within the next 2 weekends, otherwise, i've favorited this thread to remind me to come back to it asap.
also just wanted to mention: the [detonate] object helpfile shows some similar sequencing techniques to what you mention you wanted(within the [p detonate_example] subpatcher there), just to add another technique you could try.
it's ok, no problem, I have plenty of advice in here so I'll try this and see what works. For instance I had never heard of the [detonate] object before, seems like something I could use a lot! Thanks!
hey again, finally got around to creating something simpler to show you what i meant:
(watch your volume level when you first start it up)
i didn't comment much, but hopefully you'll understand all the ideas(see 'thispatcher' helpfile for more messaging-by-scriptingname details)... feel free to ask about anything unclear, though, and i'll do my best to explain. hope it helps 🍻
Thanks Raja, just seeing this now, been busy, but I'll study this patch now :) Thans again, really appreciated!
first reaction : it's awesome! In addition to a nice solution to my initial problem you just offered me a nice sequencable e FM synth :)