From: Takashi Iwai <tiwai@suse.de>
To: Howard Abrams <abramsh@acm.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Application using ALSA-driver es-1968 for Maestro-2e: Bug or my fault?
Date: Fri, 21 Jun 2002 19:39:39 +0200 [thread overview]
Message-ID: <s5h1yb0a5us.wl@alsa2.suse.de> (raw)
In-Reply-To: <3D136332.1000903@acm.org>
Hi,
At Fri, 21 Jun 2002 10:32:34 -0700,
Howard Abrams wrote:
>
> Sorry, I didn't mean to mislead you, I am not using the analog on the
> chip. I am going directly in via the coax digital in. From what I
> understand the board should do "sample-perfect" transfers, but similar
> to the es1968, half my samples seem to be garbage. Playback is
> perfect, it is just recording that is broke (arecord or my own code).
well, if the arecord is broken, it must be fixed ;)
i just wanted to differentiate the problems.
>
> Your right, it may not be related, but where do I begin to figure out
> what is wrong? Does anyone reading this have a board like mine?
or, can this be a mixer configuration problem?
how did you route the digital input?
for example, if you turn on "IEC958 Mix Analog", then the signals will
be contaminated by others.
please try to turn on/off some switches regarding spdif.
the descriptions are found in alsa-kernel/Documentation/CMIPCI.txt.
ciao,
Takashi
-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
next prev parent reply other threads:[~2002-06-21 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 9:41 Application using ALSA-driver es-1968 for Maestro-2e: Bug or my fault? User for realtime audio
2002-06-17 10:33 ` Paul Davis
2002-06-17 21:00 ` Howard Abrams
2002-06-21 13:47 ` Takashi Iwai
2002-06-21 17:32 ` Howard Abrams
2002-06-21 17:39 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-17 13:08 User for realtime audio
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=s5h1yb0a5us.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=abramsh@acm.org \
--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.