lilypond-devel
[Top][All Lists]
Advanced

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

128th note flags not supported?


From: Trevor Bača
Subject: 128th note flags not supported?
Date: Sat, 29 Jul 2006 17:07:37 -0500

Hi,

Are 128th note flags not supported?

Five beams draw correctly here.

%%% WORKS %%%

\version "2.9.13"

\new Staff {
  c''128[
  c''128
  c''128
  c''128]
}

%%% END %%%


The interpreter grumbles and no flags draw here.

%%% NO FLAGS, JUST STEMS %%%

\version "2.9.13"

\new Staff {
  c''128
  c''128
  c''128
  c''128
}

%%% END %%%


GNU LilyPond 2.9.13
Processing `266.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
266.ly:7:8: warning: flag `d7' not found

       c''128
266.ly:6:8: warning: flag `d7' not found

       c''128
266.ly:5:8: warning: flag `d7' not found

       c''128
266.ly:4:8: warning: flag `d7' not found

       c''128
Calculating line breaks... [2]
Drawing systems...
266.ly:4:8: warning: flag `d7' not found

       c''128
266.ly:5:8: warning: flag `d7' not found

       c''128
266.ly:6:8: warning: flag `d7' not found

       c''128
266.ly:7:8: warning: flag `d7' not found

       c''128
266.ly:7:8: warning: flag `d7' not found

       c''128
266.ly:5:8: warning: flag `d7' not found

       c''128
266.ly:6:8: warning: flag `d7' not found

       c''128
266.ly:4:8: warning: flag `d7' not found

       c''128
Calculating page breaks...
Layout output to `266.ps'...


Note that here we get warnings, but that in the full piece where I
first noticed these errors in the wild there were enough unbeamed
128ths to crash lily entirely. Here's the output before the crash (the
last of which I'm sure are ghostscript).

g'128
1550.ly:5050:0: warning: flag `u7' not found

g''128
1550.ly:2982:0: warning: flag `u7' not found

a''128 Error: /undefinedfilename in (1550.ps)
Operand stack:

Execution stack:
  %interp_exit   .runexec2   --nostringval--   --nostringval--
--nostringval--   2   %stopped_push   --nostringval--
--nostringval--   --nostringval--   false   1   %stopped_push
Dictionary stack:
  --dict:1122/1686(ro)(G)--   --dict:0/20(G)--   --dict:70/200(L)--
Current allocation mode is local
Last OS error: 2


As a workaround I can just beam the 128ths in question, which works
fine for the current piece. But just for the record we should avoid
unbeamed 128ths?



--
Trevor Bača
address@hidden
... like the dew, or like lightning ...

reply via email to

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