[Max for Live] what will be the first device you'll build ?
sharing device will be the new destiny of ableton
just hope they'll keep this way:
sell m4L BUT gives us/share with us devices made by artists etc..
btw, we're a lot to know max already... so, we'll make the m4liver community growing
just hope they'll keep this way:
sell m4L BUT gives us/share with us devices made by artists etc..
btw, we're a lot to know max already... so, we'll make the m4liver community growing
Julien Bayle
____________________________________________________________________________________________________
art + teaching/consulting
ableton certified trainer
____________________________________________________________________________________________________
____________________________________________________________________________________________________
art + teaching/consulting
ableton certified trainer
____________________________________________________________________________________________________
-
- Posts: 2255
- Joined: Mon May 29, 2006 10:10 pm
external or otherwise, doesnt matter. i can definetly say that i would need it though, cause that would save me alot of headache.hoffman2k wrote:I already got a patch for that. I was going to incorporate it in my BCR application but that would shut it out from everybody else.friend_kami wrote:yes please.nbinder wrote:...something to store MIDI controller data snapshots
Once I released the latest version of the BCR app I'll see if I can get this out as a little application.
And although its ready for Max for Live, its probably best as an external app. Since you'll need to send MIDI to Live's remote input and that probably wont be easy if you cant use virtual midi within patches.
I can imagine we could create a website/forum/trac/project manager in order to share infos/wiki about folks who want to participate to the big m4L community.
I already involved myself in openSource project communities
I believe in that cause I'm sure union = force !
we could work together about project of devices
(I just ................ bought Live7Suite
I already involved myself in openSource project communities
I believe in that cause I'm sure union = force !
we could work together about project of devices
(I just ................ bought Live7Suite
Julien Bayle
____________________________________________________________________________________________________
art + teaching/consulting
ableton certified trainer
____________________________________________________________________________________________________
____________________________________________________________________________________________________
art + teaching/consulting
ableton certified trainer
____________________________________________________________________________________________________
I own maxforlive.com and maxforlive.org. Both could be used for something like this. However I did PM DOM and it seems likely we'll get a section of the forum dedicated to M4L and the new Live 8 "share" stuff will allow seamless sharing of M4L patches for collaboration.julienb wrote:I can imagine we could create a website/forum/trac/project manager in order to share infos/wiki about folks who want to participate to the big m4L community.
I already involved myself in openSource project communities
I believe in that cause I'm sure union = force !
we could work together about project of devices
(I just ................ bought Live7Suite
So the only thing left that might be cool is a wiki as a tutorial and FAQ archive. That's what I was planning on doing with it but I'm always up for suggestions.
MBP | Live 9 Suite | Max for Live | Push | MOTU Ultralite | iPad | Analog Modular Synths | Moog Voyager
aka "Tempus3r" | Music | Blog | Twitter | Soundcloud
aka "Tempus3r" | Music | Blog | Twitter | Soundcloud
First things I will build depends on exactly how it's implemented but... I want to turn the Jitter VJ app I built into a Live device.
This would not only have a device that triggers video based on midi data, but it will also have a sister device that you put on other midi tracks so that musical automation data can be automatically (and randomly) translated to Video effects.
Other than that I'll mess with custom sequencer/lfo apps like everyone else I'm sure...
This would not only have a device that triggers video based on midi data, but it will also have a sister device that you put on other midi tracks so that musical automation data can be automatically (and randomly) translated to Video effects.
Other than that I'll mess with custom sequencer/lfo apps like everyone else I'm sure...
MBP | Live 9 Suite | Max for Live | Push | MOTU Ultralite | iPad | Analog Modular Synths | Moog Voyager
aka "Tempus3r" | Music | Blog | Twitter | Soundcloud
aka "Tempus3r" | Music | Blog | Twitter | Soundcloud
tempus3r, if I can help, I will!
I guess you know well CMS and server scripting (php etc) so ...
I guess you know well CMS and server scripting (php etc) so ...
Julien Bayle
____________________________________________________________________________________________________
art + teaching/consulting
ableton certified trainer
____________________________________________________________________________________________________
____________________________________________________________________________________________________
art + teaching/consulting
ableton certified trainer
____________________________________________________________________________________________________
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!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?
Yea that is a cool one.Parametex wrote:Great idea!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?
-
- Posts: 175
- Joined: Thu Sep 09, 2004 12:24 pm
good point if im wrong! i wanted to hear that, id like to build a real speed vizual feedback interface.so max can make a button blink at let say 25hz and the gui will reshresh speed enough?Machinate wrote:yes you are.Euklid.fox wrote:max is far from to be as user friendly, maybe it will change with v5, but from now what I ve seen is so amazing but so ugly and low rate refresh on the Gui aspect, am I wrong?
-
- Posts: 2255
- Joined: Mon May 29, 2006 10:10 pm
dude, thats a pretty clever thing id say.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?
Here is something that I have often thought of doing but never took the time to do. Take a Jitter object, like anything from the cv.jit bundle, and run some note outs. Attach these to parameters to live and use a visual data to modulate parameters on consistent or slightly changing tones. Record this data in the arrangement screen. FInd instances along the timeline that you like. Save the rack as different names. Make a livepack. Sell it.Tone Deft wrote:how can we randomize the parameters in Operator, Analog, Sampler etc??
want.
Of course this can also be done using random number generators, but I feel that limiting the source is conducive.
I have used this method to produce positive results. I now use an application from a previous collaboration for similar results (as opposed to a Jitter patch), though I do not have permission to share that application, unfortunately. All of my earlier Jitter patches were lost so I can't share those either.
I'm not the only one thenlola wrote:Yea that is a cool one.Parametex wrote:Great idea!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?