Is there high level strategy about which tracktion engine classes are designed to be accessed from multiple threads?
It looks like te::Edit
methods and members are generally not thread safe. What about te::Engine
and its methods? Should all calls to the various Engine
members’ methods be done from the thread that owns the engine instance?
I’m writing an application that will load and process multiple Edit
s simultaneously, and want to make sure I’m structuring my app in a sensible way.