On Fri, 16 Aug 2002, Patrick Shirkey wrote:
> Takashi Iwai wrote:
> > At Fri, 16 Aug 2002 00:46:02 +0900,
> > Patrick Shirkey wrote:
> >
> >>Takashi Iwai wrote:
> >>
> >>>Hi,
> >>>
> >>>how about to gather the bugs of the current driver and list them as
> >>>known bugs on the web?
> >>>it would
Jaroslav Kysela wrote:
>>>hmm, i got:
>>>
>>> Fatal error: Failed opening required '../../components/head.php3' in
>/home/alsa/www/alsa-doc/index.php3 on line 2
>>>
>>
>>Works here using mozilla, netcape, lynx.
>
>
> Because I've fixed this problem ;-)
>
Ahh shit. I was looking at the wr
At Thu, 15 Aug 2002 17:44:30 -0500,
Matt Walker wrote:
>
> I had successfully compiled rc2 when it came out, so I don't see any wildly
> off-base config problems. I have SuSE 7.3 on AMD K6, with a Creative SB
> Vibra-16x and Midisport 2x2 --
>
> ./configure --with-cards=sb16,usb-midi --with-s
Hi,
looks like a wrong file came into rc3 tarball accidentally.
for compiling rc3 alsa-driver, please remove the file
alsa-driver-0.9.0rc3/include/linux/isapnp.h
before running configure script.
this is fixed on cvs - equivalently you can apply the attached patch.
Takashi
rc3-conf
hallo,
the attached patch exports two functions of usb-midi,
so other "device-owning" drivers can use usb-midi's
capabilities.
the patched usb-midi driver is used by the us428
driver through those exported functions.
we can avoid having different alsa-devices for the
same physical device this wa
>> What is the purpose of the ctl.rme9652 declaration? My plugin devices
>> seem to work without it.
>>
>
>It is a configuration for the onboard mixer. Very little is known about
>why we use it. Some programs (JACK) won't work without it.
not really.
the control device for a card is the way th
Paul Davis wrote:
>>>What is the purpose of the ctl.rme9652 declaration? My plugin devices
>>>seem to work without it.
>>>
>>
>>It is a configuration for the onboard mixer. Very little is known about
>>why we use it. Some programs (JACK) won't work without it.
>
>
> not really.
>
> the control
Hi,
There are 3 standard PCM ioctls, and a driver could potentially support others
via its own ioctl function registered in the snd_pcm_ops_t structure. Could
anyone give me a hint regarding how an application could then call such
standard and other ioctls?
Thanks,
Guilhem.
___
Hi,
It is my understanding that the SNDRV_PCM_FORMAT_IMA_ADPCM format supported by
ALSA is the 32kbps variant of G.726 standard in telephony (vs. propriatory
variants like MS-ADPCM).
I would like to add support for at least the 16kbps variant of G.726 (24kbps
and 40kbps are other possibilities),
