From: Steve Simon <firstname.lastname@example.org>
Subject: Re: [9front] pi4 wifi and audio
Date: Sat, 12 Feb 2022 18:46:47 +0000 [thread overview]
Message-ID: <5FC4FAA8-FB1D-464B-97DB-ED467195F0D3@quintile.net> (raw)
i assume you mean adding a DAC to I2S, I2C doesn’t have the bandwidth for quality audio even at 400khz.
using and external dac over I2S can make a very significant (very measurable) difference to the quality of the audio you can extract from a rpi.
the most important part of this is locking the pi’s i2s stream to external crystals, and having quiet power supplies for the dac and any downstream gain stages.
i am afraid $1 chinese usb dacs are a poor second choice.
> On 12 Feb 2022, at 6:16 pm, hiro <email@example.com> wrote:
> yes, miller's version has wifi. i don't remember if anybody did the
> work to bring it to 9front, but in any case they didn't finish it ( ==
> mainline it).
> audio, some people wasted their time with the incomplete audio
> solution in the rpi, it but then gave up IIRC.
> some people like to add a DAC to the I2C bus, but i consider that also
> a waste of time, esp. as long as you can get 1$ USB->audio converters
> including shipping from china, the quality is 100% matching the rpi
> hardware, and a lot better than most DIY rpi audio add-ons.
> as much as i hate USB, for soundcards that's good enough and we
> already support it.
>> On 2/12/22, firstname.lastname@example.org <email@example.com> wrote:
>> So 9front on pi4 seems pretty stable. But has anyone got audio and wifi
>> working. I recall
>> reading some place that pi hardware developers kind of deviated from
>> convention so its a bit
>> tricky to get some of that stuff working. Perhaps I might also be asking for
>> some sort of
>> guide to read on how to build or deal with making drivers in 9front and some
>> steps to follow. Ponies and Unicorns I want those also, so yea.
next prev parent reply other threads:[~2022-02-12 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 17:43 thinktankworkspaces
2022-02-12 18:07 ` hiro
2022-02-12 18:46 ` Steve Simon [this message]
2022-02-12 20:56 ` Thaddeus Woskowiak
2022-02-12 22:45 ` thinktankworkspaces
2022-02-13 0:40 ` hiro
2022-02-13 2:55 ` thinktankworkspaces
2022-02-13 3:25 ` Thaddeus Woskowiak
2022-02-13 7:37 ` Steve Simon
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).