itsmattkc f6064b40df hold worker busy state in renderbackend rather than in renderworker ...

Workers run in different threads and the backends can poll whether the worker
is currently busy or not. However the previous iteration has the worker (and an
atomic int) provide the busy state which could easily desync with the main
thread (since all workers run in different threads). By holding the busy states
in the main thread, the main thread will always be able to poll the busy state
accurately.

2019-12-06 19:38:57 +11:00

..

audiobackend.cpp

hold worker busy state in renderbackend rather than in renderworker

2019-12-06 19:38:57 +11:00

audiobackend.h

fixed signal/slot connections which had been renamed and weren't resolving

2019-12-06 00:43:51 +11:00

audioworker.cpp

render one frame per thread for increased parallelism

2019-12-06 15:37:31 +11:00

audioworker.h

render one frame per thread for increased parallelism

2019-12-06 15:37:31 +11:00

CMakeLists.txt

overhauled render classes to support video AND audio

2019-11-15 13:50:58 +09:00