Re: [Alsa-user] Unable to find an audio port (1) for channel 1

2006-01-02 Thread Jaroslav Kysela
On Fri, 30 Dec 2005, Adam Nielsen wrote: ALSA lib pcm_ladspa.c:1283:(snd_pcm_ladspa_parse_ioconfig) Unable to find an audio port (1) for channel 1 aplay: main:547: audio open error: Invalid argument So what does this mean? It looks like solving this problem will fix the mono-only LADSPA

Re: [Alsa-user] Unable to find an audio port (1) for channel 1

2006-01-02 Thread Adam Nielsen
ALSA lib pcm_ladspa.c:1283:(snd_pcm_ladspa_parse_ioconfig) Unable to find an audio port (1) for channel 1 It means that the used LADSPA plugin has no second audio port. When you say no second audio port is that different to processing a stereo signal? Because it was my understanding that

Re: [Alsa-user] Unable to find an audio port (1) for channel 1

2006-01-02 Thread Jaroslav Kysela
On Mon, 2 Jan 2006, Adam Nielsen wrote: ALSA lib pcm_ladspa.c:1283:(snd_pcm_ladspa_parse_ioconfig) Unable to find an audio port (1) for channel 1 It means that the used LADSPA plugin has no second audio port. When you say no second audio port is that different to processing a stereo

Re: [Alsa-user] Unable to find an audio port (1) for channel 1

2006-01-02 Thread Jaroslav Kysela
On Mon, 2 Jan 2006, Jaroslav Kysela wrote: Running speaker-test -c2 -Dplug:test only plays the front right audio out of both front speakers. Confirmed. It seems that the problem has nothing with the ALSA LADSPA plugin code but with the latest mmap code optimizations. I'm still figuring

Re: [Alsa-user] Unable to find an audio port (1) for channel 1

2006-01-02 Thread Adam Nielsen
The attached patch fixes this bug. Brilliant! The LADSPA EQ is now in stereo again! Thanks for tracking this down and fixing it! Cheers, Adam. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems?

[Alsa-user] Unable to find an audio port (1) for channel 1

2005-12-29 Thread Adam Nielsen
Aha, well now I think I might be tracking down why stereo output via LADSPA isn't working. If I change policy duplicate in the LADSPA PCM definition to policy none then suddenly ALSA starts paying attention to all the 'bindings' definitions, and if I do this: ... input { bindings { 0 0