-
Notifications
You must be signed in to change notification settings - Fork 323
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
Expression 'paTimedOut' failed in 'src/os/unix/pa_unix_util.c', line: 400 #870
Comments
I don't know whether this is the cause of the timeout, but there is an "obvious" issue in There is a meta-issue for And here is the equivalent bug in the JACK back-end: #795 That said, looking at the code, if |
possible dup of #266 |
I checked and PortAudio cannot find any devices anymore, so I really could not say. It could find devices before, so I'm not sure what is happening. |
@nodemand thanks for checking. Could you confirm that you were previously testing the latest version of our master branch? If not, could you please check whether devices are visible when using our current master? In other news, I've updated the PR with some fixes and improvements, but nothing that should impact device visibility. |
Missing devices possibly related to #804 |
@RossBencina I tested previously on PortAudio 0x00130700, V19.7.0-devel. That is all I know. And I checked #804 and adding |
@nodemand It would be helpful if you could test our current master branch to determine whether this "no devices" issue is related to my PR or is a previous regression. |
Hi @RossBencina, success! It lists my sound card and the code execution goes past |
@nodemand so, to be clear, are you saying that now our master branch is working for you (or at least not exhibiting this bug) but that the PR #877 version is not listing any devices? or are both versions now working? One way to check whether there is a problem with code inside the callback function would be to simply make the callback function return |
@RossBencina And the segmentation fault had to do with me indexing the input/outputbuffers wrong. So I guess I can close this issue... |
@nodemand thanks for the feedback. Glad to hear everything is working for you now. However, you wrote:
This sounds like a bug. I mean, PortAudio should still be able to list devices. Could you describe how to reproduce this issue? Can it be reproduced by running |
@nodemand any comment on my previous question? |
Replace Code:
|
Note to self: Running the code in the previous comment in two shells results in the second shell listing no devices. This is not the expected behavior. |
@nodemand Thanks for the reproduction test case. I have created issue #891 to track the "no devices listed" issue. I think I have captured all relevant details from this thread but I'd be most appreciative if you could check #891 and add anything that I've missed. The main thing I'm a bit uncertain of is when the issue started happening, but I gather that it is definitely an issue on our master branch. I'm closing this one (#870) since the timeout issue is resolved. |
I'm getting the following errors when executing
Pa_StartStream
:My code:
I would expect the input audio to be piped to the output, but instead my application crashes at
Pa_StartStream
... This does not happen when I use the blocking example. I only added the callback function and then these errors appeared.EDIT: I tried a couple of portaudio examples that use callbacks, but all exit with the same errors...
The text was updated successfully, but these errors were encountered: