Re: [LAU] midi control of seq24

On Mon, Dec 14, 2009 at 10:35 PM, Josh Lawrence wrote:
> On Thu, Dec 10, 2009 at 3:32 PM, Gabriel M. Beddingfield wrote:
>> He explains it in the next paragraph or six:
>
> ok, I've spent the weekend reading the file, and I still can't get it.
>  I can't tell if you're being snarky in your response or not, so I'll
> go ahead and admit that I'm having trouble understanding what I'm
> supposed to do and how I'm supposed to do it, and fully admit that
> it's probably my fault.  that being said...
>
>> It does.  That's what all this is configuring.
>>
>> -gabriel
>
> I guess what I can't understand is:
>
> 1. the SEQ24 file does not specify what message should be sent to
> control these things.  is there a preference for how these messages
> should be formed?  maybe someone could send their .rc file as an
> example, it sure would help me.
>

.seq24.rc is a template, it contains no default
assignments, only zeros.

You could copy-paste and adapt the
examples given in the SEQ24 file.

> 2. aseqdump gave me a textual representation of what was coming from
> my keyboard, and it looked nothing like what is in the SEQ24 file
> (i.e. [0 0 0 0 0 0] ).  I must be missing some obvious part of the
> translation here...can someone point out the missing pieces for me?
>

Three filters on each line:
[toggle] [on] [off]

The six numbers in each pare of brackets represent a filter:
[0 0 0 0 0 0]

According to the SEQ24 file, these numbers mean:
[(on/off) (inverse) (midi status byte (channel ignored))
(data1) (data2 min) (data2 max)].
Well, truly a little cryptic.
i.e.:
(on/off)
    disable/enable the filter by setting this to 0/1

(inverse)
    well - invert filter (somehow)

    if set to 1 it makes values outside the specified
    min-max range revert the action.
    The range is then a condition for _being_ on/of instead
    of for _setting_ on/of. I've never tried this with toggle
    though.

(midi status byte (channel ignored))
    the midi status byte, in decimals.
    look here for the full list:
    http://www.midi.org/techspecs/midimessages.php#2

    as the channel is ignored, it is sufficient
    to just use the values from one channel,
    e.g. channel 1:

    128/129 for any note on/note off event
    160 polyphonic aftertouch
    176 controller event
    192 program change
    208 aftertouch
    224 pitch wheel

(data1)

    corresponds to the third column, labelled
    '2nd byte' in the above linked list.

    use it to e.g enter the note number or controller
    number as displayed by aseqdump.

(data2 min) and (data2 max)
    specify the range of the 3rd byte value

best,
d
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
Received on Tue Dec 15 08:15:01 2009