Ableton Forum

Hi, I'm using several tracks as control/trigger tracks. The tracks are Midi tracks that contain only midi control envelopes. The output of the tracks are being sent to the internal Mac IAC driver (sends midi out then back into ableton). I have a Midi map set up so that each trigger (each sending a different CC#) is mapped to the monitor section of other midi tracks to turn the monitor on (in) or off.

That all works. The issue is that the behavior of live when triggering the scene is very odd! I have different scenes set up. Each scene contains multiple tracks...including external midi devices as well as the trigger tracks. Each scene is a different song. The goal is to start each scene, manually, one at a time. When the scene starts, the appropriate tempo is set, the click starts, midi patch change messages are sent, and the triggers set the appropriate midi monitors as needed.

When I trigger the first scene, it fires off, but then it starts the trigger clips for the second scene as well. Most of the time, the clips for the second scene get stuck looping even though the loop switch for the clip is turned off. It's almost like it gets stuck in a loop. I have to hit the stop control a number of times fast in order to finally get it to stop.

I've uploaded a screen movie to show this behavior...except I think due to the video driver/screen recording, it never gets stuck in the final loop. But you can still see me starting the 1st scene and then the clips from the second scene start as well. (no audio either so watch the mouse).

Here's the link:

http://youtu.be/xswsfaY2OTg

I've checked each clip. No follow action is set. The loops are turned off on all of the clips. It's just odd.

Any pointers would be greatly appreciated. It's a somewhat complicated live set and has a lot of tracks, clips and plugins so I really don't want to have to recreate the whole thing from scratch.

Thanks!

It hard to understand. Thanks for making a video.
Maybe you midi mapped the second clips by mistake ?

You were right. Somehow the triggers were mapped to other clips. I'm relatively new to this but I have no idea how that happened. Fixed it. But now the project crashes every time I try to open it. AHHH!

Opening a new thread on that.

Ha !
i had a good feeling. This happens when you do complicated stuff with inside midi routing, sometimes you got midi flow running, hit cmd+m and map things without knowing it !
beware of midi flow loops, too ! that can make a set crash easily....
open a new set, and check your midi ins and out. Disable them one by one and point out the source.
Good luck.

Thanks for that. I tried disabling ports one at a time but it kept crashing. I've disabled every port, sync, and remote option and it still crashes. I'm wondering if that is now pointing to the max device...