Re: [Denemo-devel] MIDI events for shortcuts

[Andreas Schneider]

I see, thank you. Now that I know how it works, I can see the MIDI
messages. I can translate the numbers to hexadecimal with a calculator.
But with my sparse scheme skills, one large number is not easy to handle
. You offered to extend d-GetMidi to return a list of bytes. That would
make things much easier (though I need to learn how to handle several
return values).

I will try to write some scheme filter next weekend, using AngryDelete
as a template. In this context, I have another question: What is the
scheme command to toggle the link to the MIDI keyboard (what the caps
lock key does)? Will it work to use it, as I don't know if the message
to turn the link back on will be received? Maybe it is better to
implement the keyboard link functionality in the scheme filter directly,
i.e. set a variable whether to evaluate the MIDI messages or not (and
wait for the "turn the link back on" message).

Andreas


Am 30.09.2014 um 20:21 schrieb Richard Shann:
> On Tue, 2014-09-30 at 19:33 +0200, Andreas Schneider wrote:
>> Thank you for your help. Now I have some time to test a bit. I have been
>> running the disp debug scheme you provided with "execute script" and got
>> reasonable results for a few times, but now I only get a message box
>> saying "Not exiting the previous MIDI capture loop". What am I doing
>> wrong?
> There is a call
> (d-PutMidi 0)
> which is treated as a re-set for MIDI capture. The details are not at my
> fingertips (you will see command this under Input->MIDI->MIDI filter
> off).
> 
> 
>>  Can the scheme be triggered every time Denemo gets a MIDI event?
> 
> It is triggered by the first MIDI event after d-GetMidi, and so a loop
> doing that effectively captures all MIDI events.
> Hmm, that is a strange way of saying that the scheme code following
> (d-GetMidi) is triggered once a MIDI event is received. You can think of
> the call (d-GetMidi) as "hanging" until a MIDI event is received. If you
> tried to execute the same call (d-GetMidi) while this was going on, you
> should get that message box popping up. In which case click on
> Input->MIDI->MIDI filter off to clear the blockage.
> 
> I think there may well be something to winkle out in this code (it is
> rather ancient) and I will be very happy to do this. If you can send me
> your code I will be glad to look at it. (I might have to simulate MIDI
> events coming in on other channels than 0, but that won't be difficult -
> send me a description of the MIDI bytes that you are sending from your
> controller).
> 
> Richard