Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Bruce Paterson <bruce@tele-ip.com>,
	alsa development <alsa-devel@lists.sourceforge.net>
Subject: Re: Am I asking the right people ?
Date: Mon, 02 Dec 2002 15:57:46 +0100	[thread overview]
Message-ID: <s5hvg2ca2ol.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5hsmxlzo83.wl@alsa2.suse.de>

At Thu, 28 Nov 2002 16:51:56 +0100,
I wrote:
> 
> At Wed, 27 Nov 2002 10:46:53 +0100 (CET),
> Jaroslav wrote:
> > 
> > On Wed, 27 Nov 2002, Bruce Paterson wrote:
> > 
> > > Am I sending these queries about the operation of alsa through the API 
> > > to the right place ?  I'm trying to use alsa for a real scientific
> > > application and I'm starting to worry it simply isn't ready yet.
> > > 
> > > I don't pretend to be a developer of alsa drivers themselves, and I'd 
> > > hoped I didn't need to become one.  I understand alsa needs many people 
> > > debugging it and finding problems to make it bulletproof (afterall there 
> > > would be a myriad of different possible configurations people can use).
> > > 
> > > However, the silence I get in reply to queries is golden (unlike the
> > > distortion I'm getting from the soundcard) !
> > > 
> > > It's possible I'm not using the alsa API in the way intended and 
> > > bringing the problems upon myself, but please, somebody tell me !
> > > 
> > > It would be a real blow to the progress of linux in this company if all 
> > > the alsa work had to be scrapped.
> > > 
> > > Apologies for the frustrated tone.
> > 
> > Sorry, I haven't EWS88 on my table. It seems that the problem is with the 
> > DAC initialization, but it's difficult to debug these things without 
> > hardware. Perphaps, if you can gather information about wiring of 
> > electrical components on this soundcard, I can look to datasheets what can 
> > be wrong.
> 
> this hardware is out of my box atm, but i can check it tomorrow.

as far as i've tested, my ews88mt works fine with the current cvs
release.  32bit/96kHz playback seems for 10min.

except for the distortion problem about two minutes with your app,
what kind of problem are you having?  i'd been on vacation so i
couldn't keep tracking the thread.

i'll be able to test the same program on my machine.


Takashi


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

  reply	other threads:[~2002-12-02 14:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21  0:57 Plea to help save me from Windows !!! Bruce Paterson
2002-11-21  2:06 ` Daniel Haus
2002-11-21  6:02   ` Bruce Paterson
2002-11-25  7:36     ` Half Speed on rc6 ? Bruce Paterson
2002-11-25 12:02       ` Jaroslav Kysela
2002-11-26  0:41         ` Bruce Paterson
2002-11-27  7:23           ` Am I asking the right people ? Bruce Paterson
2002-11-27  9:46             ` Jaroslav Kysela
2002-11-28 15:51               ` Takashi Iwai
2002-12-02 14:57                 ` Takashi Iwai [this message]
2002-11-27 13:24             ` Paul Davis
2002-11-27  7:48         ` James Courtier-Dutton
     [not found] <20021127133237.71BFE33E8C@mail.tele-ip.com>
2002-11-28  2:00 ` Bruce Paterson

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=s5hvg2ca2ol.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=bruce@tele-ip.com \
    --cc=perex@suse.cz \
    /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