3 ms·
I'm currently testing an M1-based Air to see if I'd like to purchase something similar. I can confirm this for sure; the project files that made my current, not
by readyp1 5y ago
I'm currently testing an M1-based Air to see if I'd like to purchase something similar. I can confirm this for sure; the project files that made my current, not-even-old Windows laptop with similar stats choke are running like a dream even on this Air.
BTW, if you have a license for Live 11, version 11.1 forward has a Universal build, so it can run natively on M1 Macs rather than through Rosetta. [0]
[0] https://help.ableton.com/hc/en-us/articles/115001261150-Mac-Compatibility-with-Live https://help.ableton.com/hc/en-us/articles/115001261150-Mac-...
- tallytarik 5y agoThe parent commenter's problem sounds like it's third-party plugins rather than Live itself. FL Studio also has a build for ARM, but it runs each non-ARM plugin in a wrapper which somehow uses an entire CPU core. After loading more than a couple of plugins I see something that is otherwise unheard of on my M1 Macbook - 1000% CPU usage and fans at full speed. So I stick to running the app via Rosetta - higher-than-average CPU usage in general, but it means my plugins behave.
- ungamedplayer 5y agoAlso, you can't compare io work on OSX to anything else, it's fsync () is a no-op. When file cache can stream to disk at a delay, io always looks super fast. I guess the risk of data loss is acceptable .