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

Increase SAMPLES_TO_TRANSFER #47

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fredclausen
Copy link

I was seeing SoapySDR readStream failed: OVERFLOW appear in my logs with some frequency while using SoapSDR + Soapy AirSpyHF in conjunction with dumphfdl. I realize the issue is likely my computer is being hamstrung in some way (CPU usage or USB bus being slow).

Increasing the buffer size appears to solve the issue and allow the program to keep up with the buffer.

@touil
Copy link
Member

touil commented Dec 19, 2023

Why not fix SoapySDR (or whatever code is using it) instead of imposing a shitty latency for everybody else?

@luzpaz
Copy link

luzpaz commented Feb 5, 2024

@fredclausen is there an upstream ticket for this ?

@fredclausen
Copy link
Author

@luzpaz there is not. I don't know if the issue is in this library, Soapy, SoapySDRPlay or dumphfdl. Based on the reply from the library author I investigated a little more as to why this solution "fixed" my problem and I chose to take the easy route and buy two new computers to run this stuff on because I suspect the issue I was facing was simply USB bus speed issues/number of devices I had connected on the original computer. I still the issue, but it's significantly more intermittent. I don't believe in the current setup I should see it at all, but it is what it is. Bus speed, computational power, memory etc are not constrained on this system.

My suspicion if I'm honest is that there isn't a single causal factor, as software unrelated to my use case (RTL SDR Airband to mind) had this problem with this library/soapy/soapysdrplay and their solution if my memory is correct is to catch the error and ignore it. If I'm correct, this commit is where they're doing that.

I admit I don't fully understand why increasing the buffer size is a bad thing, but I do trust that I'm not qualified to make the judgement and I rolled the change back on the software I'm using. Honestly, I'm at the end of my technical ability to understand and diagnose who or what was causing the issue and open appropriate issue(s).

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

Successfully merging this pull request may close these issues.

3 participants