From: "Keith A. Milner" <maillist@superlative.org>
To: alsa-devel@alsa-project.org
Cc: Ember Autumn Rose Leona <emberleona@gmail.com>
Subject: Re: Help with editing the Raw Midi data with ALSA?
Date: Fri, 06 Sep 2013 23:08:17 +0100 [thread overview]
Message-ID: <4431902.sYuv2gyIvb@kamdesktop> (raw)
In-Reply-To: <CAAVa-AFWJwBAYK2ix643bEVVraG0FkaEO-ovhfrYPZSSU53vdQ@mail.gmail.com>
On Friday 06 Sep 2013 11:02:19 Ember Autumn Rose Leona wrote:
> Dear ALSA team,
>
> I just joined the mailing list on after being referred to it.
I actually think this is the wrong place. Alsa-user might be more appropriate
as you are probably talking about a program which uses the ALSA APIs, rather
than developments to ALSA itself, which is what this list is for.
https://lists.sourceforge.net/lists/listinfo/alsa-user
Despite being off-topic, I will try to give some guidance.
>
> Is it possible for me to edit the Raw Midi data with ALSA... I looked
> a RtMidi and that opens a port but doesn't help me Midi Poison or Midi
> Message Map.
>
> What I want to do is edit the Midi Messages, re-mapping the notes. I simply
> want to flip the progression of the keys on a midi piano from high
> notes to low notes. On the fly. Basically I want to take the note on
> message byte and use the
> note number as an index for an array of remapped keys.
>
> I want to flip the keyboard on a D note for now... then later allow
> users to turn this remapping off and on (on the fly.) Also it would be
> nice to have certain note ranges mapped to different programs/patches.
>
It sounds like you want to receive note events from a MIDI IN interface (e.g.
from a keyboard) and want to transform them before pushing them out of a MIDI
OUT interface?
If so, I strongly recommend you consider looking at Jack Connection Kit for
this sort of application.
http://jackaudio.org/
Jack is a layer which sits over ALSA and provides, amongst other things,
flexible connections and routing for audio and midi data. It will give you a
lot of flexibility and allow you to connect your application to other
applications (e.g. virtual midi keyboards like VMPK, and sound generators like
Qsynth or Pianoteq).
If you aim to produce something that you will publish for other people to use
in audio production, Jack is really the standard that people will expect.
If you want a starting point, something like KMidimon, which works directly
with ALSA as well as via Jack, would give lots of useful example code:
http://kmidimon.sourceforge.net/
Cheers,
Keith
next prev parent reply other threads:[~2013-09-06 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 18:02 Help with editing the Raw Midi data with ALSA? Ember Autumn Rose Leona
2013-09-06 22:08 ` Keith A. Milner [this message]
2013-09-07 10:01 ` Clemens Ladisch
2013-09-09 1:24 ` Ember Autumn Rose Leona
2013-09-09 1:37 ` Ember Autumn Rose Leona
2013-09-09 8:21 ` Clemens Ladisch
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=4431902.sYuv2gyIvb@kamdesktop \
--to=maillist@superlative.org \
--cc=alsa-devel@alsa-project.org \
--cc=emberleona@gmail.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.