wednesdayayay's Recent Posts
i understand that the external controller jacks will be a user mod... for my interests i would love to see an expression pedal and something like the pots linked below.
http://shop.electrotap.com/products/ten-turn-pot
i can imagine a couple of these (or this http://radionics.rs-online.com/web/p/products/6917705/ ) would be pretty slick for the main oscillators in aalto
it looks like a nice space. I am quite excited to see this project come to life
monome app based on ciat-lonbarde's Cocolase with soundplane mod ideas
here is a link to the topic, the app itself is made with max 6 (i didn't have anything to do with making it) http://post.monome.org/comments.php?DiscussionID=13731&page=1#Item_13
i was thinking wouldn't it be wonderful to still use the monome as and indicator of connections made and a portion of the soundplane to act as body contacts, but to take it a step further then the amount of pressure (either summed and averaged or from only one of the presses) would change how much the speed or playhead movement are effected.
on the other han a simpler mod might be to use a smaller bit of soundplane to act the same way the monome does but instead of acting like body contacts that had to both be pressed at the same time you would just press a single button and the pressure would then only change how much modulation was applied to that parameter
here is to the hopes of a full community of people who are willing to share applications patches and the like. I am by no means an amazing programmer but i can usually get to where i want to be with an idea in max/msp (just upgraded to 6) or PD. I will certainly be more than willing to share anything soundplane related I make or mod.
in fact i think a soundplane application idea thread is in order....but there doesn't seem to be much in the way of activity around here.
paul
Although it would be up to the user to figure it out I think being able to define an area of the sound plane as a rotary encoder would be most slick.
still exploring this wonderful combination
but i have a question about what the params seq_wave and seq_local do as far as i can see they do nothing to the gui
once things are at a more useable stage i would be more than happy to post the patch
ok at least with vst~ it is pretty easy to adress aalto in max
you can use the param number or param names.
get the param names by sending [params] message to [vst~] and printing/reading the max window
then use a combination of this information [$1) and [prepend "param name here"] sent right to [vst~] this will let you directly access aalto
it should be pretty easy to make a step pulse on/off and step sequencer randomizer, yay.
edit: [bucket 16] produces some interesting effects on the sequencer values when connected over all 16
edit2: here is an early version of what i was talking about next for the seq steps randomizer
http://pastebin.com/umPryMCB
i think this sounds good although i would personally want both the step sequences steps and sequencer values to have their own random buttons. maybe they could be addressable
would you want other sources of modulation to act as gates if they reached a certain point? this would be pretty awesome, also a threshold (possibly even a knob where the minimum and maximum can be set knob and the minimum would act as a second trigger) knob would be nice maybe.