From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Sound report
Date: Wed, 22 Jan 2003 23:56:51 +0300 [thread overview]
Message-ID: <3E2F0593.5020005@yahoo.com> (raw)
Hello.
Jan Willem Stumpel wrote:
> I applied Stas's opl1a.diff to 1.1.4.6 and I got sound out of SB
> fmorgan! The sound is quite horrible
There is a note on my page that the code
is in an alpha stage, so the problem reports
should not be sent. You've just violated
that:)
> (tweaking DIRECT_WRITE_FREQ
> in linux_sound.h helps a bit)
Strange that it makes any differences
at all in that case...
> but this is the first time I have
> heard any sound at all from this program in many years.
Unfortunately this will take many years
for that code to became a part of dosemu
(if at all).
There was a person who is willing to
volunteer for that work, in which case
this have some more chances to be ever
finished. I hope he will get to it soon:)
> Also, I can get
> either music or shooting sounds, but not both.
That means that your card or driver
doesn't support multiple sound channels
(hardware mixing). You have to try SB Live.
> Sound Blaster not responding on selected port.
Yep, the same problem.
> Using kernel 2.4.16 + alsa
I've heard somewhere that the Commercial OSS
drivers have a built-in mixing. If this is
true, use these and you'll get everything
you want (the quality of the sound will
still be miserable as the Adlib code is not
finished - requires threading).
next reply other threads:[~2003-01-22 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 20:56 Stas Sergeev [this message]
2003-01-23 7:12 ` Sound report Paul Eggleton
2003-01-24 19:54 ` Jan Willem Stumpel
2003-01-24 20:31 ` Bart Oldeman
-- strict thread matches above, loose matches on Subject: below --
2003-01-26 21:16 Stas Sergeev
2003-01-25 0:23 Stas Sergeev
2003-01-26 16:12 ` Jochen Reinwand
2002-12-24 20:40 fmorgan Stas Sergeev
2003-01-22 20:27 ` Sound report Jan Willem Stumpel
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=3E2F0593.5020005@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-msdos@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.