All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Koch <Carsten.Koch@icem.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: optical SPDIF output on Abit NF7 nforce2 main board.
Date: Tue, 02 Sep 2003 22:31:40 +0200	[thread overview]
Message-ID: <3F54FE2C.9020208@icem.com> (raw)
In-Reply-To: <s5hisobmile.wl@alsa2.suse.de>

Takashi Iwai wrote:
...
> looking at the nvidia's driver code, it seems that spdif on nforce
> supports only 48k in fact.
> i'll add the restriction on the driver side, then.
> could you try the attached patch?

Sorry for the delay, I was travelling all day.

I did apply your patch (to my old cvs version, still having
problems accessing sourceforge).

It made matters better for mpg321 and worse for alsaplayer.

"mpg321 -o alsa09 --audiodevice hw:0,1" still plays 44Khz sounds
too fast, as expected.

"mpg321 -o alsa09 --audiodevice plughw:0,1" now plays 44Khz sounds
correctly. Excellent!

"alsaplayer -d hw:0,1"  still plays 44Khz sounds too fast, as expected.

"alsaplayer -d plughw:0,1" now issues the following error messages:
error on set_period_size (512)
Unavailable hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (166 341334)
PERIOD_SIZE: (7 15053)
PERIOD_BYTES: (28 60212)
PERIODS: (0 2151)
BUFFER_TIME: (158 341316)
BUFFER_SIZE: [7 15052]
BUFFER_BYTES: [28 60208]
TICK_TIME: 10000
error on set_period_size (1024)
Unavailable hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (166 341334)
PERIOD_SIZE: (7 15053)
PERIOD_BYTES: (28 60212)
PERIODS: (0 2151)
BUFFER_TIME: (158 341316)
BUFFER_SIZE: [7 15052]
BUFFER_BYTES: [28 60208]
TICK_TIME: 10000
failed to configure output device...trying OSS

And plays the sound file via the analog output.

Carsten.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-09-02 20:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-01 11:28 optical SPDIF output on Abit NF7 nforce2 main board Carsten Koch
2003-09-01 12:56 ` Takashi Iwai
2003-09-01 13:42   ` James Courtier-Dutton
2003-09-01 13:51     ` Takashi Iwai
2003-09-01 13:45   ` Carsten Koch
2003-09-01 14:11     ` Takashi Iwai
2003-09-01 14:40       ` Carsten Koch
2003-09-01 15:17         ` Takashi Iwai
2003-09-01 15:58           ` Carsten Koch
2003-09-01 16:39             ` Takashi Iwai
2003-09-01 17:57               ` Carsten Koch
2003-09-01 18:40                 ` Takashi Iwai
2003-09-01 19:13                   ` Carsten Koch
2003-09-01 21:00                     ` Carsten Koch
2003-09-02 13:06                       ` Takashi Iwai
2003-09-27 18:00                       ` optical SPDIF output on Abit NF7 nforce2 main board. (Summary) Carsten Koch
2003-09-28 19:41                         ` Carsten Koch
2003-09-28 20:31                           ` James Courtier-Dutton
2003-09-28 20:41                           ` optical SPDIF output on Abit NF7 nforce2 main board.(Summary) Gerald Raaf
2003-09-02 13:21                     ` optical SPDIF output on Abit NF7 nforce2 main board Takashi Iwai
2003-09-02 20:31                       ` Carsten Koch [this message]
2003-09-03  8:35                         ` Takashi Iwai

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=3F54FE2C.9020208@icem.com \
    --to=carsten.koch@icem.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.