Hey hello, you know the fetch message for [multislder] its quite handy.

Also live.grid can be used for this stuff I think.

You could also create a list of values and get them with [zl lookup]

Just because you say analog, I like signal based sequencers quite a lot.

greetings!

just the multislider thing.

Hi Woyteg,

So would you generally opt to use the metro object for the main time keeping duties. To be honest im not quite sure what the application of the multi slider could be in this case.

I am going to explore the use of the live.grid object, as it seems to be a neater alternative to multiple toggles!

Any other advice would be greatly appreciated.

As i said I pesonally would opt to go signal driven.

The metro was just a source of bangs to illustrate the function of multislider.

What don't you understand about the multislider/fetch combo?

Its a GUI that stores values and allows you to fetch those sequencally, essentially a sequencer.

No i have never been exposed to the mulitslider/fetch combo. I was a casual pure data user for a while so i still have some of that mindset going on. Trying to convert the knowledge. Are there any examples of said sequencers i could possible break down and learn from?

After another day playing around I am starting to get the hang of things. I am now using live.grids rather than multiple toggles. Slowly taking shape. I would appreciate if anyone could just have a look at it and tell me whether i am doing any part of the project in a non economical way. I would like to try avoid bad habits!

Cheers,

t

First impression after a quick look: You don't need the 16 gates connected to the [sel 1-16]. Simply connect a [sel 1] from the outlet of the upper live.grid to the midi note section [t70] will work as well...

In general (and especially if you are eventually planning to use this as a M4L device), it may be wise to look at the [transport] object (rather than metro) and re-design the timing part of the patch to work with that.