Martin Langer wrote:
So, if my client is aconnected (aconnect 80:0 73:0) I can't catch an error
with rawmidi trying all four possibilties.
When the sequencer has opened the port, others cannot access it, so that's
OK.
BTW: Does input through the sequencer work?
If I disconnect (aconnect -x)
Fernando Pablo Lopez-Lezcano wrote:
OSS: rawmidi -v -I /dev/midix
./rawmidi -v -I /dev/midi1 -- works fine
ALSA direct: rawmidi -v -I /dev/snd/midiCxD0
./rawmidi -v -I /dev/snd/midiC1D0 -- works fine
These two tests access the driver directly, without going through the ALSA
Patrick Shirkey wrote:
I'm getting a lot of wierd sound quality bugs while using JACK. It seems
like the driver is storing the crappyness somewhere and each time I
access it the quality gets worse. Is it possible that the driver could
allow the data to linger and make things unstable?
I have
Patrick Shirkey wrote:
I guess that ssm (and possibly JACK) has some mem leaks.
It seems I spoke too soon. I'm seeing memory leaks while using
alsaplayer or xmms. Alsaplayer connected via the alsa driver and xmms
through oss.
I'm going through about 1 MB/min :(
Is this an alsa issue or
On Fri, Nov 08, 2002 at 09:17:45AM +0100, Clemens Ladisch wrote:
Martin Langer wrote:
BTW: Does input through the sequencer work?
yes it's working with the same keyboard using classical MIDI OUT jack, not
USB. I have done this:
tuba:~# aconnect 64:0 73:0/* using classical midi jack works
The cvs-alsa tree compiled ok, but the module will not load. This could be an
operator error, as the compiling machine isn't the test machine (portable).
So I could have forgotten to copy some files.
#boot.msg:
notice/etc/init.d/rc5.d/S12alsasound start
Starting sound driver: opl3sa2
Hi, I'm trying to configure asound.conf to support two cards as one
(but with 3, 8 channel cards!) as suggested in the .asoundrc doc. When I
try to aplay the new device however I get:
ALSA lib pcm_multi.c:928:(_snd_pcm_multi_open) Invalid or missing
schannel for channel 0
aplay: main:462:
Damien Sandras wrote:
I subscribed to this mailing list, because GnomeMeeting users have
reported a problem using ALSA 0.9.0RC5 together with GnomeMeeting and
RedHat 8.0.
Actually, the problem is simple to explain, hard to fix, at least for
me. Several users complained that using GnomeMeeting
On Fri, 2002-11-08 at 14:35, Paul Davis wrote:
Hi, I'm trying to configure asound.conf to support two cards as one
(but with 3, 8 channel cards!) as suggested in the .asoundrc doc. When I
try to aplay the new device however I get:
ALSA lib pcm_multi.c:928:(_snd_pcm_multi_open) Invalid or
Greetings!
I'm new to developing with ALSA. I'd like to ask two questions:
1. Is there a good guide to porting applications written for 0.5.x to
0.9.0? I'm trying to fix mpg123 to work with ALSA 0.9.0 natively;
current stable version (0.59r) barfs when compiling all over
audio_alsa.c.
2. I'd
1. Is there a good guide to porting applications written for 0.5.x to
there are no good guide to anything related to ALSA at this time.
0.9.0? I'm trying to fix mpg123 to work with ALSA 0.9.0 natively;
current stable version (0.59r) barfs when compiling all over
audio_alsa.c.
the API in 0.9.0
Will the alsa driver in 2.5.xx for the cs46xx with the new dsp code enabled
ever gain bass/treble control in the OSS mixer? Thanks.
Jordan
---
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power Color in a
So should the drive be able to set period size with this patch?
Reason I ask is this.
spongypete:~$ alsaplayer
error on set_period_size (1024)
Unavailable hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (181
13 matches
Mail list logo
