Live performance on M1
-
- KVRAF
- 2140 posts since 16 Jan, 2013 from USA
So there's an M1 Mini at work that I've fired up Live 10 on. It's extremely snappy in all basic operations, but it does hit the CPU hard during playback. I'm wondering if that's because some of the code isn't actually being translated, but emulated at run time. Anyone with experience or info on what's going on?
-
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
If you're on beta, there's thread about it:
https://ableton.centercode.com/project/ ... BFD038CA23}
Sounds like it's a mixed bag.
https://ableton.centercode.com/project/ ... BFD038CA23}
Sounds like it's a mixed bag.
-
- KVRer
- 23 posts since 12 Feb, 2021
I am using Ableton Live 10 Lite for testing my plugins which i compile on Macbook Air M1. The Interstellar Waterphone 1.0 plugin is running more much better under Ableton 10 than Reaper 6. Ableton gained my point here.
-
- KVRian
- 504 posts since 12 Oct, 2003
Ableton just released a new Live10 Beta (10.1.35) with M1 improvements along with a lot of bug fixes.
This is a very class act few days before the official 11 release.
10.1.35b1 Release Notes
New features and improvements:
Users should see more reliable engine performance on machines with the Apple M1 CPU.
Updated the bundled Max build to version 8.1.9.
Bugfixes:
Audio hangs if in Live 9 created Simple Delay clip automation on audio track is changed in the Delay Device
Fixes a bug that caused Live to enable the Warp switch and to reset the audible region of unwarped audio clips when locating missing samples or replacing sample files on disk under certain circumstances.
Fixed an issue where starting playback via the Novation Launchkey Mini MK3, Launchkey MK3 or Launchpad Pro MK3 control surface scripts could result in MIDI notes getting cut off. With the Launchkey MK3 control surface script, it is now possible to continue playback by holding down the Shift button and pressing the Play button.
Previously on macOS, Live's installer did not ask the user to accept the EULA when mounting the disk image from the command line.
MIDI notes from the Oxygen Pro keyboard are now sent to MIDI track inputs by default when the keyboard is autodetected.
Previously, a visual glitch could appear around the Groove Pool selector button, under certain circumstances.
Fixed an issue where a pending auto-update would sometimes not be applied after downloading. (Note: this fix only affects auto-updates to future versions of Live.)
Previously, the Operator device could crash or calculate inaccurate frequencies when its Fixed Mode and Spread parameters were enabled.
The EQ Eight device will now scale its displayed spectrum the same way as the Channel EQ and Hybrid Reverb devices.
Live's window no longer turns red when loading a Set with missing plug-in devices.
Previously, Live would hang when turning its audio engine off, under certain circumstances.
Fixed a bug that prevented certain low-resolution plug-in devices from scaling correctly on macOS.
Fixed a crash that could occur when cancelling an "Export Audio" operation during the "Wait for silence" step.
Fixed a crash that could occur when running certain plug-in devices.
This is a very class act few days before the official 11 release.
10.1.35b1 Release Notes
New features and improvements:
Users should see more reliable engine performance on machines with the Apple M1 CPU.
Updated the bundled Max build to version 8.1.9.
Bugfixes:
Audio hangs if in Live 9 created Simple Delay clip automation on audio track is changed in the Delay Device
Fixes a bug that caused Live to enable the Warp switch and to reset the audible region of unwarped audio clips when locating missing samples or replacing sample files on disk under certain circumstances.
Fixed an issue where starting playback via the Novation Launchkey Mini MK3, Launchkey MK3 or Launchpad Pro MK3 control surface scripts could result in MIDI notes getting cut off. With the Launchkey MK3 control surface script, it is now possible to continue playback by holding down the Shift button and pressing the Play button.
Previously on macOS, Live's installer did not ask the user to accept the EULA when mounting the disk image from the command line.
MIDI notes from the Oxygen Pro keyboard are now sent to MIDI track inputs by default when the keyboard is autodetected.
Previously, a visual glitch could appear around the Groove Pool selector button, under certain circumstances.
Fixed an issue where a pending auto-update would sometimes not be applied after downloading. (Note: this fix only affects auto-updates to future versions of Live.)
Previously, the Operator device could crash or calculate inaccurate frequencies when its Fixed Mode and Spread parameters were enabled.
The EQ Eight device will now scale its displayed spectrum the same way as the Channel EQ and Hybrid Reverb devices.
Live's window no longer turns red when loading a Set with missing plug-in devices.
Previously, Live would hang when turning its audio engine off, under certain circumstances.
Fixed a bug that prevented certain low-resolution plug-in devices from scaling correctly on macOS.
Fixed a crash that could occur when cancelling an "Export Audio" operation during the "Wait for silence" step.
Fixed a crash that could occur when running certain plug-in devices.
-
- KVRAF
- 2036 posts since 15 Mar, 2002 from Seattle, WA - USA
That’s a nice move by Ableton to continue improving L10 on the eve of L11’s launch. It’s been surprising just how well it runs, save for the CPU usage where it seems like the whole program is just running on one processor core. I’ll be curious test out this beta.
-
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
M1 is literally a new CPU, so how can you have both?Tronam wrote: Sat Feb 20, 2021 9:58 pm...It’s been surprising just how well it runs, save for the CPU usage...
-
- KVRAF
- 2036 posts since 15 Mar, 2002 from Seattle, WA - USA
Mainly because the stability, plugin compatibility, M4L, overall snappiness, etc... has been far better than expected considering this version of Live was coded for a completely different architecture. The CPU usage just seems higher than it should be compared to many other x86 apps running under Rosetta.