Ableton Forum

not a fair comparison. to get mu working you'll need to purchase max for live and the lemur app. if you just want to control live, touchable is great, more than capable, and great value. the mu/lemur/m4l ecosystem definitely packs a powerful punch. however i think it'll take a few more months before...

It's good to remain positive...after all, if MIDI sync has finally been addressed after all these years maybe there's hope yet for m4l timing

crashes have been occurring in arrangement view...all i'm doing is opening and closing projects or renaming files. more bugs with the latest update...haven't tested in session view yet. however, i think i'm going to stick with 8.2.1 for live performance. btw, i'm on os x 10.6.7.

How about Numark's DJ2GO:

http://www.numark.com/dj2go

It's like Korg's nano series controllers.

great tutorial:

http://www.jethroe.com/2010/01/28/how-t ... on-live-8/

I notice there has been more M4L improvements with the latest beta release (8.2.2b3). Any chance we could get some development love to tighten the move playing position?

awesome! can't wait to try it out

awesome tips! thanks for sharing

thanks for the update...and good luck with tomorrow's demo

there is a [timepoint] object for the global timeline that triggers a bang at any specified position. Perhaps something similar could also be implemented for individual clips.. would this need to be implemented in live itself or can this be done in max for live? it's good to know what can be causin...

i'll give this a try tomorrow when my collaborator comes over with his serato rig. currently we're leaning towards abandoning the Bridge (for the time being) and just running separate instances of Live and SSL

@broc would this implementation of the observers explain the timing problems between live and max for live? it sounds as if a possible solution would be to significantly decrease the polling interval...which may of course adversely affect performance. anyway, just trying to get a better understandin...

i wonder if it wouldnt be very nice and usefull when the slave just smoothly adjusts to that external clock but keeps his actual timing offset up to the next restart event..this way one can prepare for slave operation by switching the EXT button without damaging the performance and the straight res...

i think the test results would be more meaningful if i could actually calculate the mean value of the tempo fluctuations. as nico stated earlier, live recalculates the tempo on the slave machines every 48 clock ticks/half bar. so you can imagine it's quite a challenge - and not very precise - eyebal...

awesome tip! thanks for sharing