From: Matthew Frederico <matt@ultrize.com>
To: dante@virtualblueness.net
Cc: Andrew Langdon-Davies <ald2@arrakis.es>, linux-newbie@vger.kernel.org
Subject: Re: remote sound
Date: Fri, 02 Apr 2004 11:52:12 -0600 [thread overview]
Message-ID: <1080928332.6927.2.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0404020923060.31267-100000@reddevil.virtualblueness.net>
On Fri, 2004-04-02 at 08:28, dante@virtualblueness.net wrote:
> I want to do the same thing. This afternoon I'm going to try to implement
> the following idea:
>
> 1) on the client box where I plan to listen to the sound (music in my
> case), I'm going to listen for incoming tcp/ip connections using nc or
> the like and pipe the stream to /dev/dsp locally.
>
> 2) on the server box where the sound is to originate, I'm going to replace
> /dev/dsp with a local unix socket, open it using nc or the like, establish
> a tcp/ip connection to the client box and stream the data.
>
> Does this sound like a stupid idea to anyone?
Sounds like its going to use a lot of bandwidth to me.
Correct me if I am wrong, but isn't /dev/dsp for raw sound data AFTER
conversion FROM e.g. MP3 OGG WAV etc? So "redirecting" /dev/dsp will
probably lag your network substantially. I think this is a very cool
idea though, and you're probably on the right track.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2004-04-02 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 11:10 remote sound Andrew Langdon-Davies
2004-04-02 14:22 ` James Miller
2004-04-02 14:28 ` dante
2004-04-02 17:52 ` Matthew Frederico [this message]
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=1080928332.6927.2.camel@localhost.localdomain \
--to=matt@ultrize.com \
--cc=ald2@arrakis.es \
--cc=dante@virtualblueness.net \
--cc=linux-newbie@vger.kernel.org \
/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