-
Notifications
You must be signed in to change notification settings - Fork 100
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
Input buffer overflow #15
Comments
Also on ARM R8 chip@chip:~/nrsc5/build$ nrsc5 88500000 0 |
Fixed with |
If the input buffer is overflowing, then that means it couldn't process the data fast enough. Or, as might be the first case, it could mean that processing got stuck trying to output the audio. By disabling threads, it eliminates the use of these intermediate buffers, so it is now impossible to have this issue. The solution depends on the root cause. If it is because libao is hanging due to issues processing the audio, then the ideal solution is to drop audio samples. If it is because the machine isn't fast enough to do all of the processing, then the solution is likely dropping radio samples but this will cause desynchronization. |
Let me know if you are still having buffer overflow issues after this commit. It should now properly drop audio buffers if for some reason libao is hanging. |
Thank you, build with threads gracefully handles overflow now. chip@chip:~/nrsc5/build$ nrsc5 -g 14 88500000 0 |
I've found the source of my issue. It is related to using a bluetooth headset and nrsc5 being unable to output the sound to it. Essentially if the bluetooth starts dropping or is about to disonnect, nrsc5 produces the error and it segmentation faults. |
I'm going to pull the new code and compile it now. |
The issue is resolved. The program gracefully returns audio back to on board sound if it can't send it to bluetooth. Thanks. |
While using a bluetooth headset on ARM experimental branch I received this error:
03:00:59 WARN input.c:239: input buffer overflow!
Segmentation fault (core dumped)
It happens while using bluettooth audio. I can test the behavior on x86 as well if you would like.
The text was updated successfully, but these errors were encountered: