Drum Machine Patch

Anyone have any thoughts?

first off I don't know what it is that used to work but now doesn't...you need to be more specific. Second if it IS a specific problem it is clearer if you post only the part of the patch which concerns it. Finally I would neaten up the whole patch as it will make it easier to trouble shoot and is helpful for people who want to look over your work. I had to tidy it up in order to make sense of what was going on :)

I think your problem if I'm right is that the [preset] object has saved the states of you [gswitch] objects. This is causing a conflict with your system for recalling the preset at the start of the next bar. You can get around this by using a normal [switch] object instead.

Also from perusing your patch, you have an extraneous counter object in your tempo patch. You should look into [textbutton] as it is more flexible and pleasant ;) than using message boxes connected to message boxes. You will also need to look at [trigger] at some point.

enjoy!

Here's some general advice for a beginner.

If you're patching in an organized way it's very rare that you'll have to cross cords. Audio chords can cross a bit more because they aren't subject to execution order. If you can't see clearly what your code is doing and in what order it's doing it, you need to rethink things. Believe it or not, most of your code should look like columns of objects.

look into the following objects they will help you quite a bit:
p
v
s
r
t
zl.mth
pvar
poly~ (When you're ready for it)

Also knowing how to create abstractions helps immensely.

PS I know this doesn't help you with your patch and I probably sound like an asshole but it's good advice. You need to code for your future self. So that in a week, when it stops working, you don't look at it and go "what... the... f*&%?"

Hi Guys.
Any chance you can explain in laymans terms how to order my patch without using cords?

Also I can't find many of the above objects in the max helpfile..

Aw friend.. I said you won't need to *cross* cords. In other words ordganize yourself before you start patching

Also,

p is short for patcher
v is short for value
s is short for send
r is short for receive
t is short for trigger
zl.mth is part of the zl object.
pvar
poly~

you can type p instead of patcher into an object box and it does the same thing. same for value, send, receive, and trigger.

These are objects that help keep the spaghetti from happening.

So is there no way for me to tidy it up at this stage? I'm also having difficulty getting max to interpret my midi keyboard. I have midiin- which is obviously the raw data, and also tried midi parse... It is for a sub bass patch and i'm a bit confused. Apologies for all the questions.