As I mentioned back in December, I can get the alsa driver to
work on my Tecra 8100 by reloading the alsa driver until it
works. This takes somewhere between 0 and 20 reloads. Mihai
has confirmed this behavior on his machine and also noted that
the sound functional/nonfunctional state persists th
Greetings --
The alsa ymfpci drivers haven't worked on toshiba tecra 8100's
since 0.5. But the OSS drivers derived from the 0.5 alsa drivers
work fine. This is a non-deterministic problem in 1.0.0.rc2.
I've found that I can switch the ymfpci on or off by
repeatedly starting/aplaying/stopping
hi --
The appended has been moderating for a few weeks.
The funny thing is the other night I had 2.6.0-test11 playing sounds as
clear as could be for a while. But it has since, after miscellaneous
reonfigs and reboots, reverted to making scratchy noises only.
Getting toshiba specific acpi ext
Patrick Shirkey writes:
> --- Paul Davis <[EMAIL PROTECTED]> wrote:
> >Not at all. arecord(1) can capture audio, but it can't capture 26
> >channels of audio at 64 frames/interrupt. Handling latency is partly
> >an application issue, partly a kernel issue, and partly a requirement
> >that lib
Peter Enderborg writes:
>
> Roger E Critchlow Jr wrote:
[ ... ]
> > Does this help?
> >
>
> Well. I guess it do. I will give it a try. It should work. What about non midi
> snd_seq_event_t.
> The internal alsa stuff, like subscribe?
>
Hmm, hadn
Peter Enderborg writes:
> Jaroslav Kysela wrote:
>
> > On Fri, 1 Mar 2002, Peter Enderborg wrote:
> >
> > > Paul Davis wrote:
> > >
> > > > >Yes! And the device that is using running status is alsa rawmidi device.
> > > >
> > > > What makes you think that? AFAIK, the raw MIDI device code
Roger E Critchlow Jr writes:
>
> The mixer reports itself as "Asahi Kasei (5)", is this an abbreviation
> for the ak4545?
>
No, it's an Asahi Kasei codec with id=0x414b4d05 which must have come
between the AK4543 (id=0x414b4d02) and the AK4544A (id=0x414b4d06).
e ak4545?
Still hoping to get some help with this,
-- rec --
Roger E Critchlow Jr writes:
> Hi --
>
> The ymfpci driver in the current alsa-cvs release isn't working on
> my laptop and hasn't been working since at least December. The OSS
> driver in kernel 2.4.9
Hi --
The ymfpci driver in the current alsa-cvs release isn't working on
my laptop and hasn't been working since at least December. The OSS
driver in kernel 2.4.9 does work and the driver in alsa-driver-0.5.12a
does work. I'm currently running kernel 2.4.17 with patches on top of
Redhat 7.2.
[EMAIL PROTECTED] writes:
>
> Now I'm writing an pure C extension for ALSA-0.9 . I encountered
> the following strange problem:
>
> When I try to initialize the pcm device, I get the following
> error message:
>
For what it's worth, if I write a dynamically loaded Tcl extension
that imp
Just a typo I happened across.
-- rec --
--- alsa-lib/include/seq_event.h~ Wed Jan 9 18:57:15 2002
+++ alsa-lib/include/seq_event.hSun Feb 3 00:09:05 2002
@@ -354,7 +354,7 @@
typedef enum snd_seq_stop_mode {
SND_SEQ_SAMPLE_STOP_IMMEDIATELY = 0,/**< terminate playing
Gerald Grabner writes:
> Hi,
>
> is there any place where I could find easy examples of how to use the
> alsa 0.5 API? Something like just listening to a midi port and
> printing the incoming events on the standard output...
>
> Would be great to get started!
>
> Thx a lot in advance,
Paul Davis writes:
> >Hello all,
> >
> >it seems that I've finished an initial version of documentation
> >for alsa-lib's configuration files and PCM interface. Here is URL:
>
> looks like a decent start. i hope i can find time to improve some
> parts of this. in reading the section on
I found the following archives of the current alsa-user, alsa-devel,
and alsa-cvslog that have a functioning search:
http://www.mail-archive.com/alsa-user%40lists.sourceforge.net/
http://www.mail-archive.com/alsa-devel%40lists.sourceforge.net/
http://www.mail-archive.com/alsa-cvslog%4
14 matches
Mail list logo
