Loops

[pfeatherstone]

Say I want to run a loop on a separate thread, is there a way to use this library to setup a chain of calls which essentially run as a loop on the thread pool?
For example, my use case is reading audio from an ADC in a loop. Currently, I'm creating a thread manually and I invoke callbacks inside the thread when samples are ready. I'm wondering if using a thread pool is more appropriate, a bit like how one sets up callback loops in Asio. Is this library suitable for this kind of stuff? Or is using raw threads still better for this kind of thing?
Cheers

[FelixPetriconi]

From my point of view I would not use a thread pool for this. This is a realtime problem because you must not miss any samples. It is even worse: You are not allowed to use any locks in such an environment. There are several talks on that topic online from the ADC conference in England.
Normally the operating systems have the possibility to mark a thread as a realtime thread to avoid any kind of latencies. I am working in such an area where we make samplers and audio effects and we have always dedicated audio threads with a hot buffer to read or write audio samples. This is of course a kind of energy burning, but it is the only way to avoid any kind of blibs or cracks. (The human ear is much less forgiving than your eyes, when there is a short artifact in a video stream.)

[pfeatherstone]

Thank you very much that was useful.