David, There are a couple of problems with using the selector in this configuration.
1) If you plan to just disable the sinks in GRC, then you don't need the selector at all. That block is intended to be used to change the configuration during runtime. You can just connect all the sinks to the same output and disable with the D key. 2) In the case where devices are present when the flowgraph is run, when the selector output is set to, e.g. 0, the outputs 1 and 2 produce no samples. This will starve the SDR sinks of samples and have some consequences (depends on the sdr) As far as the SDRs being instantiated, this is just how GRC works - it instantiates all the blocks that are present in the flowgraph. So if an SDR isn't present, then the block needs to be disabled - selector doesn't help you. Josh On Thu, Mar 3, 2022 at 11:07 PM David Cherkus <dcher...@yahoo.com> wrote: > Asked this on chat, thought it might need a broader audience so am asking > here too... > > Part of my flowgraph looks like: > > [image: Inline image] > > > > I.e. a selector that selects between output to null sink, osmocom sink or > PlutoSDR sink. > > Problem is when I run the flow and no SDR is present (I select Null Sink > by default) the code still tries to instantiate the osmocom Sink and that > fails. If I disable the sinks for radios that aren't present with the 'D' > key, then the selector complains that the output is no longer connected. > Any ideas how to work around this? > > Regards, > Dave, N1AI > > >
