-
Notifications
You must be signed in to change notification settings - Fork 453
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
Airspy in Macos #1327
Comments
May I express my disappointment for not having recieved any reaction on my problem? The Airspy's are found, but do NOTHING |
I'm observing the same (lack of) behavior on a MacBook Air M1 under Monterey. I've downloaded the i64 DMG and installed flawlessly. The program opens with no error messages, it then recognizes the HF+ as an input device, it can even switch between HF and VHF, but nothing happens in the Spectrum window. Before reading your issue, I thought I made something wrong. Maybe it's that... Is there a mailing list or a group where we can ask directly to f4exb? SDRangel is indeed complex but highly attractive as a cross-platform app. I'm also using GQRX and SDR++ with no such issues. |
Sorry, it's the recent "macx64" DMG... |
I have an Airspy r2 on an M1, compiled for arm64. A single breakpoint set in AirspyWorker::rx_callback would never hit after starting the input. After some debugging, I found I could get the Airspy input working properly by:
My guess is that there is some kind of timing issue in the worker thread startup sequence. The effective sequence is:
I'm unfamiliar with the mechanics of a QThread, as that is how m_airspyWorkerThread is defined. sdrangel/plugins/samplesource/airspy/airspyinput.cpp Lines 236 to 247 in d1a4fca
sdrangel/plugins/samplesource/airspy/airspyworker.cpp Lines 45 to 62 in d1a4fca
|
Note
Note: this seems to only work with a debugger breakpoint, so far. I've tried sleeping just before the I'm thinking that the issue might exist in a separate thread, as pausing on a breakpoint results in all threads being paused. |
I just tried the airspyhf_rx example program that is included with airspyhf library, and that doesn't work for me on MacOS (Big Sur). Does it work for anyone else? |
Gave it a try as well.
Indeed, no recording all.
…On 20 Sep 2022, 18:02 +0200, f4exb/sdrangel ***@***.***>, wrote:
airspyhf_rx
|
Do you have a USB 2 hub to plug it in to? I remember a previous issue where it wouldn't work with Linux with USB 3 ports, but would with USB 2. |
I have.
Tried:
• First session with BWFM: nothing
• Second session: cannot start sample source
Why does it work with GQRX and SDR++……?
…On 21 Sep 2022, 17:50 +0200, srcejon ***@***.***>, wrote:
Do you have a USB 2 hub to plug it in to? I remember a previous issue where it wouldn't work with Linux with USB 3 ports, but would with USB 2.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Well, SDR++ doesn't work for me either. Haven't tried GQRX yet. |
Have opened an issue for airspyhf airspy/airspyhf#42 |
Airspy HF+ doesn’t work with the usb-2 hub, but works when plugged in directly in one of the Mac-ports.
…On 21 Sep 2022, 18:02 +0200, srcejon ***@***.***>, wrote:
Well, SDR++ doesn't work for me either. Haven't tried GQRX yet.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sorry, it works on SDR++ with usb-2, when I give it some power ….duh….
Not on SDRangel.
…On 21 Sep 2022, 18:06 +0200, Loe Walter ***@***.***>, wrote:
Airspy HF+ doesn’t work with the usb-2 hub, but works when plugged in directly in one of the Mac-ports.
On 21 Sep 2022, 18:02 +0200, srcejon ***@***.***>, wrote:
> Well, SDR++ doesn't work for me either. Haven't tried GQRX yet.
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Airspy HF+ and Discovery don't work in Macos, neither selfcompiled nor DMG.
Windows and Linux work fine.
The text was updated successfully, but these errors were encountered: