From: Peter Heatwole <peter599@gotnet.net>
To: alsa-devel@lists.sourceforge.net
Subject: Re: SPDIF output finally working properly with CS4630
Date: Tue, 23 Jul 2002 23:29:27 -0700 [thread overview]
Message-ID: <20020724062927.GC6131@porky> (raw)
In-Reply-To: <3D3E2D08.3070800@cucumelo.org>; from gorm@cucumelo.org on Tue, Jul 23, 2002 at 21:28:56 -0700
On 2002.07.23 21:28 Benny Sjostrand wrote:
> Now I've generated a patch against alsa-driver-0.9.0rc2, so you can try
> to merge it with your CVS snapshot,
> maybe it works better ....
Thanks. It took a tad of modifying to patch the CVS because it was
expecting a 0.9.0rc2 postfix on everything, but that was simple to fix.
I patched the CVS, and am getting the same error. I stuck the following
into alsa-lib/src/pcm/interval_inline.h, and am getting some feedback on
what's going wrong:
printf("snd_interval_min()::: i->empty == %d\n", i->empty)
<<<which results in>>>
[peter@porky als]$ aplay footsteps.wav Playing WAVE 'footsteps.wav' :
Signed 16 bit Little Endian, Rate 44100 Hz, Mono
snd_interval_min()::: i->empty == 0
snd_interval_min()::: i->empty == 0
snd_interval_min()::: i->empty == 0
snd_interval_min()::: i->emtpy == 0
snd_interval_min()::: i->empty == 1
aplay: interval_inline.h:66: snd_interval_min: Assertion
`!snd_interval_empty(i)' failed.
Aborted...
Also, I tried the driver with the xmms-alsa plugin, and it
failed the same test, but in the function snd_interval_refine_min().
I haven't developed with ALSA yet, so I don't know the ropes
completely. Anyone have any idea what's happening here? I checked
the online docs and couldn't find any references regarding
"interval"s. Is this a timing issue?
-- Peter Heatwole
"Murphy was just a well known pessimist."
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-24 6:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 20:33 SPDIF output finally working properly with CS4630 Benny Sjostrand
2002-07-24 1:34 ` Peter Heatwole
2002-07-24 4:28 ` Benny Sjostrand
2002-07-24 6:29 ` Peter Heatwole [this message]
2002-07-24 18:19 ` Peter Heatwole
2002-07-24 18:41 ` Benny Sjostrand
2002-07-24 20:12 ` Peter Heatwole
2002-07-24 19:59 ` Benny Sjostrand
2002-07-24 21:23 ` Peter Heatwole
2002-07-24 21:53 ` Benny Sjostrand
2002-07-24 23:37 ` Peter Heatwole
2002-07-24 23:53 ` Peter Heatwole
2002-07-25 22:23 ` Peter Heatwole
2002-07-26 6:40 ` Benny Sjostrand
2002-07-24 9:52 ` 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=20020724062927.GC6131@porky \
--to=peter599@gotnet.net \
--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