My VXPocket V2 records perfectly each time at -f S24_3LE
-c2 -r 48000 for the first 30 seconds. After 30 seconds have
passed, however, it records only a loud, hissing noise with
no evidence of the original sound source.
The length of time until noise (30 seconds) seems very
accurate and repeatabl
I recently upgraded from ALSA 0.9.5 to 0.9.8.
It appears that "amixer -D hw:1" no longer works:
[EMAIL PROTECTED] etc]$ amixer -D hw:1
amixer: Mixer attach hw:1ult error: No such device
I notice that it is sticking in the last three
characters from the word "default". This
also occurs for other
Capturing audio on VT8235/AD1980 with 0.9.8 seem to have a lots of problems.
I hope to be clear in reporting it. Feel free to ask me more detail.
In short, if I turn capture on CD, Aux capture is turned off, but I can
still capture a mono audio from Aux port. The same if I turn capture on Aux,
I ca
My original message:
> I use a stock 2.4.22 kernel and an emu10k1 soundcard.
>
> Alsa-drivers, -libs, and -utils all compile successfully. However,
> after loading modules with "modprobe snd-emu10k1" the following error
> message occurs when I run alsamixer:
>
> alsamixer: function snd_mixer_load
At Fri, 31 Oct 2003 02:22:42 -0600,
Dan Cyr wrote:
>
> I have no "captureable" device in my alsamixer display, does anyone have a
> clue why? (i did a google on revolution + alsa + capture and wasnt
> successful).
in fact there is no capture volume. it seems always high.
Takashi
At Fri, 31 Oct 2003 14:39:27 +0200,
Andrei Boros wrote:
>
>
> Takashi Iwai wrote:
>
> > > > > gate:~# modprobe snd-opti92x-ad1848
> > > > > /lib/modules/2.2.24/misc/snd-opti92x-ad1848.o: init_module: Device or
> > > > > resource busy
> > > > > snd: Device or resource busy
>
> > could you check
At Thu, 30 Oct 2003 14:59:17 -0600,
William Hubbs wrote:
>
> Hi Takashi,
>
> On Thu, Oct 30, 2003 at 05:56:22PM +0100, Takashi Iwai wrote:
> > At Thu, 30 Oct 2003 07:45:53 -0600,
> > William Hubbs wrote:
> > >
> > > Hi all,
> > >
> > > I am running linux 2.6.0-beta9 and the alsa drivers include
Frans Ketelaars wrote:
AFAIK CONFIG_SOUND=y means that soundcore is compiled into the kernel
and everything should be ok.
That's what I suspected.
So I have it in my kernel but still it doesn't help.
Anything else I can try?
Thanks,
--Amos
-
Takashi Iwai wrote:
> > > > gate:~# modprobe snd-opti92x-ad1848
> > > > /lib/modules/2.2.24/misc/snd-opti92x-ad1848.o: init_module: Device or
> > > > resource busy
> > > > snd: Device or resource busy
> could you check at which point the error happens, e.g. by putting
> printk()'s ?
Ok, here it
On Wednesday 29 October 2003 18:35, [EMAIL PROTECTED] wrote:
> Frans Ketelaars wrote:
> > Ok, then here are the instructions to set up ALSA:
> > http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=N
> >vidia&card=nForce&chip=NM2360&module=intel8x0
>
> Hi,
>
> I followed this page but
Hi all,
I would be grateful for any hint why the isapnp_reserve_irq option is
not working.
--
Milos Prudek
_
Most websites are
confused chintzy gaudy conflicting tacky unpleasant... unusable.
Learn how usable YOUR website is! http://www.spoxdesign.com
--
I have RH9.0 (2.4.20-20.9) running on my athlon with a Sound Blaster Live Value.
Redhat detected the card and uses the emu10k1 driver which works fine, but
unfortunately it doesn't support 4.1 sound,
bass, treble, etc...
I downloaded and installed alsa-driver-0.9.7-1.fr.i386.rpm and
kernel-modu
I have no "captureable" device in my alsamixer display, does anyone have a
clue why? (i did a google on revolution + alsa + capture and wasnt
successful).
thanks
Dan
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceFo
13 matches
Mail list logo
