From: Bob Ham <node@users.sourceforge.net>
To: ALSA Development Mailing List <alsa-devel@lists.sourceforge.net>
Subject: Re: dolby digital output
Date: 18 Feb 2002 15:00:56 +0000 [thread overview]
Message-ID: <1014044456.1131.10.camel@insanity> (raw)
In-Reply-To: <20020218140812.B21938@ecs.soton.ac.uk>
On Mon, 2002-02-18 at 14:08, Steve Harris wrote:
> AC3 is much
> more complicated, and you couldn't feasibly reproduce the encoded output
> without having followed the spec (unless I'm missing something).
Assuming you haven't signed (or clicked "yes" on) any agreement in order
to get the spec, I can't see what they can legally do. Unless there's
software patents, but those are US-specific anyhow (for the moment) so
they don't really matter.
Bob
--
Bob Ham: bob@ham.org
My music: http://mp3.com/obelisk_uk
GNU Hurd: http://hurd.gnu.org/
Do your bit for UK drugs law reform: http://www.angeldeclaration.com/
A pessimist expects the weather to get worse.
An optimist hopes it will improve.
A realist adjusts the sails.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next prev parent reply other threads:[~2002-02-18 15:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-17 6:33 dolby digital output Hod McWuff
2002-02-17 17:15 ` Andy Lo-A-Foe
2002-02-17 17:47 ` Markus Plail
2002-02-17 18:09 ` James Courtier-Dutton
2002-02-18 14:08 ` Steve Harris
2002-02-18 14:19 ` Steve Harris
2002-02-18 15:00 ` Bob Ham [this message]
2002-02-18 16:13 ` Steve Harris
2002-02-18 13:20 ` Takashi Iwai
2002-02-17 17:48 ` James Courtier-Dutton
[not found] <1013970073.2394.17.camel@samoyed.wuff.dhs.org>
2002-02-17 18:44 ` 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 19:09 ` Dan Hollis
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=1014044456.1131.10.camel@insanity \
--to=node@users.sourceforge.net \
--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.