Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it easier to get PortAudio debug logs #4

Closed
dechamps opened this issue Oct 15, 2018 · 0 comments
Closed

Make it easier to get PortAudio debug logs #4

dechamps opened this issue Oct 15, 2018 · 0 comments
Assignees

Comments

@dechamps
Copy link
Owner

Some issues can be difficult to troubleshoot even from the FlexASIO debug logs, because often the issue is coming from somewhere within PortAudio. FlexASIO does surface PortAudio error codes in its debug logs but these are notoriously vague, e.g. paInvalidDevice can mean any number of things (see #3 for an example).

PortAudio itself has fairly detailed error logs (see pa_debugprint.c), but they're not easy to get to. They get logged to STDERR, which is accessible for console applications (such as jackd), but, AFAIK, not for graphical applications. As a result, in most cases there is no way to get them.

Fortunately, PortAudio seems to provide a function, PaUtil_SetDebugPrintFunction(), that allows library users to override this behaviour and intercept debug messages themselves. FlexASIO could use that to incorporate PortAudio debug messages into its own debug log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant