The low power long wave radio network is in the talking stage, related to our long wave transmitter projects, and these thoughts rattled in the head while raking leaves.
The low power long wave radio network is in the talking stage, related to our long wave transmitter projects, and these thoughts rattled in the head while raking leaves.
Last week I registered the domain name “worldroundradio.net,” without actually having a need for it. I just liked the fact that nobody else is using my main slogan. It could be a radio network site, or it could simply link to the kdx site.
I also learned that no one owns the domain name lrn.net or lrn.com
I am not going to register those names, so if you want to own the LRN domain name, now’s your chance.
If you do register lrn as a domain name I could provide the website it points to, and the programming, which is to be submitted by low power net members, could be programmed and streamed as a joint-effort by me and you.
For the network, if it happens and if I am the stream site, I would add a SAM broadcaster that would be programmed to start program audiofiles at their scheduled time, along with network IDs and announcements.
After a cluster of network program feeds is concluded, the LRN Network would go silent and the local stations would fill with their own local programming, just like traditional network-affiliate relations.
Some programs could be fed at several times, giving stations a choice of when they decide to fit it to their schedule. And so on.
Like old time radio networks, the LRN could be active only during certain times of the day.
The leaves were raked, I came indoors, typed this e-mail, and plan a cup of coffee.
Cart First
The cart is ahead of the horse, and there is no horse.
The LRN is a great idea in principle, and the ideas I just posted are truly amazing, but several ingredients are missing.
Second, there are no programs for the network to run as of this time;
Third, or, First, There are no long wave Part 15 stations and non of the stations that don’t exist have agreed to carry network programs which don’t exist;
Fourth, that is, third, once the network is all put together as I so well described it, who would actually do the day to day work keeping it running? See…. nobody. No horse.
I still haven’t had that coffee.
Episode IV…A New Hope
“There are no long wave Part 15 stations”
This is not entirely true. Although my LW TX is still on the prototype board, it is operating and feeding a long wire 45 feet in length with a 5 foot ground lead connection to the ground radial system of my MW 3 meter stick, and currently transmitting A3E of the regular programs running on the AM, FM and 3 net streams.
“there are no programs for the network to run as of this time”
Programs specifically for the LW network perhaps, but that does not mean that participating stations can’t submit other recorded programs to the ftp system I set up specifically for this network. So far there are 3 stations singed in to the ftp and have access.
“who would actually do the day to day work keeping it running?”
This is why I recommended the ftp system first before going with a live stream network system. This allows the stations to mesh in the LW network programs into their existing schedules and operations. It also allows for more time to properly set up a main network feed and iron out the “who’s doing what, when, how, etc” in regards to maintaining and operation of a primary network stream.
Some of us operate 24/7/365. My LW station will be a 24/7/365 operation as is my other stations. Other stations out there also operate 24/7 so a primary network stream feed would also need to be a 24/7 operation.
Also timing will be an issue due to the nature of internet streaming and its inherent delays. Stream servers work in a “series” mode, meaning each connection to a stream server is buffered by as much as 2 minutes between each connection, and that delay time depends on two main factors, the stream bit rate and hop count between stream source point and destination point. The higher the bit rate of the stream, the less delay, but if the hop count is high, that delay can increase.
There is no way to accurately go in and come out of the network stream feed without taking into account the issues I just mentioned.
Also this network stream feed MUST be from a co-located server on a major database center to ensure network stream stability and reliability. There is NO WAY any home internet connection is going to be stable enough to supply the network stream feed. You can encode to the network stream server from home if the server is located on a stream provider or host, and that is because the stations will not be connecting to the home connection’s IP address directly. You would need at least a T1 DEDICATED connection or better to have a reliable network stream feed. Anything else below that is useless and pointless.
Now the bigger problem with a network stream feed is that there is really no way to have net cue signals transmitted along with the program content. About the only way to do this would be to embed sub-audio tones and decoders to trigger events such as going to local breaks, station ID’s, station liners, and exiting the network feed properly. Otherwise stations will end up with dead air gaps or programs cut off too early or joined too late.
Until these concerns can be addressed and resolved in a practical manner, I think the ftp method is best for now, and later once all the little issues are worked out, go with a live network stream feed.
RFB
That’s Right
I forgot you invented a FTP Site for the LRN. That’s it, then. I need to link it on the Deep Voice page, which is a focal point for the transmitter project. Good work, RFB.
http://www.kdxradio.com/deepvoice.html