If you post your patch, I will have a quick look. The most common reason for your issue is literally where the objects are placed in a patch (not presentation mode, but normal edit mode). Objects to the right or bottom will get sent to first. As a simple example, lets say you have an int object with changing values on each beat that you wish to bang as a note on the same beat. If you place the int object to the left, the note bang will happen first and therefore the changed value will not have happened until the next trigger. To fix, you would simply move the int object to the right so it gets sent to first.uberdrums wrote:Sorry for not being more clear, I was hoping to document my findings here to help other people... but i think this thread has been comsumed by my nubeness.
I have been making other patches using udp. which are not as complex and more sucessful.
I am still learning about midi, filtering messages, triggering and numbers in max. All of which have been the issues with my device.
I stopped using the sunsend devices as i thought they could be over complicating everything.
I am trying to make a midi pitch shifter with the shift controlled by another midi note signal.
It works, but I had issues with flush holding notes. Which i sorted it out selecting another source for the flush.
Now the issue is if i have the 'carrier' notes at 16th notes only playing C and on the 2nd beat i send a 16th note to shift it up to D, the shift doesnt occur until a 16th after the 2nd beat.
I think it is more an issue of triggering rather than the udp.
Another thing you should look into is to stop treating midi pairs as such if possible. You can use "makenote" to make a note from a single value - or optionally you can include velocity if you wish. This is really handy for when you want notes of fixed length as given the fact it generates note offs, it does away with any stuck notes etc. You can of course change velocity and note length dynamically if you wish with this object. Another object called "stripnote" is pretty much the opposite in that it ignores note offs.
The "coll" object is another one that should become your friend. It stores lists in a way that the first value in the list is the index and the send value will be sent out any time you send the index value into the coll object. Really useful for all sorts of applications.