Bug#225585: ITP: ac3jack -- realtime AC3 stream encoder for JACK
Hello!
[CC-ing Jesse Chappell because the text is essentially his.]
[Tue, 30 Dec 2003] Alexander Winston wrote:
> On Tue, 2003-12-30 at 16:35, Robert Jordens wrote:
> > Package: wnpp
> > Severity: wishlist
> >
> > Package name : ac3jack
> > Version : 0.1.0-1
> > Upstream Author : Jesse Chappell <jesse@essej.net>
> > URL : http://essej.net/ac3jack/
> > License : GPL
> > Description : realtime AC3 stream encoder for JACK
> >
> > ac3jack is a tool for creating an AC3 (Dolby Digital) multichannel
> > stream from its JACK input ports. Using this tool, an AC3 stream (up
> > to 5.1 channels) is created in realtime and either written to a file or
> > streamed to standard output.
> > .
> > When streamed to stdout and piped through the ALSA tool "ac3dec -C",
> > the AC3 stream can be passed out the SPDIF port on your audio interface
> > for connection to a multichannel surround receiver. In this way, you
> > can achieve full 5.1 surround mixing and monitoring of your JACK
> > applications with a single digital cable, and no need for hardware
> > supporting discrete outputs and inputs.
> > .
> > AC3 is a compressed audio stream, so quality will suffer somewhat, but
> > it is the price you pay for easy surround sound.
> > .
> > JACK is a low-latency sound server. JACK allows the connection of multiple
> > applications to an audio device, as well as allowing them to share audio
> > between themselves. ac3jack also supports the features of the JACK
> > transport extension.
> > .
> > Further information can be found at
> > http://essej.net/ac3jack/.
>
> Here are my suggestions:
>
> * Change "AC3" to "AC-3," which is the way that Dolby Laboratories Inc.
> punctuates its technology.
Yes. Thanks. But people might expect "ac-3jack" or something similar then.
> * Change the first instance of "realtime" to "real-time," and change
> the second instance to "real time."
Out of my immediate judgement. English is not my native language.
Will do.
> * Enclose the URI at the bottom in <> angle brackets as discussed in
> RFC 2396, Appendix E.
Yes. You might want to suggest that in debian-policy@lists.debian.org as
general practice. For long descriptions.
Thanks for the careful reading!
Robert.
--
FORTRAN, "the infantile disorder", by now nearly 20 years old, is hopelessly
inadequate for whatever computer application you have in mind today: it is
too clumsy, too risky, and too expensive to use.
-- Edsger W. Dijkstra, SIGPLAN Notices, Volume 17, Number 5
Reply to: