On Wed, 4 Dec 2002, Erik Steffl wrote:
> > On the SB Live, yes. On the Audigy, no!
>
>is there any way to make the front panel midi work?
I've had an SB Live then upgraded to the Audigy (about 4 months ago). I
don't remember getting the front panel midi to work back with I had the
sblive, b
On Tue, 3 Dec 2002, Adam Jones wrote:
> > ALSA lib pcm_hw.c:866:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed:
> > Device or resource busy
> > aplay: main:462: audio open error: Device or resource busy
> >
> > Surely the -N switch shouldn't be blocking like that?
>
> Well, I guess that isn't /bl
On Fri, 29 Nov 2002, Takashi Iwai wrote:
> > > don't you have /dev/snd/midiC0D1 ?
> > > if not, it must be a devfs config problem...
> > >
> > > btw, the second midi device is mapped usually onto OSS device
> > > /dev/amidi00.
Ah.. ok, so out of the four devices in that directory, which ones ar
On Sun, 1 Dec 2002, Erik Steffl wrote:
>so if there is only one midi register on sb live then how is it
> supposed to work? are the two connectors basically just one midi port (I
On the SB Live, yes. On the Audigy, no!
Also, on the SB Live, you can't record from sp/dif and aux2 at the same
Hiya,
I've got an sbawe 64, and I'm trying to get multple streams working. It
only shows one subdevice available, but I thought alsa could mix into that
stuff.
I've done this:
$ aplay -N foo.wav & aplay -N bar.wav
The first wav plays, but second reports this:
ALSA lib pcm_hw.c:866:(snd_pcm_hw
to be a device matching up to it in /dev/sound
(I'm using devfs).
What's going on?
--
Giles Constant, Systems Programmer
Hyperlink Interactive
http://www.hyperlink-interactive.co.uk
---
This sf.net email is sponsored by:ThinkGe
Hi there,
I'm confused.. I'm trying to reduce latency on linux (possibly to the same
standards as ASIO), and I'm aware that there's about 100 things out there
to do with latency, but I'm not sure which ones I need, or even if such a
driver-level API exists..
Last time I installed alsa, there was
