mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Trefzer <ctrefzer@gmx.de>
To: Stephen Clark <Stephen.Clark@seclark.us>
Cc: wine-devel-request@winehq.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Alsa sound vs OSS with wine and riven
Date: Sat, 3 Jun 2006 23:11:06 +0200	[thread overview]
Message-ID: <20060603211106.GA4452@zeus.uziel.local> (raw)
In-Reply-To: <4481E816.4090600@seclark.us>

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

On Sat, Jun 03, 2006 at 03:50:46PM -0400, Stephen Clark wrote:
> I have been working to get "Riven" the sequel to Myst to work with the
> latest wine from cvs on the latest FC5. It works and the sound is
> almost perfect with OSS, but is totally screwed up when I use ALSA, I
> don't know whether this is a WINE or Linux issue, so I am cross
> posting to both lists.

I had the same experience even with a little lower requirements wrt.
CPU performance - music player daemon (mpd) tends to eat a lot more
cycles when it is configured to use alsa style devices, but is pretty
low-impact when it talks to the OSS emulation provided by the very same
alsa drivers.

With wine and starcraft on my not-so-recent yet well maintained laptop
the difference in results was ultimate.

By the way, I still have to apply some scheduler tricks, makes me wonder
about wine's development during the past few years. I used to play
starcraft through wine on an ancient Pentium, and now a Mobile Pentium
III is almost choking on it. I wonder what is going on...

Kind regards,
Chris

[-- Attachment #2: Type: application/pgp-signature, Size: 829 bytes --]

      parent reply	other threads:[~2006-06-03 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-03 19:50 Stephen Clark
2006-06-03 20:48 ` Lee Revell
2006-06-03 22:57   ` Stephen Clark
2006-06-03 23:02     ` Lee Revell
2006-06-03 21:11 ` Christian Trefzer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060603211106.GA4452@zeus.uziel.local \
    --to=ctrefzer@gmx.de \
    --cc=Stephen.Clark@seclark.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wine-devel-request@winehq.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®