Support

If you have a problem or need to report a bug please email : support@dsprobotics.com

There are 3 sections to this support area:

DOWNLOADS: access to product manuals, support files and drivers

HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects

USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here

NEW REGISTRATIONS - please contact us if you wish to register on the forum

Users are reminded of the forum rules they sign up to which prohibits any activity that violates any laws including posting material covered by copyright

Bitmasking in DSP Code

DSP related issues, mathematics, processing and techniques

Re: Bitmasking in DSP Code

Postby tulamide » Wed Dec 27, 2017 7:55 am

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
"There lies the dog buried" (German saying translated literally)
tulamide
 
Posts: 2714
Joined: Sat Jun 21, 2014 2:48 pm
Location: Germany

Re: Bitmasking in DSP Code

Postby adamszabo » Wed Dec 27, 2017 10:46 am

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.
adamszabo
 
Posts: 667
Joined: Sun Jul 11, 2010 7:21 am

Re: Bitmasking in DSP Code

Postby tulamide » Thu Dec 28, 2017 5:30 pm

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).
"There lies the dog buried" (German saying translated literally)
tulamide
 
Posts: 2714
Joined: Sat Jun 21, 2014 2:48 pm
Location: Germany

Previous

Return to DSP

Who is online

Users browsing this forum: No registered users and 62 guests