public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-msdos@vger.kernel.org
Subject: Re: App database, libsynth
Date: Mon, 14 Jul 2003 16:06:00 -0500	[thread overview]
Message-ID: <20030714210600.GO1031@dbz.icequake.net> (raw)
In-Reply-To: <3F12EBDE.4080907@aknet.ru>


Hi Stas,

On Mon, Jul 14, 2003 at 09:43:58PM +0400, Stas Sergeev wrote:
> Hello.
> 
> Ryan Underwood wrote:
> >>Overall I might be misunderstanding you, but it
> >Definitely not :)
> Then why do you think it is necessary for
> midid to use your server? For overall
> completeness? Do it an ALSA-compatible I
> would say, and if someone is ever to find
> it usefull for midid to talk to your OPL3
> server, that can be easily implemented, but
> I don't think it can have any use.

Ok :)

> >However, the user might like to use an OPL-emulated chip
> >for playing MIDI music from DOS programs that don't
> >support OPL for music.
> Yes, but what's the use? What is the use??
> Is it because someone have a very limited
> internet connection to download the timidity
> and all the samples for it? Or too slow CPU
> to power up the timidity? But I think MAME
> OPL emu eats even more CPU than the timidity
> does:)

Nah, some people (like me) just like that FM sound.  Perhaps I am crazy?
:) Probably...

> OK, never mind. If you do that lib and you
> think it is usefull for midid to be able to
> use it - then it is.

The lib for direct access comes first priority because we need working
FM in dosemu.  Currently I have it spawning a synthd and talking to it,
but sometimes it doesn't clean up after itself, and the concurrent
usage of libsynth by multiple programs is not working.  Also I need to
hack dosemu to use it, I am testing it only with wolf3d for the moment.

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

  reply	other threads:[~2003-07-14 21:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 17:43 App database, libsynth Stas Sergeev
2003-07-14 21:06 ` Ryan Underwood [this message]
2003-07-15  8:38   ` Paul Eggleton
2003-07-15 10:10     ` Ryan Underwood
2003-07-15 12:26       ` Paul Eggleton
2003-07-15 23:48         ` Ryan Underwood
  -- strict thread matches above, loose matches on Subject: below --
2003-07-17 16:07 Stas Sergeev
2003-07-17 23:09 ` Ryan Underwood
2003-07-13 19:50 Stas Sergeev
2003-07-13 21:27 ` Ryan Underwood
2003-07-13  2:37 Stas Sergeev
2003-07-13  5:00 ` Ryan Underwood
2003-07-13  0:29 Stas Sergeev
2003-07-13  0:59 ` Ryan Underwood
2003-07-13  0:21 Stas Sergeev
2003-07-13  0:56 ` Ryan Underwood
2003-07-13  0:09 Stas Sergeev
2003-07-12 23:47 Stas Sergeev
2003-07-13  0:50 ` Ryan Underwood
2003-07-11 19:02 Stas Sergeev
2003-07-11 19:59 ` Ryan Underwood
2003-07-11 20:23   ` Bart Oldeman
2003-07-11 22:03     ` Ryan Underwood
2003-07-12 20:57       ` Bart Oldeman
2003-07-12 22:40         ` Ryan Underwood
2003-07-12 16:30     ` Jan Willem Stumpel
2003-07-12 19:03       ` Ryan Underwood
2003-07-12 20:13         ` Jan Willem Stumpel
2003-07-12 19:19       ` Bart Oldeman
2003-07-10 17:20 App database Stas Sergeev
2003-07-11 17:30 ` App database, libsynth Ryan Underwood

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=20030714210600.GO1031@dbz.icequake.net \
    --to=nemesis-lists@icequake.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