Discuss music production with Ableton Live.
-
hoffman2k
- Posts: 14718
- Joined: Tue Jun 15, 2004 6:40 pm
- Location: Belgium
-
Contact:
Post
by hoffman2k » Thu Apr 03, 2008 11:01 am
julienb wrote:bjorn,
you need to assign a note for each clip...
indeed, i discovered this feature very late.. but for my own opinion, it is very unsatisfying to assign a note for each clip before a live performance...
it costs too minutes, i mean
but you're right, it works fine!
You can assign a note to the track play button (appears in MIDI map mode where the stop button is).
So you only need 1 note for each track.
-
julienb
- Posts: 1843
- Joined: Sat Oct 29, 2005 1:15 pm
- Location: France
-
Contact:
Post
by julienb » Thu Apr 03, 2008 11:05 am
yes, bjorn.
you're right (as usual!)
I tested it several weeks ago and made a mistake in my posts
sorrrrrrry!
this feedback will be a part of the features required for a really powerful live perf.
-
Tuur
- Posts: 622
- Joined: Thu Jun 02, 2005 7:56 am
Post
by Tuur » Thu Apr 03, 2008 5:33 pm
hoffman2k wrote:You're thick and this is already possible
Assign a note to a clip, enable remote output in Live's prefs.
It'll send out the following velocity messages:
0 = Clip stopped
1 = Clip repeat
126 = Clip Triggered
127 = Clip started
I'm already using these. Hence my request (all the other stuff that's missing on your list).
Thanks anyway!
Edit - now that I've got your attention; what exactly does #1 mean? And why does Live send it out at random (well, not completely random of course - but you know what I mean)?
-
hoffman2k
- Posts: 14718
- Joined: Tue Jun 15, 2004 6:40 pm
- Location: Belgium
-
Contact:
Post
by hoffman2k » Thu Apr 03, 2008 5:58 pm
Tuur wrote:hoffman2k wrote:You're thick and this is already possible
Assign a note to a clip, enable remote output in Live's prefs.
It'll send out the following velocity messages:
0 = Clip stopped
1 = Clip repeat
126 = Clip Triggered
127 = Clip started
I'm already using these. Hence my request (all the other stuff that's missing on your list).
Thanks anyway!
Edit - now that I've got your attention; what exactly does #1 mean? And why does Live send it out at random (well, not completely random of course - but you know what I mean)?
1 is when a loop repeats. So you'll get it every 4 bars in a 4 bar clip. Every 2 bars in a 2 bar clip.....
Exiting message is easy. If one clip is entering, the other one is exiting. No need for an extra message there. Its a track, there can only be one (clip playing).
-
Tuur
- Posts: 622
- Joined: Thu Jun 02, 2005 7:56 am
Post
by Tuur » Thu Apr 03, 2008 6:33 pm
hoffman2k wrote:1 is when a loop repeats. So you'll get it every 4 bars in a 4 bar clip. Every 2 bars in a 2 bar clip.....
Not what I'm seeing.
E.g. I'm getting this message every 4 bars when there is a loop
at all. My clip has a loop at bar 65 or something, Live sends the message after bar 4 - 8 - etc. Why oh why?
Exiting message is easy. If one clip is entering, the other one is exiting.
I meant / said exiting the loop.

Last edited by
Tuur on Wed Apr 09, 2008 8:38 am, edited 1 time in total.
-
hoffman2k
- Posts: 14718
- Joined: Tue Jun 15, 2004 6:40 pm
- Location: Belgium
-
Contact:
Post
by hoffman2k » Fri Apr 04, 2008 10:13 am
I guess it all depends on how you look at it.
In my case the 1 is enough, because if I want to see where the clip is at - I just set up a counter to start/retrigger at 1.
Exiting is also something I don't really need from Live (your milage may vary).
Because there can only be 1 clip playing per track. Knowing that another clip is entering is visual feedback enough IMO.
-
Tuur
- Posts: 622
- Joined: Thu Jun 02, 2005 7:56 am
Post
by Tuur » Fri Apr 04, 2008 10:58 am
Makes sense.
I want my controller to respond with the correct visual feedback. For that I need either a #1 message on entering the loop or at launch of the clip. Not somewhere in between.
Also, since the clip will be going on for a while after exiting the loop, an exit message would be fantastic.
Edit - link to the loop feedback bug post:
http://www.ableton.com/forum/viewtopic.php?t=89396
-
Dj-Grobe
- Posts: 812
- Joined: Sun Mar 19, 2006 12:13 pm
Post
by Dj-Grobe » Sun May 10, 2009 9:37 pm
Ableton 8.0.2 this problem back again and Option.txt not fix the trouble!
Please some official repply?
-
julienb
- Posts: 1843
- Joined: Sat Oct 29, 2005 1:15 pm
- Location: France
-
Contact:
Post
by julienb » Mon May 11, 2009 7:18 am
I guess "official API" will solve all of these problems.
Actually, our python hack scripts do the trick.
check LiveAPI on Assembla website..
-
Dj-Grobe
- Posts: 812
- Joined: Sun Mar 19, 2006 12:13 pm
Post
by Dj-Grobe » Mon May 11, 2009 11:04 am
After working 2 days on this, i find a workaround of have correct MIDI feedback with this new way ableton 8 use.
Really be good know, if ableton plain work in this wayt from now, or if this is a mistake.
Best regards.
-
mbira
- Posts: 159
- Joined: Sun Apr 26, 2009 5:58 pm
Post
by mbira » Fri May 22, 2009 3:24 am
I was just directed to this thread with a similar question. I am trying to build a LED system that is able to read this feedback information. Specifically, when we hit our midi trigger, I need an LED to indicate that a scene (not just a clip) has been triggered (like how it blinks on the screen) and then to get a solid light while the scene is playing.
I am using Live 8. Any advice? I hope that Ableton reads this and knows that the APC won't work for everyones needs for the feedback. My band is jumping all over the stage and hitting midi triggers and the computer is far off to the side so we need the visual feedback to know that we correctly hit the trigger...
Thanks for your time!
Joel