All of lore.kernel.org
 help / color / mirror / Atom feed
From: stef <stef@hardco.de>
To: alsa-devel@lists.sourceforge.net
Subject: Re: audio via ethernet (was: dolby digital output)
Date: Mon, 18 Feb 2002 18:00:44 +0100	[thread overview]
Message-ID: <3C71333C.1C775561@hardco.de> (raw)
In-Reply-To: NGBBLNODKDFPBFMBBFAFOECBCBAA.James@superbug.demon.co.uk

I think sending realtime audio data via eternet will be
extremely difficult. It should be impossible to synchronize
sample clock via ethernet. So each device has to have its
own sample clock. This requires:

- resampling units (=no lossles connections possible)
or
- large buffers to slowly adapt sample rates
  (huge variing latency, clock jitter, ...)

With S/PDIF or any other common digital audio interface
it is at least possible to synchronize the receiver
to the transmitter's clock.
So you have to resample only if you're mixing
two or more digital inputs into one output.

If you're using pro equipment, it is even possible
to remotely clock digital audio sources (wordclock line).
In this case, you never have to resample and digital
audio processing can be lossless.

But with ethernet connections it is even impossible
to use separate digital-input amplifiers for
your right and left speaker. (unless you add
extra wordclock cabling...)

I don't know how the 'Wireless Multimedia Alliance'
(www.wimedia.org, JVC, Sony,...) is going to handle these
problems. Seems as if they extend the wireless lan standard
by some sort of real-time transfers. Like USB. They call
it IEEE 802.15.3.

Any comments? Am i wrong? What about Yamaha's MLAN (ieee1394)?

Stef(an).




James Courtier-Dutton wrote:
> 
> So all I need now, is an Digital Amp with an Ethernet port for all 6 Channel
> PCM, AC3 and DTS output.
> I already have an ethernet card for my PC and a HUB.
> 
> magic.gibson.com must be stupid not to realise that what we really want is
> an AMP with an Ethernet port, not yet another sound card.
> 
> We could then just connect the AMP to the ethernet port on any PC, and have
> perfect digital quality output.
> Alsa would then not be needed, because once the audio is in packets, it
> would be better to keep it that way in the application.
> 
> One could even use Radio Lan technologies, and thus remove all the cabling
> as well.
> 
> Cheers
> James

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

  parent reply	other threads:[~2002-02-18 17:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1013970073.2394.17.camel@samoyed.wuff.dhs.org>
2002-02-17 18:44 ` dolby digital output James Courtier-Dutton
2002-02-18 14:51   ` Bob Ham
2002-02-18 15:46     ` James Courtier-Dutton
2002-02-18 16:26       ` Bob Ham
2002-02-18 16:48         ` Bob Ham
2002-02-18 17:05         ` James Courtier-Dutton
2002-02-18 18:10           ` Bob Ham
2002-02-18 19:31           ` Dan Hollis
2002-02-18 17:00       ` stef [this message]
2002-02-18 17:43         ` audio via ethernet (was: dolby digital output) James Courtier-Dutton
2002-02-18 19:33         ` Dan Hollis
2002-02-18 21:59           ` stef
2002-02-18 22:10         ` Bob Ham
2002-02-18 23:00           ` stef
2002-02-18 23:11             ` Dan Hollis
2002-02-19 11:15               ` Steve Harris
2002-02-19 13:59                 ` Jeremy Hall
2002-02-19 21:48                 ` Dan Hollis
2002-02-20 10:12                   ` Steve Harris
2002-02-18 23:12             ` Bob Ham
2002-02-18 23:13             ` Dan Hollis
2002-02-19  3:39             ` James Courtier-Dutton
2002-02-18 19:09     ` dolby digital output Dan Hollis
2002-02-18 18:20 audio via ethernet (was: dolby digital output) Jez Humble

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=3C71333C.1C775561@hardco.de \
    --to=stef@hardco.de \
    --cc=alsa-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.