how to automate CC's within ableton
OK, I'm getting somewhere:
Controller data are captured if they are assigned to a knob etc.
So I can't record them in clips and have them assigned at the same time?
// C
Controller data are captured if they are assigned to a knob etc.
So I can't record them in clips and have them assigned at the same time?
// C
PC Laptop Acer, XP Home SP2, build in crappy sound card.
Bleeps and Blops!
http://bluemoose.greatnow.com/
Bleeps and Blops!
http://bluemoose.greatnow.com/
Ok, so I set Live exactly the way Ryan suggested (I'm on a pb g4). This tip allows you to record CC automation into the individual clips, correct? I thought this was already possible...Even without doing what was suggested I'm able to record automation into my clips. What does it exactly do? Sorry for the stupid question. I've been using Live for the past year and I thought I had a grasp on it, but maybe I should think otherwise.
So, if someone could clear up what this actually does in terms of making my live experience better, It'd be greatly appreciated. Thanks.
So, if someone could clear up what this actually does in terms of making my live experience better, It'd be greatly appreciated. Thanks.
-
- Posts: 1743
- Joined: Sun Jul 11, 2004 5:07 am
- Location: Melbourne AU
- Contact:
Conny, the idea is that you can record your controller movements into clips in a midi track. in workflow terms the midi controller (in your case the keystation) goes into a midi track and gets output to a midiyoke thats only set as a remote input in live. that way you can record clips of your controller movements into that track and let them loop as automation while you twiddle other knobs (so to speak..) it sounds like you're merging two tracks in some way which isn't really whats going on here (although you can do it if you want to...)
zfigz, you can record CC's in midi clips in session view, but you can't record them into existing audio clips (very well... ). using the stuff in this post you can capture your controller movements live and loop them back effectively creating your own clip automation and leaving your hands free to do something else.
as far as your live experience goes, it means you record your automation once in a clip in a single track instead of turning record arm buttons on and off and changing where the control inputs get routed to and reassigning stuff per track... all things i know i like to avoid doing too much of when performing. it's probably not really useful for doing intricate stuff if you're working in arrangement view as you can take the time in that situation to reassign and tweak things, but for live work it can be a helpful thing to use.
the other thing to remember also is that you can take your controller in through as many tracks as you like and route them out through 16 midi channels on 16 different midi yokes meaning you could have up to 256 different assignments for each knob on your controller depending on which midi tracks you have muted and/or unmuted.... ie you can have 256 presets for your controller through routing in live...
zfigz, you can record CC's in midi clips in session view, but you can't record them into existing audio clips (very well... ). using the stuff in this post you can capture your controller movements live and loop them back effectively creating your own clip automation and leaving your hands free to do something else.
as far as your live experience goes, it means you record your automation once in a clip in a single track instead of turning record arm buttons on and off and changing where the control inputs get routed to and reassigning stuff per track... all things i know i like to avoid doing too much of when performing. it's probably not really useful for doing intricate stuff if you're working in arrangement view as you can take the time in that situation to reassign and tweak things, but for live work it can be a helpful thing to use.
the other thing to remember also is that you can take your controller in through as many tracks as you like and route them out through 16 midi channels on 16 different midi yokes meaning you could have up to 256 different assignments for each knob on your controller depending on which midi tracks you have muted and/or unmuted.... ie you can have 256 presets for your controller through routing in live...
Hp Elitebook 2.8Ghz. Live 7.0.14 & Live 8.1.5, XP Pro. and stuff...
This may help?
USB device is midi ctr source.
Midi Yoke 4 is used for external control in, USB is not set so in prefs.
// C
USB device is midi ctr source.
Midi Yoke 4 is used for external control in, USB is not set so in prefs.
// C
PC Laptop Acer, XP Home SP2, build in crappy sound card.
Bleeps and Blops!
http://bluemoose.greatnow.com/
Bleeps and Blops!
http://bluemoose.greatnow.com/
I do a lot of CC stuff with the IAC driver. I've got buttons for 2, 4, 8, 16, 32, and even 64 beat automated smooth crossfades, as well as automatically setting up all BCR2000 settings (Click track volume, Deck A and Deck B volumes and sends to front and rear for main track, 4 loops, live percussion and IEM... lots of sends!) on scene launch. I'm still mesmerized watching the BCR LEDs jumping to their new positions, or automatically scrolling around the crossfade knob (I'm easily amused...)
It works great! I'm learning the BCR ergonomics, too. Don't put a track stop button near a crossfade button! I put the Deck A controls on the left, B on the right, common controls on the front row (scene scroll, tempo, crossfade, IEM), FOH sends on the middle row, and rear PA sends on the back row.
It works great! I'm learning the BCR ergonomics, too. Don't put a track stop button near a crossfade button! I put the Deck A controls on the left, B on the right, common controls on the front row (scene scroll, tempo, crossfade, IEM), FOH sends on the middle row, and rear PA sends on the back row.
Last edited by hambone1 on Sun Jan 15, 2006 4:19 pm, edited 1 time in total.
i feel like there's a larger trend going on of people diving deeper and deeper into control ergonomics for ableton -- so that their hands can move as fluidly as the software does.
this isn't ready yet, but this is the Dashboard Widget that will handle all my midi control routing in Ableton. It allows the free assignment of piano keyboard ranges to different tracks. It allows each audio track to use Impulse (dr.sample icon), Simpler (xylophone icon), or Audio Track (tape machine icon). It also allows the association of the MIDI controller's knob ranges to a given track (notice the doorknob on top of one of the icons).
this isn't ready yet, but this is the Dashboard Widget that will handle all my midi control routing in Ableton. It allows the free assignment of piano keyboard ranges to different tracks. It allows each audio track to use Impulse (dr.sample icon), Simpler (xylophone icon), or Audio Track (tape machine icon). It also allows the association of the MIDI controller's knob ranges to a given track (notice the doorknob on top of one of the icons).
Widget? I have not bothered with this function of tiger yet- I am still experimenting with agregate devices and oter things. If you don't mind telling me, how does this picture translate as a widget?
Also, thank you for posting this trick. I have already had luck with sending midi out of live to the iac, and back to live to start clips, but I don't have a grasp on all of this yet. Once I have exhausted all of the information on parallel, url'd threads, and had the chance to do a little research, I will post with a few more direct questions.
Also, thank you for posting this trick. I have already had luck with sending midi out of live to the iac, and back to live to start clips, but I don't have a grasp on all of this yet. Once I have exhausted all of the information on parallel, url'd threads, and had the chance to do a little research, I will post with a few more direct questions.
Im really bad at this stuff please bear with me.conny wrote:This may help?
USB device is midi ctr source.
Midi Yoke 4 is used for external control in, USB is not set so in prefs.
// C
Which track do i drop the vsti in? once i do that the ouput turns into audio.
so USB Device = hardware controller?
What is midi yoke 4?