Ableton Forum

lola wrote:

Parametex wrote:

ikeaboy wrote:A simple thing I'd like to build would be something that turns clip colours black after they've been triggered once then stopped. I'd use this for livesets to get past the "have I used these clips already?" dilema I get about half an hour in. Am I the only one who can't remember what stuff they already played out sometimes?

Great idea!

Yea that is a cool one.

I'm not the only one then

Geezus wrote:
I am perfectly fine with people stealing my stuff, music or otherwise. However, I myself am not going to just hand out a year's worth of work for free. I'll let the pirates pirate and anyone else who feels they can spare a measly 10 bucks give me the 10 bucks. ... but I'm not going to be pissed off or judge people for stealing it.

The fact that you are willing to share it (if it doesnt take a year to make) is cool.

Just remember the difference between charging 10 bucks and sharing is that you are selling an *expectation* for 10 bucks which means support

I got an old Yamaha A5000 Sampler which can be used as really nice 6 x FX unit and filters etc. that would benefit from a M4L interface.

And whos going to do the first Jomox Xbase 09 interface !!!
If that was interated into live it would be pretty dope.

ikeaboy wrote:

lola wrote:

Parametex wrote: Great idea!

Yea that is a cool one.

I'm not the only one then

Thats funny

But a REALLY good idea.

If the API allows to programmatically load a clip by sending a path to a file on disk (and the session view coordinates) to live, then I'm gonna build a custom filebrowser which will work on a midi controller's LCD displays.

Does anyone know if the API will allow this kind of stuff?

grooveWhiz Akeem wrote:If the API allows to programmatically load a clip by sending a path to a file on disk (and the session view coordinates) to live, then I'm gonna build a custom filebrowser which will work on a midi controller's LCD displays.

Does anyone know if the API will allow this kind of stuff?

I really hope so.

I haven't had a chance to look through all 6 pages of this thread, but do you reckon this would be possible...

I'd like an app that allows me to associate a photo with each clip in the session view. So, as I launch clips the associated photo's are shown on an external screen (e.g. on a large screen when playing live.)

Even better, if the photo's flashed up and disappeared rhythmically in time with what is happening in the clip.

You'd then get a visual mix happening

grooveWhiz Akeem wrote:If the API allows to programmatically load a clip by sending a path to a file on disk (and the session view coordinates) to live, then I'm gonna build a custom filebrowser which will work on a midi controller's LCD displays.

Does anyone know if the API will allow this kind of stuff?

mmm yeah i was thinking about that too, although on a separate screen instead. but the whole idea of a better browser, really.

Wow... I am impressed by the geniuses here!

Everyone is gonna make all these really complex devices for their first one!!!

I suspect my first one will be exceedingly simple...

I´m a total programming dweeb, but I hope that someone replicates the Ammobox app for Reaktor natively in Live....

friend_kami wrote:

grooveWhiz Akeem wrote:If the API allows to programmatically load a clip by sending a path to a file on disk (and the session view coordinates) to live, then I'm gonna build a custom filebrowser which will work on a midi controller's LCD displays.

Does anyone know if the API will allow this kind of stuff?

mmm yeah i was thinking about that too, although on a separate screen instead. but the whole idea of a better browser, really.

If the live.x objects work in the manner I suspect, then two-way browser control will be a doodle as well - then "all you have to do" is figure out the system for the LCDs.

yeah, live.path sounds like it could be excatly what would be needed. Maybe the other objects too. Too bad there's currently not much info about those objects. The current python based API does not allow this stuff, unless anything changed in the new _framework?

For the LCD system, I don't think it will be too difficult. I imagine displaying an itunes like (genre, artist, album, ..., whatever) filter on the remote sl zero or the mackie c4 (for both there are dedicated MAX objects). Good times ahead.

will the Live API let us communicate with it via another world than m4L ???

I mean, I have already a java app between my monome and Live:
[monome] <---> [monomeserial] <---> [java app] <---> [Live Python API]

I guess if it won't, it will be easy to port this java app to a m4L patch ...

For the LCD system, I don't think it will be too difficult. I imagine displaying an itunes like (genre, artist, album, ..., whatever) filter on the remote sl zero or the mackie c4 (for both there are dedicated MAX objects). Good times ahead.

The lcd screens on the remote sl series are suprisingly easy to send data to. Its a simple series of hex encoded sysex messages.

I was a bit disappointed at first that no improvements were made to sampler in Live 8. Ie. no timestretch/ graular mode. No easy way to scrub like in simpler. etc. But then I realized that Max4Live will probably be a sampling device playground.

Imagine all the great little devices that can made for sampling. Especially new devices to hold drum sounds to go in drum racks, like mini one slot multi-layer impulses with stretch and all manner of FSU type parameters. It could be like reaktor's granular devices, but mixed with Live's drag and drop of recorded samples, and device integration, it'll be much better in terms file management and accessibility hopefully.

i'm gonna make a lowpass filter...