From: YAMANASHI Takeshi <9.nashi@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /dev/audio test file
Date: Wed, 8 Dec 2004 15:43:30 +0900 [thread overview]
Message-ID: <964fd089a821b1fb2fb1cabe6f514e01@orthanc.cc.titech.ac.jp> (raw)
> my bet is on the volume. a000 is already in "/dev/audio format"
> though you might want to turn the speed down to 44100 in audioctl.
Thanks all.
I see. I should have had the speakers giving noises at least...
madplayer was the same: speakers were silent at all.
My usb configuration should be the problem, then.
As I have tested this on rather old 4th ed, I will try it with
the modern 4th ed.
--
next reply other threads:[~2004-12-08 6:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 6:43 YAMANASHI Takeshi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-13 5:56 YAMANASHI Takeshi
2004-12-13 2:44 YAMANASHI Takeshi
2004-12-12 8:56 YAMANASHI Takeshi
2004-12-13 2:35 ` Kenji Okamoto
2004-12-13 9:06 ` vdharani
2004-12-08 3:07 YAMANASHI Takeshi
2004-12-08 6:07 ` Russ Cox
2004-12-08 8:49 ` vdharani
2004-12-08 3:46 ` Dan Cross
2004-12-08 13:27 ` Sape Mullender
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=964fd089a821b1fb2fb1cabe6f514e01@orthanc.cc.titech.ac.jp \
--to=9.nashi@gmail.com \
--cc=9fans@cse.psu.edu \
/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).