[unpack] ? It seems the differences between both is that you have to give arguments to unpack about the data types + you can get the extra elements of the lists with the right outlet of unjoin.

Yeah the MaxforLive programming series has been created in Live9/Max 6.1

It will all work in Live 8/Max 5 but you may need to make the odd change here and there for new objects.

In this case you can just use [unpack i i]

Let us know if there are any other situations where you get stuck, we'll gladly supply workarounds.

Cheers

Andrew

In part 2 of the Live API Sequencer - http://www.youtube.com/watch?v=yKVFUs8Sleo&list=PLasl9I6VeCCrNLAoOiKibDqJc1rsjLSDi&index=18

The method for changing the loop length does not work correctly. Changing the loop length for some reason changes the tempo of the sequence. Although there is no audio example for that part of the tutorial you can actually see the count slowing down and speeding up as the loop length is changed, also I built it myself in Max6 and the same happens. I imagine what most people want from sequencers is a constant tempo and any changes to the loop length to be updated on a quantized beat.

@grizzle this is by design.

All of these tutorials were created with the idea of our users taking the end device and adding more functionality, joining them with other tutorial devices and so on....

In this case, adding options and alterations in your patch to the phasor~ will allow you to alter the sequencer rate in conjunction with the loop points. You'll find rate~ to be your friend here.

We encourage uses to make variations on these and add them to the wiki under the relevant tutorial to help and inspire others.

cheers -TH