From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] opus support
Date: Mon, 13 Jan 2020 19:49:13 -0500 [thread overview]
Message-ID: <69040F07-0D94-4D94-8372-FB30240BED2E@stanleylieber.com> (raw)
In-Reply-To: <alpine.LNX.2.00.2001140040550.7981@phi>
On January 13, 2020 6:45:37 PM EST, Julius Schmidt <aiju@phicode.de> wrote:
>I'm against important 70k lines of foreign source code into the
>plan9front
>repository.
>
>It would be nice to have a 9front-extra repository for stuff like this.
>It
>wouldn't be part of the default install, but there'd be some script
>included to pull it.
>
>Not sure where a good canonical place in the file hierarchy would be..
>/sys/extra?
>
>On Mon, 13 Jan 2020, qwx wrote:
>
>> Hello,
>>
>> I recently investigated if it's worth it to me to replace mp3 with
>another codec
>> such as opus for storing my music library in. I've concluded that it
>is.
>>
>> Based on mischief's own earlier efforts, I've ported the latest
>versions of xiph's
>> opusdec and opusenc implementation along with their supporting
>libraries. I've
>> also changed their basic usage to adhere with our own, and their
>defaults to
>> conform with default audio(3) format. Additionally, I've added
>changes to
>> file(1), play(1), /sys/lib/plumb/basic and the audio(1) manpage to
>integrate
>> these fully.
>>
>> For those interested, here's a summary of my investigations:
>>
>> http://nopenopenope.net/posts/audcomp
>>
>> It also contains instructions for setting opus up.
>>
>> I have not updated my contrib directory yet, sorry.
>>
>> Note that the mkfiles the patches add for building the alien code
>need work.
>>
>> I am not sure this is worth importing into 9front, although I'd
>welcome it. The
>> programs and libraries are over 70k lines of code.
>>
>> Cheers,
>>
>> qwx
>>
/sys/dst
sl
next prev parent reply other threads:[~2020-01-14 0:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 22:47 qwx
2020-01-13 23:45 ` [9front] " Julius Schmidt
2020-01-14 0:49 ` Stanley Lieber [this message]
2020-01-14 11:41 ` hiro
2020-01-14 12:04 ` Steve Simon
2020-01-14 12:32 ` Rodrigo G. López
2020-01-14 12:55 ` Steve Simon
2020-01-14 13:02 ` hiro
2020-01-14 13:09 ` Steve Simon
2020-01-14 15:50 ` Rodrigo G. López
2020-01-14 16:02 ` Steve Simon
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=69040F07-0D94-4D94-8372-FB30240BED2E@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).