From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-msdos@vger.kernel.org
Subject: Re: App database, libsynth
Date: Sat, 12 Jul 2003 19:50:38 -0500 [thread overview]
Message-ID: <20030713005038.GQ1031@dbz.icequake.net> (raw)
In-Reply-To: <3F109E10.8060004@aknet.ru>
Hi Stas,
On Sun, Jul 13, 2003 at 03:47:28AM +0400, Stas Sergeev wrote:
> Hello.
>
> Ryan Underwood wrote:
> >>dosemu, or it is somehow possible to use dmix via an
> >>OSS emulation layer?
> >The synth server's output would be completely separate
> >from the application using it, so the synth could use
> >ALSA where dosemu could still use the OSS emulation.
> Yes. But I was wondering will they be able
> to use dmix both. Is it available via the
> OSS emulation layer at all?
Unfortunately not without the wrapper. The dmix is done in userspace,
so writing to /dev/dsp kernel device would bypass it. The aoss wrapper
intercepts those writes and puts them through alsalib instead, allowing
dmix to be used.
> >Yeah. Also what about sending pc-speaker output to the
> >dsp?
> Yes. I wanted to mention that in my previous
> posting but was distracted and forgot.
> This will require translating the 6-bit PDM
> stream to a 8-bit PCM stream. This is very
> easy IIRC, I think I've done something like
> that in my ZX Spectrum emulator back in 1995.
> Dosbox is doing that so (considering other
> messages in that ML today) also we have to:)
> Would be nice to see that in your lib. This
> will require an additional stream, but what's
> the deal provided we have the dmix.
Interesting. It would fit the model of the library because I am
supporting any synth that is accessed only through port writes and
nothing more complicated like interrupts/DMA. The PC speaker would seem
to fit that model, so if you have some emulation code, I should be able
to include it.
This would help in portability effort too.
> >>So does it interact with ALSA, or you decided to do it
> >>a standalone?
> >(1) Theoretically, it can output to either ALSA or OSS,
> >though I use ALSA to test it.
> There was a discussion in the past where you
> said you'll make it the timidity-sequencer alike
> plugin for alsa. I was asking about that. Now
> It seems you decided to make it completely
> standalone.
Yeah, that is going to be a separate thing, since this libsynth supports
any synth you want, whereas there is only MIDI sequencer for the OPL3,
so only a emulated-OPL3 sequencer client would make any sense.
> >Once that is complete I can implement the emulator core
> >as an ALSA sequencer client, which if dosemu had alsa
> >support, it could connect to that sequencer slot and use
> >the MT-32. Or else maybe something could be done with
> >midid?
> midid is fully functional and together with
> timidity it can provide you with General Midi
> and (limited) MT-32. I've heard timidity is not
> powerfull enough for the *real* MT-32, so they
> (dosbox) needed their own code, but I am not
> a musician and what timidity produces sounds
> rather good for me.
It may be possible to implement another backend to timidity but that
would require more research.
If the timidity/mt-32 emulator becomes an ALSA sequencer client (which
is the optimal situation so it can be used in any ALSA application), how
would dosemu/midid support it?
> >Is midid a good idea to keep around for the long
> >term?
> Yes. Among other things it allows to capture
> your favourite music from games into a .mid files.
Interesting. What about making the ALSA sequencer a backend
for midid?
--
Ryan Underwood, <nemesis at icequake.net>, icq=10317253
next prev parent reply other threads:[~2003-07-13 0:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 23:47 App database, libsynth Stas Sergeev
2003-07-13 0:50 ` Ryan Underwood [this message]
-- 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-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-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=20030713005038.GQ1031@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