I guess most people know it by now, but I've finally had some time to
try it out myself, so...
https://github.com/wine-compholio/wine-staging/wiki/Installation
Wonder how long it'll take for pulse related patches to get into
upstream Wine (if they ever will), but so far this is the closest thing
We should all acknowledge that they're not gonna add pulseaudio support,
due to reasons that lack any technical relevance (whatever you say, "use
a plugin for alsa" makes any argument used along a *joke*). After all,
this project belongs to AJ & his crew, so we really can't do anything to
force a c
(In reply to Susan Cragin from comment #413)
> My above post is confusing in one regard. I was able to get Youtube music on
> my linux Firefox, and NatSpeak on my wine, simultaneously.
> I did one more test.
> I set pulseaudio autospawn to No, killed pulseaudio, and started Natspeak
> wine. Natspe
(In reply to Austin English from comment #406)
> Bugzilla is not for discussion, as has been pointed out, e.g.,
> http://bugs.winehq.org/show_bug.cgi?id=10495#c251.
>
> Please take the discussion somewhere else.
To avoid further discussion in this bug report, which seems to come back
to life ever
(In reply to Ben Klein from comment #404)
> One of my major objections to the existing Winepulse code is that it seems
> to completely ignore MIDI support. Even without the other hurdles to
> inclusion, an audio driver simply would not be considered if it will
> completely break applications that a
(In reply to Rosanne DiMesio from comment #400)
> (In reply to Michael Gooch from comment #399)
>
> > audio issues on these distros when run in wine, DESPITE the distros
> > patching in winepulse support (
> >
>
> Doesn't that just prove that a winepulse driver is NOT the answer to the
> audio
Just a friendly reminder, but after another 4 months of waiting, how is
this being handled? Is pulseaudio support still considered
trivial/unneeded, although it's mandatory on some systems (eg. those on
which a good/easy way to control audio streams is needed)?
I'd also like to add that using the
I was waiting to ask this as well... Since wine 1.6 is out now, will
winepulse be one of 1.8's goals? I haven't seen many references to this
on the mailing list either lately
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in U
(In reply to comment #393)
> Patches have been sent, people posted reviews/comments. E.g.,:
Thanks a lot for the info!
(In reply to comment #393)
> Check the first comment, it's a feature request => enhancement.
>
> Pulseaudio is supposed to be compatible with ALSA, which Wine already
> supports
So, it's been a month since the last update about this... How are things going?
Will winepulse make it into upstream? Has there been an actual collaboration
between Maarten and the devs?
Also, just for the record:
http://www.phoronix.com/scan.php?page=news_item&px=MTIxOTg
By the way, I think thi
I know I'm just a user and I probably don't understand much of wine's
developement, but Maarten put a lot of effort into a patch that fixes an issue
( or a serious lacking, up to you ) that wine'd had for 5 years now, shouldn't
that be enough to prove himself to the devs' team? At least take a
Many people who tried Maarten's winepulse can testify how well it works. Even
if there'd been some misunderstandings in the past, he put much effort in his
work, in an area where upstream wine's progress was non existent. Face it,
"supporting" pulse via alsa-plugins is just not viable, it didn't
12 matches
Mail list logo
