![]() Thanks you in said in I am porting a standalone application to plugin (VST2). OR should I use QCoreApplication, and call exec, from within a separate thread I spawn in my plugins initialization, to keep the event loop going there without blocking? So, in this plugin, what should the role of QCoreApplication be? Is there an alternative to it I should use in this case? Which of course makes sense, there is no need to start another "main event loop" inside of a plugin, which should be slaved to the event loop of the host calling its methods at the right moments. If I don't add a QCoreApplication at all, I get a lot of errors like QSocketNotifier: Can only be used with threads started with QThread.īut if I call ->exec() on the QCoreApplication instance, the program freezes there when debugging, never advancing past the call. ![]() The standalone application has a QCoreApplication instance, on which it calls ->exec(). We have an existing standalone application which uses QT, that I am now porting to a C++ VST 2.4 plugin (Steinberg VST plugin, for audio processing). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |