From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Steve Longerbeam <stevel@embeddedalley.com>,
ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: a new synthesizer driver
Date: Thu, 19 Jul 2007 08:32:37 +0200 [thread overview]
Message-ID: <1184826757.2575.1200931737@webmail.messagingengine.com> (raw)
In-Reply-To: <469EBE3A.30002@embeddedalley.com>
Steve Longerbeam wrote:
> I'm embarking on a big task: writing a new synthesizer driver. My device
Which one?
> has all the ingredients for a MIDI wavetable sythesizer: 64 voices, each
> voice with envelope, pitch, and LFO controls. Also global effects like
> reverb. It's similar to the emu10k1.
>
> So my first question would be, is the synth code under synth/emux/
> general enough to use for a different synthesizer chip? Ie, can I
> implement my own operators in 'struct snd_emux_operators' and pass that
> to snd_emux_register() ?
Probably not. The sound font loading code is somewhat generic, but that
is because the sound font format was designed to be the equivalent of
the Emu chips' hardware capabilities.
All that code has been written for Emu hardware. How much it must be
changed depends on how different your hardware is.
> Would it be a simple matter to make synth/emux/ a generic synth layer,
> by moving all the source in synth/emux/ up one level to synth/, and then
> rename all functions and data structures starting with "snd_emux" to
> "snd_synth" ?
I think it is possible to reuse some of that code, but it wouldn't be
as easy as just renaming some things.
(The generic synth code is supposed to be in core/seq/seq_midi_emul.c.
The synth/emux directory just exists to factor out common code of the
Emu8000 and Emu10k1 drivers.)
Regards,
Clemens
next prev parent reply other threads:[~2007-07-19 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 1:28 a new synthesizer driver Steve Longerbeam
2007-07-19 6:32 ` Clemens Ladisch [this message]
2007-07-19 18:18 ` Steve Longerbeam
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=1184826757.2575.1200931737@webmail.messagingengine.com \
--to=cladisch@fastmail.net \
--cc=alsa-devel@alsa-project.org \
--cc=stevel@embeddedalley.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.