Follw actions on scenes

conny · Post by **conny** » Sat Jan 15, 2005 11:39 pm

As I said in

http://www.ableton.com/forum/viewtopic.php?t=15642

and here is an (not musically interresting but supporting my thought) Live set that demonstrates how to use follow actions for scenes.

http://web.telia.com/~u19126355 - link under Live header. [Gone away...]

Edit: Direct
http://web.telia.com/~u19126355/Live/scene_follows.zip

The set uses midi yoke 4 as external midi controller, you might have to adjust tyhat to something that siuts your set up.
When triggering one of the midi clips in track 6, scenes 5 to 7 will be triggered according to the follow actions for the clips in track 6.

The audio clips in track 3 have their own follow actions in their group that will run until a new scene is triggered from the controlling clips in 6.

// C

supster · Post by **supster** » Sun Jan 16, 2005 1:32 am

Wow. Thank you!

I was thinking about this the other day, and wanted a way to do exactly that ...trigger scenes automatically.

I tend to write using clip lengths of 4 bars. So I normally think in terms of trigging the next row of clips every 4 bars. Often I'm not really looking to have to trigger them 'live', manually ...

I just want to conceptualize building the arrrangement in rows of four bars clips, make modifications, and keep triggering them down the list that way

This is awesome. I simplified it to meet my purposes right now:

- create Scene Launch MIDI Track on the far right of the grid.

- create a 4 bar clip in this track, Scene 1. No looping. Global quantization.

- place notes in this clip on C-2, beat 4 ... and C#-2, beat 4.1.3.

These notes are at the bottom of the keyboard to where they would be rarely used by any instruments

- MIDI assign C-2 to global Scene Down control, C#-2 to global Scene Launch

- assign MIDI Yoke 4 as an input and an output in Preferences.

Viola. Trigger the first scene manually, and my scene automatically jumps down to the next, and triggers on the next bar (Global is set to bar)

For each scene I want to play for 4 bars, gets a "SCN 4" clip. 8 bars? "SCN 8" clip. 16? "SCN 16". etc ...

Beautiful! You just solved a major issue for my producing. This can be modified in so many ways, its amazing ...

Cant imagine yet how using MIDI Yoke to control the live interface is going to come in handy in about a million ways, but as time goes on I'm sure Im going to come up with more ...

conny · Post by **conny** » Sun Jan 16, 2005 12:48 pm

I'm happy this could really help you out.
I'm most in the experimental mood, equals no really structured songs will be produced, so that this helps when doing proper songs it's an extra bonus!
There are, as the usually says, just the imagination that sets the limits. You could as well send CC messages over external midi yoke to control parameters as sample start in Simpler on another track from controlling midi clips.
When I looked at your example, it occured to me that go to next/prev/trigg current on tracks are missing in Live. They are only on scenes. If we had them on tracks too, that could complicate/ease some special trigger logic!

// C

supster · Post by **supster** » Sun Jan 16, 2005 4:41 pm

conny wrote: When I looked at your example, it occured to me that go to next/prev/trigg current on tracks are missing in Live. They are only on scenes. If we had them on tracks too, that could complicate/ease some special trigger logic!
// C

Yes, good point. Because - of course - at the point you could "play" the entire grid automatically using MIDI notes to trigger any clip, any where ...

Got your msg conny - I'll put something together for you in a bit ..

LOFA · Post by **LOFA** » Wed Dec 28, 2005 6:10 pm

Personally I use the IAC found in mac, but this needs to be seen by all!

Liam · Post by **Liam** » Wed Dec 28, 2005 7:14 pm

Can Tracks not be triggered from assigned MIDI notes/sequence//loop or controllers?

TheAnimal · Post by **TheAnimal** » Wed Dec 28, 2005 7:19 pm

Thanks a lot for this tip, Conny! I was wondering why it works at all but the secret is to have no stop buttons on the track controlling the others. Live is so full of possibilities...

Lofa, good idea to use IAC. I'm used to use MidiPipe for everything. But IAC is just much easier to use in this case. (First time I ever used it.

)

LOFA · Post by **LOFA** » Wed Dec 28, 2005 7:44 pm

TheAnimal wrote:Lofa, good idea to use IAC. I'm used to use MidiPipe for everything. But IAC is just much easier to use in this case. (First time I ever used it. )

I take no credit. This is all the work of Nixon Hambone and Machinate (and of course Conny!)

I just felt it deserves some more exposure immediately.

http://www.ableton.com/forum/viewtopic. ... 167#210167

There should be stickies (imo)

Edit: please include Hoffman2k in this list! I was so careful to put Nixon, who I seldom interact with that I forgot one of the most important playa's!

telekom · Post by **telekom** » Thu Dec 29, 2005 12:58 am

supster wrote: I tend to write using clip lengths of 4 bars. So I normally think in terms of trigging the next row of clips every 4 bars. Often I'm not really looking to have to trigger them 'live', manually ...

Hi supster,
I haven't checked out the midi yoke method, but if conny did it I bet it's cool.

However, can't you just do what you say above by having the same follow action in each track set to four bars? Basically when you launch the first scene, the 4 bar follow action will trigger the next scene down (or whatever you program it to do) after 4 bars (if you program it to do that).

Or am I missing something from your post? I may not have understood what you're looking for.
HTH

Machinate · Post by **Machinate** » Thu Dec 29, 2005 1:46 am

LOFA wrote:I take no credit. This is all the work of Nixon Hambone and Machinate (and of course Conny!)

I just felt it deserves some more exposure immediately.

http://www.ableton.com/forum/viewtopic. ... 167#210167

also, don't forget hoffman2k

We've actually had lenghty discussions on this topic a while back, I wonder if someone could dig up the most informative one, and add it to hoffman2ks list?

LOFA · Post by **LOFA** » Thu Dec 29, 2005 7:51 am

Machinate wrote:
LOFA wrote:I take no credit. This is all the work of Nixon Hambone and Machinate (and of course Conny!)

I just felt it deserves some more exposure immediately.

http://www.ableton.com/forum/viewtopic. ... 167#210167

also, don't forget hoffman2k
We've actually had lenghty discussions on this topic a while back, I wonder if someone could dig up the most informative one, and add it to hoffman2ks list?

All taken care of!

TheAnimal · Post by **TheAnimal** » Thu Dec 29, 2005 9:07 am

LOFA wrote: I take no credit.

So you're getting the credit of repeating it exactly when I needed it!

The biggest problem when information is abundant is retrieval. Unfortunately I am no exception to that rule.

hambone1 · Post by **hambone1** » Thu Dec 29, 2005 10:14 am

I'm building all of my lighting, video, and surround sequencing and control in Live using the IAC driver technique. Combined with follow actions, I'm getting faster at sequencing custom choreographed lighting and video for each audio track.

So much to do... so little time... no more new ideas, please Conny, Machinate & Hoffman2K!

Machinate · Post by **Machinate** » Thu Dec 29, 2005 11:03 am

hambone1 wrote:So much to do... so little time... no more new ideas, please Conny, Machinate & Hoffman2K!

hehe, that really only depends on the feature sets included in Live 5.1 (shouldn't be that long until we see that) and Live 6, in 6-7 months - we start doing the tricks in the beta-period

hoffman2k · Post by **hoffman2k** » Thu Dec 29, 2005 11:14 am

Machinate wrote:
hambone1 wrote:So much to do... so little time... no more new ideas, please Conny, Machinate & Hoffman2K!
hehe, that really only depends on the feature sets included in Live 5.1 (shouldn't be that long until we see that) and Live 6, in 6-7 months - we start doing the tricks in the beta-period

I already got tricks for features that are not implemented yet.
I don't know if they will ever be implemented....
But it wouldn't be the first time that we need to figure out a work-around.