Hi all!
I was just wondering if there is any chance of implementing more than
one codec on the CS4205 (intel8x0 module) soundcard found in laptops, so
that the soundcard can at least do 2 streams at the same time? (my
understanding is that this soundcard supports at least 2 if not more
simultaneo
I had shot some emails around with the esound maintainers regarding using
plughw:# instead of hw:# as the default device and it was decided to leave
it at hw:#. I'd prefer it to be plughw as well.
In the meantime, if you need plughw:# to make you card work, just
put it in the spawn options
Hi, I'm farly new to ALSA I would like to have a simple but advanced GUI
mix/configuration program. This program should be for (l)users like me
that only wonts play around a bit with his/hers sound system but don't
wont to the extreme things that you can do with ALSA.
My problem is that I have a
I still really think my nForce chip does support hardware mixing...
I see in alsamixer, three things at the end that I wonder may be a sign
the chip supports hardware mixing?
I have Mix, Mix Mono, and External. Those are the names of the things.
The 'Item' field lists External as being 'Exter
Ok, here are the new results. I've decided to include most of the
output as attached files. Figured it would be easier this way for most
people.
The tests were done with the cvs tree from around 14:30EST with your
test define included in the usbmixer code. Included are:
lsusb-out.txt: lsusb -vv
Hi all!
These are the errors I came up against compiling either CVS or the latest
official rc3 version. I do not know the guts of the alsa to be able to fix it
myself, so I would greatly appreciate any help I can get on this matter:
creating cache ./config.cache
checking host system type... i6
Takashi Iwai <[EMAIL PROTECTED]> writes:
> I would like to confirm the consensus about $SUBJECT.
> Does anybody still have objections against this action?
I have withdrawn my objections.
Compatibility with de facto kernel standards is a good reason to make
this change.
--
Jack O'Quin
Aus
On Mon, 14 Oct 2002, Richard Bown wrote:
> A question - if you're sending a load of MIDI notes (as opposed to
> noteons/noteoffs) with very long duration and to curtail these notes
> you're sending notes with shorter (finite if you like) duration to same
> channel/pitch should the longer ones
On Mon, 14 Oct 2002, Clemens Ladisch wrote:
> Jaroslav Kysela wrote:
> > On Mon, 14 Oct 2002, Clemens Ladisch wrote:
> >
> > > If the sequencer device for a card is requested unsuccessfully (e.g.
> > > "pmidi -l" when a USB MIDI device isn't yet connected), the device is
> > > plugged in, and the
A question - if you're sending a load of MIDI notes (as opposed to
noteons/noteoffs) with very long duration and to curtail these notes
you're sending notes with shorter (finite if you like) duration to same
channel/pitch should the longer ones clear down from ALSA and get cast
away?
At the m
Has anyone run a diagnosis tool like "memprof" on an application that
uses alsa for audio out ?
I recently did this, and have found that alsa is a little leaky. It is
mainly the mixer part of alsa.
Here is an example backtrace for the call to the malloc that is never
freed even if the applicati
At Sat, 12 Oct 2002 17:18:49 +0200,
Jan Bernatík wrote:
>
> Dne pá 11. říjen 2002 16:41 Takashi Iwai napsal(a):
> > At Fri, 11 Oct 2002 16:24:36 +0200,
> >
> > Jan Bernatík wrote:
> > > Hallo everyone
> > >
> > > I have alsa drivers 0.9rc3 working with my via8233 (ALC650) onboard
> > > soundcard.
At Fri, 11 Oct 2002 13:39:01 -0500,
[EMAIL PROTECTED] wrote:
> > the attached patch will ignore the errors from the usb controller
> > after a mixer control is inquired. the error above shall be avoided
> > by this patch. please check the kernel messages. so we can know
> > which control is wr
Jaroslav Kysela wrote:
> On Mon, 14 Oct 2002, Clemens Ladisch wrote:
>
> > If the sequencer device for a card is requested unsuccessfully (e.g.
> > "pmidi -l" when a USB MIDI device isn't yet connected), the device is
> > plugged in, and then the device is accessed, ALSA doesn't load the
> > seque
Hi,
I would like to confirm the consensus about $SUBJECT.
Does anybody still have objections against this action?
The problem of compatibility remains, of course.
The moderate solution is to provide a converter script such like:
sed -e 's/^[[:space:]]*options[[:space:]]\+snd/s/snd_//g'
On Mon, 14 Oct 2002, Clemens Ladisch wrote:
> If the sequencer device for a card is requested unsuccessfully (e.g.
> "pmidi -l" when a USB MIDI device isn't yet connected), the device is
> plugged in, and then the device is accessed, ALSA doesn't load the
> sequencer driver.
>
> The reason for t
At Mon, 14 Oct 2002 11:44:18 +0200 (METDST),
Clemens Ladisch wrote:
>
> snd-usb-audio isn't loaded when hotplugging devices with multiple
> interfaces because the hotplug system doesn't pass the interface class.
>
> This patch removes the interface class specification (except from those
> device
If the sequencer device for a card is requested unsuccessfully (e.g.
"pmidi -l" when a USB MIDI device isn't yet connected), the device is
plugged in, and then the device is accessed, ALSA doesn't load the
sequencer driver.
The reason for this is that snd_seq_client_use_ptr() assumes that the
seq
snd-usb-audio isn't loaded when hotplugging devices with multiple
interfaces because the hotplug system doesn't pass the interface class.
This patch removes the interface class specification (except from those
devices where it matters).
--
Clemens
Index: usb/usbquirks.h
=
19 matches
Mail list logo