cocamon

Does anyone here have an idea of how to separate two cases through boolean tests? I would like to test if two bangs are received at the same time or if only one (of two possible) bang(s) is received- in other words, im looking for a way to test if my input fulfills the logic of XOR or of AND. Any help would be much appreciated.

HELLO!
Does anyone here have an idea of how to separate two cases through boolean tests? I would like to test if two bangs are received at the same time or if only one (of two possible) bang(s) is received- in other words, im looking for a way to test if my input fulfills the logic of XOR or of AND. Any help would be much appreciated.
c


distingushing-two-cases-of-bangs-xor-and-and

shot in the dark :) you'll have to define "at the same time"

or: use 0 and 1 and make them bangs later, after you separated them.

a belated thanks from me here! was trying to apply this to my patch and see if other questions came up first, but to be honest, it seems that will take a while longer. very humbling, Max.Thank you!

Roman is right on the money here. A "bang" is a blip in time, where zeros and ones are states you can work with.

it seems like Benny's patch works fine for now, but could you please elaborate? how would you for instance use binary in the context of a sequencer that runs with counters?

What do you mean? A gate sequencer is full of binary! :D Either something is supposed to happen on a step, or it isn't. So instead of seeing it as a stream of "bangs", see it as a stream of ones and zeros.

If you need anything specific, I'd love to cobble something together.

i'm back after a long exam season: @Wetterberg- here comes the patch in case you still feel like cobblin something. It's based on this sequencer: 

 and was started in an effort to better understand such a monster of a sequencer and perhaps add some features-not to replace it.

the patch is inteded for use in max4live, where we should receive two midi notes (one at midi note 0 and the other at midinote 127) to drive an x and y index in our note matrix. There are two primary problems at the moment. 1. the algorithm in the subpatch called questions is responsible for outputting two note values upon receving two clock pulses (this however should only output a single note value, since we are only moving from one coordinate to the coordinate diagonally adjacent to it). 2. the subpatch called mess, because its a boolean test on 16 coordinates- a recipe for disaster. Would be very happy for any help with the patch.

i'm back after a long exam season: @Wetterberg- here comes the patch in case you still feel like cobblin something. It's based on this sequencer: http://makenoisemusic.com/rene.shtml, and was started in an effort to better understand such a monster of a sequencer and perhaps add some features-not to replace it.

 the patch is inteded for use in max4live, where we should receive two midi notes (one at midi note 0 and the other at midinote 127) to drive an x and y index in our note matrix. There are two primary problems at the moment. 1. the algorithm in the subpatch called questions is responsible for outputting two note values upon receving two clock pulses (this however should only output a single note value, since we are only moving from one coordinate to the coordinate diagonally adjacent to it). 2. the subpatch called mess, because its a boolean test on 16 coordinates- a recipe for disaster. Would be very happy for any help with the patch.


distingushing two cases of bangs (XOR and AND)