Oliver Jowett

What is source of the second precompiled package? I don't see a libbladeRF2 in anything other than Debian `experimental` (and if you're using experimental then you're pretty much on your...

I committed a minimal polyfill for building on both bladerf1 & bladerf2 in e419719731e515866f5077da7b13e4ad8be8b2b4

For the original PR, I'd lean towards a similar polyfill-like approach, i.e. assume that we're on libbladeRF2 and provide implementations of the missing functions if we're actually on the older...

Now that I've simplified the SDR interface, I'm leaning a bit more towards just having this as a separate SDR implementation (i.e. `sdr_bladerf2.c`) and build one or the other depending...

I don't understand what you mean. beast-splitter forwards the raw packets unchanged; there is no "decimal form"? (More generally, beast-format packets are just the raw data, no position decoding is...

I would guess that the lack of positions in VRS is because VRS does not know your receiver location. Surface positions are globally ambiguous, to decode them you need to...

The "decimal" values are dump1090 doing some position decoding work for you. These values are not included in the raw data. dump1090 is the same as VRS, dump1090 needs to...

Currently only a single source of data is supported

Like all the other options, `--force` should do this. nb: mlat-client doesn't touch this option, see https://github.com/mutability/mlat-client/blob/master/mlat/client/receiver.py#L127 Can you explain what you're actually trying to do here?

Looks like this regex needs updating: https://github.com/flightaware/beast-splitter/blob/master/splitter_main.cc#L126