[Seattle-editorial] Re: [Imc-seattle-radio] modified radio button proposal

nathaniel t vsea75 at hotmail.com
Sat Oct 5 14:47:12 PDT 2002


It's been brought up to me privately that 96K audio service might not be a 
good use of our DSL line.  That's certainly a reasonable opinion.

Anyone can check our total current stream load on one page at

http://www.shoutcast.com/?s=indymedia

These things are easy to change.  We could actually change the bandwidth 
menu every few minutes if we wanted to, but there would be no reason to do 
that.

I think it's a good idea to serve at 16K for people with 26.4 connections 
(which are actually very common), but 16K really sounds nasty, and I think 
we should have a higher-quality option or options for listeners who would 
appreciate them.

What that option or options should be is a subject for discussion.

I'll be happy to help implement whatever y'all suggest.

Another option is putting the stream encoder DSP's and the DNAS applications 
on different machines and co-locating the DNAS box at Speakeasy or Loudeye 
or somewhere else where more bandwidth would be available.  That way only 
one copy of each kind of stream would go through the DSL line.  I personally 
think this would be a good idea.

For everyone's information, the fact is that we rarely have more than four 
listeners at once.  I suspect the streams have only been a significant 
resource load during Reclaim The Media.  It would have been great to serve 
at 16K then, but I hadn't figured it out yet.

GLOSSARY:
>DSP    digital dignal processor
>        feeds one copy of a stream to a DNAS
>DNAS   distributed network audio server
>        sends N copies of a stream out to listeners

----Original Message Follows----
From: jonathan lawson <jonathan at indymedia.org>
To: "nathaniel t" <vsea75 at hotmail.com>,imc-seattle-radio at indymedia.org, 
seattle-editorial at indymedia.org
Subject: Re: [Imc-seattle-radio] modified radio button proposal
Date: Sat, 05 Oct 2002 09:34:26 -0700

Hey.

Since there hasn't been an actual radio group for a while, Jason and I and 
sometimes others have been just kind of making decisions as to where things 
point on the website, what the programming is, etc. It's great to have 
someone actively thinking about this stuff and I'm going to go ahead and 
make the change Nathaniel suggests. [as soon as Stallman is back up 
anyway--appears to be down]. I'm sure that post-RTM there will continue to 
be more interest in radio progamming--in fact it looks like there's a little 
radio group forming who can continue to make decisions about progamming, # 
and bandwidth of streams etc.

On a related note, at the last general meeting Brandon wisely brought up the 
complicated topic of ad-hoc vs. process--could also be called autonomous vs. 
collective, or "how do you decide what things at the IMC you have to just do 
yourself, which things you can ask someone else to do and expect to get 
done, and which things are done only by the approval of working groups, the 
spokescouncil or at general meetings?" Editorial probably has a lot to say 
about this since (1) we have a relatively clear working group charter and 
process for getting certain things done and (2) there are also things within 
the editorial/tech continuum which get done more ad hoc--changing info on 
the sidebar has been an example.

I think this is on the agenda for the next general meeting, which I am not 
sure I'll be in town for. Maybe this group could kick some conversation 
about this onlist before then...

JL


At 11:40 PM 10/4/2002 -0700, nathaniel t wrote:
>I propose to list three separate links immediately below the graphic button 
>on the Seattle indymedia website that says "Radio IMC."  The specific text 
>I propose is as follows:
>
>bandwidth (bps):
>16K | 40K | 96K
>
>The specific code I propose is listed below between the tags
><!-- *** PROPOSED NEW CODE STARTS HERE *** -->
>and <!-- *** PROPOSED NEW CODE ENDS HERE *** -->
>
>I have included enough of the current web page code that you can clip the 
>following text, save it as whatever.html, open it with a browser, see what 
>it looks like, and test the new part yourself.  The audio connections are 
>already implemented and have been tested to my satisfaction :-)








_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com




More information about the Seattle-editorial mailing list