[Openal-devel] EFX Echo effect on Linux
pierre at digitalstar.net
Thu Nov 19 05:51:34 PST 2009
Thanks! Now have an echo effect :)
Regarding pulseaudio, when I enable it, I get no sound and all OpenAL
call return AL_INVALID_OPERATION it seems....sorry that's all the info I
can give for the moment.
Keep up the good work!
Chris Robinson wrote:
> On Wednesday 18 November 2009 9:29:15 am Pierre Proske wrote:
>> Currently I'm using OpenAL soft and firstly thanks for the great work.
>> I've got things up and running and managed to get the EFX reverb
>> working, but I tried the Echo and it crashed my application.
> Hi, thanks. :)
> Odd for the crash, though. Can you paste the code that's causing the problem,
> and give a backtrace?
>> I did a quick search and came across this written by Chris Robinson on
>> this list:
>>> The current alext.h doesn't contain the EFX defines and types. However,
>>> you can get Creative's OpenAL SDK which includes a header that defines
>>> To note, though, the Echo effect isn't available without hardware drivers
>>> (or through accelerated DSound3D). The standard reverb effect and lowpass
>>> filter should always be available with EFX, though, even in software.
>> What's the status of the Echo effect on openal soft? It appears to be
>> implemented, and openal-info reports this:
>> Max auxiliary sends: 2
>> Available filters:
>> Available effects:
>> EAX Reverb
> Yeah, I said that before the echo effect was implemented. It should fully work
> now in 1.8 and newer.
>> Additionally I can't seem to get the pulseaudio backend to work. It
>> seemed to work in the last version of OpenAL soft, I think I tried it
>> briefly. I'm on Ubuntu 9.10.
>> Any suggestions that I can try to fix this? Although I guess I won't be
>> using it but rather ALSA anyway.
> Weird.. OpenAL Soft 1.9 had problems with the PulseAudio backend that
> prevented it from working, while 1.10 should have fixed it (1.8 would work
> with older versions of PulseAudio, but would lockup on newer versions). What
> happens with 1.10?
>> One more thing, the openal-info reports the following with the portaudio
>> Available playback devices:
>> PortAudio Software
>> Available capture devices:
>> Segmentation fault
>> Is this normal? PortAudio seems to work otherwise, although I haven't
>> tried recording anything yet.
> The crash isn't normal, no. What seems to happen is that the alcGetString
> query for the capture device list returns NULL, since there's no capture
> devices (PortAudio doesn't provide one, and no other backends were available).
> The spec says querying for a default device will return NULL if there aren't
> any devices, but doesn't say what the device list will be in that case (NULL?
> an empty string, or two null chars?). So I don't know if OpenAL Soft is wrong
> for returning a NULL list, or if the info program is wrong for not checking
> the returned pointer.
> Openal-devel mailing list
> Openal-devel at opensource.creative.com
More information about the Openal-devel