Use the Max for several years, always used as a tool of analysis, as an interface between programs and hardware, reader sensors, such as a filter. I did small patches, fx and synths, etc ...
I needed to make a looper for playing live, SooperLooper, Mobius and less "Live" could cover my exact needs. I thought Max could do it, bah I thought I could develop something in time, try "record ~", "groove ~" but needed to synchronize with a master track, plus some midi functionality, also had to change the speed and working with loops of variable size and no default.
A buffer of larger, phasor and objects rate, index and poke, poke and then wave (even try iPoker) but nothing when I solve the clicks clicks on one hand emerged on the other hand, finally looking at the forum I found other users with similar experiences, concern for the sample holly Tim Lloyd, Andrew Benson's solution, ~ 0.5 round, index and interpolation, artifacs and artifacts ... The frustration was before I remembered that many of the projects face in the Max FEASIBLE not always ended up being "practical" and above all reliable.
Max is still a good option to use along with any MIDI controller or atmega, fx is served to test for fft but I do not need to be thought of as a programming system and the unavoidable drawbacks are many.
It's not just my ignorance but I did not find a single case where a user has solved all these problems, the solutions always dealt leave out some functionality, counting samples, time domain, no one is sending messages is itself a full choice of some characteristics or mode of infrastructure has a very clear limit.
If you want a live looper with some type functionality like mobius or SooperLooper
Do not waste time with Max.