All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: bownie@bownie.com
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: sequencing ALSA ports and clients
Date: Wed, 10 Apr 2002 17:04:22 +0200	[thread overview]
Message-ID: <s5hit6zlhmx.wl@alsa2.suse.de> (raw)
In-Reply-To: <200204101341.AFH83147@msgdirector1.onetel.net.uk>

Hi Richard,

At Wed, 10 Apr 2002 14:38:04 +0100,
Richard Bown wrote:
> 
> Ok, earlier I sent this question to LAD but this is probably a better place
> to be asking it.  Apologies if you've already seen it.
> 
> Basically I'm still confused about synth clients and ports.  My
> SBLive presents four synth ports as default.  I create a port and
> subscribe or connect_to a specfic SBLive port and client.  When I'm
> sequencing out to this port should I be multiplexing among the other
> ports to exploit the synth's full polyphony?

what do you mean exactly "full polyphony"?
if it means "playing tones with the same note number on the same
channel on the same port at the same time", then, no, emu10k1 and
sbawe drivers don't do this.
notes are exclusive on the channel, i.e. you can play only a single
note A on the channel 1.  but of course, notes A can be played on
different channels, or on different ports at the same time.

if a note on the port 1 is affected by another port, then it's a bug
of the driver (except the case when all 64 voices are exhausted).

well, it's not difficult at all to reimplement the driver to allow
multi-notes-on-a-channel, but i don't think it's common.


> Should I be adding to the ports myself or can I get away
> with just using the one?  If the latter then why are there four
> ports made available?  I'm sure there's a dunce's document someone
> can point me to! 

four ports are provided to support more than 16 channels.


ciao,

Takashi

  reply	other threads:[~2002-04-10 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10 13:38 sequencing ALSA ports and clients Richard Bown
2002-04-10 15:04 ` Takashi Iwai [this message]
2002-04-10 16:40   ` Richard Bown

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=s5hit6zlhmx.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=bownie@bownie.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.