Need help understanding the logic of the program

[giff25]

so Ive started combing over the code to understand it and noticed that the processing function within edrumulus.c blocks. I just want clarification on the architecture of the code.
is it something along these lines:

read input sensors ---------> FIFO
Process(FIFO) ----------> MIDI format ----------> send over USB

I know this is oversimplified but I'm still just trying to get a general sense of how the code works.

[corrados]

Actually not. There is no input FIFO. It is a sample-based algorithm. The FIFOs are only used for filters, etc. But each sample is used directly from the hardware without buffering.

[giff25]

What are the benefits of doing it that way rather than spike detection putting the samples into a queue and having multi threading for processing that queue? It seems to me that the blocking the processing function does is inefficient.

[corrados]

We want to have the lowest possible delay. Btw, I am already using multi threading on the ESP32 dual core to capture and process data in separated threads.

[giff25]

Which module In the code has the multi threading? I’m just struggling to understand the way it’s implemented then

[corrados]

Here is where the second thread is created:

edrumulus/hardware.cpp

Line 312 in 8fd1bde

xTaskCreatePinnedToCore(start_timer_core0_task, "start_timer_core0_task", 1200, this, 1, NULL, 0);