Re: dynamic/beam/stem/tuplet number/tuplet number collisions

[James]

Hello,

On 24 March 2012 06:57, Jeffrey Trevino  wrote:
> Hi there,
>
> I'm rendering some dense notation, and there are lots of collisions between
> beams, stems, dynamics, tuplet numbers, and tuplet brackets. I'd like to be
> sure I'm aware of best practices with two questions:
>
> 1) What are the global actions I should take to keep this from happening
> upon render (I think there's something called "padding" for most of the
> grobs, according to the online documentation? Perhaps the order the things
> are engraved?)?

Yes you can use padding, however LilyPond should do most collision
avoidance out of the box. I'd also recommend making sure you are on at
least 2.14.2 - the latest stable and if possible try the latest dev
release (2.15.34) as there have been many improvements on layout since
then. If you are using 2.12.x you'd just be making more work for
yourself unnecessarily.

It is possible to have both dev and stable releases installed on a
system (with Windows, it is just a case of renaming the LilyPond dir
that is installed in 'Programs', ditto mac (just rename the .app) and
flick between the two types.

You don't give any tiny examples so it is hard to say if you want to
add 'padding' or not, and to what grob/glyph etc.

Give us a chance to 'see' your problem. Perhaps even just a small screenshot.

>
> 2) Failing #1, what are the best ways to solve these problems by locally
> moving these things around via position overrides after I see my mangled
> output?

Yes again that is possible, but really, unless you are hitting known bugs

http://code.google.com/p/lilypond/issues/list

It should just work(tm).

To be honest, I'd say these questions are too broad o give anything
other than 'possibly', 'maybe', 'it depends' or 'could do' answers,
and you'd do well to give us an 'idea' of specifics - without filling
the list with a hundred line .ly file.

I'd say the most common question we get from beginners about 'dense'
and 'colliding' things are either because of known bugs (which will
need overrides and tweaks) or because of incorrect usage of multiple
voices in the same staff.

For example NOT using explicit voices but trying to use < .. >
constructions or << // >> constructions with \xxxUp \xxxDown type
commands peppered all over.

Sorry I cannot give you more explicit instructions, but if you find
yourself having to make more and more overrides starting out, you may
not as I think you are guessing, be 'thinking in LilyPondese'.

James

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Fine with dashed double barline occurring in middle of bar

[Nick Payne]

I'm setting a short piece by Julio Sagreras that has a Fine with dashed 
double line in the middle of a bar. At the moment I'm duplicating the 
dashed with a postscript hack, because from reading the documentation I 
could only see a single dashed barline as available. Is it possible to 
get a dashed double barline?


\version "2.15.32"

% postscript dashed vertical double line
#(define dashedbar "0.1 setlinewidth [0.62 0.2] 0 setdash -0.3 -2.95 
moveto 0 -4 rlineto stroke

0 -2.95 moveto 0 -4 rlineto stroke")

\relative c'' {
<<
{ 4-\tweak #'extra-offset #'(0.8 . 0)^\markup\large {
\concat { "Fine" \postscript #dashedbar } } r e4. dis8 }
\\
{ e,,4 r r2 }
>>
}

The piece is the last of the three in the IMSLP scan here: 
http://imslp.org/wiki/3_Piezas_f%C3%A1ciles,_Op.19_(Sagreras,_Julio_Salvador) 



Nick
<><>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Need to suppress bar number checking in midi block

[Michael Ellis]

The NR advises using \unfoldRepeats to produce a midi file that plays
all the repeats.  I use a lot of \barNumberChecks in my work because
it saves time spotting errors.  In pieces with repeats, this produces
many "Barcheck failed" warnings.  Is there a way to suppress bar
checking within the midi score block?

% Tiny example
mymusic = {
   \time 4/4
   \repeat volta 2 {
 g'1
      \barNumberCheck #2
   }
   c'1
   \barNumberCheck #3
}

\book {
  \score {
     \mymusic
     \layout {}
  }
  \score {
     % Causes "Barcheck failed" warnings
     \unfoldRepeats \mymusic
     \midi {}
  }
}

\version "2.14.1"

Thanks,
Mike


unfold.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Programming error: vertical alignment called before line breaking

[J Ruiz]

I'm running v2.14.2.
 
My multi-page book .ly is growing quite complex, pulling several "include" .ily 
files, where I've segregated individual scores.
However, most included .ily's don't compile separately, as many functions I 
reuse are only defined in the main .ly file.
 
A side-effect of this approach is that Lilypond's compile errors are 
increasingly difficult to trace and decypher when the error is sourced in the 
\include sub-files.  If I make a syntax error (i.e. missing bracket or what 
have you), what I typically get now is a failed compile run, where Lilypond 
stops compiling before generating .pdf, and no error msg is thrown.
 
I just discovered the following error listed in the compilation output, which I 
neglected to notice earlier, and now I can't figure out which of the last 3-5 
.ily files I've added, may be causing it.  It compiles and the output seems OK, 
but I'd still like to fix my code to avoid this error and potential future 
troubles.
 
If anyone has a tip for me of specific commands that may be involved in this 
error, I'd appreciate the help.
 

Calculating line breaks...
Drawing systems...
Interpreting music...
Preprocessing graphical objects...
programming error: vertical alignment called before line breaking
continuing, cross fingers
Calculating line breaks...
Drawing systems...
.

Javier Ruiz-Alma___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need to suppress bar number checking in midi block

[Nick Payne]

On 25/03/12 10:31, Michael Ellis wrote:

mymusic = {
\time 4/4
\repeat volta 2 {
  g'1
   \barNumberCheck #2
}
c'1
\barNumberCheck #3
}


Use the "|" character instead for barchecks:

mymusic = {
   \time 4/4
   \repeat volta 2 {
g'1 |
   }
   c'1 |
}



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Font size setting explanation is a bit misleading in documentation

[Nick Payne]

In the text formatting documentation at 
http://lilypond.org/doc/v2.15/Documentation/notation/formatting-text, 
when talking about the size of characters, the phrasing at one point is: 
"the font size can be set to an absolute value with \fontsize". Maybe 
this should be changed to something like "the font size can be set to an 
particular numeric value with \fontsize", as \fontsize is still relative 
to the staff size, and the size of the font will change if the staff 
size changes.


Rather strangely, \abs-fontsize, which does set the absolute size of the 
font without regard to the staff size, doesn't get a mention in this 
section, but only in s.A.9.1.


Nick

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user