docwebster (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
docwebster) wrote2004-10-14 09:34 pm
docwebster) wrote2004-10-14 09:34 pm
Radio N - Tomorrow night's show
I had mentioned running the Concert For Change and The Wall Live In Berlin 1990 tomorrow night, but got absolutely no responses. Are people just not up for it?
no subject
:)
For future reference, though, what do the acronyms you used mean? I'm just computer literate enough to use one which doesn't have problems and for my mother to phone me every two days asking if her machine is going to blow up (I tell her no, phone the Dell guys, Mum, I'm halfway across the country...).
On a side note, Doc, you ever hear of a guy named Cory Tetford? blues, gospel, rock... the man's voice has afterburners :) Think you'd like him.
alphabet soup
Windows Terminal Server: You make a TCP connection to a server. Your client displays an image of what that server would have shown if you'd logged into its GUI console. Things that would have been shown there are routed back to you, including screen updates (as bitmaps) and audio (as raw PCM). Unbelievably inefficient... but it works. You *can* browse the web from the company's webserver if you really want to.
ssh: secure shell. See also sshd. In context, allows a port on one host to be forwarded through an encrypted tunnel to another host. Connections to localhost:1056, for example, may come out on the other end as a connection from someserver:16530 to the shoutcast server carrying doc's music.
So, uhm, what usually breaks it? University freaky firewall thing isn't all that descriptive.
Re: alphabet soup
I'm not entirely sure. I'm 100% sure it's not my computer itself, as my computer is brand new and virus free (I have virus protection, but no individual firewall installed). I get my internet connection from the university network. When I asked the C&C guys what might be causing the problem, they told me it was probably the firewall causing issues.
It seems to be working okay tonight, which leads me to believe (my dad's an engineer, and he taught me to always ask 'what has changed which might be affecting this?') that it may be attributable to bandwidth - a lot of students have gone out this Firday night, and midterms are coming up, so people are hitting the books rather than the net.
I really should get myself a 'for dummies' book or eight. I did the research and learned the basics of automobile and motorcycle mechanics so that I'd understand the problems, do basic maintenance and know when my mechanic was ...er... well, shitting me. I don't even own a car at the moment - seems like the least I can do is figure out the computer and connection basics.
player buffer size, maybe?
Yes, lack of available bandwidth would do it. If the throughput to your client doesn't keep up with the shoutcast's input data rate then eventually it will drop the copy of the stream going your way... or just skip a song or two and try again. Depends on the server.
Using WinAmp version 2.80 (because it sounds better than version 5.03) navigate to plugins/input/MPEG audio/streaming and set a pretty big buffer. I have 128KB which, at doc's high datarate, should be about 18 seconds of audio. I set the threshholds at 40 and 80 percent for "start of stream" and "after buffer underrun".
I can unplug my switch from its router for several seconds without stopping the music. That should allow joe-random-neighbor to get his livejournal show_your_boobs fix without killing the tunes.
C:\WINDOWS\Desktop>ping -t callahans.seanmcpherson.com
From home I get numbers mostly in the mid 60ms range with nothing lost. Try that from school when the music won't play. Sudden increases or outright drops are the result of other demands on the network between you and doc's reflector.
From the server colocated at hurricane electric (a cable-throw over the wall from mae-west) I get times in the low 90ms range.