... until further notice.
Windows did an update on the computer, and when it came back up it no longer worked. OpenWebRX+ running on Windows under Docker is so fragile.
I was going to work on the Linux version, but when I went back to the Linux computer, the Decktop Interface kept crashing after logging in. Talk about fragile! For those who are unfamiliar with Linux, I had installed the server/command line version of Ubantu, and then added a desktop package for ease of use. So much for that idea. I'll stick with the command line version when I get around to reinstalling the system.
As I've stated many times in the past, open source software, which is free, can be a blessing, until it doesn't work and it isn't. You can say what you want about Windows, and many people not having much knowledge do, but at the end of the day it works.
[And yes, I realize that some with weird environments have difficulties with Windows, but when you consider the sheer number of systems it runs, and the variety of hardware/software that it supports, the fact that it almost always works is a testament to the technical skills at Microsoft. I had installed plain vanilla Ubantu, with the plain vanilla Ubantu desktop on a Dell laptop, nothing fancy, and it just up and stopped working. With a 'system error message' but absolutely no indication of what went wrong. Garbage.]
The SDR is back up and running for both AM and FM.
For those unfamiliar with OpenWebRX+, you can choose the appropriate listening profile in the settings window, to the right within the waterfall display. The parameters of the profile itself can't be modified (unless you have the super secret password). You can tune across the portion of the band contained within the profile (although there's not much there, as the antennas used to capture the Artisan Radio signals are minimal).
Generally, you can modify the visual display of the SDR within that settings window. If you don't like the window being there, you can change the opacity.
- Im a little confused with it. Why is "WFM" the band instead of "AM", (and what is WFM?).
WFM is 'Wide FM'. AM is the other band
What I mean is the talk about utilizing the SDR with the AM broadcast.. So why is the sdr playing on the WFM channel instead of the AM channel?
I admit I dont really understand the SDR 4eceiver at all. I haven't followed Artisians SDRcadventures that closely, not even sure what the ultimate objective is, or even if there is an ultimate objective, other than just to experiment with the technology (which is probably the case).
It just seems like it should be AM instead of WFM band... but like I said, I know nothing about it.
I've got both an AM and FM transmitter (the Talking Sign and the Decade MS-100 respectively). The SDR picks up over-the-air signals from both those transmitters, and the OpenWebRX+ software plays them back on your computer via a browser. It can also play other signals in the frequencies within the AM and FM profiles I set up (each about 1Mhz in width). In addition to just audio (mono only unfortunately), the software also displays the signals in both graph and waterfall form.
The FM signal is WFM (Wide FM, as distinguished from plain FM, which is narrow band, and is used, for example, by amateur radio operators on the 2 meter band). The AM signal is self explanatory.
You can switch back and forth from the AM and FM signals by changing OpenWebRX+ profiles. I attempted to explain how in the previous thread, but obviously didn't do it very well.
Yes, this is experimentation, but it is also experimentation with a purpose. I was looking for an alternate way to distribute an audio signal over the Internet without running into those onerous streaming copyright fees.
This is obviously a gray area, but you can play a radio in a public place, because the copyright fees are deemed to have been already paid by the broadcaster. There are currently no copyright categories for SDR's, but it, imo, is equivalent to playing a radio.
OpenWebRX+ is the only SDR software application that is true client/server. All processing is done on the server end (and there's a lot), where the SDR is located. All the user interface elements are generated on the server, and distributed to the client computers via a browser. That limits the network bandwidth being used, as only those user interface elements are communicated. For the FM profile I set up, it's about 250Kbps, about twice that of a normal radio audio stream. For the AM one, it's less than 100Kbps.
Most other SDR software is client-based only, with the processing and the user interface (usually custom) on a single computer with the SDR on the same computer. SDR++, another software package, does have what they call a server, so you can have the SDR on a separate computer, but all the processing and user interface is still on a single computer. That leads to excessive bandwidth use, on the order of 5-15 MB/s. You can flood your local area network quickly with those kinds of numbers, never mind bog down your Internet connection.
I hope that clarifies a few things.
Clarify somethingvfor me, are you saying that. http://artisanradio.hopto.org/ is not actually on the internet anywhere? That when I go to your website I am actually connecting directly to your computer?
Yes. Artisan Radio has its own SDR and Streaming servers.