On Thu 22 Jun 2017 at 17:10:56 (-0700), tisimst wrote:
> My experience tells me that although the staff-size is larger in the second
> \bookpart, the horizontal treatment isn't going to be a normal 17pt. It
> will still be more like the 15pt global one. The only way I've found to get
> true horizo
Peter,
On Wed, Jun 21, 2017 at 5:14 PM, Peter Crighton [via Lilypond] <
ml+s1069038n203959...@n5.nabble.com> wrote:
> I need some bookparts to use a different staff size than the rest of a
> book, thus the usage of layout-set-staff-size. This resets the afore
> defined fonts and I cannot seem to
N. Andrew
Under
http://lilypond.org/doc/v2.18/Documentation/notation/figured-bass
scroll down to “continuation lines.”
Mark
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of N. Andrew Walsh
Sent: Thursday, June 22, 2017 10:57 AM
To: lilypond
On 22.06.2017 23:06, Maxime's Music wrote:
Hi all,
Sorry if this is glaringly obvious, but when using convertly it
updates "\cresc" to "\deprecatedcresc". Could someone tell me what I'm
supposed to use instead. The documentation still lists "\cresc".
The code for \deprecatedcresc is here:
<
Hi all,
Sorry if this is glaringly obvious, but when using convertly it updates
"\cresc" to "\deprecatedcresc". Could someone tell me what I'm supposed to
use instead. The documentation still lists "\cresc".
All the best,
Craig
___
lilypond-user mailin
Thanks Harm, I'll package it up for you today.
On Fri, 23 Jun 2017 at 5:24 am, Thomas Morley
wrote:
> 2017-06-22 6:27 GMT+02:00 Maxime's Music :
> > Hi Lilyponders,
> >
> > I've been working on a very big score, adding staves one at a time.
> > There are 34 staves, and the PDF is 107 pages long.
2017-06-22 6:27 GMT+02:00 Maxime's Music :
> Hi Lilyponders,
>
> I've been working on a very big score, adding staves one at a time.
> There are 34 staves, and the PDF is 107 pages long. When I add in either of
> the final two staves I get this error message:
>
>
> lilypond(43147,0xa70c91c0) malloc
"Maxime's Music" writes:
> Hi,
>
> I'm on a Mac Sierra 10.12.5, Lilypond 2.19.36
> It has 8GB of RAM but when engraving my score Lilypond is using almost 3GB.
> When it gets close to the 3GB point is when it crashes and I get the malloc
> error. Could it be simply that I don't have enough RAM?
M
Hi,
I'm on a Mac Sierra 10.12.5, Lilypond 2.19.36
It has 8GB of RAM but when engraving my score Lilypond is using almost 3GB.
When it gets close to the 3GB point is when it crashes and I get the malloc
error. Could it be simply that I don't have enough RAM?
Craig
On Thu, 22 Jun 2017 at 7:14 pm,
Hi List,
I can't seem to find how to do what I imagined would be a fairly simple
thing to code. I have a figured bass sequence that looks like this in the
original:
4 #
2
7 8
It's fairly obvious from the layout that the 4 goes to a major 3rd, the 7
goes to an octave, and the 2 dr
On Fri 23 Jun 2017 at 01:12:12 (+1000), Andrew Bernard wrote:
> But this is in the NR in the section on bar numbers, is it not?
>
> \relative c' {
> \set Score.currentBarNumber = #111
> \override Score.BarNumber.break-visibility = #all-visible
> % Increase the size of the bar number by 2
>
I have checked the NR
http://lilypond.org/doc/v2.18/Documentation/notation/bars . Indeed,
there is not any problem, as long as you do not use chord names.
May be, there is another chapter in the NR concerning this case of
interfering with chord names? If any please point me to that. Thanks.
BB
Hello BB,
But this is in the NR in the section on bar numbers, is it not?
Andrew
==
\relative c' {
\set Score.currentBarNumber = #111
\override Score.BarNumber.break-visibility = #all-visible
% Increase the size of the bar number by 2
\override Score.BarNumber.font-size = #2
% Print a
The bar number is just above the 7 of the fis2:min7 and makes the chord
name unclear.
How can I avoid this? How can I generally (always) set the bar number
directly above the bar line by default?
Snippet:
\version "2.18.2"
melody = { \override Score.BarNumber.break-visibility = ##(#t #t #t)
\t
Hi Craig,
Version number and platform?
I have very large, very complex scores of similar length (100 pages +) that
compile with no problem (but keyboard music so perhaps considerably fewer
staves).
Andrew
On 22 June 2017 at 14:27, Maxime's Music wrote:
> Hi Lilyponders,
>
> I've been working
15 matches
Mail list logo
