|
|
|
|
Viewed 790 times. 4 people liked this blog. You can rate it below if you haven't already.
-->
So I got the demo of max 5.. . I've never really used a modular kinda environment before.
Its cool. way cool
Anyhow the reason I got it is to develop an interface between my midi controllers and live. One of the key things in this is oldschool style step sequencing, (like on old modulars etc, with a knob for each parameter of each step)
I've managed to cobble together a 16 step note sequencer, at the moment it has fixed velocity and note length. . . that will change, its just a matter of copy/pasting I guess
Anyhow, I'm guessing its horribly innefficient, and ugly too.. but here it is in all its barely working glory (switch to presentation view...its not so bad haha)
StepFrequencer V.0.0zero.zero.alpha.pro.xtreme....0
link
I'd very much like to hear from people as to how much this could be efficientised. . . at the moment its kind of a mess, includes small delays where I couldnt be bothered figuring out the order of calculation etc etc....
Probably some complex data structures or something are what i need but eh!
One of you can tell me yeah? much easier.
Eventually the plan is to have this as a 64 step sequencer with multiple tracks, 1 or 2 automation sequences for each track, as well as pitch/velo/length - controls will be optimised for either 1 or 2 BCR2000's
*EDIT*
Version 0.0.0.0.1a! (codename stepfrequencer2 ;p)
32 step midi controllable sequencer of pitch, note length & velocity.
link
| |
Comments
05/01/08
+
PM |
QUOTE |
PERMALINK |
REPORT
elronhubbard
im at work right now so i cant check out the patch until i get home. the biggest advice i can offer when building step sequencers where you want to avoid the patch spaghetti is to harness the power of lists, the multislider object, and the coll object
05/01/08
+
PM |
QUOTE |
PERMALINK |
REPORT
packetst0rm
Looks interesting, Can't have a proper look at work but it looks like you have a better understanding of max than me already!
05/01/08
+
PM |
QUOTE |
PERMALINK |
REPORT
cartesia
harness the power of lists, the multislider object, and the coll objec
Heh. . yeah I should probably look into these things!
I did use coll... but not the others
edited: May 01 2008
+
PM |
QUOTE |
PERMALINK |
REPORT
elronhubbard
looks pretty good. like i said i prefer the multislider because you can output a list of integers or floats and not have to connect each patch cord. but for someone who just started out, its great. took me a year of meddling to get my head into max mode.
nukequencer2.maxpat - 0.21MB here's one i made a while ago, and redid in max 5. note: it uses send and recieve objects so you cant really open up more than one instance of it.
edit:
you need this transport.maxpat - 0.00MB to make it run. sorry. forgot. the reason why i have a seperate transport is for syncing several devices.how it works is simply that a midi channel from a sequencer sends out clicks in the form of notes to trigger a steady stream of bangs. you can do interesting rhythmic patterns with the notes as well.
ps: there is plenty of room for improvement to that sequencer patch as well. for instance, i'm trying to think of a way to get rid of the array of gswitches in the "switchrelay" subpatcher. i just need some time to clear my head and think about it. lol.
ps.ps: the numbers to the right of the bottom three sliders are CC destinations.
05/01/08
+
PM |
QUOTE |
PERMALINK |
REPORT
elronhubbard
also the sliders are, in order from top to bottom: fine pitch adjustment (by note, range of 12), coarse pitch adjustment (by octave), velocity, duration, and the three CC multisliders.
sorry, its horibbly undocumented because i didnt expect to share it.
05/01/08
+
PM |
QUOTE |
PERMALINK |
REPORT
cartesia
thanks, Ill ahve a look tonite..
Register / login
|
^
EM411 is Copyright 2001-2008 EM411.com
All rights reserved. | Contact | RSS
|
