i notice the gate object maxes out at 100, but i want to make a 64th note sequencer with 16 beats per bar, which makes it require 256 gates for certain things ive included in the sequencer. is there a way to change this, or easy way around it?
maybe a clever combination of 3 [sel] and 3 gate objects? possibly with some re-mapping of the values if it requires it
edit: as in, select numbers under 100, select numbers between 100 and 200 and select numbers over 200. then pass to gates. could use [if then] i guess, might be easier
unless theres a much more elegant way to do this, something audio rate would probably be a good idea…
if you use [route] you can split things up in sets of 16, 64, whatever you want. Just use [prepend 1] [prepend 2] etc. for each index, it acts very similarly to [gate] in this regard.
You could also have different sets of notes go to different gates, so in banks of 64, etc.
This sounds much for a different approach in thinking about solutions of the problem.
I would never even start thinking about how to connect such a huge gate, I’d rather think about how to split my solution into smaller parts…
You can also think about alternatives to gate. There are plenty and as you talk about a sequencer, what do you send through the gate? If its just bangs, take a select object for example.
Creativity starts when you allow trashing old concepts because they don’t work anymore…
Other objects to look at: router, poly~, route, funnel & spray…
I would be fine if gate maxed out at 16 actually…;-)
a gate with 256 outputs will have 256 outlets .. which is
not really perfect for maxmsp.
i would say, IF you really want to use a gate, then use a
dynamic [forward] and 256 static [receive]s to biuld such
a big gate..
Log in to reply
C74 IN YOUR INBOX
C74 RSS Feed | © Copyright Cycling '74 | Terms & Conditions
Let us tell you about notable Max projects, obscure facts, and creative media artists of all kinds.