All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Longerbeam <stevel@embeddedalley.com>
To: ALSA devel <alsa-devel@alsa-project.org>
Subject: a new synthesizer driver
Date: Wed, 18 Jul 2007 18:28:26 -0700	[thread overview]
Message-ID: <469EBE3A.30002@embeddedalley.com> (raw)

Hi all,

I'm embarking on a big task: writing a new synthesizer driver. My device 
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() ?

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" ? For instance, snd_emux_operators becomes 
snd_synth_operators, snd_emux_control() becomes snd_synth_control(), etc.

It seems this path is already partially completed, since 
synth/emux/soundfont.c is a generic soundfont loader.

The thing I want to avoid doing is creating a synth/my_synth/ directory 
and duplicating lots of code from synth/emux/ (including just copying 
soundfont.c verbatim!).

Steve

             reply	other threads:[~2007-07-19  1:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19  1:28 Steve Longerbeam [this message]
2007-07-19  6:32 ` a new synthesizer driver Clemens Ladisch
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=469EBE3A.30002@embeddedalley.com \
    --to=stevel@embeddedalley.com \
    --cc=alsa-devel@alsa-project.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 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.