petition: tighten move playing position in M4L
Posted: Sat Jul 24, 2010 5:22 pm
Greetings. I'm an enthusiastic end user of the "live clip chopper" m4l patch which enables me to chop Live clips and replay the samples on my monome. The patch has grown by leaps and bounds since January. However, there has always been an intermittent timing issue between a monome button press and moving the clip playing position in Live.
The developer, nonagon, first described the problem in cycling 74's forum:
http://cycling74.com/forums/topic.php?id=23924
Specifically:
-----
"it appears that every call to move_playing_pos causes Live to re-trigger the clip. This isn't noticeable in the audio stream while chopping, but it does cause the first LED on the monome to flash briefly whenever the playing position is changed. We can also see this in the playing position data, for example:
If the clip is playing back on a monome with 8 buttons in a row, clip playback will normally progress sequentially, lighting the buttons on the row in sequence:
0 1 2 3 4 5 6 7 ...
If a button is pressed during playback, the playing position jumps to the associated with that button. For example, if button 2 is pressed partway through playback, the stream might look like this:
0 1 2 3 4 5 2 3 ...
What we're seeing though, is a momentary 0 in the stream:
0 1 2 3 4 5 0 2 3 ...
which corresponds to the retriggering of the clip."
"big problem here is that the observed playing position of the clip jumps to zero momentarily whenever the position is changed…you should be able to see a discontinuity in playing position (jumping to zero) every time you set the playing position to a non-zero value."
-----
After reading the entire thread, it sounds like this issue with the move playing position is related to Live's core development. Is there a workaround or a solution to help improve the performance of this awesome patch?
Thanks for your consideration!
---Related Threads---
http://cycling74.com/forums/topic.php?id=23924
http://forum.ableton.com/viewtopic.php?f=35&t=144018
http://docs.monome.org/doku.php?id=app: ... ip_chopper
---Growing user base & New developments---
http://createdigitalmusic.com/2010/07/2 ... new-album/
http://forum.ableton.com/viewtopic.php?f=35&t=146364
The developer, nonagon, first described the problem in cycling 74's forum:
http://cycling74.com/forums/topic.php?id=23924
Specifically:
-----
"it appears that every call to move_playing_pos causes Live to re-trigger the clip. This isn't noticeable in the audio stream while chopping, but it does cause the first LED on the monome to flash briefly whenever the playing position is changed. We can also see this in the playing position data, for example:
If the clip is playing back on a monome with 8 buttons in a row, clip playback will normally progress sequentially, lighting the buttons on the row in sequence:
0 1 2 3 4 5 6 7 ...
If a button is pressed during playback, the playing position jumps to the associated with that button. For example, if button 2 is pressed partway through playback, the stream might look like this:
0 1 2 3 4 5 2 3 ...
What we're seeing though, is a momentary 0 in the stream:
0 1 2 3 4 5 0 2 3 ...
which corresponds to the retriggering of the clip."
"big problem here is that the observed playing position of the clip jumps to zero momentarily whenever the position is changed…you should be able to see a discontinuity in playing position (jumping to zero) every time you set the playing position to a non-zero value."
-----
After reading the entire thread, it sounds like this issue with the move playing position is related to Live's core development. Is there a workaround or a solution to help improve the performance of this awesome patch?
Thanks for your consideration!
---Related Threads---
http://cycling74.com/forums/topic.php?id=23924
http://forum.ableton.com/viewtopic.php?f=35&t=144018
http://docs.monome.org/doku.php?id=app: ... ip_chopper
---Growing user base & New developments---
http://createdigitalmusic.com/2010/07/2 ... new-album/
http://forum.ableton.com/viewtopic.php?f=35&t=146364