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

SDRPlay Clone 0x1DF7/0x2500 is not recognized on Mac #2376

Closed
saschaludwig opened this issue Jan 16, 2025 · 5 comments
Closed

SDRPlay Clone 0x1DF7/0x2500 is not recognized on Mac #2376

saschaludwig opened this issue Jan 16, 2025 · 5 comments

Comments

@saschaludwig
Copy link

When I try to use the Mirics chipset based blue (dolphin) MSI.SDR receiver, it isn't listed in the device dialogue on Mac x64 in SDRangel Version 7.22.4:

Image

The USB Prober on Mac however recognizes the USB device:
Image

Any Idea what I can do to find the issue?

This is the device in question:
Image

@saschaludwig
Copy link
Author

I think I just found the info, that the SDRplay isn't supported (anymore) in the MacOS build?
https://github.com/f4exb/sdrangel/blob/master/plugins/samplesource/sdrplay/readme.md

@srcejon
Copy link
Collaborator

srcejon commented Jan 17, 2025

The Mac build uses the SDRplay v3 driver, that uses SDRplay's API, so clones probably not supported unless you build it yourself.

@Axpelle
Copy link

Axpelle commented Jan 26, 2025

Have a look at this warning from SDRPlay: https://www.sdrplay.com/fakealert/

@saschaludwig
Copy link
Author

Have a look at this warning from SDRPlay: https://www.sdrplay.com/fakealert/

How does that fix the problem?
I also have a SDRplay RSPdx that works totally fine. But that's not the point. My issue was, that I wanted to use the Mirics SDR device with sdrangel.

@Axpelle
Copy link

Axpelle commented Jan 27, 2025

There are numerous references regarding that SDR to the effect that it uses fake or cloned Mirics chipset. In particular Mirics only sells to OEMs and ODMs and I very much doubt that this SDR is one of them. There may be workarounds or more or less successful attempts at reverse-engineering the drivers. But more likely than not the level of performance will fall far short of that obtainable from the genuine chipset. So yes that won't fix your problem.

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

No branches or pull requests

3 participants