Closed for Company Meetings: Between September 18 (5pm PDT) and September 22 (12pm PDT), Support and Sales requests will be delayed. Only time-sensitive issues will be addressed during that time. Thanks for your patience.
CPU (again)
Feb 01 2014 | 3:31 pm
I've been away from the Max world for a while, but started tinkering again today with my projects.
Lately I've started using Ableton Live for music, and noticed how CPU efficient it is at some tasks (notably drawing the spectrum display in the equaliser). I thought how nice it would be to have the same graphical quality and update rates in Max with the same efficiency.
Most of us know about Max's cranky objects(waveform~, meter~, etc), and then have to work around them. In the past I've done all sorts of peculiar workarounds to try and get the CPU down in my patches, but have started to wonder if it wouldn't be too much for C74 to make some of the core objects a bit more efficient?
Does anyone think this is this on the horizon, or are we stuck until Max... 10??
- Feb 01 2014 | 5:19 pmHi mike . ive got similar wishes . what can surprise you also is significantly huge difference between playing back audio samples in Ableton comparing to playing back those with your own Max setup (or M4L) . u will notice that playing with groove and others is much more expensive than playing back samples with Ableton sampler which is suited with filters , envelopes and interpolation at start . things getting worster when you compare it with polyphonic playback . Ableton sampler show no difference , but poly~ with groove has huge cpu impact .
- Feb 01 2014 | 5:31 pmWell yes, but can you edit Live's devices while audio is playing? No, you'd need to recompile the source code to make a change.
- Feb 01 2014 | 5:42 pmits not worth the price :) i would prefer efficiency first ,then comfort of editing , which is mainly in conjunction with developing stage . if i want USE my device then it means im not in developing stage , rather consuming it
