-
Notifications
You must be signed in to change notification settings - Fork 447
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
Issue with Audio Out from SoundCard #581
Comments
You obviously have some issues with your audio setup that are not in control of SDRangel. The "L16/429..." value means that the sample rate returned was -1 (error). It is also unusual to see only the system default device in the list. You should have some messages in the log that tell that the audio device cannot be opened or something like that. So you need to fix your audio as a first step. |
Thanks for your swift response f4exb. Appreciate it. To get the logs, i am assuming you are referring to the log collection procedure mentioned here using docker? https://github.com/f4exb/sdrangel-docker Let me know, if i am headed in the right direction. Thanks again! |
Hi Again f4exb, Here is a log from SDR angel: 2020-07-28 19:41:00.394 (I) SDRangel 5.1.0 Qt 5.9.5 64b x86_64 Ubuntu Core 18 DSP Rx:24b Tx:16b PID 2144 When i query the system for attached audio device..here is the response i get: **** List of PLAYBACK Hardware Devices **** I also scooped around and found this: Do you think its worth going through the steps that you mention the above post or should i try something else? If something else, where would you suggest? Full log attached |
There is something wrong in your audio setup and I cannot help you with this. However the failing audio device should be marked not usable somehow. Later this yields to an erroneous sample rate and can have adverse consequences. In this case it should result in a disabled audio and possibly show it in the UI somehow and report it in the report fetched with the API. This situation appears clearly in the plugin baseband constructor. Although failure is logged and the
|
Actually it is already "marked" unusable as the But the A similar situation probably exists in all plugins using audio. |
closed in favor of #585 |
Hey @merlinladruid and Edouard Now, I know next to zero about so-called "snapcraft", but it looks like a kind of chroot jail to me,
and immediately I see:
Supposedly sdrangel has all the permissions or "connections" to run correctly inside snap,
but it cannot access audio devices inside the snap. Maybe something to do with the pulse config files inside /etc in the snap? I really don't know enough about it. Anyway, I don't mean to hijack a closed thread on this project to discuss snapcraft + pulse, but this note might help others who come across the issue, or maybe @f4exb, if you maintain the snap, this is something that could be fixed? I'd be happy to test anything on my system for you. As always, thanks for all the code! |
I do not support snaps in any way in fact I have removed snap from my system as it interferes with the sudo settings. I can only discourage the use of snaps for SDRangel. You should rather compile from source: https://github.com/f4exb/sdrangel/wiki/Compile-from-source-in-Linux |
Hi f4exb/Edouard,
I am new to SDRAngel and GIT hub. So apologies if i am posting this in the wrong place. Please feel free to move it in the right section. I am having issues with setting up the sound device(computer) using SDR Angel. I have made sure PulseAudio is installed and levels are high, but sttill i dont know if i am missing anything. See attached snips that show settings in SDRAngel and PulseAudio. What am i forgetting to set? The build version of SDR Angel is in the screenshot. Let me know if you need anything else like logs etc. Thanks in Advance - Merlin
The text was updated successfully, but these errors were encountered: