Re: Bitmasking in DSP Code
Posted: Fri Sep 22, 2017 8:37 am
This is going well Martin!
One of the trickiest things for me to grasp in the past was that after a single pass of a DSP “visit” floats can be left changed for the next “visit”. In this way the DSP code remembers the result of the previous visit and acts accordingly. Of course this seems simple and obvious now, otherwise we couldn’t have sample counters etc.
Another thing I found out early on is that some code needs to be executed in the correct order to function correctly. Again, from programming, this may seem obvious but the sequence of some steps seems more critical than others. For example, the order of Float naming doesn’t matter but it can be very critical at what point in the code you increment a counter.
Also I remember I was surprised to find that a streamout value is held until the next visit, so can actually be used in a calculation for the next visit. This was counter-intuitive to me because I tended to think of an output as done and gone once it’s been generated.
I’m looking forward to an explanation of using that HUGE number instead of the abs function.
Many thanks for taking the time to cover all this stuff.
Spogg
One of the trickiest things for me to grasp in the past was that after a single pass of a DSP “visit” floats can be left changed for the next “visit”. In this way the DSP code remembers the result of the previous visit and acts accordingly. Of course this seems simple and obvious now, otherwise we couldn’t have sample counters etc.
Another thing I found out early on is that some code needs to be executed in the correct order to function correctly. Again, from programming, this may seem obvious but the sequence of some steps seems more critical than others. For example, the order of Float naming doesn’t matter but it can be very critical at what point in the code you increment a counter.
Also I remember I was surprised to find that a streamout value is held until the next visit, so can actually be used in a calculation for the next visit. This was counter-intuitive to me because I tended to think of an output as done and gone once it’s been generated.
I’m looking forward to an explanation of using that HUGE number instead of the abs function.
Many thanks for taking the time to cover all this stuff.
Spogg