Ableton Forum

you are almost there -----begin_max5_patcher---------- 458.3ocuU1saBBCEG+Z3onoWyHzBUY6tsWiEioJUsKPKApatY7ce8CXpa5fM IbAkzSaZ+e9c9n688fKj6X0PvCfmAdd6887rlLF7Zl6AKn6VlSqsaCJXuIW7 BLvsjhsSYMWVwEpVqqjBkfVvrq7XEmlCdRlm0trXaAWjyT1CD0XrjpVtgKVO uhsT4DDNkDFE.vjIlewwlQTZXDX1wCRtU0dRQmb607Or2NJJr0LOyJGs3uKF Z...

I am tempted to say that atm there is no way to link to the file system, neither for live sets nor for clips.

The release of the API with the MaxForLive release was both wonderful, and a cause of great consternation in the Live users who are drawn towards MaxForLive. to understand, Keep in mind two things (GT, you of course know all this): 1) The API was not even going to be released initially: it was a gr...

Hi Gregory,

so where do we find the free manual for the ControlSurface class ?

not here obviously

http://cycling74.com/docs/max5/refpages ... model.html

nick

not sure I am on the right track but the control_surfaces LOM object isn't really documented, so using the api explorer lets you walk the tree exposing the functions and attributes each node exposes.

It's done by calling getinfo on any live.object.

hope that helps

as I said, live.observer can't be used to set values From this moment on, the value is sent on each change of the property 1. navigate the LOM 2. set the id 3. specify the property to be observed 4. live.observer reports the current value once 5. from now on, live.observer reports the value whenever...

@s4racen

you lost me with live.observer.....isn't that a notification object to notified of changes ? how would you change values with it ?

especially as changing values upon getting notifications is not allowed in M4L.

MonoMIDI is a step sequencer to be controlled via the monome. It's based on manipulating Live MIDI clips. Part of the code base was taken from the Ableton Clip Step sequencer, thx for that. the features in a nutshell: - support for MIDI clips with up to 64 steps (1 step = 1/16 note, which makes it 4...

probably not possible as the Live Object Model (LOM) only allows to access the generic parts of Live, such as track, device, clip etc.

It doesn't let you access audio buffers, neither for clips nor for the Looper. You would have to implement a M4L-based Looper using it's own buffer.

There is a quite in-depth article from Gregory around porting pure max patches into M4L devices. http://cycling74.com/2010/02/19/lfo-tutorial-6-live-if-you-want-it/ Basically, as already stated, M4L brings additional UI counterparts which provide better integration into Live sets, parameter modulati...

you are quite correct, there is no way to get to the operator internals with M4L, it's limited to the same parameters as available to automation and clip envelopes. gotta build an fm synth yourself, not sure whether this would be such a hard thing to do, also not sure whether it would have to be don...

Hey there, as presented at the Berlin monomeet, here is the second part of the MonoLive suite (after MonoParaSteppa). MonoLive is multiple things in one: - an advanced clip launcher with session matrix navigation - an EQ + mixer controller - a device controller - a send controller - a dummy clip con...

just different levels, underneath Reaktor building blocks, it's all math as well.

@Tone Deft

if you ever decide to solely concentrate on Max, let me know...I buy Reaktor off you

you should be able to route the MIDI events to another MIDI track and record there.