bgribble/mfp

Logging from DSP engine is mishandled when DSP backend is launched from LV2 host

Opened this issue · 0 comments

The default logging behavior (using stdout with formatted messages to get picked up by the RPCRemote listener thread) doesn't work when there's nothing reading that thread's stdout on the Python side. Log messages get printed to the LV2 host's stdout in a format that's not useful.