Re: Edition Engraver and \markLengthOn

[Craig Dabelstein]

Hi Jan-Peter,

You were exactly right. For the score I had to use:

\editionMod score 615 0/4 hallager.partI.Score \markLengthOn
\editionMod score 622 3/4 hallager.partI.Score \markLengthOff

But for an individual part:

\editionMod parts 615 0/4 hallager.partI.fluteI.Staff \markLengthOn
\editionMod parts 622 3/4 hallager.partI.fluteI.Staff \markLengthOff

Thanks for your help. All the best,

Craig


On Fri, 31 Aug 2018 at 01:19, Jan-Peter Voigt  wrote:

> Hi Craig,
>
> it should work. \markLengthOn just consists of some overrides, which are
> directed to the Score Context.
> So Maybe you should address the Score context with
> \editionMod parts 626 0/4 hallager.partIII.Score \markLengthOn
>
> or you use (I don't know your current setup, so this is a guess)
> \editionMod parts 626 0/4 hallager.partIII.clarinetI.Staff \markLengthOn
>
> because the overrides are directed to the Score context anyway.
>
> HTH
> Jan-Peter
>
> Am 29.08.2018 um 21:15 schrieb Craig Dabelstein:
> > Hi all,
> >
> > Can the EE be used to add \markLengthOn? Maybe I've got the context
> > wrong but the following line is having no effect:
> >
> > \editionMod parts 626 0/4 hallager.partIII.clarinetI.Score \markLengthOn
> >
> > Craig
> >
> >
> > --
> > *Craig Dabelstein*
> > Maxime's Music
> > craig.dabelst...@gmail.com 
> > /http://maximesmusic.com/
> >
> >
> > ___
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
> >
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>


-- 
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
*http://maximesmusic.com *
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Defining 4 \breve time in Carmina Burana

[Simon Albrecht]

Hi Andrew and David,

of course you are right, I misrepresented that and went too far – sorry.
A reengraving is no different from a photocopy in that you cannot give 
it to anybody or use it for performing, regardless whether parts of that 
may not be enforcible. But you can do whatever you want in your house, 
so to speak.


Best, Simon

On 05.09.2018 16:13, Andrew Bernard wrote:

Hi Simon,

That's not illegal at all anywhere in the world just so that other 
list members don't get the wrong impression. Selling multiple copies, 
i.e., making a derivative work, without permission or licence from the 
copyright holder would be. Similar to photocopying of complete works 
for study purposes.


a


On Wed, 5 Sep 2018 at 23:40, Simon Albrecht > wrote:



PS. I’d like to just mention that Carl Orff’s music is under
copyright
worldwide and retypesetting his music is illegal.



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



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

Re: cadenza when having multiple staffs

[Edmundo Carmona Antoranz]

Actually, it didn't take me long to test it. It's spot on. Thanks!
Will let you know when I upload it into its repo.
On Wed, Sep 5, 2018 at 4:18 PM Edmundo Carmona Antoranz
 wrote:
>
> Thanks for your feedback. Let me give it a try and will let you know
> how it went.
> On Wed, Sep 5, 2018 at 12:01 AM Andrew Bernard  
> wrote:
> >
> > Hi Aaron,
> >
> > My thoughts exactly.
> >
> > Andrew
> >
> >
> > On Wed, 5 Sep 2018 at 15:55, Aaron Hill  wrote:
> >>
> >>
> >> It is not a cadenza, per se, but rather an omission of tuplet numbering.
> >>   The piece seems to omit tuplet numbering in nearly all cases, rather
> >> relying solely on beaming groups to indicate the timing.
> >>
> > ___
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > https://lists.gnu.org/mailman/listinfo/lilypond-user

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

Re: cadenza when having multiple staffs

[Edmundo Carmona Antoranz]

Thanks for your feedback. Let me give it a try and will let you know
how it went.
On Wed, Sep 5, 2018 at 12:01 AM Andrew Bernard  wrote:
>
> Hi Aaron,
>
> My thoughts exactly.
>
> Andrew
>
>
> On Wed, 5 Sep 2018 at 15:55, Aaron Hill  wrote:
>>
>>
>> It is not a cadenza, per se, but rather an omission of tuplet numbering.
>>   The piece seems to omit tuplet numbering in nearly all cases, rather
>> relying solely on beaming groups to indicate the timing.
>>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

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

Re: Defining 4 \breve time in Carmina Burana

[Andrew Bernard]

Hi Simon,

That's not illegal at all anywhere in the world just so that other list
members don't get the wrong impression. Selling multiple copies, i.e.,
making a derivative work, without permission or licence from the copyright
holder would be. Similar to photocopying of complete works for study
purposes.

a


On Wed, 5 Sep 2018 at 23:40, Simon Albrecht  wrote:

>
> PS. I’d like to just mention that Carl Orff’s music is under copyright
> worldwide and retypesetting his music is illegal.
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Defining 4 \breve time in Carmina Burana

[David Kastrup]

Simon Albrecht  writes:

> On 05.09.2018 11:15, Jogchum Reitsma wrote:
>> The first bar of part 5: Ecce gratum, from Orff's Camina Burana
>> states a time of 4 \breve notes. In the Schott-edition I have, that
>> is noted not on the staff, but above it. 
>
> PS. I’d like to just mention that Carl Orff’s music is under copyright
> worldwide and retypesetting his music is illegal.

Uh, no?  _Redistributing_ typesettings of it may be, but what kind of
material you create for yourself from legally acquired copies is usually
entirely your own business in typical jurisdictions.

It's certainly not the typesetting that is problematic.  It just may
have less uses (without getting appropriate license) than one would wish
for.

-- 
David Kastrup

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

Re: Defining 4 \breve time in Carmina Burana

[Simon Albrecht]

On 05.09.2018 11:15, Jogchum Reitsma wrote:
The first bar of part 5: Ecce gratum, from Orff's Camina Burana states 
a time of 4 \breve notes. In the Schott-edition I have, that is noted 
not on the staff, but above it. 


PS. I’d like to just mention that Carl Orff’s music is under copyright 
worldwide and retypesetting his music is illegal.

Best, Simon

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

Re: Defining 4 \breve time in Carmina Burana

[Simon Albrecht]

To elaborate a little on David’s response:

On 05.09.2018 11:15, Jogchum Reitsma wrote:
The first bar of part 5: Ecce gratum, from Orff's Camina Burana states 
a time of 4 \breve notes. In the Schott-edition I have, that is noted 
not on the staff, but above it.


This would be replicated in LilyPond by \omit Staff.TimeSignature and 
creating custom markups for the time signatures, either as \mark or 
inside a special context (for example using the method in 
http://lsr.di.unimi.it/LSR/Item?id=1010).


Is there a possiblility in Lilypond to define that time? Simpy issuing 
"time 4/\breve" gives an error message in version 2.19.65 


This is because a duration isn’t the same as any number to LilyPond; 
specifically the \time command expects to be given a fraction (of 
numbers) (that is then internally represented as a Scheme pair). 
Technically, this would be 4/(1/2) in your case, but that isn’t 
supported by Lily, so you have to use 8/1. I have to say, it would be 
kind of cool to write


\version "2.19.82"
{ \time #'(4 . 1/2) \breve \breve \longa }

but that’s not how it works ;-)

Best, Simon

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

Re: Edition Engraver and staff changes

[Jan-Peter Voigt]

Am 05.09.2018 um 15:01 schrieb Urs Liska:
> 
> 
> Am 5. September 2018 14:27:06 MESZ schrieb Simon Albrecht 
> :
>> On 15.08.2018 07:50, Jan-Peter Voigt wrote:
>>> yes you are right, \change Staff cannot be used with the EE. Some
>> time
>>> ago I tried to make it possible, but it results in a fatal crash of
>>> lilypond if the EE sends such an event. I add this to the issues.
>>
>> Maybe with a minimal example this should also be added 
> 
> Yes.
> 
>> to the LilyPond 
>> issue tracker?
> 
> No, here: https://GitHub com/openlilylib/edition-engraver/issues
https://github.com/openlilylib/edition-engraver/issues/24

But still it might be added to the lilypond issue tracker because it is
a reproducible crash not dependent of the EE.

Jan-Peter


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

Re: Defining 4 \breve time in Carmina Burana

[David Kastrup]

Jogchum Reitsma  writes:

> Hi,
>
> The first bar of part 5: Ecce gratum, from Orff's Camina Burana states
> a time of 4 \breve notes. In the Schott-edition I have, that is noted
> not on the staff, but above it.
>
> Is there a possiblility in Lilypond to define that time? Simpy issuing
> "time 4/\breve" gives an error message in version 2.19.65

Well, you can fudge your own stuff, like

\new Staff
{
  \tweak stencil #(lambda (grob)
   (grob-interpret-markup grob
#{ \markup \vcenter \fraction \number "4" \note { \breve } 
#UP #}))
  \time 8/1
  c'\breve \breve \breve \breve
}

Basically, provide your own visuals.

-- 
David Kastrup

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

Re: Edition Engraver and staff changes

[Urs Liska]

Am 5. September 2018 14:27:06 MESZ schrieb Simon Albrecht 
:
>On 15.08.2018 07:50, Jan-Peter Voigt wrote:
>> yes you are right, \change Staff cannot be used with the EE. Some
>time
>> ago I tried to make it possible, but it results in a fatal crash of
>> lilypond if the EE sends such an event. I add this to the issues.
>
>Maybe with a minimal example this should also be added 

Yes.

> to the LilyPond 
>issue tracker?

No, here: https://GitHub com/openlilylib/edition-engraver/issues

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

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

Re: Accidentals and Ledger Lines

[Malte Meyn]

[Forwarding to bug-lilypond]

Hi foxfanfare,

Am 05.09.18 um 11:07 schrieb foxfanfare:

As you can see, the ledger line of the note containing the accidental is
shortned as expected, but the other aren't and you can see here the natural
appears too close.


that’s true, neighbouring ledger lines should be shortened in some 
cases. LilyPond’s documentation advertises the ledger line shortening 
(http://lilypond.org/doc/v2.18/Documentation/essay/engraving-details#ledger-lines), 
IMHO that’s a good reason why it should really work ;)



I can fix this by moving the accidental with \once \override
Accidental.X-offset = #-1.25, see:

accidentals2.JPG


But this tweak has to be done every time... My question is: is it possible
to add more padding between ledger lines and accidentals? I tried many
combinations but nothing worked so far...


Of course you could use \override instead of \once \override but of 
course that’s not optimal, therefore I’m forwarding this to the bug 
list. The following code shows in which cases also a neighbouring ledger 
line should be shortened and where there are ledger lines that are 
shortened but shouldn’t be.


%
\version "2.19.82"
<<
  \new Staff \relative c''' {
\set Score.extraNatural = ##f
ceses feses % feses: no need for shortening
ceseh feseh % feseh: no need for shortening
ces fes % fes:   no need for shortening
ceh feh % ok
c! f!   % both: more shortening needed
cih fih % ok
cis fis % ok
cisih fisih % ok
cisis fisis % ok
  }
  \new Staff \relative {
aeses eeses % ok
aeseh eeseh % ok
as es   % ok
aeh eeh % both:  more shortening needed
a! e!   % a: more shortening needed
aih eih % aih:   more shortening needed
ais eis % ais:   more shortening needed
aisih eisih % aisih: more shortening needed
aisis eisis % ok
  }
>>
%

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

Defining 4 \breve time in Carmina Burana

[Jogchum Reitsma]

Hi,

The first bar of part 5: Ecce gratum, from Orff's Camina Burana states a 
time of 4 \breve notes. In the Schott-edition I have, that is noted not 
on the staff, but above it.


Is there a possiblility in Lilypond to define that time? Simpy issuing 
"time 4/\breve" gives an error message in version 2.19.65



regards, Jogchum Reitsma


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

Re: Edition Engraver and staff changes

[Simon Albrecht]

On 15.08.2018 07:50, Jan-Peter Voigt wrote:

yes you are right, \change Staff cannot be used with the EE. Some time
ago I tried to make it possible, but it results in a fatal crash of
lilypond if the EE sends such an event. I add this to the issues.


Maybe with a minimal example this should also be added to the LilyPond 
issue tracker?


Best, Simon

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

Re: Lilypond website down?

[Simon Albrecht]

On 16.08.2018 23:37, Han-Wen Nienhuys wrote:
Well, currently, it's coming out of the $300 new user credit that 
Google offers to new cloud users. $300 is enough to keep it running 
for a year or two.


This sounds slightly dangerous and like we should search for a new 
solution rather sooner than later, doesn’t it?


Best, Simon




On Fri, Aug 10, 2018 at 9:20 PM Ralph Palmer 
mailto:palmer.r.vio...@gmail.com>> wrote:




On Fri, Aug 10, 2018 at 3:14 PM Simon Albrecht
mailto:simon.albre...@mail.de>> wrote:

So you provide the funding? If so, thanks a lot!

Best, Simon

Please accept my thanks, as well.

Ralph


> On 10.08.2018 - 13:10, Han-Wen Nienhuys wrote:
>
>
> Looks like a payment problem. I've added my creditcard, and
restarted the server.
>>
>>
>> On Wed, Aug 8, 2018 at 9:39 PM Phil Holmes
mailto:m...@philholmes.net>> wrote:
>>
>> It's hosted by Google these days, so I assume they have a
means of monitoring and fixing this...
>>
>>
>> --
>> Phil Holmes
>>
>>
>>
>>
>>
>> - Original Message -
>>
>> From: Saul Tobin
>>
>> To: Lilypond-User Mailing List
>>
>> Sent: Wednesday, August 08, 2018 6:37 PM
>>
>> Subject: Lilypond website down?
>>
>>
>> Looks like Lilypond.org has been down since yesterday.
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org 
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>>
>>
>> --
>>
>> Han-Wen Nienhuys - hanw...@gmail.com
 - http://www.xs4all.nl/~hanwen

>

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



-- 
Ralph Palmer

Brattleboro, VT
USA
palmer.r.vio...@gmail.com 



--
Han-Wen Nienhuys - hanw...@gmail.com  - 
http://www.xs4all.nl/~hanwen 



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



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

Re: how to whiteout an ottava bracket

[Simon Albrecht]

On 21.08.2018 19:13, Pierre Perol-Schneider wrote:

As you can see, a stem whiteout would also affect staff and beam.


This I have to correct: normally, one can always find an arrangement so 
that the whiteout affects exactly those parts you want it to. In this case:


\version "2.19.82"
rD = { \change Staff = right \stemDown }
lU = { \change Staff = left \stemUp }
right = \relative b {
  \ottava 2 b8 \lU
  \once\override Stem.layer = -1
  \once\override Stem.whiteout = #1
  a, \rD b' \lU g, \rD b' \lU f, \rD b' \lU e,,
}
left = {
  \override Staff.OttavaBracket.layer = #-2
  \ottava #1
  $(skip-of-length right)
}
\score {
\new PianoStaff
  <<
    \new Staff= "right" { \right }
    \new Staff = "left" { \left } >>
}

I use the development version because apparently the 2.18.2 
implementation of whiteout doesn’t work in this case.


Best, Simon

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

Re: LilyPond 2.19.82 and Fedora 28: exit code 6

[Davide Liessi]

2018-09-05 13:22 GMT+02:00 David Kastrup :
> The \tempo does
> not actually appear, though.

Indeed.

> So which architecture and GCC version are we talking about in your case?

$ uname -a
Linux dmif-lm2 4.17.18-200.fc28.x86_64 #1 SMP Wed Aug 22 19:08:07 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
$ gcc --version
gcc (GCC) 8.1.1 20180712 (Red Hat 8.1.1-5)
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

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

Re: LilyPond 2.19.82 and Fedora 28: exit code 6

[David Kastrup]

Davide Liessi  writes:

> Hi all.
> Compiling this file:
>
> \version "2.19.82"
> {
>   c1
>   \tempo "a"
>   %c1
> }
>
> with the system-provided LilyPond 2.19.82 on Fedora 28 I get this error:
>
> lilypond 2.19.82 [Senza nome] in avvio...
> Elaborazione di «/tmp/frescobaldi-nw1vbdie/tmpe_aojklz/document.ly»
> Analisi...
> Interpretazione della musica...
> Pre-elaborazione degli oggetti grafici...
> Uscito con codice 6.
>
> Uncommenting the last c1 compiles correctly.
> With LilyPond 2.19.82 from lilypond.org both versions compile correctly.
>
> Let me know if you need further information to diagnose the problem.

Works on current Ubuntu Alpha (to become 18.10) at least with the binary
I last installed (June 19) and with a binary freshly compiled from
master (on x86_64, gcc (Ubuntu 8.2.0-4ubuntu1) 8.2.0).  The \tempo does
not actually appear, though.  Now Fedora tends to be sort-of on the
bleeding edge with regard to GCC so I won't rule out that this is
GCC-related, but the above-mentioned Ubuntu GCC is not exactly old
either and I just did a clean build to make sure everything is compiled
by that GCC version.

So which architecture and GCC version are we talking about in your case?

-- 
David Kastrup

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

Re: Offset PedalMarking

[Andrew Bernard]

Hi Aaron and Malte,

I have been looking for this concept for ages! Thanks Gents.

Andrew


On Wed, 5 Sep 2018 at 19:18, Aaron Hill  wrote:

>
> You might be able to achieve this by adjusting both the
> `parent-alignment-X` and `self-alignment-X` properties.  See the
> following:
>
> 
> \version "2.19.82"
> music = \relative c' {
>c2. \sustainOn c4 \sustainOff
>\override Staff.SustainPedal.parent-alignment-X = 2
>\override Staff.SustainPedal.self-alignment-X = 2
>c2. \sustainOn c4 \sustainOff
> }
> \score { << \new Staff \music >> }
> 
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

LilyPond 2.19.82 and Fedora 28: exit code 6

[Davide Liessi]

Hi all.
Compiling this file:

\version "2.19.82"
{
  c1
  \tempo "a"
  %c1
}

with the system-provided LilyPond 2.19.82 on Fedora 28 I get this error:

lilypond 2.19.82 [Senza nome] in avvio...
Elaborazione di «/tmp/frescobaldi-nw1vbdie/tmpe_aojklz/document.ly»
Analisi...
Interpretazione della musica...
Pre-elaborazione degli oggetti grafici...
Uscito con codice 6.

Uncommenting the last c1 compiles correctly.
With LilyPond 2.19.82 from lilypond.org both versions compile correctly.

Let me know if you need further information to diagnose the problem.

Best wishes.
Davide

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

Re: Offset PedalMarking

[foxfanfare]

Malte Meyn-3 wrote
> You can add a tweak to the definition of sustainOn:
> 
> \version "2.19.82"
> 
> sustainOn =
> #(define-event-function () ()
> #{
>   -\tweak X-offset 3
>   -#(make-span-event 'SustainEvent START)
> #})
> 
> {
>b4\sustainOn 4 4 4
>b4\sustainOff 4 4 4
> }
> 
> ___
> lilypond-user mailing list

> lilypond-user@

> https://lists.gnu.org/mailman/listinfo/lilypond-user

That's perfect, thank you Malte. I really need to learn this kind of code
because I don't know how I could have found this solution...




--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Re: Offset PedalMarking

[Malte Meyn]

Am 05.09.18 um 10:53 schrieb foxfanfare:


I found in the configuration file how the sustainOn/Off works:

sustainOn = #(make-span-event 'SustainEvent START)
sustainOff = #(make-span-event 'SustainEvent STOP)

I think it would be possible to add an offset for the sustainOn shortcut but
I didn't manage to find the solution...


You can add a tweak to the definition of sustainOn:

\version "2.19.82"

sustainOn =
#(define-event-function () ()
   #{
 -\tweak X-offset 3
 -#(make-span-event 'SustainEvent START)
   #})

{
  b4\sustainOn 4 4 4
  b4\sustainOff 4 4 4
}

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

Re: Offset PedalMarking

[Aaron Hill]

On 2018-09-05 01:53, foxfanfare wrote:
I'd like to move globally the pedal markings for piano to the left, but 
only
the SustainOn sign, not the release one. If I write someting like 
\override
SustainPedal.X-offset, they will both move. I wonder how it is possible 
to

be done.


You might be able to achieve this by adjusting both the 
`parent-alignment-X` and `self-alignment-X` properties.  See the 
following:



\version "2.19.82"
music = \relative c' {
  c2. \sustainOn c4 \sustainOff
  \override Staff.SustainPedal.parent-alignment-X = 2
  \override Staff.SustainPedal.self-alignment-X = 2
  c2. \sustainOn c4 \sustainOff
}
\score { << \new Staff \music >> }


-- Aaron Hill

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

Accidentals and Ledger Lines

[foxfanfare]

Hi all,

I find LilyPond default output for accidentals a bit weird with ledger
lines. Here's a little exemple in a score context:

accidentals.JPG
  

As you can see, the ledger line of the note containing the accidental is
shortned as expected, but the other aren't and you can see here the natural
appears too close.

I can fix this by moving the accidental with \once \override
Accidental.X-offset = #-1.25, see:

accidentals2.JPG
  

But this tweak has to be done every time... My question is: is it possible
to add more padding between ledger lines and accidentals? I tried many
combinations but nothing worked so far...



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Offset PedalMarking

[foxfanfare]

Hi all,

I'd like to move globally the pedal markings for piano to the left, but only
the SustainOn sign, not the release one. If I write someting like \override
SustainPedal.X-offset, they will both move. I wonder how it is possible to
be done.

I found in the configuration file how the sustainOn/Off works:

sustainOn = #(make-span-event 'SustainEvent START)
sustainOff = #(make-span-event 'SustainEvent STOP) 

I think it would be possible to add an offset for the sustainOn shortcut but
I didn't manage to find the solution...

A little help would be appreciated, thanks!



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Re: Spacing issue with magnifyStaff

[Malte Meyn]

Am 05.09.18 um 05:57 schrieb Simon Albrecht:

On 03.09.2018 18:35, Malte Meyn wrote:

\layout {
  \context {
    \Staff
    \name "SmallStaff"
    \alias "Staff"
    fontSize = #(magnification->font-size 4/7)
    \override StaffSymbol.staff-space = #4/<
  }
  \context {
    \Score
    \accepts "SmallStaff"
  }
  \context {
    \StaffGroup
    \accepts "SmallStaff"
  }
  %% add more of these blocks with \accept if you need 


Better: use
\layout {
   \inherit-acceptability "SmallStaff" "Staff"
}
:-)

Best, Simon



Wow, that’s cool. Like foxfanfare, also for me there’s lots of things to 
learn :)


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