No cant help by program it, dont know how to built a drum-sequencer on Mios… in max msp yes… some counter, some arrays, some matrix, some sync (well this would be the hardest…) some storrage some interface (touchsreen) and its done
I also need a drumsequencer in the next time, but it would be built and programmed very pure-the ui will be 10-15" multitouch with OSC-Program on it, the hardware simply a mios core with ethernet, because my skills are not geek - and i need to be in sync i cant risk to overload such fundamental with to much stuff-that dont have much to do with something like a Trigger-Generator… these all additional features will be done by a other Device that is switched after the Sequencer, the Trigger-Matrix.
- so if you find some, or get knowledge, write all in a tread, maybe i can learn from it :shifty:
anyway here are some tips, from my grooveboxes and programs that i have programmed since 2008, the following features are for me a must, they do so much, and i do so less, so good for live :
good live features that i have programmed in all my stepsequencers… and finally also in a midibox based project (trigger-matrix - tekkstar:
Encoder for Velocity controller - for me: Velocity offset: in middle position=orginal velocity, turn left, all notes will be lowered by an amount, turn right all notes will be encreased by a amount (all are loud)
Random Trigger Kill Encoder/Poti: Change the ammount of “how possible is it that a velocity comes out of your sequencer” — the best feature ever - make breaks by turning a Knob 90°!
2 or 3 or 4 Velocity Kill-Buttons: That Kill a range of Velocity – exactly, it kills notes that are below Velo64, the other Velo90 the other velo127 >>> thin out your Drumset >>> straightn it!
Velocity Invert button: Loud will be not so loud, and not so loud very loud… (all these Velocity Things are differ by turning your velocity Offset Encoder— very much differencys…)
OverRoll: route all Sequencer-output data to all DOUT-Trigger-Modules
Individual Roll: Activate the roll on one Track, easiest solution: Overroll, better selution - the possibility to change what trigger will go to what Trigger output when you press the IndividualRoll-button >>> best to setup with a 8x8SID-Style Matrix, or over OSC with some tablet, or even with your Step-Sequencer Input (if you have enough rous) >>> the cheapest solution is maybe really a Touchdisplay with an microComputer with an OSC-touchscreen-Software on it…
Locost “See all Tracks”-Feature: Realised by a 8x16 LED Matrix over your Buttons (See Snare BD and all others…) – a matrix is good for really much things like: deactivating some tracks from be-ing RandomKilled, or Overrolled, or invert… (Kick drum e.g.!) also very good to Route the different tracks of your sequncer to different Trigger outputs…, and so on… i programmed a own app for this as i said the trigger matrix it is made to midipluged in after a drumsequencer… my pure programm-knowledge bring me to the point that i need a own lpc17 only for the trigger-matrix and all the features i explained…
If you connect in Additon/or future some Midi Synths, maybe its a good idea to implement some bankchange send…(just to dont forget when you definie the Patch-structure on your SD-Card…)
