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 fixme:dsound:mmErr Unknown MMSYS error 3 dsound.c:701: Test failed: DirectSoundCreate failed: 0x80004005 dsound.c:1035: Test failed: DirectSound test failed
Attached: dsound.results & propset.results. Results of a rerun with --debugmsg +something available if needed.
Note : The same tests run ok if the tests are launched with wineoss and OSS emulation.
===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels
"What if tomorrow the War could be over ?" Morpheus, in "Reloaded".
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
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_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels
"What if tomorrow the War could be over ?" Morpheus, in "Reloaded".
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
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 pcm.c:1908:(snd_pcm_open_noupdate) Unknown PCM ºÝ@ þB Pc@ while it should be: Unknown PCM hw.
Please check the result of --debugmsg +wave or send it to me, maybe we can find a clue.
These logs doesnt show anything brilliant/remarkable to me. Could this be an uninitialised pointer problem ?
--- Jerry Jenkins Jerry_J_Jenkins@hotmail.com a écrit :
===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels
"What if tomorrow the War could be over ?" Morpheus, in "Reloaded".
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
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* h = NULL; snd_pcm_info_t * info; snd_pcm_hw_params_t * hw_params; WINE_WAVEOUT* wwo; char device[] = "hw"; The last variant should be declared as static char device[]="hw";
-
Jerry Jenkins -
Sylvain Petreolle