public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: Sound support (2), using hardware directly
Date: Fri, 22 Jul 2005 08:03:36 +0400	[thread overview]
Message-ID: <42E07018.4040300@aknet.ru> (raw)

Hello.

Julius Schwartzenberg wrote:
> The current system seems to work pretty well for me
It doesn't even work with ALSA.
Also, your AWE probably have the
hardware mixing, but for those
with the cheap sound cards, it
is not possible to get the midi
together with sound (provided they
do not have the wave-table too).
I myself can't get this to work on
my pc-speaker, and that really annoyed
me enough to start writing the new
code. Now as for the DOS programs:
FT2 doesn't work, sound in DOOM
stutters, sound in Aladdin have a
big latencies, etc. It is not very
good.

> While OPL3 emulation would be really nice, wouldn't it be better to 
> implement support for real OPL3 chips and emulate and OPL3 at another 
> level in the system if one isn't availlable?
Problematic. Access to the real OPL3
will require root or the kernel module.
And then you can just use $_ports to
get this working that way, no need to
write anything (yes, I know it doesn't
work for you right now, but thats a
different problem). So the real value
is to have the good OPL3 emulation.

> Then also other
> applications such as FreeSCI and
> ScummVM would be able to make use of
> it.
They all use the MAME OPL3 emulation
engine. I don't think they'll want
something else. And really, having
the OPL3 emulation system-wide doesn't
sound sane to me - this is too specific
to the old-PC emulators.

> About the new system. If the new code isn't comparable to the current 
> code yet, maybe release 1.4 of Dosemu should still contain the old 
> code?
Noone knows when 1.4 will be released.

> I'm really looking forward to the new stuff.
You will get it and the sound code
is not even the main part.


             reply	other threads:[~2005-07-22  4:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-22  4:03 Stas Sergeev [this message]
2005-07-22 13:11 ` Sound support (2), using hardware directly Julius Schwartzenberg
  -- strict thread matches above, loose matches on Subject: below --
2005-07-23 19:18 Stas Sergeev
2005-07-24 15:13 ` Julius Schwartzenberg
2005-07-23 12:30 Stas Sergeev
2005-07-23 12:27 Stas Sergeev
2005-07-23 18:16 ` Julius Schwartzenberg
2005-07-23  9:45 Stas Sergeev
2005-07-23 11:16 ` Julius Schwartzenberg
2005-07-23 12:19   ` John R. Sowden
2005-07-22 17:56 Stas Sergeev
2005-07-22 18:20 ` Julius Schwartzenberg
2005-07-19 12:54 Stas Sergeev
2005-07-21 20:17 ` Julius Schwartzenberg
2005-07-19  4:18 Stas Sergeev
2005-07-19 11:11 ` Julius Schwartzenberg
2005-07-18 19:25 Julius Schwartzenberg

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=42E07018.4040300@aknet.ru \
    --to=stsp@aknet.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox