Thank you SO much. Relatively new to the ableton game after running tracks off an SPD-SX for years and have been getting increasingly exasperated that I couldn't find a midi triggerable equivalent of shift + space, but you've given me the answer (or damn near close enough). Huge help!
Just a little suggestion: instead of mapping to a specific locator, you can map the note to the “next locator” button. This way you don’t need to create a midi clip for every locator.
I use previous locator often, but I personally would stay away from it for this use. 1-Whenever students have issues with this technique, it’s normally because they’re mapping “previous locator” and it isn’t always consistent. 2-Using a dedicated locator allows me to re-program my set easily. Because I do this in my template, I only had to map my locators and clips once
@@fromstudiotostage so glad I just read your comment! I tried using the "next locator" button and was getting inconsistent results. Very unreliable. I've now done it the way you suggested and it's works reliably and consistently! Just when I thought, "hmm, maybe I thought of something that Will isn't thinking of and I'll program a different button that's better than what Will is using!" and sure enough...Will's way is better! Will already knew that!! Of course he did! thank you brother!
Thank you again! This gets me closer to a stop/jump to solution. Unfortunately the video is missing some key steps to make this work for multiple songs in a sequence. A. You can Copy/Paste the Stops to multiple locations. B. But you can't with a Jump To. Make sure each Jump To is a unique MIDI note for the mapping. Map each one carefully. Other problems experienced: 1. Stop ignored after copy/paste to new location. Eventually this did work. Unclear why for the first hour of hacking away it didn't. Just removed all MIDI mapping and started over 3x's and eventually it did. Whew. 2. After stop jump too ignored - always jumped to Song 2, this also stopped happening after a time. Seems to be the Spacebar playback head was "stuck there". If things don't work, remove all MIDI mappings (right click on target) and start again. Eventually things will work.
I'm having an issue. I can get the playhead to skip to the Song 2 marker but it doesn't stop, it keeps on playing. I'm using Windows 10. I'm using a generic midi driver called loopMIDI.
I have set everything up correctly (From what I can tell) and when the midi note triggers to go to the next locater it doesn't pause at the locater like yours did in the video.It just triggers the next song and starts the song. Any tips on how to get Ableton to stop when it goes to that next locater?
Strangely, the STOP track works perfectly, but this method doesn't work for me. The track stops and the play locator jumps to the correct next locator, but it jumps back to STOP when I press play. When I press PLAY a second time, it jumps to the correct location.
Hi, thank you for the information! There is an issue though with assigning locators to notes. Whenever i use midi controllers as remotes, the notes on the keyboard take me to the locators. Is there any way to avoid this?
Can I use this to automatically open another (or the next) .ALS file? Each of my songs has its own ALS and because there are a large number of midi cues in each song, it would be unmanageable to create entire sets for each permutation, and thus recreating the cues and backing tracks of each song. Or is there another way they can all fit together without doing this?
Will - your videos are very helpful. thanks much. I'm using Ableton Live 11 Intro. Question - For some reason the jump to locator automation only happens at the END of the clip ( 1 measure) When I use the stop track + the go to next clip - Ableton just stops and is not able to use the jump to locator on the other clip. driving me a bit nuts. other triggers like metronome on/off happen at the beginning of the clips but not jump to locator... I'm doing something wrong but have no idea what it is. thanks
Really helpful, thanks! Do you have any videos that go into more detail on saving the mappings for use in other projects like you mention around 2:05-2:25?
Hi Ronnie, that’s deff. possible, but I’ve run into issues using previous locator in this context, and would jump to the wrong locator, which is why I teach it this way in particular
This is my overall FAVORITE feature discovery for Live. Thanks Will!
Really cool tips. I’m starting to play with this type of automation myself. Good vids man.
Thank you SO much. Relatively new to the ableton game after running tracks off an SPD-SX for years and have been getting increasingly exasperated that I couldn't find a midi triggerable equivalent of shift + space, but you've given me the answer (or damn near close enough). Huge help!
Glad to help!
Just a little suggestion: instead of mapping to a specific locator, you can map the note to the “next locator” button. This way you don’t need to create a midi clip for every locator.
I use previous locator often, but I personally would stay away from it for this use. 1-Whenever students have issues with this technique, it’s normally because they’re mapping “previous locator” and it isn’t always consistent. 2-Using a dedicated locator allows me to re-program my set easily. Because I do this in my template, I only had to map my locators and clips once
@@fromstudiotostage so glad I just read your comment! I tried using the "next locator" button and was getting inconsistent results. Very unreliable. I've now done it the way you suggested and it's works reliably and consistently! Just when I thought, "hmm, maybe I thought of something that Will isn't thinking of and I'll program a different button that's better than what Will is using!" and sure enough...Will's way is better! Will already knew that!! Of course he did! thank you brother!
Thank you again! This gets me closer to a stop/jump to solution. Unfortunately the video is missing some key steps to make this work for multiple songs in a sequence. A. You can Copy/Paste the Stops to multiple locations. B. But you can't with a Jump To. Make sure each Jump To is a unique MIDI note for the mapping. Map each one carefully. Other problems experienced: 1. Stop ignored after copy/paste to new location. Eventually this did work. Unclear why for the first hour of hacking away it didn't. Just removed all MIDI mapping and started over 3x's and eventually it did. Whew. 2. After stop jump too ignored - always jumped to Song 2, this also stopped happening after a time. Seems to be the Spacebar playback head was "stuck there". If things don't work, remove all MIDI mappings (right click on target) and start again. Eventually things will work.
Thanks for the kind words! This is a short tutorial, but I go step by step through the process in the IAC driver course
Hey Audio Terrorist. Looks like I am hitting the same wall you did. Ideas?
thanks for the idea, it does help greatly to a drummer on ableton living
Do you have a video on creating the go-to-next templates you spoke of in the beginning? Thanks!
Still looking for it. Did you found it? 🙏🏼
I'm having an issue. I can get the playhead to skip to the Song 2 marker but it doesn't stop, it keeps on playing. I'm using Windows 10. I'm using a generic midi driver called loopMIDI.
Hi great video, though what about a PC? How can you stop a track and then go to the next through a PC? Thank you
How do we create a template with these things?
I have set everything up correctly (From what I can tell) and when the midi note triggers to go to the next locater it doesn't pause at the locater like yours did in the video.It just triggers the next song and starts the song. Any tips on how to get Ableton to stop when it goes to that next locater?
Strangely, the STOP track works perfectly, but this method doesn't work for me. The track stops and the play locator jumps to the correct next locator, but it jumps back to STOP when I press play. When I press PLAY a second time, it jumps to the correct location.
Hi, thank you for the information!
There is an issue though with assigning locators to notes. Whenever i use midi controllers as remotes, the notes on the keyboard take me to the locators. Is there any way to avoid this?
thanks for sharing
This is so great! Exactly what I needed. Thank you!
so helpful! cheers
This doesn't work for me when I play the entire song through. it always seems to jump to a random locator or a previous locator. Any advice?
Can I use this to automatically open another (or the next) .ALS file? Each of my songs has its own ALS and because there are a large number of midi cues in each song, it would be unmanageable to create entire sets for each permutation, and thus recreating the cues and backing tracks of each song. Or is there another way they can all fit together without doing this?
Brillinant!
Will - your videos are very helpful. thanks much. I'm using Ableton Live 11 Intro. Question - For some reason the jump to locator automation only happens at the END of the clip ( 1 measure) When I use the stop track + the go to next clip - Ableton just stops and is not able to use the jump to locator on the other clip. driving me a bit nuts. other triggers like metronome on/off happen at the beginning of the clips but not jump to locator... I'm doing something wrong but have no idea what it is. thanks
sounds like track delay isn't set correctly.
Really helpful, thanks! Do you have any videos that go into more detail on saving the mappings for use in other projects like you mention around 2:05-2:25?
Did you ever find out how to do this? I'd love to be able to save it for quicker use in other projects.
Great Advise, thanks!
Is there a way to do something similar in session view, with each scene being one song?
As long as “Select Next Scene on Launch” is enabled, that’s the natural state of Session view.
instead of IAC Driver mapping each start-of-song locator in your whole set, you could just map the previous/next locator buttons
Hi Ronnie, that’s deff. possible, but I’ve run into issues using previous locator in this context, and would jump to the wrong locator, which is why I teach it this way in particular