Re: Fate of PulseAudio in WINE

2009-06-17 Thread Francois Gouget
On Tue, 16 Jun 2009, Arthur Taylor wrote: [...] > This is all simple enough except for how variable it is. Applications > usually allocate a set size of wavehdrs and then use them circularly. > Applications usually use when a wavehdr is returned for timing > purposes rather than waveOutGetPositi

OpenAL and DSound (was Re: Fate of PulseAudio in WINE)

2009-06-16 Thread Chris Robinson
On Tuesday 16 June 2009 8:44:36 pm Stefan Dösinger wrote: > There is such a DLL around - search the wine-devel and wine patches > archives from it. Alexandre said he'd accept such a openal->openal > thunk(but not an openal winmm driver). The problem why it is not included > yet is that the latest s

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Stefan Dösinger
Am Wednesday 17 June 2009 05:24:01 schrieb Arthur Taylor: > As a curious aside, would it be possible write an OpenAl dll that > backended to the native OpenAl library similarly to the way OpenGl is > handled? Would this not mean that if the native platform supported > hardware accelerated OpenAl th

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Ben Klein
2009/6/17 Arthur Taylor : > As a curious aside, would it be possible write an OpenAl dll that > backended to the native OpenAl library similarly to the way OpenGl is > handled? Would this not mean that if the native platform supported > hardware accelerated OpenAl that the benefits would be reaped

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Arthur Taylor
On Tue, Jun 16, 2009 at 3:24 PM, Michael Stefaniuc wrote: > Arthur Taylor wrote: >> >> Recent activity in http://bugs.winehq.org/show_bug.cgi?id=10495 has >> caused some issues. This is also a response to >> http://www.winehq.org/pipermail/wine-devel/2009-April/074666.html > > [...] >> >> It is tru

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Michael Stefaniuc
Arthur Taylor wrote: Recent activity in http://bugs.winehq.org/show_bug.cgi?id=10495 has caused some issues. This is also a response to http://www.winehq.org/pipermail/wine-devel/2009-April/074666.html [...] It is true that currently whitespace is an issue with the patches in the bug report. I

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Chris Robinson
On Tuesday 16 June 2009 3:33:12 am Arthur Taylor wrote: > I can't imagine stopping pulseaudio just so I can listen > to music through foobar2000, as that would stop all my voice chats, > notification sounds, and other native audio, etc. There is no need to use PulseAudio if the issue you have is y

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Matteo Bruni
2009/6/16 Trevor Davenport : > On Tue, Jun 16, 2009 at 4:14 AM, Roderick > Colenbrander wrote: >> Hi Arthur, >> >> I would recommend you to also read this thread: >> http://www.winehq.org/pipermail/wine-devel/2009-June/076102.html >> >> As mentioned before we would like not to have a pulse audio dr

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Trevor Davenport
On Tue, Jun 16, 2009 at 4:14 AM, Roderick Colenbrander wrote: > Hi Arthur, > > I would recommend you to also read this thread: > http://www.winehq.org/pipermail/wine-devel/2009-June/076102.html > > As mentioned before we would like not to have a pulse audio driver if > it isn't needed at all. Some

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Stefan Dösinger
Am Dienstag, 16. Juni 2009 17:39:47 schrieb Remco: > Well, but Wine doesn't fix bugs for Windows programs. If a program > doesn't work in Windows, it's not a requirement that it works in Wine. > > I think that the PulseAudio developer means the same thing for PA. > Some apps use ALSA in a way that

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Remco
On Tue, Jun 16, 2009 at 4:48 PM, Stefan Dösinger wrote: > Am Dienstag, 16. Juni 2009 13:41:26 schrieb Jerome Leclanche: >> One of the problems is, every time one of these issues is brought up, >> we hear people complaining "But Pulseaudio should be a drop-in >> replacement! We shouldn't have to cha

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Stefan Dösinger
Am Dienstag, 16. Juni 2009 13:41:26 schrieb Jerome Leclanche: > One of the problems is, every time one of these issues is brought up, > we hear people complaining "But Pulseaudio should be a drop-in > replacement! We shouldn't have to change our code". > There is a major (and irritating) circle of

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Reece Dunn
2009/6/16 Jerome Leclanche : > On Tue, Jun 16, 2009 at 2:14 PM, Roderick > Colenbrander wrote: >> I think a lot of issues can already be fixed without requiring a new driver. > > One of the problems is, every time one of these issues is brought up, > we hear people complaining "But Pulseaudio shoul

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Jerome Leclanche
On Tue, Jun 16, 2009 at 2:14 PM, Roderick Colenbrander wrote: > I think a lot of issues can already be fixed without requiring a new driver. One of the problems is, every time one of these issues is brought up, we hear people complaining "But Pulseaudio should be a drop-in replacement! We shouldn'

Re: Fate of PulseAudio in WINE

2009-06-16 Thread Roderick Colenbrander
Hi Arthur, I would recommend you to also read this thread: http://www.winehq.org/pipermail/wine-devel/2009-June/076102.html As mentioned before we would like not to have a pulse audio driver if it isn't needed at all. Some suggestions have been made to use some pulseaudio rules of thumb in our wi

Fate of PulseAudio in WINE

2009-06-16 Thread Arthur Taylor
Recent activity in http://bugs.winehq.org/show_bug.cgi?id=10495 has caused some issues. This is also a response to http://www.winehq.org/pipermail/wine-devel/2009-April/074666.html First the background. WinePulse has been an attempt to write a winmm backend for pulseaudio for wine. Currently the p