Hi Simon,
thank you very much for the link and the hint.
My problem is that I get it working in Frescobaldi (i.e. lilypond).
But when I use the layout environment inside a LaTeX-document and compile it
via lilypondbook, lilypondbook seemingly doesn’t catch the \layout block.
The same happened t
Noeck writes:
> Hi Simon
>
> Am 06.02.2017 um 00:02 schrieb Simon Albrecht:
>> if you use \set, the Staff is created without a setting for
>> instrumentName, and instrumentName is set at the timestep where the \set
>> command is issued.
>
> Are you sure? I might be misreading David's mail, but as
Thanks for this additional caveat, David!
You convinced me ;)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Simon
Am 06.02.2017 um 00:02 schrieb Simon Albrecht:
> if you use \set, the Staff is created without a setting for
> instrumentName, and instrumentName is set at the timestep where the \set
> command is issued.
Are you sure? I might be misreading David's mail, but as far as I
understood, the s
Simon Albrecht writes:
> On 05.02.2017 23:58, Noeck wrote:
>> In other words: if the \set happens early enough (with the staff
>> creation) there is no difference.
>
> Technically, there is still a difference: if you use \with{}, the
> Staff is _created_ with that particular setting for the conte
On 05.02.2017 23:58, Noeck wrote:
In other words: if the \set happens early enough (with the staff
creation) there is no difference.
Technically, there is still a difference: if you use \with{}, the Staff
is _created_ with that particular setting for the context property, if
you use \set, the
In other words: if the \set happens early enough (with the staff
creation) there is no difference.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi David,
>> What are cases in which that makes a difference? I always thought they
>> were equivalent.
> Once you take over the job of LilyPond, we might take note that you
> consider them equivalent and change the documentation. In the meantime,
> LilyPond's thoughts about the issue are more re
Noeck writes:
> Hi,
>
> I read on the dev list and in the issues [1] that setting some
> properties in the \with block is advisable, instead of setting them
> somewhere in the music. So
> \new Staff \with { instrumentName = "Flute" } { a }
> is better than
> { \set Staff.instrumentName = "Flute"
On 05.02.2017 22:50, "Dr. Raphael D. Thöne" wrote:
I would like to increase the space between a chord symbol and the
first staff, so that all chords are placed slightly higher than default.
I presumably can use a set command for this, but unfortunately in the
documentation, I didn’t find the app
Hi,
I read on the dev list and in the issues [1] that setting some
properties in the \with block is advisable, instead of setting them
somewhere in the music. So
\new Staff \with { instrumentName = "Flute" } { a }
is better than
{ \set Staff.instrumentName = "Flute" a }
even though the output is i
Hi,
thanks for the help on the system-system-spacing topic, it now works.
I would like to increase the space between a chord symbol and the first staff,
so that all chords are placed slightly higher than default.
I presumably can use a set command for this, but unfortunately in the
documentatio
Am 5. Februar 2017 16:34:08 MEZ schrieb "Dr. Raphael D. Thöne"
:
>Hi,
>
>I have created this simple code for use inside of lilypondbook.
>
>right = { s1 s s s \break s s s s}
>left = { \clef bass s1 s s s \break s s s s }
>
>
>\score
>{
>\new PianoStaff \with {\override StaffGrouper #'
Hi,
I have created this simple code for use inside of lilypondbook.
right = { s1 s s s \break s s s s}
left = { \clef bass s1 s s s \break s s s s }
\score
{
\new PianoStaff \with {\override StaffGrouper #'staff-staff-spacing
#'basic-distance = #10
}
<<
14 matches
Mail list logo