aalto in max msp?
i am running the aalto au in max 6, osx lion.
what message do i need to send [vst~ aaltocomponent] to start up and sync the aaltos host sequencer?
also... does it not accept midi in?
I would try the audiounit~ object with the AU version instead-- it seems to be more stable in Max than the vst.
MIDI is certainly possible-- I'd start from the vst~ or audiounit~ help patch and try to change as little as possible.
I'm not sure if host sync is possible. I haven't been able to spend too much time working with Max/MSP, so hopefully someone else can offer advice here.
So, I took the time to install Max 6 today and here's the state of things:
the vst~ object runs VST and AU plugins, so forget what I said about audiounit~.
the Aalto VST does not hear MIDI events in MSP. The AU version does.
Neither AU nor VST seems to hear the MSP clock for host sync.
So, the AU version should work well overall except for host sync. I'll try to work with the Cycling elves to resolve these issues.
my experience lead to similar findings, except i found the VST to always crash Max 6, whereas the AU is stable. (i am referring to loading the .component and .vst files, not the vst~ object in Max 6)
host sync is not working. internal seq is.
thanks for the report and help. let me know what you learn.
for any curious about the experiments -- i have sent the aalto .component all kinds of messages and transport information in max 6, but have been unable to successfully run aalto sequencer set to host sync.
has anyone experienced success running aalto's host sync (engaged) in versions of max prior to 6?
i will keep experimenting and report back. aalto and max 6 will be quite the duo.
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
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
"seq_wave parameter probably should not show up in automation. It's just for the three buttons in the sequencer that set a preset "wave" seqeuence. Since the sliders themselves are automated, this doesn't need to be automated at all and should go away."
(from my correspondence with Randy)
seq_local switches whether sequencer corresponds to its own rate or to BPM of a DAW. There is a switch in the UI so I guess you should notice when it is changed.