[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] Jackmidi Status?

From: Jeremiah Benham
Subject: Re: [Denemo-devel] Jackmidi Status?
Date: Thu, 24 Sep 2009 10:21:06 -0500

On Wed, 2009-09-23 at 10:12 +0100, Richard Shann wrote:

>  Another point about the passing strings convention: I dislike those
> NULL separated strings appearing in the scripts. On the other hand, a
> haphazard collection of different types of parameters, which would then
> require a whole apparatus of documentation seems unattractive.
> Anybody any thoughts on this?

Strings are fine with me. Is space separation fine? Like 
(d-OutputMIDI "0x90" "0x3c" "0x40")
I think some midi messages are 4 byte. I am not sure which ones off the
top of my head though. I think we can start with three and if there is a
demand for 4 byte we can add that. Perhaps d-OutputMIDI can take an
optional 4th byte. 

for d-PlayNote we could do (d-PlayNote "0x3c"). This would use the
selected staffs channel/volume etc.. If the user wanted to change that
they would use a different script to change the staff properties. So if
they wanted to play a note on every channel they would do something

(d-StaffPropertiesMidiChannel "2")
(d-PlayNote "0x3c") 

This can be placed in a loop or whatever. We can also have maybe a more
complicated (d-PlayNote "notenum" "duration"). 

I also wonder if it would be better for complicated things like
StaffProperties if we used regex or something that way it looks like

(d-StafProperties "midi_channel=1 midi_volume=127") 
Then all the other values are left alone. Perhaps something like:

(d-StaffProperties "help") 
can list variables to set. 

Sorry I am just kind of brainstorming here. 


> Richard
> _______________________________________________
> Denemo-devel mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]