There are other applications/tools you can use, one of which is JACK
that allows for multiple audio streams mixed in software and lots of
other cool stuff.
Cool, I'll see if I can find some information about that. I hadn't
heard of it before... is it GPL'd?
Rob
At Mon, 07 Oct 2002 19:46:44 +0200,
Abramo Bagnara wrote:
but the current behavior is incorrect from the interpretation of
POSIX. so this must be a bug.
if we have to change it, then i would choose the new one, because
it's more intuitive without exception.
As pointed by
At Mon, 7 Oct 2002 21:47:08 +0100 (BST),
Chris Rankin wrote:
Now that the ARRAY_SIZE macro has been migrated to adriver.h, it can come out of
here. And there's a whitespace diff too.
applied. thanks.
Takashi
---
This sf.net email is
At Sun, 06 Oct 2002 23:25:13 -0500,
Philip Thiem wrote:
I've been running up again the FM synethesis wall with my aopen card and
conflicting information, and finally decided to post to the dev group.
From some skimming of technical documentation for ymf754. It looks like
the ymf7xx
Hi,
Sagi Bashari hat gesagt: // Sagi Bashari wrote:
James Courtier-Dutton wrote:
There are other applications/tools you can use, one of which is JACK
that allows for multiple audio streams mixed in software and lots of
other cool stuff.
I used ARTS until now. But I don't want to use
At Sun, 6 Oct 2002 00:56:08 +0100,
Peter L Jones wrote:
Hi there,
Is this a known problem?
kernel: bad: scheduling while atomic!
kernel: Call Trace:
kernel: [schedule+61/724] schedule+0x3d/0x2d4
kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20
kernel:
At Fri, 4 Oct 2002 13:20:32 -0400 (EDT),
Pavel Roskin wrote:
Hello!
There is another configuration problem that needs to be fixed. I had ALSA
already installed (CVS version as of a week ago or so). Today I compiled
alsa-driver, alsa-lib and alsa-util and then started installing them.
At Fri, 04 Oct 2002 11:04:23 -0700,
Florian Bomers wrote:
Jaroslav Kysela wrote:
On Thu, 3 Oct 2002, Florian Bomers wrote:
Hi,
there is snd_pcm_sw_params_current() but not snd_pcm_hw_params_current(). How
can I get the current hardware configuration for a given snd_pcm_t
Dear everyone
I have a question on using this api call.
In the last argument, we need to pass in the frame. But the problem
is that I dont understand the term frame. Could anyone explain to me a
little bit what it is? And also, what is meant by a period?
I have read
Hi,
so far, all alsa modules use snd_ prefix for each module option.
iirc, there was a problem regarding namespace at the time of 2.0
kernel, and this was some workaround to avoid confliction.
but 2.2 and later kernels have no such a problem at all.
so, i'd like to ask you how do you think to
I just wanted to inform that I have changed the cards with SoundBlaster
4.1 Digital (driver snd-ens1371) and they are working together like a
charm!
It has also been a nice opportunity to test the new Mandrake Linux 9.0
which comes bundled with the latest alsa drivers.
Thanks,
Franc
Hi,
the last update of Config.in in alsa-kernel/pci will require the
update of Makefile.conf on alsa-driver.
if you update the alsa-kernel from cvs, please re-run configure script
on alsa-driver before building it.
thanks,
Takashi
---
Hello
Can someone please explain to me the use of snd_pcm_status_get_delay()
If a buffer size is 16384, and avail=6384, should delay therefore equil
1 ? In all cases ?
I have found that in SND_PCM_STATE_RUNNING, delay = buffer_size - avail.
I have found that in SND_PCM_STATE_PREPARED,
At Wed, 09 Oct 2002 02:25:40 +1000,
James Courtier-Dutton wrote:
Hello
Can someone please explain to me the use of snd_pcm_status_get_delay()
If a buffer size is 16384, and avail=6384, should delay therefore equil
1 ? In all cases ?
no, the current implementation is the
On Tuesday 08 Oct 2002 15:04, Takashi Iwai wrote:
[snip]
so, i'd like to ask you how do you think to remove this snd_ prefix.
of course, there is one and only big problem - compatibility!
the questions are
- whether we should really do it or not? is it worthy?
Yes - I find it confusing:
Clemens Ladisch wrote:
Abramo Bagnara wrote:
No data may be read/written in current stream state in the case we are
discussing.
(...)
The point is that stream is in bad state wrt read/write, this is the
reason why poll should return POLLERR.
I think the stream is _not_ in a
the thing that looks like bad API design is that snd_pcm_sw_params_current()
exists and snd_pcm_hw_params_current() does not. I think it wouldn't even hurt
if snd_pcm_hw_params_t would be cached in the lib for that. Maybe in a later
ALSA revision, ALSA kernel support for that could be
I like it a lot. Due to the prefix I was able to cleanly remove 0.5.x from my
system, and we might want to do that later on with 0.9, too :)
And since I don't see any benefit in removing the prefix - other than cosmetic -
keeping it will save time for distribution's programmers, sysadmins,
Takashi,
I was going to send this message:
Thank you very much for your response, I appreciate the help.
I turned AUX up, but that doesn't seem to have helped.
I've also taken the opportunity to update my system info textfile.
Overview of changes:
* latest CVS stuff
*
which device are you using?
The Apple Speakers that come with the cube. (They're just 2 usb
speakers. No subwoofers or anything like that).
please try the cvs version if you use a usb driver.
the usb driver has been changed largely since rc3.
I upgraded my drivers to the latest usb
Hello all,
I have just released v0.4.0 of the seq24 midi sequencer.
This release adds A performance editor
http://www.filter24.org/seq24/
New screen shots are up too..
cheers,
.rob
--
music + technology
On Mon, 30 Sep 2002, tomasz motylewski wrote:
On Mon, 30 Sep 2002, Jaroslav Kysela wrote:
me directly that - the current position in the buffer?) I can calculate when
the required position _will_ happen. So I can just schedule the timer or sleep
until that time. When it arrives I
On Tue, 8 Oct 2002, [iso-8859-1] Chris Rankin wrote:
--- Takashi Iwai [EMAIL PROTECTED] wrote: Hi,
so, i'd like to ask you how do you think to remove
this snd_ prefix.
of course, there is one and only big problem -
compatibility!
I think it's a worthy goal. It's just noise in
23 matches
Mail list logo
