Do you guys still need audio testing help? I found this here http://www.winehq.org/?issue=313#Testing%20Wine%27s%20Audio. If you do that would be good, I have a couple of days off coming up. And I would like to help get this audio stuff figured out, because I can install WinAmp and it works fine, but games that I install will not play any sound at all, even when I change my audio settings. (The main game that I have been trying to get worked out is Star Trek Voyager: Elite Force).
Kenny Armstrong
Kenneth Armstrong wrote:
Do you guys still need audio testing help? I found this here http://www.winehq.org/?issue=313#Testing%20Wine%27s%20Audio. If you do that would be good, I have a couple of days off coming up. And I would like to help get this audio stuff figured out, because I can install WinAmp and it works fine, but games that I install will not play any sound at all, even when I change my audio settings. (The main game that I have been trying to get worked out is Star Trek Voyager: Elite Force).
Kenny Armstrong
Yes. Running the wave and direct sound regression tests in interactive mode and with various drivers and settings and reporting the results will help developers fix any problems that turn up.
There is one bug in winealsa that makes longer use of it pretty annoying:
deadlock in alsa driver: CriticalSection WINEALSA_mmap_crst http://bugs.winehq.org/show_bug.cgi?id=4093
I tried but I didn't find the actual code that is wrong for this bug, because it's threading related and sensitive to it's scheduling. With traces it sometimes goes away and I haven't yet found a debugger that can replay a program run including it's exact scheduling ... *insert your favorite page long rant*.
It would be realy nice if someone could solve this.
Jan
-
Jan Zerebecki -
Kenneth Armstrong -
Robert Reif