Ableton Forum

Hi there!
Does anyone know if I can set up a midi clip or a scene to stop the whole session/arrangement (not just the clips), without having to press the STOP button or to assign it to an external controller /keyboard?
Thanks for your help
Nicolas

Sorry - I don't mean to hi-jack your message thread but I wanted to know if you can tell me how to assign a remote midi controller/keyboard to trigger clips and import midi. I have a roland A-70 controller keyboard that is hooked up to my midi in and out of my interface which is linked to my PC via firewire. Somewhere along the line- the interface is transmitting midi signals but it does not trigger the clips in LIve.

Have you tried switching on the "Remote" setting in the Midi preferences?

There is no way that I know of in vanilla Live to map the stop button to be triggered from a clip. However, if you have Max4Live, you can probably do this, though I've never tried it since I don't. The other way I've heard of people doing this is getting some kind of software MIDI loopback device (I think Bome's MIDI tools can do this, as can MIDI-OX on Windows), and sending that clip's output to that device. Meanwhile, that device is considered a MIDI input in live which can be mapped to things like the transport controls.

It always struck me as sort of kludgey, but I think it should work. Hope this helps

Paulmac wrote:Sorry - I don't mean to hi-jack your message thread but I wanted to know if you can tell me how to assign a remote midi controller/keyboard to trigger clips and import midi. I have a roland A-70 controller keyboard that is hooked up to my midi in and out of my interface which is linked to my PC via firewire. Somewhere along the line- the interface is transmitting midi signals but it does not trigger the clips in LIve.

So... don't hijack it? I'm not really sure why you put this question here.... Your question is perfectly legitimate as its own thread, especially since it'll have its own title and people who know the answer might be able to see the question more easily. If you don't want to make a forum thread out of it you can always ask on Q&A sites such as the one in my signature.

Live has some pretty good info in its manual and its lessons about setting up MIDI controllers. The oversimplified version is that you need to have the control enabled in MIDI Preferences for "Track" if you want to record MIDI data and "Remote" if you want to map it to Live controls like clips, knobs, or transport. Best of luck.

Warrior Bob wrote:There is no way that I know of in vanilla Live to map the stop button to be triggered from a clip. However, if you have Max4Live, you can probably do this, though I've never tried it since I don't. The other way I've heard of people doing this is getting some kind of software MIDI loopback device (I think Bome's MIDI tools can do this, as can MIDI-OX on Windows), and sending that clip's output to that device. Meanwhile, that device is considered a MIDI input in live which can be mapped to things like the transport controls.

It always struck me as sort of kludgey, but I think it should work. Hope this helps

Hi, thanks for your reply!
I've tried in the past stuff like Bome or Jack, but these tools created more problems than what I was trying to solve, so I got rid of them. Guess I'll wait for the next update, hoping that this feature request be integrated...

njulliard wrote:Hi, thanks for your reply!
I've tried in the past stuff like Bome or Jack, but these tools created more problems than what I was trying to solve, so I got rid of them. Guess I'll wait for the next update, hoping that this feature request be integrated...

You're most welcome! Out of curiosity, what are you trying to do that necessitates having Live stop playback based on information in a clip? If you're trying to have Live stop automatically based on a session clip, then you still have to trigger the clip yourself, so I would think it would be just as much work to hit the stop button. I can't think of a situation where it'd be useful. This isn't to criticize your workflow of course, so much as to see if there might not be some alternative I could suggest, or if you're doing something cool that I haven't thought of.

Warrior Bob wrote:

njulliard wrote:Hi, thanks for your reply!
I've tried in the past stuff like Bome or Jack, but these tools created more problems than what I was trying to solve, so I got rid of them. Guess I'll wait for the next update, hoping that this feature request be integrated...

You're most welcome! Out of curiosity, what are you trying to do that necessitates having Live stop playback based on information in a clip? If you're trying to have Live stop automatically based on a session clip, then you still have to trigger the clip yourself, so I would think it would be just as much work to hit the stop button. I can't think of a situation where it'd be useful. This isn't to criticize your workflow of course, so much as to see if there might not be some alternative I could suggest, or if you're doing something cool that I haven't thought of.

My aim was to use one footswitch to trigger one scene after another (return key style), and then to be able to stop the session automatically at one point (say at the end of verse 1, for instance), restart from scene X with another switch when I want, without having to use three switches for that. Nothing particular in that, it was just a question of saving footwitches for other functions. Nothing vital, but that would have been nice anyway...

Ok everybody!
I finally delved into Max For Live, and managed to find a solution for my request. If you have Max For Live, you can use this object on a midi channel, and then create a simple midi clip to send anything with a velocity of 127, thus sending the "bang" that triggers the start/stop function of the transport bar. Enjoy!
Fauve

<pre><code>
----------begin_max5_patcher----------
555.3ockT0ziaBCD8LQJ+Gr3LkBzjvlJ0Ca+Czpt4V0pHGXHwsFOHiglzU8+
dMlOBrwAs6EaqYF+7yu2X+xxENtGvyPoK4yjeRbbdQGwwDqIhSe.G2b54DNs
zTnaBlmCBkqWWREbVYR7ztG+wNxGIOs6aeeHKmIfDrRXJIpOZgDJ0XPULTr2
dIYnPIn4fA5GkLJm7UjmN.rnJGqTbPYXUPeXVpYC3ge8gMtVONIjnZuwa15G
3Qh+Ty3lnlwHcDxyioPI6uFJDF3ObFETUxIl33HnVGXfZUy35vagZLCLvM5Z
vD82hPSv+sbQyrdx6MaJbVM3enRozv2CslhsFiRxNdDjj+bBDjZfiIL0kuPB
ihGpslJGDaaXMUsCsn1gC01Vn5RAzpMtt10gQxW3CMRV3Zy3pngoqajlnzz5
vwDjix1ME3GGuYUbnm0UgSj+acrHi4uxbvOrse7M3XulCQqWs0yxhWQ.oVdU
fbOHnG3vL8.8QKo0P5dpR6dZy.ttprqQnuSnw83U.l0GeHw3ykihiyYwSJNG
S0Tx7vZnseJZLwuaPaxiuaf.Sg6lmIxPCWrRfJAqUNrmFkof7tPmBYyjsr.f
TNK2H192ga0rRVmMYGDETb+6NUHvtd7AI258.zVe2iDLKy0SOIt9ZYZomKPA
z9h9Nz1HZpKccW1cE8uFyfP97td+a5H6hFSo+kdTCtck6DJUuqFwNFGE6GzU
Q2OjWWb8KSxyKWnm9Ova7EqS
-----------end_max5_patcher-----------
</code></pre>