[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
A tricky example -- polyMETER against polyRHYTHM
From: |
mclaren |
Subject: |
A tricky example -- polyMETER against polyRHYTHM |
Date: |
Wed, 2 Nov 2016 22:52:12 -0700 (MST) |
Took some skull sweat to figure this one out. But someone may get a kick out
of it.
What I wanted to do was to set up two polymeters (different accent patterns)
with a shifting polymeter against 'em.
Here's a png image of the score: http://i.imgur.com/RtYUgRR.png
<http://i.imgur.com/RtYUgRR.png>
Here's the Lilypond code:
\version "2.18.2"
\header {
tagline = "" % removed
}
% Lilypond bug #1 -- placing the \paper command anywhere else fails to
% produce the desired output, but placing it here generates an EXITED WITH
% ERROR CODE 1 message even though the score output looks correct and is
% as desired.
\layout {
\paper {#(set-default-paper-size "a4" 'landscape)}
indent=0
\context {
\Score
\accepts "TimeLine"
\remove "Timing_translator"
\remove "Default_bar_line_engraver"
}
\context {
\Staff
\consists "Timing_translator"
\consists "Default_bar_line_engraver"
\consists "Time_signature_engraver"
}
% End of code.
}
{
<<
\new Staff { \clef "treble"
\relative c'''
{
\time 9/8
{ c8-> d f e-> b c d16-> f e8 b}
\time 8/8
{c8[-> d16 f e8 b] c16[-> d f8 e b]}
\time 9/8
{ c8[-> d f] e[-> b16 c d8] f[-> e b16 c]}
\time 8/8
{e8[-> b16 c d8 f] e[-> b16 c d8 f]}
\time 9/8
{ d8-> b c a-> b g e16-> f g8 d}
\time 8/8
{c8[-> d16 f e8 f] e16[-> g a8 b a]}
\time 9/8
{ g8[-> f d'] e[-> g16 c, d8] g,[-> a b16 c]}
\time 8/8
{a8[-> b16 c d8 e] g[-> f16 e f8 d]}
}
}
\new Staff { \clef "treble"
\relative c'
{
\time 8/8
{e8[-> b c d16 f] e8[-> b c d16 f]}
\time 9/8
{e8[-> b c16 d] f8[-> e b] c[-> d f]}
\time 8/8
{e8[-> b16 c d8 f] e[-> b16 c d8 f]}
\time 9/8
{ e16[-> b c8 d] f[-> e b] c[-> d f16 e]}
}
\relative c'
{
\time 8/8
{e8[-> b c d16 f] e8[-> b c d16 f]}
\time 9/8
{g8[-> a c16 d] e8[-> a, b] g[-> b c]}
\time 8/8
{b8[-> c16 a d8 g] f[-> c16 b a8 f]}
\time 9/8
{ e16[-> b c8 d] f[-> e b] c[-> d f16 e]}
}
}
\new Staff { \clef "bass"
\relative c
{
\time 11/8
\once \omit TupletNumber
\set Timing.measureLength = #(ly:make-moment 8/8)
\tuplet 11/8 { g8[-> e' b c d f e b16 c d8 f e]}
%\scaleDurations 8/11 { f8[-> e b c d f e b16 c d8 f e]}
|
\override TupletNumber #'text = #tuplet-number::calc-fraction-text
\set Timing.measureLength = #(ly:make-moment 9/8)
\tuplet 11/9 { b16[-> c d8 f e16 b c8 d f e d f g]}
|
\once \omit TupletNumber
\set Timing.measureLength = #(ly:make-moment 8/8)
\tuplet 11/8 { f8[-> e b c d f e b16 c d8 f e]}
\override TupletNumber #'text = #tuplet-number::calc-fraction-text
\set Timing.measureLength = #(ly:make-moment 9/8)
\tuplet 11/9 { e8[-> b c d16 f e8 b c d16 f e8 b c16 d]}
\bar "|"
\break
\time 11/8
\once \omit TupletNumber
\set Timing.measureLength = #(ly:make-moment 8/8)
\tuplet 11/8 { c8[-> b d b a g f c16 b e8 g f]}
%\scaleDurations 8/11 { f8[-> e b c d f e b16 c d8 f e]}
|
\override TupletNumber #'text = #tuplet-number::calc-fraction-text
\set Timing.measureLength = #(ly:make-moment 9/8)
\tuplet 11/9 { e16[-> c e8 d a'16 b c8 e g f a g b]}
%\scaleDurations 11/8 { b16[-> c d8 f e16 b c8 d f e d f g]}
|
\once \omit TupletNumber
\set Timing.measureLength = #(ly:make-moment 8/8)
\tuplet 11/8 { c8[-> e, a f g f e c16 d b8 c g]}
\override TupletNumber #'text = #tuplet-number::calc-fraction-text
\set Timing.measureLength = #(ly:make-moment 9/8)
\tuplet 11/9 { e8[-> b c d16 f e8 b c d16 f e8 b c16 d]}
\bar "|"
\break
}
}
>>
}
===========
Incidentally, I seem to be getting a bug, and it's an odd one. If you try
to compile this Lilypond score from scratch, you get an exit with ERROR=1.
Then if you comment out the lines
\layout {
\paper {#(set-default-paper-size "a4" 'landscape)}
indent=0
and recompile, the score runs fine. Here's where it gets weird... If you
then immediately uncomment out those 3 lines, you still get an exit with
ERROR=1, but this time the score gets engraved properly in landscape mode.
Can't figure this one out. What am I doing wrong with setting landscape
mode?
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/A-tricky-example-polyMETER-against-polyRHYTHM-tp196030.html
Sent from the User mailing list archive at Nabble.com.
- A tricky example -- polyMETER against polyRHYTHM,
mclaren <=
Re: A tricky example -- polyMETER against polyRHYTHM, David Wright, 2016/11/03