[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
midi performance hacking
From: |
Michael Welsh Duggan |
Subject: |
midi performance hacking |
Date: |
Mon, 19 Apr 2004 01:28:06 -0400 |
User-agent: |
Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux) |
The included file demonstrates one of the things I want to do on a
general basis: to be able to determine at what context levels midi
tracks are aggregated upon.
It would be nice if this were less tortuous, and didn't require
making a new type of Staff. Can anyone think of a good way to do
this? (Doesn't necessarily have to be possible in current LilyPond.
Something which makes good sense which could be implemented would be
just fine. Of course, I am volunteering to help with
implementation.)
\include "english.ly"
\version "2.2.3"
\score {
<<
\new StaffTrack \notes a'1
\new PianoStaff
<<
\new Staff \notes a'
\new Staff \notes {\clef bass a}
>>
>>
\paper { raggedright = ##t }
\midi {
\context {
\ScoreContext
\accepts StaffTrack
}
\context {
\name StaffTrack
\accepts Voice
\type "Staff_performer"
\consists "Key_performer"
\consists "Tempo_performer"
\consists "Time_signature_performer"
}
\context {
\StaffContext
\type "Performer_group_performer"
\remove "Key_performer"
\remove "Tempo_performer"
\remove "Time_signature_performer"
}
\context {
\PianoStaffContext
\type "Staff_performer"
\consists "Key_performer"
\consists "Tempo_performer"
\consists "Time_signature_performer"
}
}
}
--
Michael Welsh Duggan
(address@hidden)
- midi performance hacking,
Michael Welsh Duggan <=