Exactly- 10% will be 100s of useful MAX/Extensions- I’ll take that. Definitely better than nothing whilst we wait for things to be coded in by the Ableton Team, and this is a free minor point update, nothing you have to use, its just a single line entry in a menu so easily ignored unlike the ‘hard coded’ clutter I have seen in my other DAWS.
3 Likes
Lol, this again. Still think this line of criticism is kinda silly - I just can’t see how it’s supposed to be a bad thing that there are a range of options for implementing your own custom approach. And imho fundamentally misunderstands what Live actually is - it’s probably the most popular ecosystem for electronic production exactly because it’s wide open to be tweaked into working the way a lot of different people want it to work.
And on the other hand, a lot of the time I see people complaining about “basic” features these days, they explain what they’re trying to do and I’m thinking … ok I guess, but while that might sound obvious to you it seems niche as hell to me. People really have a pretty much limitless different ways of using this thing.
I don’t think there’s really many things I’d consider “basic” that Live is missing at this stage, give or take having its own approach at certain points that can be hard to see when carrying over assumptions from other gear or DAWs.
Although, full disclosure - I’m pretty unenthused by extensions at least right now. So I don’t use 'em. And for max devices, the only one I use regularly that I’d consider a utility has a bunch of options for routing midi between tracks. Which I personally would like to see implemented natively for sure, but I’m equally sure that there are a lot more users who would get their heads melted by the additional complexity that they don’t need.
Which I think is the point - if Ableton implemented everyone’s “basic” ask it’d end up being an absolute and utter Homercar. But if you really care that much about it doing the thing, as opposed to complaining about the developers, they’ve opened it up to the extent that there’s probably a way to get on with it and make music
20 Likes
Chains are the ‘layers’ in a rack (device chains as the manual also calls them). The Chain Selector is something else.
Yep. But for those not used to that general term, they might be clicking on the Chain button and adding them there. Which won’t work.
I remember seeing a cool technique that allows you to change and/or automate the position of this loop region on the fly, and I wouldn’t be able to find whatever video this was for the life of me. Does anybody do this? What are some cool approaches?
1 Like
You can midi-map the loop’s Position (changes the loop brace itself, keeps the start point within the loop too) or you can use the lesser known Nudge FWD/BWD feature tucked away on the Launch tab, (2 small circular buttons above the Legato button) which will move the start point within a loop, in-time)
8 Likes
Hi, i just started using Ableton Live 12 to hopefully get rid of an anoying problem with the Akai Force as it doesnt slave well. I come from Cubase which doesnt support Ableton Link.
I also got a Nome II.
Ive been testing sync and everythings seems very good with the Nome sending midi clock to my gear. But when i enable ableton link to get the Force in sync it drifts a bit during recording. Its getting more and more off. I can also see that the reported tempo on the recordings shift from 143.00 to 142.99 when enabling Link.
Anybody else have experience with Ableton link in combination with sync boxes like the Nome, Multiclock or similar?
Have you tried Ableton Link with Akai Force without using the Nome II?
I use an MPC and get good sync using Ableton Link and I don’t have another sync device.
That seems to work fine. The Akai series isnt known for beeing very tight, so it looks like it is as normal.
I try not to look at fluctuating bpm’s too much. The metric that I use with the MPC (this would be the same with the Akai Force), Is when syncing via ableton link, can I get tight audio clips recorded with no clicks that sound in time at 140bpm. In my head if it sounds tight with perfect loops that’s good enough.
3 Likes
I don’t know about link, but fluctuating bpm is something I’ve gotten used to when the mpc is the lead and the digitakt is the follower via 5pin MIDI and I completely ignore this fluctuation because when I record to the daw, the resulting recordings are 100% on grid always so whatever the screen reads means nothing when the stuff coming out of the output is locked in.
3 Likes
100%. I have the mpc sending midi to a midi>cv module which sync’s to PAM which clocks my modular system. BPM is all over the place on PAM’s screen, but the audio clips are perfect. As much as I hate seeing the bpm bounce, the sound is what matters.
3 Likes
First time I’ve seen someone refer to the 2020s as the 20s. I like it.