I believe the NOAA AM bandwidth is 5 kHz...especially on the older transmitters... a sampling rate of 16 kHz would be expected to handle up to 8 kHz without aliasing -- however, aliasing could also be introduced with higher volume input levels, and noise within the source, so an even higher sampling rate could produce a "cleaner" sound, to the ears, than the lower sampling rate...especially if you have a 'dirty' or poor signal in, in many cases, believe it or not... I use 24 to 56 K

Exactly, when I first did the WU stream, I started with the recommended 16 bit rate and it sounded like it was coming out of a tin can and very digital sounding, so I upped it 24, better, then 32, better yet and then finally settled on 64 with 48k sampling and it sounded more like you were listening to it from the weather radio itself.

I suppose it's about getting the word out, not many know about this. Also, if Weather Underground is actually "working on it", that suggests they will have their server back up at some point and everyone would go back to streaming to them. Time will tell I guess.

Agreed, the vast majority of the WU suppliers for instance, I am sure are not aware of this option, probably are not on this forum. Although I doubt we have everyone yet who has a stream and is on this forum. How to get out the word? Note should also have an invite on the page itself.

I have found the side discussion on the SDR method to be quite useful to the point where I am in the process of putting one together with a raspberry pi myself and see if I can't bring in another feed.

Ok, so I switched to using an RTL SDR instead of a regular radio for the MSP one. It's about the same, but now I don't need the radio or sound card and it's on a Raspberry Pi 3 and I'm using this: http://www.nooelec.com/store/sdr/sdr-receivers/nesdr-mini-2-plus.html and I purchased a kit that includes an SMA adapter which have connected to an antenna in my attic. Here's what I used for the command line, I started it in screen so that I can detach from it:

Tim - Can you elaborate on what was needed to set this up? In particular, what is listening on port 8000? I'm trying to replicate your work, hoping to build a script to automate the installation so anyone can easily set up a NWS stream.....

Ok, so I switched to using an RTL SDR instead of a regular radio for the MSP one. It's about the same, but now I don't need the radio or sound card and it's on a Raspberry Pi 3 and I'm using this: http://www.nooelec.com/store/sdr/sdr-receivers/nesdr-mini-2-plus.html and I purchased a kit that includes an SMA adapter which have connected to an antenna in my attic. Here's what I used for the command line, I started it in screen so that I can detach from it:

Tim - Can you elaborate on what was needed to set this up? In particular, what is listening on port 8000? I'm trying to replicate your work, hoping to build a script to automate the installation so anyone can easily set up a NWS stream.....

Sure, so I started with a Raspberry Pi and installed the following (after updating of course):

Change the sourcepassword element to the password you set in icecast.xml and change filename to stdin, update the url and change /stream to what you want your stream to be mounted to, also update the svrinfo elements:

<ezstream> <url>http://localhost:8000/tim273/edina</url> <sourcepassword>your_password</sourcepassword> <format>MP3</format> <filename>stdin</filename> <stream_once>1</stream_once> <!-- The following settings are used to describe your stream to the server. It's up to you to make sure that the bitrate/samplerate/channels information matches up with your input stream files. Note that <svrinfoquality /> only applies to Ogg Vorbis streams. --> <svrinfoname>Minneapolis, Minnesota Weather Radio</svrinfoname> <svrinfourl>http://www.wunderground.com</svrinfourl> <svrinfogenre>Weather</svrinfogenre> <svrinfodescription>NOAA Weather Radio KEC65 162.55Mhz</svrinfodescription> <svrinfobitrate>64</svrinfobitrate> <svrinfochannels>2</svrinfochannels> <svrinfosamplerate>48000</svrinfosamplerate> <!-- Prohibit the server to advertise the stream on a public YP directory: --> <svrinfopublic>0</svrinfopublic></ezstream>

#!/bin/sh -e## rc.local## This script is executed at the end of each multiuser runlevel.# Make sure that the script will "exit 0" on success or any other# value on error.## In order to enable or disable this script just change the execution# bits.## By default this script does nothing.

This attaches to the screen that was created, and then Ctrl+A, D to detach from it. Don't type Ctrl+C as that will kill it. Using screen is an alternative to using a service, but if you're good with service scripts, feel free to write one of those. I had to add the sleep in there to give all the other services time to start up.

And then substitute the device ID of the RTL SDR dongle (obviously plug it into the USB port) for the ATTRS{idVendor} (0bda in this case) value and then the model in the ATTRS{idProduct} part (2838 in this case). In terms of order, this one should probably be done before installing everything. You'll need to reboot for it to take effect.

I will give this a shot myself this weekend. I think I have everything I need at this point. I hope to get another feed up in addition to Manassas this weekend, Hagarstown MD using the SDR comes through quite nicely when properly filtered.

I have a question regarding the standardization of stream names. At least in these parts, each NWS office operates more than one transmitter within their service area...and each transmitter sends alerts for only its service area (and sometimes also relays them for neighboring NWS offices).

For example, NWS Albany operates 7 different "satellite" transmitters outside of their main Albany one - three in NY, one in western CT, two in western MA, and one in southern VT. The one nearest to me (WXL37/Highland NY) also relays alerts from NWS NYC for my county, which doesn't have direct radio coverage from the NYC office. Obviously, the transmitter location is important in the stream name. If someone in southern VT put up an "Albany" stream, I would never hear the local alerts!

Currently, it appears that the streams are named in the format: State, City, Frequency. I propose that the stream names be standardized as: State, NWS Forecast Office City, Transmitter City, Callsign, Frequency. That should clarify what transmitter the stream is coming from, to clear up any ambiguities.

It is a very good question. My NWS office has 11 transmitters scattered around central part pf the state. This does not count the 4 other NWS offices that cover the 4 corners with their repsective transmitters. There are a total of 20 transmitters in my state.

Thank you for the links. I had not seen the .pdf in the first one. Downloaded that. The second link, I see they finally updated it. I had downloaded all of the maps for Arkansas several years ago.

RE station names:First, I'm working on new player which will link back to your website that's providing the stream. which I cannot accomplish in the current player, for some reason..I think it best to use the Station "location" or "Station Name" for that particular transmitter that is being streamed, rather than the 'parent' station... which I'm trying to do...For example, a 'repeater' goes down, and naming after parent would imply parent was down...

Only have a few stations, and already have one with NOAA giving "name/location" as one thing on their map, and two possibilities for either "location" or "Transmitter Name"...

This is what I'd like to see 'standard', I think... When they identify themselves, the tag it with something like "transmitting from' or 'located at' or something... a few say something like "NWS OFFICE in Louisville, transmitting from a station located in Frankfort..." or something else confusing... the "Frankfort, location Callsign, and Frequency" is what I think we standardize with...

This is what I'd like to see 'standard', I think... When they identify themselves, the tag it with something like "transmitting from' or 'located at' or something... a few say something like "NWS OFFICE in Louisville, transmitting from a station located in Frankfort..." or something else confusing... the "Frankfort, location Callsign, and Frequency" is what I think we standardize with...

Whatcha think?Mike

So I think that's what I have going, if you look at my screenshot above my listed as:

I will give this a shot myself this weekend. I think I have everything I need at this point. I hope to get another feed up in addition to Manassas this weekend, Hagarstown MD using the SDR comes through quite nicely when properly filtered.

My test SDR was previously online running dump1090 for a few years, and it has stutters/hiccups from heat and old age. I'll have to order two new SDR's, since I can pick up NOAA signals from two different transmitters/forecast offices and stream both. I'm going to leave the stream running, with a disclaimer that it does have occasional dropouts and "Max Headroom" moments.

Well never worked with a Raspberry Pi before so this is becoming a bit of a learning experience. Got the op system installed (that was the easy part). I think I have the rtl fm software installed, although other than saying it is receiving I have no way to verify yet. (I know the dongle works because I had it working on more normal machine and using the windows version of SDR. Now trying to get either icecast or sox working, but have run out of time today. Downloaded but have to compile it, and there is no good docs that I can find at this point on the steps one must follow and the proper directories to put the files, so I keep tripping over myself. I hate to say how long it been that I had to go through a step by step process to compile code, and things have changed a lot since that time (I didn't have grey hair then among other things).

Anyway will pick this up tomorrow and see if I can't at least get it talking on my internal network.

Well never worked with a Raspberry Pi before so this is becoming a bit of a learning experience. Got the op system installed (that was the easy part). I think I have the rtl fm software installed, although other than saying it is receiving I have no way to verify yet. (I know the dongle works because I had it working on more normal machine and using the windows version of SDR. Now trying to get either icecast or sox working, but have run out of time today. Downloaded but have to compile it, and there is no good docs that I can find at this point on the steps one must follow and the proper directories to put the files, so I keep tripping over myself. I hate to say how long it been that I had to go through a step by step process to compile code, and things have changed a lot since that time (I didn't have grey hair then among other things).

Anyway will pick this up tomorrow and see if I can't at least get it talking on my internal network.

Bob

Hi Bob,

Actually you shouldn't have to compile anything, everything you need should be in the repository.

What you can do is type sox and it should tell you something like 'sox not found, type sudo apt-get install sox' so whatever it is it should be in the repository.

Now trying to get either icecast or sox working, but have run out of time today. Downloaded but have to compile it, and there is no good docs that I can find at this point on the steps one must follow and the proper directories to put the files, so I keep tripping over myself.

As Tim wrote, all of the software is already built/packaged in the Raspbian package repository! These three lines will install it all:

Thanks folks, I didn't see that they were already there in any of the docs, so as usual went off and made things a lot harder than I had to. Now lets see if I managed to mess it all up because of trying to work things from scratch. When you put together your script be sure to cover the unfamiliarity issue with the hardware.

Thanks folks, I didn't see that they were already there in any of the docs, so as usual went off and made things a lot harder than I had to. Now lets see if I managed to mess it all up because of trying to work things from scratch. When you put together your script be sure to cover the unfamiliarity issue with the hardware.

Bob

The beauty of the Raspberry Pi is you mess things up, just wipe your your SD card (or get another one) and start over. I've done that many times.

For those not familiar PI, SDR, etc It can be done "simpler" if your mind is as stiff as mine is ... I got into this stuff 20 years too late, and have a severe brain dietary restriction on PI, raspberry or otherwise.

It can be done "simpler" if your mind is as stiff as mine is ... I got into this stuff 20 years too late, and have a severe brain dietary restriction on PI, raspberry or otherwise.

This old dog has been working in the IT field for 31 years now, and he intends to make a bootable Raspberry Pi SD card image that will only require you to enter your wifi network password, pick a frequency, and enter a stream name.....

darn... all I've got is a radio, weather pc, broadwave and an audio cable... but I did enough of that other stuff in my 35 year electronics career... if it's smaller than a 25 watt resistor I can no longer see it. . Took 2 Star Wars films before I figured out Obi Wan wasn't a prototype OB2 regulator , which did resemble a light sabre prototype when fired up... ...tried a couple of em stacked to run Blitzortung, but made too much noise...

Gotta version 2 stream player about to go online... think got111 streams available now...

Now trying to get either icecast or sox working, but have run out of time today. Downloaded but have to compile it, and there is no good docs that I can find at this point on the steps one must follow and the proper directories to put the files, so I keep tripping over myself.

As Tim wrote, all of the software is already built/packaged in the Raspbian package repository! These three lines will install it all: