-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Multiple audio source. #9
Comments
So I think most of this is a matter of proper device selection. @cjcliffe Is SoapyAudio missing a way to specify the device? If I was using portaudio, it would report perhaps a dozen audio devices. Currently I have SoapyAudio's rtaudio built with pulse support and it reports only one device.
I haven't tried jack support though. Just curious, what have you been doing for rtaudio linux support (jack/pulse/oss)? Or am I missing something obvious :-)
This also might be an issue of selecting the correct audio device. The rates are just forwarded from rtaudio
Thats good news in a way. Adding proper FCD support means figuring out which API calls rigctl makes and adding this to SoapyAudio::setFrequency(). @bdn76 What was your rigctl command line options? That would help me trace through the software to see what calls its making. |
fcd1@oem-desktop: But via hamlib i can not select FCD (i'm opened issue in hamlib). |
Hey, sorry, I didn't forget about this. It looks like there are two problems
Do you know which audio backend SoapyAudio was compiled with? There are several other backends depending upon the cmake options: https://github.com/pothosware/SoapyAudio/blob/master/CMakeLists.txt#L87 |
Yes, you are right. PulseAudio backend. |
I'm try to use four FCD pro on remote PC via CubicSDR/SoapyRemote/SoapyAudio:
The text was updated successfully, but these errors were encountered: