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: Thu, 17 Jul 2003 18:09:16 -0500	[thread overview]
Message-ID: <20030717225130.GO1031@dbz.icequake.net> (raw)
In-Reply-To: <3F16C9BD.2090301@aknet.ru>


Hi Stas,

On Thu, Jul 17, 2003 at 08:07:25PM +0400, Stas Sergeev wrote:
> Hello.
> 
> Ryan Underwood wrote:
> >The design is simple to me.  The programmer of the 
> >application need do nothing but SynthOpen the correct 
> >devices, and then SynthWrite the data to them.
> Sounds good. It would probably be a good
> idea to provide an optional way to query
> user's time and request the timer events
> from user. It may be that the user's time
> is different than the real time. dosemu
> uses the real time, but AFAIK dosbox uses
> the emulated time (CPU-emu relative).
> It may also be possible that the real card's
> sampling rate is not very precise (the pcsp
> driver rounds the sampling rate rather cruely),
> in which case you'll have one more timing
> source with which you also have to keep in
> sync. Last time I dealt with all that mess,
> it wasn't very simple (see linux_sound.c :)

Ok, I will look into this.

> >Plan to support the following synths in the library, all 
> >can be either hardware or emulated:
> How are you accessing the hardware btw?
> ioperm() ?

For the OPL chips, I use the direct-FM API of OSS/ALSA.  (This is not
implemented yet because I do not have a working OPL-chip on my
soundcard.  I will swap out my card with SB16 to test it or else hack
the vortex driver to get FM access).

For any other chips, it will have to use iopl(3).  I can create ALSA
hwdep driver to handle all the other chips, but I might wait until
people wiht the actual hardware request the capability. :)

But the design of the library does not exclude it.

> >The OPL-chip has an internal IRQ but it can be triggered
> >or cleared by simply writing to the OPL's port.
> AFAIK it is not even connected to any of
> the PIC wires, but why can't you provide an
> optional way to notify the user about an IRQ?
> Simply calling the user's registered call-back
> function might just do the trick, so why not?

You have a good point, I will look into this.

I rewrote the library last few days, now having trouble with some
"chainsaw" noise in wolf3d music. :)  Hopefully won't be hard too
fix.

Thanks,

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

  reply	other threads:[~2003-07-17 23:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 16:07 App database, libsynth Stas Sergeev
2003-07-17 23:09 ` Ryan Underwood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-14 17:43 Stas Sergeev
2003-07-14 21:06 ` Ryan Underwood
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
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=20030717225130.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