Paul Morris wrote
Or, probably better, introduce some kind of passes as property where you
could tell other contexts to treat this context like X context for
purposes of accepting/rejecting it.
On second thought, why not just use the existing \alias for this too? Most
of the time if we want
Jim Long wrote
I'm experimenting with defining and using custom contexts.
Hi Jim, Looks like Harm has you covered. See also this snippet that shows
how to define a custom staff context:
http://lsr.di.unimi.it/LSR/Item?id=882
If you are generating midi files you will also need to define your
Noeck wrote
To make the use of spacing settings easier, I put the most relevant
settings on
this page:
http://joramberger.de/files/LilypondSpacing.pdf
Thanks Joram, this is very helpful!
Here's another visual guide that Abraham Lee created that's similar:
Hi Kaj,
Kaj Persson wrote
I think that aids like this are very valuable to lead the novice past
all the pitfalls surrounding her/his way towards the bigger
understanding. At first you just use it, finding it a good help, which I
will do now. Later on by investigating how it works, it also
Hi Kaj,
In my experience adjusting vertical spacing in LilyPond can be particularly
complicated and low-level. I wrote an include file to simplify things.
You can read about it and access it here:
https://github.com/openlilylib/openlilylib/tree/master/notation-snippets/scale-vertical-spacing
Hi Urs,
Good to hear about the recent progress on this. Looks like you have put a
lot of thought and work into it. Your post was a lot to take in, so here
are just a few thoughts off the top of my head.
- What is the plan for existing oll code/content? Will there be a library
for more bubbly
Urs Liska wrote
Of course, but when you are searching for solutions, approaches or even
tutorials on Scheme you'll get a bunch of different resources, some for
Racket, some for MIT Scheme, some for guile-1.8, some for guile-2.0 and so
on. While often there is something to the solution that you
Urs Liska wrote
Now I've checked - it's perfect. Thank you again!
There is no alist? predicate, but it's very easy to define:
#(define (alist? lst)
(and (list? lst)
(every pair? lst)))
Glad to help and glad someone else is benefiting from this. (On a related
note, I also
Urs Liska wrote
So does anyone have an idea how I can attach an alist to a grob so that
an engraver can retrieve it?
Is it for example possible to add an arbitrary property to a grob?
Hi Urs, I've had good luck creating custom grob properties, which sounds
like what you're looking for.
Paul Morris wrote
%% I use cn- to keep my functions separate from standard
%% LilyPond functions (like a poor man's namespace).
Well, I should have said functions, custom property names, etc.
separate...
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Attaching
Welcome to LilyPond!
Peter Jongh Visscher wrote
I started using Lilypond and the in the PDF output the first line(staff)
jumps a little bit forward(see Example)
I can not find a command to set all the staff starting at the same point.
For this, use indent = #0 in the \layout block as
Ted Lemon wrote
Yeah, so, this is intensely frustrating for anybody who tries to google
for help with lilypond, because there are several dozen archives of the
lilypond mailing list, each slightly different, so that if you do
virtually any google search for help with lilypond, it returns a
Werner LEMBERG wrote
Vertical spacing can get tricky, so here's a helpful visual guide:
http://lilypond.1069038.n5.nabble.com/attachment/164161/0/vertical-spacing-paper-variables.pdf
Very nice! Do we have a comparable image in the lilypond documentation
already?
Abraham gets the credit
Jesus Arocho wrote
Is this failure to compile with guile 2 libraries general or for most
people?
At least that is what I gathered from searching for information on the
failure. If so, could the references to compiles with 1.8 be removed?
As I understand it, LilyPond needs guile 1.8 at
Jesus Arocho wrote
In build/INSTALL.txt: Guile
(http://www.gnu.org/software/guile/guile.html)
(1.8.2 or newer)
I interpreted the or newer using the plain meaning of the text, that newer
is
not circumscribed to the 1.8 branch of guile.
I recall seeing the same in the user manual.
Hi and welcome,
lindleymo wrote
I'm fairly new to lilypond and I'm trying to figure out how to set the
vertical heights in a staffgroup (the height of each staff, the height
between staves and the height between staff groups) to precise values (in
points, which I understand is the default).
Keith OHara wrote
so I am taking Michael Ellis' suggestion to use an include file containing
the note names I use
Ok, for anyone else interested, here is the full include file for using 'gn'
style note names:
english-n.ly
http://lilypond.1069038.n5.nabble.com/file/n169409/english-n.ly
The
Gerjan Piksen wrote
I would be very very very happy with some help on this : )
Let me see if I can help. I think the first step is to use something
besides embedded-ps. make-connected-path-stencil will be easier to work
with. The following will let you set the width like you want.
I forgot to link to these snippets:
make-connected-path-stencil
http://lsr.di.unimi.it/LSR/Item?id=891
another option:
ly:make-stencil and path
http://lsr.di.unimi.it/LSR/Item?id=623
-Paul
--
View this message in context:
Just for the record, I'm using this way of getting and setting paper
variables with scheme in the latest version of my scale vertical spacing
code, along with some other changes and improvements:
https://github.com/openlilylib/openlilylib/tree/master/notation-snippets/scale-vertical-spacing
Keith OHara wrote
Then I'll propose that LilyPond accept 'cn' only when the user requests
that input style, and I won't call that style 'American'.
Another inconvenience with \languageenglish is that its default names
are the long forms, so
\displayLilyMusic \transpose c e {fs as cs}
is
Peter Gentry wrote
\version 2.18.2
;;; OS Vista and Frescobaldi
;;; attempt to improve include file enharmonic.ly
;;; why does guile display fail to produce an output to thefresobaldi log
file
#(ly:message Test debug 1\n)
#(define (naturalize-pitch p)
(let ((o (ly:pitch-octave p))
(a (* 4
Another American here, but I don't have a very strong opinion on this. I can
see arguments on both sides.
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/would-gn-for-G-natural-be-useful-in-language-english-tp165872p168834.html
Sent from the User mailing list
Thomas Morley-2 wrote
Hi Paul,
maybe something at the lines of:
my-paper-settings =
#'((system-system-spacing . (padding . 10))
;(score-system-spacing . (padding . 0))
;(markup-system-spacing . (padding . 0))
;(score-markup-spacing . (padding . 0))
Thomas Morley-2 wrote
I looked in the source:
lily-library.scm
paper.scm
Though, I'm not an expert with this.
For example, have a look at 'paper-variable' from lily-library.scm.
You'll find a local 'get-papers'-variable, seems there is probably
something more to think of.
It's beyond my
Greetings all,
Is there currently a way to get the scheme function below (a minimal
example) to do what it's trying to do, namely return a paper block with
several parts that are conditionally added or omitted?
I have tried various combinations of # and $ for introducing the scheme
expressions,
Chris Trahan wrote
I figured that the spacing had to go in the \paper section but I couldn't
figure out what parameters to adjust.
The options for vertical spacing in LilyPond can be pretty overwhelming.
Here's an invaluable visual guide that Abraham put together:
Urs Liska wrote
Unfortunately not.
Type check for `color' failed; value `(quote darkgreen)' must be of type
`color'
I don't know what you've tried. Have you tried it without the quote? See
the following:
\version 2.18.2
#(display red)
#(newline)
#(display 'red)
#(newline)
#(display red)
Here we go:
\version 2.18.2
#(display (color? red))
#(newline)
#(display (color? 'red))
#(newline)
#(display (color? red))
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Colors-in-alists-tp168384p168391.html
Sent from the User mailing list archive at Nabble.com.
Jay Anderson wrote
Try quasiquote + unquote:
#(define types
`((one . ,red)
(two . ,blue)))
#(display types) = ((one 1.0 0.0 0.0) (two 0.0 0.0 1.0))
-Jay
That does it, or you can use list and cons. Allow me to provide a tiny
example:
%
\version 2.18.2
Urs Liska wrote
I would be extremely happy if someone could take the time and write a
slow-paced tutorial about this on Scores of Beauty!
Meanwhile here's a slow-paced video tutorial on quoting in scheme (although
it doesn't get to quasi-quoting-and-un-quoting):
Jay Vara wrote
Is there a similar way to get at the accidental grob from the NoteNames? I
tried a similar method by overriding the NoteNames.stencil and giving the
NoteName a colour there. When I do an (accidental (ly:grob-object grob
'accidental-grob)), it always comes up with null. Also, I
Hi Jay, Looks like you got very close! And you are right about the problem:
Jay Vara wrote
Perhaps we are catching the stem after it has already been printed?
To fix this, we can use \override NoteHead.before-line-breaking, which lets
us set the grob properties sooner. The following uses
Urs Liska wrote
That sounds reasonable.
However, original breaks *are* part of the content so that's not a
mixture.
Hi Urs,
Well, I see where you're coming from, but I think we are understanding
content differently here.[1]
The original breaks are an important means to render the original
Paul Morris wrote
If you have a chance I'm curious what you mean by direct context
addressing and what the problem is there.
Actually, scratch that, I read about it in your post earlier in this thread.
Sounds like a good feature.
-Paul
--
View this message in context:
http://lilypond
Kieren MacMillan wrote
That’s exactly what I do. =)
If the \editionEngraver had anchors and direct context addressing, I
believe I would be able to finally eliminate all presentation-layer coding
(e.g., \tags, \tweaks, etc.) from my content code.
Hi Kieren, Glad we're on the same page with
Urs Liska wrote
Did you read my email quoted below? I have the impression it wasn't
delivered through the list (was it down yesterday?)
Ah, I hadn't seen your message or Kieren's that you were replying to.
Thanks, and sorry I missed it before. I now see where you're coming from on
this.
Jay Vara wrote
There is a snippet that shows how to colour based on pitch
http://lsr.di.unimi.it/LSR/Snippet?id=572 - I was not able to figure out
how to use this to capture accidentals.
Hi Jay, Check out this snippet:
Using ly:grob-object to access grobs with \tweak
I was thinking the edition engraver would be a good way to handle Urs'
original breaks functionality.
Instead of entering the original breaks (tagged or with a special break
command) in the score in the middle of the music, mixing content and
presentation... I can imagine a way to simply enter
linux wrote
So Mac Os X Yosemite 10.10 with updated Xcode and Command Line Tools
(6.1) is without lilypond for the moment!
Well, only if you are trying to install LilyPond with homebrew, right? You
can still download and install LilyPond from here, and it should work fine:
Robin Bannister wrote
A more workable approach is to modify similar snippets.
Maybe this is a good example of music-map to add to the LSR?
http://lsr.di.unimi.it/LSR/Search
Cheers,
-Paul
--
View this message in context:
Thanks for the info everyone. I've upgraded and LilyPond and Frescobaldi are
working fine. Good to know I shouldn't try to do anything with MacPorts for
now.
Cheers,
-Paul
--
View this message in context:
Anyone happen to know if there are any compatibility problems with LilyPond
or Frescobaldi on the new Mac OSX 10.10 (Yosemite)?
I have no reason to expect that there would be, but it would be nice to know
before upgrading.
Thanks in advance,
-Paul
--
View this message in context:
Kieren MacMillan wrote
breaksOff = \lineBreaksOff \pageBreaksOff
breaksOn = \lineBreaksOn \pageBreaksOn
I don't think the last two lines do what you think they do.
Perhaps not. I’ve never had to use them, so I’m not sure!
Hi Kieren, Just for the record, here you've basically done this:
Paul Morris wrote
If you give it a try, you'll want to use this newer and more flexible
version I just submitted to OpenLilyLib.
Now in OLL, with more documentation:
https://github.com/openlilylib/openlilylib/tree/master/notation-snippets/scale-vertical-spacing
Cheers,
-Paul
--
View
Simon Albrecht-2 wrote
Thanks for your help in improving the helper functions; however,
‘inverting’ string-append and cond seems to be based on a
misunderstanding. It needs to be
Ah, I see now... I was missing the forest for the trees.
Cheers,
-Paul
--
View this message in context:
Janek Warchoł wrote
The problem is that when used with relative mode, the output gets crazy:
Hi Janek, you just need to use $m1 instead of #m1 in your function.
http://lilypond.org/doc/v2.18/Documentation/extending/scheme-function-definitions
HTH,
-Paul
\version 2.18.2
voiceDivisi =
Simon Albrecht-2 wrote
well, now I did try and make a function for german note names, which
discerns major and minor also. Actually it works – the transposition is
applied correctly and there are no unexpected messages – but at testing
there seemed to be a memory problem: from some point
Urs Liska wrote
Am 09.10.2014 06:31, schrieb Marco Bagolin:
The notation contemporary music is so diverse, I know.
I wonder if actually Lilypond has commands for drawing graphic
symbols, as line circle, curve, square, circle, etc...
In addition to what Urs shared, here are a couple of
Simon Albrecht-2 wrote
I’d like to avoid having to synchronise newTonic and newTonicString
manually, but I’ve been unable to find a convenient way to convert one
into the other. Can anybody help?
Hi Simon,
This does the job. I might contribute it to the LSR.
Cheers,
-Paul
%%
Just for fun, another version, more compact, probably more cryptic:
%%
\version 2.19.12
pitch-to-string =
#(define-scheme-function (parser location p) (ly:pitch?)
(string-append
(list-ref '(C D E F G A B)
(ly:pitch-notename p))
(list-ref '(-Double-Flat -Flat -Sharp
Jay Vara wrote
I am trying to display all the names that appear in a piece of music
(NoteEvent etc.) using map-some-music. It the function musShow is only
printing the top level name. What am I missing here?
Hi Jay, Did you see my reply here:
Hi Urs,
I think part of the problem is you haven't actually defined
keepOriginalBreaks as a function/procedure, but just assigned it a value.
See:
https://www.gnu.org/software/guile/manual/guile.html#Lambda-Alternatives
and maybe also:
Paul Morris wrote
I think part of the problem is you haven't actually defined
keepOriginalBreaks as a function/procedure, but just assigned it a value.
Here's something else that might help clarify why it's not working as you
expected it to:
\version 2.18.2
origBreak = {}
% LilyPond's define
Jay Vara wrote
I am trying to display all the names that appear in a piece of music
(NoteEvent etc.) using map-some-music. It the function musNam is only
printing the top level name. What am I missing here?
Hi Jay, From music-functions.scm:
---
(define-public (map-some-music map?
Jay Vara wrote
test =
#(define-scheme-function
(parser location raga)
(string?)
(format #t Inside function raga = ~a ~% raga)
((eval-string raga))
Try changing the last line of your function to this:
(eval-string raga))
I think that should do what you want here.
This is good to know, thanks Robin!
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Generating-symbols-from-strings-tp166813p166886.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing
Richard Shann-2 wrote
Thinking about this after receiving your email, I realize that
ultimately what I am trying to do is access the font-size that is being
used for the markup being generated. Perhaps this is a simpler question
- can a markup be constructed to change depending on the
Jay Vara wrote
In the following program, I set xyz to the variable abc using scheme
string-symbol as well as the usual \abc.
Instead of giving the same value for xyz, the first one sets it to string
abc and the second sets it to value of abc.
What do I need to modify in the assignment
Jay Vara wrote
There should be a way. If I can get the measurePosition from the glob
somehow, it should be possible. Perhaps someone more familiar with the
internals can tell us.
I'm pretty sure you can't access measurePosition or measureLength by
overriding a NoteHead grob property. They
Richard Shann-2 wrote
The chordRootNamer procedure (which is itself a ChordNames context
property) is not passed the context as a parameter, so my question is
how do I reference the context? Is there some variable or procedure for
accessing the ChordNames context (or perhaps it should be the
Hi Jay,
I'm not sure if this will help, but I've found that you can either modify
things on the input/pre-processing side (writing a music function that
changes or adds things to the music that's been input before it is converted
into grobs), or on the output/post-processing side (overriding
Paul Morris wrote
I'm not sure but what you're trying to do might best be done on the input
side.
Actually, nevermind since this is before measures/positions have been
determined. So I'm at a loss... My next thought is that you may need to
create custom engraver, but I'm not even sure
David Nalesnik-2 wrote
Perhaps it's your choice of comparison by eq? I can't say what it does
with strings, but it generally tests that an object is the same object as
another, rather than simply equivalent. (If you want more on these, you
can read up on them in the Guile manual).
Here's
Urs Liska wrote
So the question is: is there a way for a voice/staff to completely ignore
the \key command?
Will \remove Key_engraver do what you want? It solves the problem you gave
in your example.
HTH,
-Paul
\version 2.19.13
\new Staff \with {
\remove Key_engraver
} {
cis''1^\markup
Richard Shann-2 wrote
This works perfectly on my minimal example but throws up a strangeness
on a real-world example. With 10 systems I get two pages with a strange
gap beneath the titles.
My guess is to try adjusting:
markup-system-spacing
the distance between a (title or top-level)
Oops, also, I see that you'll need to use:
\paper {
system-system-spacing = 0
}
Since this is not within system spacing but between system (or page
layout) spacing:
http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables
Cheers,
-Paul
--
View this
Well, make that:
\paper {
system-system-spacing =
#'((basic-distance . 0)
(minimum-distance . 0)
(padding . 0))
}
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Reducing-the-spacing-between-ChordNames-systems-tp166314p166321.html
Sent from the User
tisimst wrote
Ok, I think I've got all the bugs worked out and everything corrected.
Thanks for everyone's patience while I put this together. It's a simple
website, but hopefully helpful. Enjoy the new music fonts! The site is now
live at
fonts.openlilylib.org http://fonts.openlilylib.org/
Hi Pierre,
If you give it a try, you'll want to use this newer and more flexible
version I just submitted to OpenLilyLib:
https://github.com/PaulMorris/openlilylib/tree/scale-vertical-spacing/notation-snippets/scale-vertical-spacing
As before, it lets you scale all the vertical spacing
Hello everyone,
When it comes to adjusting vertical spacing using the flexible variables
and/or properties:
http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables
http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-within-systems
Ok, so I've made a first pass and have something that works, see these files:
adjust-vert-spacing.ly
http://lilypond.1069038.n5.nabble.com/file/n166124/adjust-vert-spacing.ly
adjust-vert-spacing-test.ly
http://lilypond.1069038.n5.nabble.com/file/n166124/adjust-vert-spacing-test.ly
There are
Patrick or Cynthia Karl wrote
Is there a way to access the input filename that lilypond was invoked with
in order to include it in text output to the pdf file generated?
This snippet shows how:
http://lsr.di.unimi.it/LSR/Item?id=197
HTH,
-Paul
--
View this message in context:
Hi Urs,
I would just use a scheme function, as follows. Does it do what you want?
Cheers,
-Paul
\version 2.19.11
myFunction =
#(define-scheme-function (parser location text) (markup?)
#{
\markup \italic \with-color #(x11-color blue) #text
#})
pizz = \myFunction pizz
{
c'1
mark damerell wrote
pitch-semitones converts a pitch to semitones. Please does the inverse
function exist?
Hi Mark, As I understand it, what is called a pitch in LilyPond consists
of three values: an octave, a note name/position within that octave
(ABCDEFG), and an alteration (sharp, flat,
Urs Liska wrote
Hi all openlilylib users,
when updating information on a few snippets (to test the documentation
generator) I think I realized something.
Currently we call the files we have ready for inclusion snippets,
which is partially true but also a 'historic' thing.
But I think
Urs Liska wrote
to give you quick access and a first impression on what I've done on the
openlilylib documentation you can have a look at
http://openlilylib.org/demo-oll/git-commands.html
Hi Urs,
This is great progress and it's looking good! I have some thoughts about
the layout but I
I came across a couple of articles on church music on Github in LilyPond
format. (Organ accompaniments for Gregorian Chant, a LilyPond transcription
of the Nova Organi Harmonia.)
http://createdigitalmusic.com/2014/07/fork-chant-github-goes-gregorian-open-source-notation/
MarcM wrote
How to keep all voices in C major?
Hi, try \modalTranspose
http://lilypond.org/doc/v2.18/Documentation/notation/changing-multiple-pitches#index-_005cmodalTranspose
HTH,
-Paul
--
View this message in context:
Urs Liska wrote
- generate HTML documentation for the library
- browse the library by snippet name, category, tag, author (and
possibly more options in the future)
- display documentation for a selected snippet (built on-the-fly from
the actual snippet)
Hi Urs,
Wow, looking good!
Marc Hohl wrote
Looks nice! Do you think that \setRepeatCommand should be included in
the sources? I'd always found the manual tweaking of the text in the
volta brackets somewhat clumsy...
Or at least it could be added to the LSR?
-Paul
--
View this message in context:
Schneidy wrote
2014-07-13 23:21 GMT+02:00 Paul Morris lt;
paul@
gt;:
Good call. Or how about a music function that takes a parameter and
scales
the default values, as shown below?
Thanks Paul, snippet updated.
Cheers,
Pierre
Thanks Pierre!
-Paul
--
View this message
Schneidy wrote
Nice Paul !
And here's a complement to get rid of the gap between startStaff and
stopStaff:
Thanks, and nice fix for that little gap, although it appears it increases
the spacing between the notes, as in the second measure here:
http://lsr.di.unimi.it/LSR/Item?id=928
One
Colin Campbell-8 wrote
How about tucking the overrides into variables, so they could be put into
an \include library?
Good call. Or how about a music function that takes a parameter and scales
the default values, as shown below?
One problem is you can end up hiding a bar line that doesn't
Charles Marshall wrote
How can the length of a ragged last line be adjusted? With
ragged-last-line = ##t , the line is too short to look good; with = ##f
, it's right-justified and too long.
The answer must be in the documentation, but I have not been able to
speak the magic Google
Noeck wrote
This leaves the question open how to adapt it for single notes or small
passages.
Here we go:
\version 2.18.2
{
g d c d
c d
\stopStaff
\startStaff
\override Staff.LedgerLineSpanner.length-fraction = #0.1
\override Staff.LedgerLineSpanner.minimum-length-fraction = #0.1
tisimst wrote
This may also help. I made this diagram because I had trouble
understanding which page layout properties did what. See attached for a
graphical example of vertical layout properties (some rigid, some
flexible).
Hi Abraham,
This is so helpful, thanks! I'd say this deserves a
I'm interested as well.
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Question-for-all-LilyPond-users-especially-power-users-tp164178p164188.html
Sent from the User mailing list archive at Nabble.com.
___
Uns Liska wrote
Hm, I think I _must not_ start with such a script right now, since I
know that this - although being not too complex - will eat up too much
of my time and concentration.
But your message triggered a little bit of thought, and I came to the
conclusion that we should use a
Uns Liska wrote
Some of them are good, some of them less so, I think.
Maybe we could start going through the existing snippets and consider
possible tags for each of them. This will make a pool of suggestions
where we can filter out from.
One question I still have is: Should the tags be
Uns Liska wrote
Starting by tagging the existing snippets sounds fine to me.
But not tagging directly but collecting suggestions first. Then decide
about a set of tags and apply them during the move.
Ok, sure.
Something to consider: since you are planning on writing a script to walk
through
Uns Liska wrote
I have updated the Wiki page
https://github.com/openlilylib/openlilylib/wiki
and added a note about the reorganization process in the README.md on
the restructuring branch.
It's looking good to me. From the wiki page:
Probably it's a good idea to assign a primary tag (=
Uns Liska wrote
Am 03.07.2014 19:50, schrieb Paul Morris:
Hi Urs, This is looking like an improvement to me. Here's a thought.
If
the emphasis is on include-ability, what about just having all the
include
files at the same level in the Library directory, without needing to
categorize
Hello list,
I'm not familiar with all of LilyPond's note head styles and I'm curious
about their use:
http://lilypond.org/doc/v2.18/Documentation/notation/note-head-styles
I assume some would typically be used for all the notes in a given piece:
default, altdefault, baroque, neomensural,
Uns Liska wrote
I can see the point and I'm ready to accept that approach. There is one
issue, however, that I'd like to discuss before making any decision.
\include file-name.ily
opens the door wide for name conflicts. The more the names are speaking
the more they will be likely
Uns Liska wrote
I think that after an initial phase of trial error we should
now do it right and create a structure we can live with for the future.
Hi Urs, This is looking like an improvement to me. Here's a thought. If
the emphasis is on include-ability, what about just having all the
Hi Pierre and Harm,
Schneidy wrote
Examples of three different ways to scale a staff to twice its size:
Thanks for the tip Paul.
Il keep it for a future snippet in the LSR v2.20 (just 2 ways if you don't
mind).
You're welcome, and sounds good, I don't mind. I think it would be good to
Simon Albrecht-2 wrote
The set-global-staff-size approach also seems
to leave the staff lines and stems proportionally thinner at larger
sizes.
… which is a good thing, since it preserves the optical impression
instead of keeping the numerical proportions.
If the proportions would remain
Hi all,
Is this way of scaling a score (by putting it inside a markup) the best way
to do it, if you want to keep all of the proportions strictly consistent at
different sizes?
The approach in the staffSize snippet does not keep the proportions
consistent, which becomes apparent at larger
Mats Bengtsson-4 wrote
Interesting! I have started typesetting some of Westhoff's solo violin
suites, which originally were typeset using a similar 8 line staff, see
http://imslp.org/wiki/Suites_for_Solo_Violin_%28Westhoff,_Johann_Paul_von%29
As an additional feature, Westhoff used unequal
201 - 300 of 605 matches
Mail list logo
