From: stan <stanl@cox.net>
To: alsa-devel@alsa-project.org
Subject: Re: SOLVED Re: snd_pcm_hw_params_set_format fails with invalid argument
Date: Tue, 7 Aug 2007 08:26:21 -0700 [thread overview]
Message-ID: <20070807082621.5a557ca4@localhost.localdomain> (raw)
In-Reply-To: <20070807080242.0da2a0ff@localhost.localdomain>
I sent this directly to Takashi by mistake. I could have sworn I saw
the list in the to field but I must be mistaken. Here it is for the
list.
On Tue, 7 Aug 2007 08:02:42 -0700
stan <stanl@cox.net> wrote:
> On Tue, 07 Aug 2007 15:38:40 +0200
> Takashi Iwai <tiwai@suse.de> wrote:
>
> > At Mon, 6 Aug 2007 09:22:01 -0700,
> > stan wrote:
> > >
> > > On Mon, 6 Aug 2007 09:04:57 -0700
> > > stan <stanl@cox.net> wrote:
> > >
> > > > I downloaded the hg alsa-lib snapshot of July 14, 2007, compiled
> > > > it, (on Fedora 7 you will have to make a link to compile,
> > > > cd /usr/include
> > > > ln -s python2.5 python)
> > > > and linked my program against it. It works again so the issue
> > > > has been fixed in the latest version of alsa lib. Any estimate
> > > > of when this version will be released for public consumption?
> > > > My app is dead in the water with the current version of alsa, so
> > > > anyone trying to use it will have a terrible user
> > > > experience. :-( I want to give some indication of when people
> > > > can expect it to start working again. In the meantime I'll
> > > > create instructions on how to install the hg version to
> > > > usr/local and change the library linking.
> > > >
> > > > Thanks.
> > > >
> > > For anyone interested, these are the formats that fail in 1.0.14
> > > final
> > >
> > > Value of last format 43
> > > test of sample format 14 failed (Invalid argument)
> > > test of sample format 15 failed (Invalid argument)
> > > test of sample format 16 failed (Invalid argument)
> > > test of sample format 17 failed (Invalid argument)
> > > test of sample format 18 failed (Invalid argument)
> > > test of sample format 19 failed (Invalid argument)
> > > test of sample format 23 failed (Invalid argument)
> > > test of sample format 24 failed (Invalid argument)
> > > test of sample format 25 failed (Invalid argument)
> > > test of sample format 26 failed (Invalid argument)
> > > test of sample format 27 failed (Invalid argument)
> > > test of sample format 28 failed (Invalid argument)
> > > test of sample format 29 failed (Invalid argument)
> > > test of sample format 30 failed (Invalid argument)
> > > test of sample format 31 failed (Invalid argument)
> > > Format returned (0)
> > >
> > >
> > > and these are the formats that fail in the hg version.
> > >
> > > Value of last format 43
> > > test of sample format 18 failed (Invalid argument)
> > > test of sample format 19 failed (Invalid argument)
> > > test of sample format 23 failed (Invalid argument)
> > > test of sample format 24 failed (Invalid argument)
> > > test of sample format 25 failed (Invalid argument)
> > > test of sample format 26 failed (Invalid argument)
> > > test of sample format 27 failed (Invalid argument)
> > > test of sample format 28 failed (Invalid argument)
> > > test of sample format 29 failed (Invalid argument)
> > > test of sample format 30 failed (Invalid argument)
> > > test of sample format 31 failed (Invalid argument)
> > > Format returned (16)
> >
> > Could you give me the simple test case for checking the same thing
> > on my system?
> >
> >
> > thanks,
> >
> > Takashi
>
> They are attached as file test_case.c and shell script mktest.
>
> Running ./mktest should generate an executable named test_case.
> Running that should generate the above output.
>
>
next prev parent reply other threads:[~2007-08-07 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 18:20 snd_pcm_hw_params_set_format fails with invalid argument stan
2007-08-05 20:10 ` stan
2007-08-06 16:04 ` SOLVED " stan
2007-08-06 16:22 ` stan
2007-08-07 13:38 ` Takashi Iwai
[not found] ` <20070807080242.0da2a0ff@localhost.localdomain>
2007-08-07 15:26 ` stan [this message]
2007-08-07 15:32 ` stan
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=20070807082621.5a557ca4@localhost.localdomain \
--to=stanl@cox.net \
--cc=alsa-devel@alsa-project.org \
/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.