From: Julius Schwartzenberg <julius@zgod.cjb.net>
To: linux-msdos@vger.kernel.org
Subject: Re: Sound support (2), using hardware directly
Date: Thu, 21 Jul 2005 22:17:24 +0200 [thread overview]
Message-ID: <42E002D4.6070009@zgod.cjb.net> (raw)
In-Reply-To: <42DCF7F5.7090508@aknet.ru>
Stas Sergeev wrote:
>> Yes, I am aware of the MIDI support in Dosemu, but I thought it was
>> only for General Midi compatibility.
>
> No. On the software synth side, midid
> have the -m option which will give you
> some basic mt32 support.
> As for the directly passing the midi
> stream to the wavetable - this is also
> possible and described, and will allow
> you to use your AWE synth fully, provided
> it all goes via the mpu-401 in a
> pass-through mode (almost always this is
> the case).
> So you can try and see if there are any
> differences with what you now have - there
> shouldn't be, but you won't need root,
> which is very important in some cases.
Ah, I already suspected this. I'll try this out at some point and see if
I'm able to hear a difference.
> Well, the primary goal is to design the
> very simple but robust sound subsystem
> from zero, so that it won't depend on
> OSS, but can work also with ALSA and
> anything, and so that it can work with
> many more DOS progs than the current one
> does. But the OPL3, again, is not in the
> list of the primary targets:)
> Of course porting the MAME OPL3 emulator
> to the planned sound system must be easy,
> but we'll see where this all will end up.
> It will probably take some time before
> something can be released though - the
> main problem is that the current code
> also happened to work somehow, and the
> replacement is possible only when the new
> code matches the current one in the
> functionality, which can take long enough.
The current system seems to work pretty well for me, although it seems
to soundquality could be a little bit higher in certain cases.
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? Then also other
applications such as FreeSCI and ScummVM would be able to make use of it.
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?
After that I think the development version could be switched over to the
new code, even if it's not fully ready yet. Then it would already get
more testing and it might be easier for development. It shouldn't be a
big problem if a development version/tree has regressions.
I'm really looking forward to the new stuff.
Thanks,
Julius
next prev parent reply other threads:[~2005-07-21 20:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 12:54 Sound support (2), using hardware directly Stas Sergeev
2005-07-21 20:17 ` Julius Schwartzenberg [this message]
-- 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-22 4:03 Stas Sergeev
2005-07-22 13:11 ` 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=42E002D4.6070009@zgod.cjb.net \
--to=julius@zgod.cjb.net \
--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