From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: Sound support (2), using hardware directly
Date: Sat, 23 Jul 2005 13:45:08 +0400 [thread overview]
Message-ID: <42E211A4.4040707@aknet.ru> (raw)
Hello.
Julius Schwartzenberg wrote:
> I have ran it succesfully on my AMD Athlon @ 1GHz, and I know there are
> softsynths that need much less, although not for Linux.
As I said, you can tune timidity++
to work even on 386, just disable
some effects processing.
There are also the alternative
synthesizers, like fluidsynth,
as someone pointed out to me, but
I am not sure if they work as an
alsa sequencer backend, or have
the server interface for midid.
> running a softsynth inside Dosemu...
That is possible for FM synth, but
you really don't want to distribute
the instrument patchsets with dosemu.
> Well, the problem seemed to be at the time that the (OPL3) driver from
> ALSA was conflicting with the OPL3 being accessed directly.
In this case simply not loading the
OPL3 driver from ALSA would help,
but IIRC it doesn't.
next reply other threads:[~2005-07-23 9:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 9:45 Stas Sergeev [this message]
2005-07-23 11:16 ` Sound support (2), using hardware directly Julius Schwartzenberg
2005-07-23 12:19 ` John R. Sowden
-- 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-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 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=42E211A4.4040707@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