DSP Robotics Support

From what I can hear, listening to sine tones - this harmonic resonance with midpoints happens (is noticable) in a specific range. Excluding resonances based on intervals (these seem to be across the octaves), signifficant effect is when borderline frequencies for midpoint are within an octave or two. When the difference is within octave - vibration is "sweet" (thumb-up), when the difference is within second octave - vibration is "tearful" (thumb-down).

So among indicators, perhaps it will be good to add one (exchangable with that which tells, that "f1-f3 < 30Hz"), to tell that the midpoint comparizon is within n-th octave range? Just a thought to consider.

Blinded by selectors I forgot about array operators.

I think it may go in this direction, because string combiners can be triggered by float operations and restrictions.

...and this one seems to remove iterations with 0's on input side.

Now it's time to check how to combine it with string operations (correlated strings).

I can imagine marking like this.
Marking midpoint types for example.

Now it's time for list of reference names.
Then I guess - combining them with values.
And midpoint based calculation is ready.

But that's not all.
Next step - interval based resonances.
puff....!

Conclusions? I think I learned how to use loops
By the way - where Trog disappeared?

Huston, we have a problem... Maybe I'm just tired; while everything else seems to work as it should be (at least for the moment) - combining descriptors - for some reason - does not works correctly. Guess there is some trigger problem. Any idea how to fix it?

Guess it was trigger order.

What makes me curious however, is - how it will behave under heavy load and larger arrays. I mean - it works now, but there are some parts that I just did by testing. I'm not sure why some thigs are in such and not different order, or whether shouldn't be there some latch, to synchronize some triggers in different way.

Thoughts? Troggie...? Trigger Master...? Are you there somewhere...?

What would be the incorrect result?
which the correct result you expect?
so you can better help.
not always one you can follow all the logic.

I can imagine, that under some spooky circumstances, some trigger "delay" (possible? not due trigger logic/order?) between modules may cause some "shift", which means that either wrong values would be combined, or values with wrong descriptors would be connected (it's too big for my head to comprehend, but small enough to connect on schematic). I'd like to be sure, that this does not happens. If you play with these green links coming from loops to array components, you will notice, that they must be in exact order to make the whole work; but there are different operations on different paths before all threads go synced to common output. Having 15+/25+ input array, to check if everything is right - takes some time (hunderts of combinations, from which some parts are rejected). Now there are only 4 elements, just to experiment with.

Btw, tonight or tomorrow, there will be final schematic for midpoint comparisons; I'm just finishing that part that connects values with descriptors.

Puff, I guess this is the "final" version for midpoints. One thing left, is to change "_" into some version of spaces, that are not ignored (during processing) in a way that white spaces are. I remember seeing somewhere a module with special characters but can't find it right now.

Tomorrow chech if there are some errors. I see one in descriptor combiner. :-/

...