All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Olofson <david@olofson.net>
To: alsa-devel@lists.sourceforge.net
Subject: Re: sequencer: handling non-registered parameter numbers....
Date: Mon, 16 Jun 2003 17:28:07 +0200	[thread overview]
Message-ID: <200306161728.07531.david@olofson.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0306161315300.11284-100000@pnote.perex-int.cz>

On Monday 16 June 2003 13.19, Jaroslav Kysela wrote:
> On Mon, 16 Jun 2003, Jaroslav Kysela wrote:
> > > thanks for the clarification. i'd be glad to help, but i doubt
> > > i could meet the coding standards of alsa-lib. at least i could
> > > help test it. do you or anyone of the alsa core developers have
> > > plans to tackle this some time soon ? i'd love to be able to
> > > use my controller box for the LinuxTag presentations in
> > > mid-July.
> >
> > I am working on it right now, but it requires to add new states
> > to sequencer event encoder...
>
> Initial code is in CVS. It is not tested, but hopefully, without
> any major bugs.

Does this code remove the (N)RPN related CC events, or does it just 
decode (N)RNPs in parallel? The latter will cause (N)RPNs to be 
doubled in apps that understand both "raw" CCs and cooked (N)RPNs. 
(Like Audiality as of a few minutes back.)

I think filtering the CCs out is the Right Thing(TM) to do when 
(N)RPNs are actually used, but if some apps want to use the full 
range of "raw" CCs, that won't work. Those apps won't see the (N)RPN 
related CCs, and they won't look for (NON)REGPARAM events. (Even if 
they did, they wouldn't be able to extract the underlying CCs 
reliably.)

Maybe ALSA shouldn't mess with (N)RPNs at all, unless applications ask 
for it?


> It seems that we have also missing encoding of
> CONTROL14 events.

Now *that's* fun stuff... *heh*

BTW, I think "applications might know better" applies here too. Apps 
that want to bother with 14 bit controls might do stuff that's 
intimately tied to the control intperpolation/smoothing. The only 
"correct" way to implement 14 bit CCs seems to involve a timeout, 
which will add latency to all CCs that can be 14 bit, and apps that 
want to be smart about it to reduce latency may not be able to do so 
without getting at the raw CCs.


//David Olofson - Programmer, Composer, Open Source Advocate

.- The Return of Audiality! --------------------------------.
| Free/Open Source Audio Engine for use in Games or Studio. |
| RT and off-line synth. Scripting. Sample accurate timing. |
`-----------------------------------> http://audiality.org -'
   --- http://olofson.net --- http://www.reologica.se ---



-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

  parent reply	other threads:[~2003-06-16 15:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-15 16:16 sequencer: handling non-registered parameter numbers Joern Nettingsmeier
2003-06-15 18:52 ` David Olofson
2003-06-16  7:51   ` Joern Nettingsmeier
2003-06-16  8:25     ` David Olofson
2003-06-16  8:29     ` Jaroslav Kysela
2003-06-16  8:41       ` David Olofson
2003-06-16  8:57         ` Jaroslav Kysela
2003-06-16  9:10           ` David Olofson
2003-06-16 15:05             ` David Olofson
2003-06-16  9:40       ` Joern Nettingsmeier
2003-06-16  9:55         ` Jaroslav Kysela
2003-06-16 11:19           ` Jaroslav Kysela
2003-06-16 12:01             ` Paul Davis
2003-06-16 15:28             ` David Olofson [this message]
2003-06-16 16:03               ` Jaroslav Kysela
2003-06-16 16:28                 ` Paul Davis
2003-06-18 13:41                 ` David Olofson
2003-06-16 15:31             ` Joern Nettingsmeier
2003-06-16 15:46             ` Joern Nettingsmeier
2003-06-16 16:04               ` Jaroslav Kysela
2003-06-19  9:17                 ` Joern Nettingsmeier
2003-06-15 18:59 ` Paul Davis
2003-06-16  7:59   ` Joern Nettingsmeier
2003-06-16 12:03     ` Paul Davis

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=200306161728.07531.david@olofson.net \
    --to=david@olofson.net \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.