perf: Ability to play precise sound sequences about flutter_soloud HOT 3 CLOSED

Hi @LeventeAsztalos, thanks for your findings.

I did some experiments using Soloud.play() and Soloud.playClocked().
On C side I wrote a thread which plays your given sample 200 times. The result is this:

The upper graph is made using Soloud.playClocked(), the bottom with Soloud.play() with a microseconds scale.
As you can see there are a lot of delays around 40ms which is the buffer length as stated in Soloud.playClocked() doc:

Note that if your "physics time" granularity is low, playClocked is not really useful. Audio buffers tend to be 40ms long at most.

To test this, I used this code on C side:

ActiveSound *sound = sounds[0].get();
std::thread th(
    [sound, time, this]
    {
        for (int i = 0; i < 200; i++)
        {
            std::chrono::steady_clock::time_point begin = std::chrono::steady_clock::now();
            this->soloud.playClocked(time, *sound->sound.get());
            // this->soloud.play(*sound->sound.get());
            usleep(time*1000000);
            std::chrono::steady_clock::time_point end = std::chrono::steady_clock::now();
            std::cout << std::chrono::duration_cast<std::chrono::microseconds>(end - begin).count() << std::endl;
        }
    });
th.detach();

There is no much difference doing the same on Flutter side with a code similar to yours. So the problem could be on SoLoud lib, but as you stated, the lib is not meant to be used as a music sequencer.

I have to investigate further, maybe there is some compiler args to pass or some other tips I missed.

from flutter_soloud.

Digging further I tried lowering the buffer size to 1024 or 512 instead of 2048 (which stores the previously mentioned 40ms).
This is the result:

There is not much difference between playClocked() and play(), anyway some better results.

Currently is not possible to change player initializing parameters, but you can try to manually modify it here

from flutter_soloud.

Thanks for the quick and detailed analysis! I tried with 512 buffer size, and the result were much better. It would be nice if we could set these params from the flutter side. On the other hand with this approach there will always be some latency. My original problem is not related to the package itself, it rather a technical method question, so I close this issue.

from flutter_soloud.