Sylvain Petreolle wrote:
These logs doesnt show anything brilliant/remarkable to me.
Could this be an uninitialised pointer problem ?
The source I looked over are not so up to data as I expected. After an
update, I find something insteresting:
LONG ALSA_WaveInit(void)
{
snd_pcm_t*
These logs doesnt show anything brilliant/remarkable to me.
Could this be an uninitialised pointer problem ?
--- Jerry Jenkins <[EMAIL PROTECTED]> a écrit :
> It's not necessary. I ask you the question just because that I am not
>
> quite familiar with the source :-(.
>
> The logs you provided
Yes, they work without problem.
I can provide logs/screen copy if needed.
It's not necessary. I ask you the question just because that I am not
quite familiar with the source :-(.
The logs you provided show that dsound or winealsa call alsa-lib with an
invalid device name. The line is
ALSA lib
Yes, they work without problem.
I can provide logs/screen copy if needed.
Note: all of them were compiled from sources (driver, lib, oss compat,
tools and utils)
> Do other programs that will call ALSA APIs such as alsamixer and
> aplay work properly?
>
=
Sylvain Petreolle (spetreolle_at_u
Do other programs that will call ALSA APIs such as alsamixer and aplay work
properly?
Sylvain Petreolle wrote:
> After an update to current cvs, dsound test with winealsa is failing.
> cature.c is ok (1 test only) but propset.c and dsound.c fail.
>
> They give the same error at almost every test
After an update to current cvs, dsound test with winealsa is failing.
cature.c is ok (1 test only) but propset.c and dsound.c fail.
They give the same error at almost every test
ALSA lib pcm.c:1908:(snd_pcm_open_noupdate) Unknown PCM
err:wave:wodOpen Error open: Inappropriate ioctl for device
fix
