public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: 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, 03 Jun 2006 16:48:17 -0400	[thread overview]
Message-ID: <1149367697.28744.45.camel@mindpipe> (raw)
In-Reply-To: <4481E816.4090600@seclark.us>

On Sat, 2006-06-03 at 15:50 -0400, Stephen Clark wrote:
> Hello,
> 
> 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.

Does it work with ALSA's OSS emulation?

Lee


  reply	other threads:[~2006-06-03 20:48 UTC|newest]

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

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=1149367697.28744.45.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --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