Mikelib

I have created this sub patch in order to be able to pick 5 different inputs. It works at the moment but the only problem is that when the counter resets itself the selection 1 option on the counter will activate twice when a bang is sent to it. Anyone have any ideas how I can avoid this happening? The patch should make this question easier to understand. Thanks, Mike. mandrews04@qub.ac.uk

Hi guys,
        I have created this sub patch in order to be able to pick 5 different inputs. It works at the moment but the only problem is that when the counter resets itself the selection 1 option on the counter will activate twice when a bang is sent to it. Anyone have any ideas how I can avoid this happening? The patch should make this question easier to understand. Thanks, Mike. mandrews04@qub.ac.uk

selector-question-new-user

1. there is no need to set limits on a numberbox when you've defined limits by patching a recursive process in max.

take away the limits and the prob is gone.

2. you should read the help file for counter: without any arguments, counter will default to having a minimum of 0, and in this case will be a problem for you.

1. there is no need to set limits on a numberbox when you've defined limits by patching a recursive process in max.
take away the limits and the prob is gone.

That works great thanks for that. The only problem is that when it is combined with the main patch it stays on selection 1 for the first two clicks only.Thanks,Mike.

if you read my post carefully, you'll see that counter takes a variety of *arguments*.

please consult the helpfile further before posting again.

if you read my post carefully, you'll see that counter takes a variety of *arguments*.
please consult the helpfile further before posting again.

Ok, I did consult the help file, many times in fact but it does not mention that counter *has* to contain an argument and as the solution patch you posted also didn't contain any *arguments* I got confused. As I said I am a new user so all this stuff is still new to me. Thanks,Mike.

it doesn't unless you'd like for the count to start at something besides zero, or if you use an initializer.

in the case of initializing it (e.g., with a 1), either set it in the left inlet (set #) or with the second/third-from-right inlets as shown.

the reason that i kept your original solution intact is to illustrate that the number you "jump" to can be set dynamically--- this could be useful for other purposes.

apologies if the post came across as confusing.

also, check out tutorial #31 in the "max4.x tutorials and topics" PDF (assuming you're using 4.x).

it doesn't unless you'd like for the count to start at something besides zero, or if you use an initializer.
in the case of initializing it (e.g., with a 1), either set it in the left inlet (set #) or with the second/third-from-right inlets as shown.

Ok thanks for all the help I will check out that tutorial. Thanks,Mike.

> Ok, I did consult the help file, many times in fact but it does not

> mention that counter *has* to contain an argument and as the solution

> patch you posted also didn't contain any *arguments* I got confused.

> As I said I am a new user so all this stuff is still new to me.

The best recipe in max against confusion, is trial and error. Take the 

help file and ask the object by connecting other stuff, try out how it 

reacts without arguments, with certain arguments and so on. Connect 

print or a [prepend set]->messagebox to the outlets... That way most 

questions answer themself. (Most answers I give on the list are not from 

my direct knowledge, but from my knowledge how to ask Max, which I 

usually have to do, I have a very bad memory... ;-)

btw counter would complain if it *had* to have arguments. Its happy 

without and there are enough crucial cases where you would not want to 

Mike Andrews wrote:
> Ok, I did consult the help file, many times in fact but it does not
> mention that counter *has* to contain an argument and as the solution
> patch you posted also didn't contain any *arguments* I got confused.
> As I said I am a new user so all this stuff is still new to me.

The best recipe in max against confusion, is trial and error. Take the 
help file and ask the object by connecting other stuff, try out how it 
reacts without arguments, with certain arguments and so on. Connect 
print or a [prepend set]->messagebox to the outlets... That way most 
questions answer themself. (Most answers I give on the list are not from 
my direct knowledge, but from my knowledge how to ask Max, which I 
usually have to do, I have a very bad memory... ;-)
btw counter would complain if it *had* to have arguments. Its happy 
without and there are enough crucial cases where you would not want to 
give counter arguments...

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


Selector question (new user)