Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Gaydenko <a@etver.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: ice1724: from 1.0.4 to 1.0.5a upgrading problem
Date: Wed, 14 Jul 2004 17:49:42 +0400	[thread overview]
Message-ID: <200407141749.42615@goldspace.net> (raw)
In-Reply-To: <s5h658qaf5b.wl@alsa2.suse.de>

Takashi,

To tell the truth, have not understood the word "yet": just now (with 1.0.4)
my receiver (as qjackctl) shows 96KHz (alsaplayer-jack-alsadriver-hw:0,1-spdif).
Does it mean some redesign was done for this driver since 1.0.4?

Andrew

======= On Wednesday 14 July 2004 17:32, Takashi Iwai wrote: =======
At Wed, 14 Jul 2004 17:18:03 +0400,
Andrew Gaydenko wrote:
> 
> Hi,
> 
> After upgrading the driver from 1.0.4 to 1.0.5a I'm not able to start jack server
> with 96000 rate for alsa driver. I use hw:0,1 device which is digital out in my
> Terratek  Aureon Space 7.1. Instead of 96000, jack server starts with 48000. For
> hw:0,0 the problem doesn't take place. Can anybody point me further direction to
> resolve the problem?

The digital out doesn't support 96kHz (yet)...


...

Takashi


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

  reply	other threads:[~2004-07-14 13:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 13:18 ice1724: from 1.0.4 to 1.0.5a upgrading problem Andrew Gaydenko
2004-07-14 13:32 ` Takashi Iwai
2004-07-14 13:49   ` Andrew Gaydenko [this message]
2004-07-14 13:57     ` Takashi Iwai
2004-07-16 10:58       ` Tommi Sakari Uimonen
2004-07-16 14:58       ` Andrew Gaydenko
2004-07-16 15:17         ` 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=200407141749.42615@goldspace.net \
    --to=a@etver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox