I am guessing that if you use the osmosdr::device::find() method, which gives you a list of available devices, the first device in the list will be the one gr-osmosdr chooses to use.
Alex
On Mon, Mar 3, 2014 at 11:17 PM, Nick Foster bistromath@gmail.com wrote:
I've been letting it autodiscover.
--n
On Mon, Mar 3, 2014 at 2:14 PM, Alexandru Csete oz9aec@gmail.com wrote:
I must be completely missing something... When you create your source now, don't you already pass it a string with a device descriptor?
On Mon, Mar 3, 2014 at 11:04 PM, Nick Foster bistromath@gmail.com wrote:
Sure. I could explicitly set this, but it means now I need a separate menu item or configuration switch for each Osmo source -- and there are a bunch. Not the end of the world, just hoping for something easier.
--n
On Mon, Mar 3, 2014 at 2:02 PM, Alexandru Csete oz9aec@gmail.com wrote:
On Mon, Mar 3, 2014 at 10:35 PM, Nick Foster bistromath@gmail.com wrote:
Hi,
gr-osmosdr is great at abstracting the device type, but now I find myself wishing to de-abstract. For instance: HackRF has large DC offset, so I'd like the option to switch in a DC blocking filter when using that source. RTL dongles can't support more than 2.4Msps reliably, so I'd like to be able to cope accordingly at initialization time.
Is there a good way to retrieve, say, a string descriptor telling me which particular source I'm using?
None that I know of, but aren't you the one who decides what device is in use by passing e.g. "hackrf=0" as argument to the constructor?
Alex