https://docs.google.com/open?id=0BxClVgdIxaVLS3pucU9YNjdNTzQ
I have been working on this for a while and it is finally getting to be useable
I have several more things planned that i deleted so I can update later
most importantly a modulation matrix for all the attenuators where you attach the patch cords
also integration of the arduino shield "repatcher" firstly for physically controlling aalto paramters with more precision than midi provides but secondly it will allow me to patch the my soundplanes signals around to different thing be it aalto/ effects/ modulation layouts
in the archive you will find two files one is the touch osc template and one is a max/msp patch
you will have to point max to your aalto vst (not component)
you will have to change the ip/port numbers to match your own
you can use this in presentation mode alone
midi map is built in so when the space bar is pressed and you are hovering over an aalto parameter it can be midi mapped by moving a midi controller
I have added a randomize all sequencer values button in the touch osc template
I have added several encoders to act as fine tuners for the parameter they are nestled within (filter cutoff, delay time, env2 repeat, feedback, pitch, ratio, LFO freq, seq rate) each encoder can easily be set to a more or less coarse tuning. a built in mechanism is planned for the update.
All five volume controls are also easily available to use
i have also added a couple extra sliders and toggles for extra control over the sequencer
in the top pair the slider controls the randomization of all 16 sequencer steps in two different ways which is switched between with the toggle to the right of the slider
the first way the slider works is by randomly cycling through different sequencer step numbers and assigning the current slider value to it
the second way uses the [bucket] object to send the current slider value down the sequencer steps right to left (this can be changed)
the slider under that controls the randomization of all 16 sequencer steps in two different ways
the first randomizes every sequencer step upon each movement the value of the slider affects the probability of each step being on/off
the second way is just the same as the first except it only randomizes the steps every 16 values entered into the slider
it is late and I am tired but I wanted to try to get this posted tonight.
hope you enjoy
I haven't had a chance to try this yet, but I am very excited to!
some things I am looking to change/update
change the value the encoder adds per step (or more to the point make it so it can easily be scaled up and down according to the end user needs)
in touch osc make individual module sections or smaller groupings more suited for an iphone in the case anyone has one of those
fix the smoothing mode for the seq val rand slider right now it only seems to show the value after it has stopped moving and slows down in a way that i must have goofed up somewhere so unless you enable it in the max msp patch you can't access it yet.
add in the chaos controls...
sometimes I accidentally hit a volume knob when I was wanting to use the encoder...But I also like where the controls are currently. So perhaps a mixing section as opposed to how I have it laid out now
Try to not change the "offest" knob to reflect it's actual name
"finnish" soundplane layout based on this http://cycling74.com/toolbox/xy-markov-player/ and incorporate the z plane as well...put 8 to 10 or them together...
take the xyz markov player and make small groupings of controls like [timbre, shape, offset] or [seq rate, seq val rand, and seq step rand] or [del freq, feedback, input/drive] then play
add modulation matrix for the attenuators that the xyz markov player would also be able to play with
fun playing tip:
try setting the step amount to 1 and playing with the seq val rand slider
or alternatively try just pressing the rand button which randomizes all values but right now being that I am no programmer, more like a tinkerer it randomizes the values twice (once upon the initial press and once for when it is let go) and while im sure there is an easy fix for this "problem" you can use it to get some neat rhythms
also i am currently uploading a video of me messing around with this
it isn't so much a tutorial or demo as just playing around with one hand/finger
This looks very nice. As I don't use a TouchOsc my question is: Are the parameters asignable to a normal midi controller? and the second question: is it possible to open the MAX patch in Max for Live to use it in Ableton?
Thanks for sharing your work!
Cheers!
Loopspool