Software-defined radio receiver application built on GNU Radio with a web-based UI and plugins. In development, usable but incomplete. Compatible with RTL-SDR.
It should be possible for several people to to use a single ShinySDR server without interfering with each other (provided that sufficient hardware is available).
Components of this project, given the current state of the code:
Support for multiple session objects with different URLs. shinysdr/i/roots.py contains the core implementation, but it has not yet been fully deployed.
Session objects need to become actually meaningfully different (right now they are really just proxies for Top as a placeholder), having different sets of receivers and different selected devices and so on.
Server-side audio routing must be reworked to allow each session, or each client, to have its own audio mixing bus. (I already wrote some further thoughts on this in issue #11.)
The major complication for both is figuring out how persistence will work in this world — because we don't really have a notion of persisted arbitrary object references (just create-or-reconfigure a child object), and we need to either change that or work around it.
It should be possible for several people to to use a single ShinySDR server without interfering with each other (provided that sufficient hardware is available).
Components of this project, given the current state of the code:
shinysdr/i/roots.pycontains the core implementation, but it has not yet been fully deployed.Sessionobjects need to become actually meaningfully different (right now they are really just proxies forTopas a placeholder), having different sets of receivers and different selected devices and so on.The major complication for both is figuring out how persistence will work in this world — because we don't really have a notion of persisted arbitrary object references (just create-or-reconfigure a child object), and we need to either change that or work around it.