Ableton Live 11
- KVRAF
- 3646 posts since 21 Nov, 2015
Actually always had a pretty stable M4L environment in Live 10; yet also using the most recent updates by the Developer and leaving the more older ones out. Which can be a Problem, in case you want to use those older #tools which might not be maintained anymore. So, yepp - also hoping for slight #improvement in Live 11, here. Overall the #Update is looking pretty great, though.
You can be creative in any right place on Earth, and not only in the wealthiest cities. Bring the world feelings from everywhere, and not only feelings of capitalistic or jail environment.
― Aleksey Vaneev
https://linuxdaw.org
― Aleksey Vaneev
https://linuxdaw.org
-
- KVRist
- 120 posts since 11 Oct, 2020
I'm on Windows 10. My impression with the stability thing from searching around for solutions is that it almost seems like the luck of the draw on the individual system regardless of OS.. My mate was solid as a rock with 10 even on an older iMac.pdxindy wrote: Thu Dec 03, 2020 5:49 pmGood to hear... what OS? I'm on OSX. I don't recall if there was any difference in stability between platforms.
Even with my issues it was weirdly inconsistent and basically impossible to reproduce anything. Like it had a mind of its own!
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
Mostly Windows user on a daily basis but iMac on a weekend and the beta hasn’t crashed once from day 1 of the beta release.
Very happy and purchased the upgrade. Haven’t used any other daw since, and I’m using it for my production.
A new world of production it’s opening up and I’m extremely please with the new features keeping the DAW evolution consistent with the established workflow.
Very happy and purchased the upgrade. Haven’t used any other daw since, and I’m using it for my production.
A new world of production it’s opening up and I’m extremely please with the new features keeping the DAW evolution consistent with the established workflow.
ABEFLGMOPPRRST 
-
- KVRAF
- 2296 posts since 23 May, 2012 from London
M4L has always been a bit temperamental on my main Windows machines but absolutely solid on my now 11yo MBP. I've generally avoided becoming to reliant upon it and when I do use it at the very least I freeze or resample and then disable, to help with stability. I choose my synths based on their modulation capabilities and usually program most of my movement there, but it's nice to use the LFOs to modulate third party FX and I'm using the Expression Control device a lot these days for keytracking EQ and multiband crossovers on my bass patches.Mumdad wrote: Thu Dec 03, 2020 7:15 pmI'm on Windows 10. My impression with the stability thing from searching around for solutions is that it almost seems like the luck of the draw on the individual system regardless of OS.. My mate was solid as a rock with 10 even on an older iMac.pdxindy wrote: Thu Dec 03, 2020 5:49 pmGood to hear... what OS? I'm on OSX. I don't recall if there was any difference in stability between platforms.
Even with my issues it was weirdly inconsistent and basically impossible to reproduce anything. Like it had a mind of its own!
Always Read the Manual!
-
- KVRist
- 222 posts since 9 Jun, 2019 from Brisbane Australia
No crashes here on beta 11 yet, using it once a day. On 10, even the old max LFO would crash Live sometimes if I stacked a few of them up. I think though its still basically a Max device they have improved something in making it a somewhat native device, as AFAIK it will be available to non Max owning Standard Live users.
As for the locking of parameters once modulated, yeah it can be annoying. We can always still automate or modulate the modulator itself, for example assign an envelope to the LFO 's offset. Plenty of options if you don't mind cluttering up your rack a little with extraneous modulators.
Really though if I want that extra layer of control now I always go for (in Session mode) unlinked automation clips. Those things are powerful, and super easy to build complex stuff with the 'right click, add and skew shapes' .
Otherwise there's the Reason rack (I picked it up free, but own a bunch of cool stuff bought for version 10 standalone) and it let's you modulate anything , and anything as much as you want. It was the original mod king before Bitwig came along.
Live's no slouch though and with the added options above plus paid things like Modulat and free monster mod synths like Vital about, I reckon Ableton have time to focus down on bigger improvements elsewhere.
As for the locking of parameters once modulated, yeah it can be annoying. We can always still automate or modulate the modulator itself, for example assign an envelope to the LFO 's offset. Plenty of options if you don't mind cluttering up your rack a little with extraneous modulators.
Really though if I want that extra layer of control now I always go for (in Session mode) unlinked automation clips. Those things are powerful, and super easy to build complex stuff with the 'right click, add and skew shapes' .
Otherwise there's the Reason rack (I picked it up free, but own a bunch of cool stuff bought for version 10 standalone) and it let's you modulate anything , and anything as much as you want. It was the original mod king before Bitwig came along.
Live's no slouch though and with the added options above plus paid things like Modulat and free monster mod synths like Vital about, I reckon Ableton have time to focus down on bigger improvements elsewhere.
Last edited by zoidkirb on Fri Dec 04, 2020 4:26 am, edited 1 time in total.
- KVRist
- 130 posts since 8 Apr, 2019
Just sharing my own experience with M4L: i never had a crash or performance drop due to M4L. Those "native" LFOs in M4L are simply too heavy on CPU, i don't use them. If i need to go crazy with sound i choose synths and effects that have inbuilt LFOs. I use M4L only for sequencers, BiP(aka Bounce in Place), Granulator2 and random devices that i just found interesting but never bothered to even use them second time in another project. So far no problems.
-
- KVRian
- 726 posts since 29 Jun, 2020
Have they fixed arrangement view group header size? The minimum size is 2 units, whether or not you are showing automation. Complete waste of space, no reason it can't just be one unit. It shows a shadow version of the groups in the track, which is totally pointless if you have the group open and can see the group tracks anyway. And groups within groups just multiplies the wasted space and you end up with rows and rows of empty space in arrangement view.
-
- KVRian
- 726 posts since 29 Jun, 2020
The automation button just hides automation. It would be better if it collapsed the group header size to 1 too, the second unit down being a lane for automation, or if this was able to be done via usual resizing operations
-
- KVRian
- 726 posts since 29 Jun, 2020
-
- KVRian
- 719 posts since 4 Feb, 2017
No it isn't.