Ableton Forum

Wouldn't it be nice if there was a M4L user library lik the NI Reaktor one?

Greetings!

look here:

http://maxforlive.com/

and here:

http://www.maxobjects.com/ <--- 4,123 objects

NI Reaktor Library has 3,156 objects.

thx a lot!

Tone Deft wrote:and here:

http://www.maxobjects.com/ <--- 4,123 objects

NI Reaktor Library has 3,156 objects.

Hmm--Is there not a type of "cross over" that must be done to make Max patches available in M4L...Unless I'm completely mistaken about it

At the object level, you mean? Nope. You'll need to do some stuff if you want to give a device which includes a third party object *to someone else*, but if the third-party objects in your patch are in your Max search path, you're good to go. I use 'em all the time. The device that's running right now, in fact....

When porting higher level patches as devices, you get to make some choices about whether or not you want all the Live bells and whistles. It's impossible to say with certainty whether everyone will want feature X or not. In general, I tend to do global search and replace for Max UI objects to their Live counterparts, but that might be just me. Your mileage may vary.

^Man---This all relatively new to me...I'm a little confused on what you mean (sorry, super Max noob here) So patches made with the full version Max will operate with M4L eh'...Do you know if there is a tutorial on how this is accomplished? Sorry if it seems I'm asking a retarded question but I'd really like to play with some pre-existing Max patches that I've come across before...So is there just a few things that must be changed within the patch to make it M4L compatible? Can you easily load a Max patch into Live just as you can with a M4L patch? Or is there not really much a difference in the file? Thanks alot for the help man...Like I said---Total noob...

AFAIK the only real difference is that Live uses specific input and output objects to get stuff into and out of a max patch. max4Live is max/msp/jitter running alongside Live, it's the real thing.

the third party stuff Gregory mentioned refers to files and add-ons that people use with max. many of those are from CNMAT (UC Berkeley's Center for New Music and Technology) a computer audio geektank.
http://cnmat.berkeley.edu/downloads
they've developed add-ons to max/msp/jitter to make the max easier to use as well as their own collection of objects.

BUT that's all completely optional and stuff you'll never need to consider.

or a patch might use a file that doesn't come with max/msp. suppose I made an object that was made from C code I wrote, you'd need to include that object in your library.

also, you don't need the API stuff to use max/msp, totally optional. you can do things very specific with Live with them, but some max4Live users may NEVER use them and still make lots of perfectly useful patches.


mostly, just try it. take a simple patch and drop it into max4Live.

There is a quite in-depth article from Gregory around porting pure max patches into M4L devices.

http://cycling74.com/2010/02/19/lfo-tut ... u-want-it/

Basically, as already stated, M4L brings additional UI counterparts which provide better integration into Live sets, parameter modulation, storage etc. In addition to that, as M4L devices live within Live, they need to plug into the "data streams" Live provides, such as plugin~/plugout~ for audio and midiin/midiout for midi, there is no direct interfacing with your hardware, Live is always the master.

nick

Thanks alot guys---

monohusche, I will definitely check the linked tutorial out--I guess I havn't come across that chapter/section of the Cycling 74' tutorials

canis wrote:Wouldn't it be nice if there was a M4L user library lik the NI Reaktor one?

Greetings!

I agree.

tempus3r wrote:

canis wrote:Wouldn't it be nice if there was a M4L user library lik the NI Reaktor one?

Greetings!

I agree.

lol

cheers
D