You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While investigating #3 it became clear that FlexASIO could make it easier to get debug logs. ASIO host applications usually don't provide error details at all (such as which ASIO call failed and how), so we need to surface them through a side channel.
Right now the side channel that FlexASIO uses is OutputDebugString(). This is great for developers, but not so great for end users because it requires them to install a debugger (such as WinDbg) to get the logs.
FlexASIO should instead make it possible to get these logs in a more user-friendly way, such as logging to a file.
While investigating #3 it became clear that FlexASIO could make it easier to get debug logs. ASIO host applications usually don't provide error details at all (such as which ASIO call failed and how), so we need to surface them through a side channel.
Right now the side channel that FlexASIO uses is
OutputDebugString()
. This is great for developers, but not so great for end users because it requires them to install a debugger (such as WinDbg) to get the logs.FlexASIO should instead make it possible to get these logs in a more user-friendly way, such as logging to a file.
Related: #4
The text was updated successfully, but these errors were encountered: