Re: Concerning the separate OpenAL32.dll thunk patch and OpenALwinmm driver patch
Nick Burns [EMAIL PROTECTED] writes: Again -- for the sound drivers -- Mac OSX has ONE sound driver ONE I would like to have a choice. Why? What does it do that you cannot do with the CoreAudio driver? Yes my wineopenal patch is not perfect (based on broken code does not help) -- I know that -- but thats why i want to get it into wine -- so other people who know more about audio can add to it and make it better Judging from past experience, people for whom it doesn't work right will simply go out and implement yet another driver, with yet another set of bugs... -- Alexandre Julliard [EMAIL PROTECTED]
Re: Concerning the separate OpenAL32.dll thunk patch and OpenALwinmm driver patch
On 1 déc. 06, at 00:54, Nick Burns wrote: Again -- for the sound drivers -- Mac OSX has ONE sound driver ONE I would like to have a choice. In fact there is at least two working sound driver: you can also use the Jack driver on Mac OS X if you've downloaded [1] at compile time which by the way seems to have a working audio input. [1] http://www.jackosx.com/ Pierre.
Re: Concerning the separate OpenAL32.dll thunk patch and OpenALwinmm driver patch
From: Alexandre Julliard [EMAIL PROTECTED] To: Nick Burns [EMAIL PROTECTED] CC: wine-devel@winehq.org Subject: Re: Concerning the separate OpenAL32.dll thunk patch and OpenALwinmm driver patch Date: Fri, 01 Dec 2006 13:49:52 +0100 Nick Burns [EMAIL PROTECTED] writes: Again -- for the sound drivers -- Mac OSX has ONE sound driver ONE I would like to have a choice. Why? What does it do that you cannot do with the CoreAudio driver? True the coreaudio driver can be made awesome -- but as it stands it has problems with many games on my machine (currently hard for me to test due to fullscreen detection changes in ogl) Problems range from deadlocking -- to crackling sound There are a few games that run flawlessly under coreaudio My openal driver also has crackling sound in some games (but i have not yet seen deadlocking -- its possible it could) Also the coreaudio driver is not testable and wont help linux ppl -- just Mac ppl An openal driver would be multi-platform -- testable under windows/mac/linux, would add a 2nd built-in driver to Mac OSX. Yes my wineopenal patch is not perfect (based on broken code does not help) -- I know that -- but thats why i want to get it into wine -- so other people who know more about audio can add to it and make it better Judging from past experience, people for whom it doesn't work right will simply go out and implement yet another driver, with yet another set of bugs... True -- it has its own set of bugs -- but I cannot iron them out myself -- I would need help from people to do so -- thats why I would like to give it as an option to you wine people (who can test it on linux) (its possible i could try and start a side project in sf.net or something -- no clue what other options there are) In a perfect world we could make an awesome cross-platform openal driver that does ... everything (winmm/dsound/dsound3d/...) everywhere (Linux/Windows/MacOSX) -- So, thats all the good stuff about it... The bad stuff is that its another driver in the tree another option to confuse people another point of failure ... (there is more badness here probably) -- Alexandre Julliard [EMAIL PROTECTED] - Nick
Re: Concerning the separate OpenAL32.dll thunk patch and OpenALwinmm driver patch
Ok this is some good feedback... (usually i dont get such a massive response from emails...) -- I was under the impression that RFC was the second to last line of defense (so it appears to be the third) I do not use IRC (unless you count the irc client in Tribes) I can demacroize the patch -- it was written that way to make it small and easy to add to (since 99% of the functions are pure passthru -- one extra line to the macro adds it and all that it needs) Personally I think its cleaner -- but it has the problem of being a macro There not much worse than a macro -- except dare I mention templates (the crowd runs for cover) Again -- for the sound drivers -- Mac OSX has ONE sound driver ONE I would like to have a choice. Yes my wineopenal patch is not perfect (based on broken code does not help) -- I know that -- but thats why i want to get it into wine -- so other people who know more about audio can add to it and make it better If the audio drivers are going to collapse -- I could wait until then and 'try' add my winmm patch in that realm. - Nick From: Alexandre Julliard [EMAIL PROTECTED] To: Detlef Riekenberg [EMAIL PROTECTED] CC: Nick Burns [EMAIL PROTECTED], wine-devel wine-devel@winehq.org Subject: Re: Concerning the separate OpenAL32.dll thunk patch and OpenALwinmm driver patch Date: Thu, 30 Nov 2006 19:58:36 +0100 Detlef Riekenberg [EMAIL PROTECTED] writes: I don't know, if wineaudio.drv this is still the way to go, but we have sound crackeling and Buffer-underun Bugs, and adding another copy of the not very well working code might be a no go for Alexandre. Exactly, we already have 8 sound drivers, and not a single one actually works properly, so I'm pretty reluctant to add yet another copy of the same broken code. The openal dll can certainly go in, but you'll need to clean up the code first, right now it looks like a pretty bad case of macro abuse. -- Alexandre Julliard [EMAIL PROTECTED]
