From: Kenji Okamoto <okamoto@granite.cias.osakafu-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] VT6306 chip is for OHCI or UHCI?
Date: Wed, 25 Aug 2004 09:23:20 +0900 [thread overview]
Message-ID: <f8c21c55e1bf6d77a7d0b0d7c77fb5fd@granite.cias.osakafu-u.ac.jp> (raw)
In-Reply-To: <83c238fa25c5eab43cf68002bd9c7437@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
Thanks Sape for your kind comment.
This time, my case is at now, however, related to the number of
channels, 8 (7.1) for this case, but hard coded as 2 in the source.
After solving this, I may touch the problem you encountered.
By the way, I learned somewhat so far:
>desc 1.0 [12] 0x24: 1.1: Audio Input Terminal Descriptor
> bTerminalId 4, wTerminalType 0x201 (<unnamed>), bAssocTerminal >0 bNrChannels 2, wChannelConfig 3, iChannelNames 0 iTerminal 0
>Device can record from <unnamed>
This 0x201 must be microphone.
>desc 1.0 [12] 0x24: 1.1: Audio Input Terminal Descriptor
> bTerminalId 5, wTerminalType 0x605 (<unnamed>), bAssocTerminal >0 bNrChannels 2, wChannelConfig 3, iChannelNames 0 iTerminal 0
>Device can record from <unnamed>
This 0x605 may be S/PDIF... This device has S/PDIF input and output for
light connectors. Unfortunately, this device has no CD input connector,
which may make me to forget internal DVD drive of the desk top?
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 3921 bytes --]
From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] VT6306 chip is for OHCI or UHCI?
Date: Tue, 24 Aug 2004 10:07:19 -0400
Message-ID: <83c238fa25c5eab43cf68002bd9c7437@plan9.bell-labs.com>
> I got a USB audio interface, too for that USB card, the name of which
> is HCMI-106, named as 玄音(gen-on) probably Japanese local, too.
> It's not included in your compatible list of course.
>
> It has problem just now, getting the error message of
> "Can't configure playout for 44000 or 48000 Hz".
I've had some struggles with this. According to the specs, one sets the
playout speed by putting the number 44100 (or some other number of course)
in a control message to set speed. I found a few devices with discrete speed
settings (the one you have has these) where, instead of writing the speed,
you have to write the number of the setting (i.e., 0, 1, 2, 3, ... or just 0 or 1
in your case). I attempt both and, if both fail, I print that message.
I would try to ignore that message for now and see if it works at all
Sape
next prev parent reply other threads:[~2004-08-25 0:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 7:56 Kenji Okamoto
2004-08-23 15:00 ` Sape Mullender
2004-08-24 0:57 ` Kenji Okamoto
2004-08-24 3:13 ` Kenji Okamoto
2004-08-24 14:07 ` Sape Mullender
2004-08-25 0:23 ` Kenji Okamoto [this message]
2004-08-25 1:02 ` Sape Mullender
2004-08-25 1:27 ` Kenji Okamoto
2004-08-25 2:00 ` Kenji Okamoto
2004-08-25 3:06 ` Sape Mullender
2004-08-24 6:53 ` Kenji Okamoto
2004-08-24 7:17 ` Kenji Okamoto
2004-08-25 4:44 ` Kenji Okamoto
2004-09-01 6:06 ` Kenji Okamoto
2004-09-01 8:58 ` Kenji Okamoto
2004-09-02 8:21 ` Kenji Okamoto
2004-09-09 8:00 ` Kenji Okamoto
2004-09-09 8:15 ` Kenji Okamoto
2004-09-09 9:06 ` Kenji Okamoto
2004-09-09 9:48 ` Kenji Okamoto
2004-09-10 3:03 ` Kenji Okamoto
2004-09-10 10:36 ` Bruce Ellis
2004-08-24 3:13 Kenji Okamoto
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=f8c21c55e1bf6d77a7d0b0d7c77fb5fd@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).