public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Victor Tsaran" <vtsaran@nimbus.ocis.temple.edu>
To: <speakup@braille.uwo.ca>
Subject: Re: hearing the audio from a remote system
Date: Sun, 8 Oct 2000 17:47:44 -0700	[thread overview]
Message-ID: <000801c031a4$8e410fc0$9c059ed8@wang> (raw)
In-Reply-To: <3.0.6.32.20001008142929.0079f990@mail.ufw2.com>

How about using Shoutcast server? You start stream from a 128K stream, then
with IPchains forward it to the IP address (you can fake one) to the
Shoutcast server, then connect to the Shoutcast server from your own
machine. Of course, Telnet will not help you in this cast, only for issuing
commands remotely.
Best,
Vic

******* ******* *******
have you thought of visiting Cybertsar's Internet Kingdom? It is still
alive!
Here is the URL:
http://nimbus.ocis.temple.edu/~vtsaran/
******* ******* *******
----- Original Message -----
From: "Brent Harding" <bharding@ufw2.com>
To: <speakup@braille.uwo.ca>
Sent: Sunday, October 08, 2000 12:29 PM
Subject: Re: hearing the audio from a remote system


> Oh, there's no way to get audio over telnet like that? I was hoping some
> how I could listen to high bandwidth streams at a bandwidth I can work
with
> on my modem, as there's quite few streams 20k and under.
> At 08:36 AM 10/8/00 -0500, you wrote:
> >It is quite simple. What you want to do can't be done. When you telnet
you
> >are working on the remote machine. Fully and completely. All commands are
> >carried out the same as if you were on that machine's console (unless
> >prohibited or some such thing).
> >
> >What you really want is some sort of proxy program to accept the
streaming
> >data and then forward it to you. As far as changing the bit rate it is
> >most likely a forget it situation. Not on current computers.
> >
> >--
> >Kirk Wood
> >Cpt.Kirk@1tree.net
> >------------------
> >
> >It's not reality that's important, but how you perceive things.
> >
> >
> >
> >_______________________________________________
> >Speakup mailing list
> >Speakup@braille.uwo.ca
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



  parent reply	other threads:[~ UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Brent Harding
 ` Tommy Moore
   ` Brent Harding
 ` Kirk Wood
   ` Charles Hallenbeck
   ` Chris Nestrud
     ` Brent Harding
       ` Victor Tsaran
       ` Chris Nestrud
         ` Brent Harding
     [not found] ` <Pine.LNX.4.21.0010080834250.789-100000@localhost.localdoma in>
   ` Brent Harding
     ` Kirk Wood
     [not found]     ` <Pine.LNX.4.21.0010081428270.789-100000@localhost.localdoma in>
       ` Brent Harding
         ` Kirk Wood
     [not found]         ` <Pine.LNX.4.21.0010081644540.789-100000@localhost.localdoma in>
           ` Brent Harding
             ` Victor Tsaran
               ` Brent Harding
     ` Victor Tsaran [this message]
       ` Kirk Wood
       ` Brent Harding
         ` Victor Tsaran
     [not found]       ` <Pine.LNX.4.21.0010081908490.789-100000@localhost.localdoma in>
         ` Brent Harding
 ` Geoff Shang
   ` Brent Harding

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000801c031a4$8e410fc0$9c059ed8@wang' \
    --to=vtsaran@nimbus.ocis.temple.edu \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).