Do you like Max for Live?

[henke]

It is indeed!
However, it will become much easier once more examples and building blocks are available. It's structure is very logical, but clearly comes from a developer perspective, since in its original state it was never meant to be open to the 'public'.

I plan to upload a collection of simple and ready to use abstractions that address basic functions like an object with a single inlet and a single outlet that allows to observe and set the on/off state of the device it belongs too.

Unfortunately I have no time left over to do this at the moment...

Robert

[Pipotron4000]

API was not even planned in the first M4L release (read henke posts http://forum.ableton.com/viewtopic.php?f=35&t=134117 )
So we can thanks the anonymous dev who helped integrate it sooner

If you want some help understanding LOM/API , look http://www.cycling74.com/docs/max5/refp ... model.html first

and take a look at my post's links http://forum.ableton.com/viewtopic.php? ... 8#p1065338 to see python scripts (the ancestor )

As python API/M4L API are unified now, python scripts should work (you need Jython installed, see link above) with minor changes

But once you see a working native python script and look the M4L API examples included in M4L, you will understand most things in API

What we really miss is a "toolbox" for controllers (even if API examples are good starters)

I think the API is the most stimulating thing in M4L but, as it was not planned, ppl want more about it than expected by Ableton and Cycling 74

Anything else than API can be (and was) made by external software, but before M4L API, only "custom scripts" solutions (like Bome's MIDI translator, autohotkey, native python...) could do things like "copy current clip, paste it on next track and arm the third" with one hit

The API is the most underrated part in M4L and will grow faster than anything else because it is the common heart of Live and M4L

[Insectec]

hey )))))))))))) Yep

Its amazing!

My only problem with it is the update situation and menus.

1. Can the update check for M4L be done for both Ableton and Max software from one check in the Ableton 'Check for Updates' ?

2. Can the file menu in both Ableton and Max be standardised to look the same? I find it annoying that it is spaced different in both programs. i.e so 'Open Recent' etc is in the same place on both menus on both programs ?

Apart from that I do really like the M4L, but it helps to get some extra tuition because I find the Max tutorials awful to read on the computer, the font is hard going on the eyes and seems to be written by someone who has a degree in computer science, not information text and graphics.

I took a beginners Max/MSP course last summer and am due to start the advanced course in April (At City Lit College in London). This really helped me get into designing my own plugins etc.

I have made a random remixer for studio work and it really 'throws' up some interesting ideas. Its a bit like The Dice Man crossed with Eno's Oblique Strategies for techno he he. When I get a interface on it that is pleasing to the eye i will post it.

Its has be used on my latest release which is out soon on 12inch vinyl and digital on Aconito Records. http://www.aconitorecords.co.uk

Ghost Bus EP

Side A1 – Ghostbus - Bioni Samp 6:46

Side A2 – Ghostbus - Bioni Samp & nAX_Acid 7:31

Side B – Ghostbus - nAX_Acid EDIT 6:54


I have also a live set done on M4L:)

http://soundcloud.com/beespace/bioni-sa ... netic-2010

Equipment List:
Toshiba laptop running Ableton - MAXFORLIVE, RME 400 audio interface, homemade Delay Unit, MAX Schwarzenator, Faderfox LC2 & LV2 midi controllers, Akai LPK 25 Keyboard.

[sacredgeometry]

loving every headache to brilliant resolution

[aminoplacid]

I think it is great. Yes, learning Max is difficult even for a developer by trade. However I'm really starting to get it (at least for what I am trying to do). My only real issue is the (what seems to be) inconsistencies of the API for some of the hardware devices like the APC40 or perhaps the Launchpad too (though I don't own the Launchpad). The functions are very non-de-script as to how to use them and some just seem inconsistent to others (such as "set_metronome_button" for a single buttons but "set_nudge_buttons" for two buttons).

[Tone Deft]

I plan to upload a collection of simple and ready to use abstractions that address basic functions like an object with a single inlet and a single outlet that allows to observe and set the on/off state of the device it belongs too.

I would really appreciate that. glad to hear I'm not the only one bewildered by the API but I'm glad to see some picked it up quickly. there are some incredible people showing up in this forum.