Page 4 of 4

Re: Bitmasking in DSP Code

PostPosted: Wed Dec 27, 2017 7:55 am
by tulamide
OMG! Time for everyone to smile about me! :lol:

I made two errors. First, the binary representation of 1 is of course totally different for floats than for integers (what I had in mind when writing).
Second, somewhere in the thought process I completly lost the purpose of this thing: A trigger! Instead I imagined constantly incoming audio data that would be "or-ed".

Thanks for taking the time. Now it's absolutely clear. Ah, what a feeling. :D

Re: Bitmasking in DSP Code

PostPosted: Wed Dec 27, 2017 10:46 am
by adamszabo
tulamide wrote:A trigger! Instead I imagined constantly incoming audio data that would be "or-ed".


Cograts! However you are correct in that its constantly changing for the incoming audio, that is each sample. So the conditions and values can be different for the next sample it processes.

Re: Bitmasking in DSP Code

PostPosted: Thu Dec 28, 2017 5:30 pm
by tulamide
adamszabo wrote:
tulamide wrote:A trigger! Instead I imagined constantly incoming audio data that would be "or-ed".


Cograts! However you are correct in that its constantly changing for the incoming audio, that is each sample. So the conditions and values can be different for the next sample it processes.

Yes, you're right, and I am aware of that. What I meant was, that "out" will never be audio data (as I stupidly thought at some point in the process), but either 0 or 1 (for each of the poly notes that is).