-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The sb 512 supposedly has support for
adding effects like chorus and reverb
to the sound. How do I enable these
effects on the sb?
One of the programs in alsa-tools is
an assembler for creating effects for
the sb 512 and live models, it gives
instruc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Does alsa support more then 4 sound cards,
or can I created device file for a 5th
sound cards. I'm sure this isn't a big
issue as it is probably very rare for anyone
to actually use five sound cards, but I've
managed to.
My setup is as follows:
1: on
Hello all,
I'm trying to get my Midisport USB midi interface working on my Debian
system. I used to have it running fine when I had RedHat on this
laptop, but since switching over to Debian have been unable to get the
firmware to load to the device properly.
/var/log/messages gives me then when I
Hi list,
I'm currently running a Debian system on with a M-Audio Quattro
midi/audio interface. Everything is working great except I get no midi
input from the device. Midi out works great, audio in/out works great.
Just... no midi in. I generally test using PD to see if I see any
midi input an
Attached the output as requested
My log looks a little different to cliff's, maybe because mine is a
UK version (delivered this week),
thanks
##
> Richard Farthing wrote:
> > Does anyone know how to make the new Soundblaster USB MP3+ (with the
> > nice Blue LED) work fully ? It is recognised
Hello,
I successfully installed the ALSA drivers 0.9.4 on an Intel Centrino
notebook (the ASUS M3410C, Linux report at
http://luca.pca.it/projects/asus/M3410C.htm). The installation completes
ok only if I enable the ACPI at boot, if not there're problems with the
IRQ addresses.
Anyway, now my
I recently switched from alsa & 2.4.x to alsa & 2.5.x. Everything seems to be going
well, and audio does actually work. However, it seems to be consuming alot of CPU just
to play audio, and stutters easilly if there's any other significant CPU usage going
on.
I'm running 2.5.71 (with preempt en
I'm no ALSA or Linux expert, but I have learned a couple of things I
haven't seen elsewhere that might help people looking at this list.
I have two sound "cards" on my machine. A Soundblaster Live Value
(Gateway OEM version), and a Plantronics DSP-500 USB headphone. Here's
my /etc/modules.conf
well, that makes 3 of us then. What error message do you get? mine says
something about synthesizer 8000 not presant, then it says isa PnP failed,
device lot found at 0x62 or something like that. I can't get alsa to work
on anything.
On Sun, 29 Jun 2003 [EMAIL PROTECTED] wrote:
> I am havi
> Richard Farthing wrote:
> > Does anyone know how to make the new Soundblaster USB MP3+ (with the
> > nice Blue LED) work fully ?
> > It is recognised as a USB sound card OK - running SuSe Linux 8.1 -
> > But the mixer doesn't work.
>
> Please post the output of "lsusb -v".
>
>
> Regards,
> Cle
hello,
i want to record something from the line in of my motherboard (VIA)
i use the alsa via82xx and all is allright for playback (xmms,
mplayer...)
i thing that my line channel is selected for record :
amixer says :
Simple mixer control 'Line',0
Capabilities: pvolume pswitch ps
Since I bought my new mainboard (ASUS A7V8X), I had a nasty little problem
with the DSP.
The ALSA driver works perfectly, I can use all features of the VIA8235
(although the mixer devices are a bit complicated to use), almost all sound
plays fine and I love this nice multichannel-playback (sever
I am having the same problem so if you find an answer please let me know
Thanks
On Sat, 28 Jun 2003, Artem Vakhitov wrote:
> Hello,
>
> I tried to build and install ALSA 0.9.4. Everything went OK until
> I tried to insert sbawe module into kernel. Modprobe
> said:
>
> /lib/modules/2.4.19/misc/s
When I try to load the module in Linux 2.5.73 (and earlier versions), I
get the following single line in the kernel log:
AC'97 0:0 does not respond - RESET
The audigy2 driver in Red Hat Linux 9 (which I think is the driver from
http://sourceforge.net/projects/emu10k1 renamed to audigy2) works
Hi,
I'm confused on MIDI deviecs. :) Rather than bore you with the details of
what I think is right, (since it is most likely wrong), can someone explain
what each of the following do?:
/dev/snd/midiC0D0
/dev/snd/midiC1D0
/dev/snd/seq
/dev/sound/dmmidi
/dev/sound/midi00
/dev/sound/sequencer
/de
15 matches
Mail list logo