Hi, im very much a max newbie, would be great to get some help with this problem, thanks!

I've made a simple step sequencer using the matrixctrl to open and close gates. by clicking on the matrixctrl the gates open and close fine, however i want to be able to make quick fire random sequences. I began by using the uzi object to fire bangs into a 'random 16' (number of steps on the seq) and a 'random 2' to decide if that step is 1 - on or 0 - off. and then into the matrixctrl itself, as my example patch shows.

unfortunatly, the red dots that show on the matrixctrl do not match up with which gates have actually been opened. As my example patch shows i tryed making a basic version of what uzi was doing using the pipe object to order the bangs and slow the process as i thought the uzi may be to fast for the rest of the patch.

anyways, please take a look! - any help would be fantastic!! ...please!

I've made a simple step sequencer using the matrixctrl to open and close gates. by clicking on the matrixctrl the gates open and close fine, however i want to be able to make quick fire random sequences. I began by using the uzi object to fire bangs into a 'random 16' (number of steps on the seq) and a 'random 2' to decide if that step is 1 - on or 0 - off. and then into the matrixctrl itself, as my example patch shows. 

unfortunatly, the red dots that show on the matrixctrl do not match up with which gates have actually been opened. As my example patch shows i tryed making a basic version of what uzi was doing using the pipe object to order the bangs and slow the process as i thought the uzi may be to fast for the rest of the patch. 

uzi-matrixctrl-problem

don't think i uploaded the patch, sorry - here it is.

> don't think i uploaded the patch, sorry - here it is.

No it's not. For info, attachements don't work. Paste your patch as text.

thanks for the info here it is in tx format.

thanks for the info here it is in tx format.
O.


just select everything you wan't to post, and copy / paste it to the forum ;)

> unfortunatly, the red dots that show on the matrixctrl do not match

> up with which gates have actually been opened. As my example patch

> shows i tryed making a basic version of what uzi was doing using the

> pipe object to order the bangs and slow the process as i thought the

> uzi may be to fast for the rest of the patch.

In general, uzi won't be "too fast" for this purpose, I didn't look into

the details yet, but its pretty likely you are fighting left-to-right

ordering issues. Best is trigger (short t) to get around these. Pipes

are expensive and for piping bangs almost useless, use delay instead (it

will pass only one bang at a time though, no problem in your example...)

To find out how the patch is behaving, use the trace mode, you can step

slowly through your patch, which will also show the actual ordering of

O Lisher wrote:
> unfortunatly, the red dots that show on the matrixctrl do not match
> up with which gates have actually been opened. As my example patch
> shows i tryed making a basic version of what uzi was doing using the
> pipe object to order the bangs and slow the process as i thought the
> uzi may be to fast for the rest of the patch.

In general, uzi won't be "too fast" for this purpose, I didn't look into
the details yet, but its pretty likely you are fighting left-to-right
ordering issues. Best is trigger (short t) to get around these. Pipes
are expensive and for piping bangs almost useless, use delay instead (it
will pass only one bang at a time though, no problem in your example...)

To find out how the patch is behaving, use the trace mode, you can step
slowly through your patch, which will also show the actual ordering of
messages.

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com

Uzi & MatrixCtrl Problem!