Running RTL-SDR in your Browser via an HTML5 App
Thank you to Jacobo Tarrio for writing in and sharing his latest project, an HTML5-based RTL-SDR application that runs directly in your browser. Jacobo writes that he'd previously created a Chrome app called FM Radio Receiver for Chrome (which we also posted about previously), but unfortunately, Google stopped supporting Chrome apps.
Jacobo goes on to write:
Last year I started working on it again. I took the original source code, modernized it to use modern TypeScript and HTML5 APIs, and then transformed it deeply to turn Radio Receiver into a general-purpose RTL-SDR application (with a waterfall and everything), which is available at https://radio.ea1iti.es/.You don't need to install anything -- it runs straight on your browser. (Well, you still need to do the usual RTL-SDR driver setup, but other than that...)It supports any computers or Android phones with the Chrome, Edge, or Opera browsers. Unfortunately, it cannot run on iPhone or iPad, or on the Firefox or Safari browsers.For hardware, it works well with the RTL-SDR Blog V3 and V4 sticks (with support for direct sampling on the V3 and for the built-in upconverter on the V4), as well as other R820-based sticks.The source code is available on GitHub under the Apache 2.0 license.
I wouldn’t ever run a Chrome based browser for anything but its interesting that this can be done. SDRConnect is the new standard to beat for Linux based SDR, the only thing I care about.
Surely very convenient. Parabéns.
It runs great on the brave browser on LMDE6
ubuntu 22.04 error
radioreceiver-main/build.mjs:103
await fs.rm(“dist”, {
^^^^^
SyntaxError: Unexpected reserved word
at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)
at async link (internal/modules/esm/module_job.js:42:21)
what i am missing??
I guess I haven’t used ‘–clean’ since forever. I’ll fix that later today. In the meantime, don’t use ‘–clean’. Thanks for the report!
Ok, the problem is that the version of NPM that comes with Ubuntu 22.04 is very old. Newer versions execute everything within an async function, but that one doesn’t, so the
awaitcodeword is not valid.I’ve wrapped the main code in an async function, which should fix it for you.
thank you