Re: Add second set of lyrics part way through a movement
On Sat 20 May 2017 at 20:27:06 (+0300), Emrecan Büyüktermiyeci wrote:
> You can use repeat unfold command for 61 blanked charackters.
>
> tcd=\lyricmode{
> \repeat unfold 61 { _ }
> do -- _ na no -- bis pa -- _ _ _ cem,
I would add one proviso to that construction, both the caveat
and the provision. It will prevent failure where the words in
common don't occur at the beginning of the text (eg the refrain
for different verses). Because I use it a lot, I give it a very
short name, \n. So an example might look like:
\addlyrics { These are the first __ _ set of nonce words for this work. }
\addlyrics { \repeat unfold 3 _ se -- cond \n \repeat unfold 6 _ }
\addlyrics { \repeat unfold 3 _ third __ _ \n \repeat unfold 6 _ }
The \n prevents all those _ syllables from making a very long
melisma, complete with extender in the third verse. Here's its
definition, and a few related extras.
nbsp = \markup % risky as invisible
%%nbsp = \markup \char ##x00A0 % safer alternative
n = \lyricmode { \nbsp } % stops a melisma being formed; only one needed
blank = \lyricmode { " " } % prevents using vertical space, but _ will do
nowt = \lyricmode { "" } % ditto, but can write a warning message
blob = \lyricmode { ▬ } % for irregular hymns
invisibledot = \lyricmode { \once \override LyricText.font-size = #-19 "." } %
take up room
Cheers,
David.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new voice with cluster changes horizontal spacing
Am 19.05.2017 um 20:22 schrieb Klaus Blum: if the clusters are preceeded by a "\new Voice" command, the horizontal spacing changes. This sounds bug-worthy. Could you please check if there’s already an issue in the tracker and else report on the bug list? Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Add second set of lyrics part way through a movement
Hello, Dirk
You can use repeat unfold command for 61 blanked charackters.
tcd=\lyricmode{
\repeat unfold 61 { _ }
do -- _ na no -- bis pa -- _ _ _ cem,
Emrecan
On Sat, 20 May 2017 16:53:56 +0100
Dirk Koopman wrote:
> I am trying to set a Victoria mass's Agnus Dei. Most of the words are
> the same, but there are two endings, basically "miserere nobis" and
> "dona nobis pacem".
>
> textocantus=\lyricmode{
>A -- gnus De -- _ _ i,
>A -- gnus __ _
>De -- _ _ _ _ i,
>A -- gnus De -- _ _ _ _ _ _ _ i,
>qui tol -- lis pec -- ca -- ta mun -- _ _ _ _ _ _ di,
>qui tol -- lis pec -- ca -- ta mun -- _ _ di,
>pec -- ca -- ta mun -- _ _ _ _ _ _ _ _ di, __
>pec -- ca -- ta mun -- _ _ _ _ _ _ di,
> }
>
> tcm=\lyricmode {
>mi -- se -- re -- re no -- _ _ bis,
>mi -- se -- re -- re no -- _ _ _ _ _ _ bis,
>mi -- se -- re -- re no -- bis,
>mi -- se -- re -- re no -- _ _ _ _ _ bis,
>mi -- se -- re -- re no -- _ bis.
> }
>
> tcd=\lyricmode{
>do -- _ na no -- bis pa -- _ _ _ cem,
>do -- na no -- bis pa -- _ _ _ _ _ _ cem,
>do -- na no -- bis pa -- cem,
>do -- na no -- bis pa -- _ _ _ _ _ cem,
>do -- na no -- bis pa -- _ _ cem.
> }
>
> The first part would look something like this:
>
> \score {
>\new ChoirStaff <<
> \new Staff = "v1" {
>\set Staff.instrumentName = "Cantus"
>\set Staff.shortInstrumentName = "C"
>\clef treble
>\new Voice = "v1" {
> \global
> \cantus
>}
> }
> \new Lyrics = "v1"
>
> \context Lyrics="v1" {
>\lyricsto "v1" {
> \textocantus
>
> %<<
> \tcm
>
> %\tcd
> %>>
>
>}
> }
>
> ...
>
> The net result wants to look rather like this:
>
> "... peccata mundi, miserere nobis."
> " dona nobis pacem."
>
> Any suggestions?
>
> Dirk
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Emrecan Büyüktermiyeci
---
http://twitter.com/Termiyeci
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Add second set of lyrics part way through a movement
On Sat 20 May 2017 at 12:26:46 (-0400), Kieren MacMillan wrote:
> Hi Dirk,
>
> > The net result wants to look rather like this:
> > "... peccata mundi, miserere nobis."
> > " dona nobis pacem."
> > Any suggestions?
>
> Since the number of syllables is identical, you *could* just put columns for
> each of those lyrics.
Any melismas wouldn't look nice.
> But the better overall attack would be to write each set of lyrics out, using
> variables and/or skips as necessary, and then layer them in as two Lyric
> contexts.
IIRC the CPDL/Victoria web site uses a simultaneous construction
to do this, but with version 1.4.12 it's rather dated syntax.
For Remy, attached.
Cheers,
David.
\header { tagline = ##f }
<<
{ c' d' e' f' g' a' c' d' e' f' g' a' c' d' e' f' g' a' c' d' e' f' g' a' }
\addlyrics { Ag -- nus _ De -- _ _ i, … mi -- _ _ se -- _ _ re -- _ _ re no
-- _ _ bis. __ _ _ }
\addlyrics { " " _ _ _ _ _ _ _ do -- _ _ na __ _ _ no -- _ _ bis pa -- _ _
cem. __ _ _ }
>>
agnus.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond newbie can't compile
Am 20. Mai 2017 18:53:54 MESZ schrieb David Wright : >On Sat 20 May 2017 at 18:26:40 (+0200), Jean Brefort wrote: >> Le samedi 20 mai 2017 à 11:18 -0500, David Wright a écrit : >> > Stable has more than one meaning. 2.18.2 has been stable for a long >> > time, and promises to be around a lot longer seeing that Debian's >> > "stretch" (as yet unreleased) still includes it. >> >> Debian Stretch currently does not include any lilypond version >(2.18.2 >> is still in sid). > >Good point. I don't know if this is relevant: >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005 Yes. Stretch doesn't include Guile 1.8 anymore, so they can't compile LilyPond. Urs > >Cheers, >David. > >___ >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: Add second set of lyrics part way through a movement
Hello, Dirk
You can use repeat unfold command for 61 blanked charackters.
tcd=\lyricmode{
\repeat unfold 61 { _ }
do -- _ na no -- bis pa -- _ _ _ cem,
Emrecan
On Sat, 20 May 2017 16:53:56 +0100
Dirk Koopman wrote:
> I am trying to set a Victoria mass's Agnus Dei. Most of the words are
> the same, but there are two endings, basically "miserere nobis" and
> "dona nobis pacem".
>
> textocantus=\lyricmode{
>A -- gnus De -- _ _ i,
>A -- gnus __ _
>De -- _ _ _ _ i,
>A -- gnus De -- _ _ _ _ _ _ _ i,
>qui tol -- lis pec -- ca -- ta mun -- _ _ _ _ _ _ di,
>qui tol -- lis pec -- ca -- ta mun -- _ _ di,
>pec -- ca -- ta mun -- _ _ _ _ _ _ _ _ di, __
>pec -- ca -- ta mun -- _ _ _ _ _ _ di,
> }
>
> tcm=\lyricmode {
>mi -- se -- re -- re no -- _ _ bis,
>mi -- se -- re -- re no -- _ _ _ _ _ _ bis,
>mi -- se -- re -- re no -- bis,
>mi -- se -- re -- re no -- _ _ _ _ _ bis,
>mi -- se -- re -- re no -- _ bis.
> }
>
> tcd=\lyricmode{
>do -- _ na no -- bis pa -- _ _ _ cem,
>do -- na no -- bis pa -- _ _ _ _ _ _ cem,
>do -- na no -- bis pa -- cem,
>do -- na no -- bis pa -- _ _ _ _ _ cem,
>do -- na no -- bis pa -- _ _ cem.
> }
>
> The first part would look something like this:
>
> \score {
>\new ChoirStaff <<
> \new Staff = "v1" {
>\set Staff.instrumentName = "Cantus"
>\set Staff.shortInstrumentName = "C"
>\clef treble
>\new Voice = "v1" {
> \global
> \cantus
>}
> }
> \new Lyrics = "v1"
>
> \context Lyrics="v1" {
>\lyricsto "v1" {
> \textocantus
>
> %<<
> \tcm
>
> %\tcd
> %>>
>
>}
> }
>
> ...
>
> The net result wants to look rather like this:
>
> "... peccata mundi, miserere nobis."
> " dona nobis pacem."
>
> Any suggestions?
>
> Dirk
>
> ___
> 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: Lilypond newbie can't compile
On Sat 20 May 2017 at 18:26:40 (+0200), Jean Brefort wrote: > Le samedi 20 mai 2017 à 11:18 -0500, David Wright a écrit : > > Stable has more than one meaning. 2.18.2 has been stable for a long > > time, and promises to be around a lot longer seeing that Debian's > > "stretch" (as yet unreleased) still includes it. > > Debian Stretch currently does not include any lilypond version (2.18.2 > is still in sid). Good point. I don't know if this is relevant: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005 Cheers, David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
re: Add second set of lyrics part way through a movement
Hello Dirk,
Could you give me the complete example. I will try to see howto to resolve your
problem.
thanks a lot
Rémy
> Message du 20/05/17 18:24
> De : "Dirk Koopman"
> A : lilypond-user@gnu.org
> Copie à :
> Objet : Add second set of lyrics part way through a movement
>
> I am trying to set a Victoria mass's Agnus Dei. Most of the words are
> the same, but there are two endings, basically "miserere nobis" and
> "dona nobis pacem".
>
> textocantus=\lyricmode{
> A -- gnus De -- _ _ i,
> A -- gnus __ _
> De -- _ _ _ _ i,
> A -- gnus De -- _ _ _ _ _ _ _ i,
> qui tol -- lis pec -- ca -- ta mun -- _ _ _ _ _ _ di,
> qui tol -- lis pec -- ca -- ta mun -- _ _ di,
> pec -- ca -- ta mun -- _ _ _ _ _ _ _ _ di, __
> pec -- ca -- ta mun -- _ _ _ _ _ _ di,
> }
>
> tcm=\lyricmode {
> mi -- se -- re -- re no -- _ _ bis,
> mi -- se -- re -- re no -- _ _ _ _ _ _ bis,
> mi -- se -- re -- re no -- bis,
> mi -- se -- re -- re no -- _ _ _ _ _ bis,
> mi -- se -- re -- re no -- _ bis.
> }
>
> tcd=\lyricmode{
> do -- _ na no -- bis pa -- _ _ _ cem,
> do -- na no -- bis pa -- _ _ _ _ _ _ cem,
> do -- na no -- bis pa -- cem,
> do -- na no -- bis pa -- _ _ _ _ _ cem,
> do -- na no -- bis pa -- _ _ cem.
> }
>
> The first part would look something like this:
>
> \score {
> \new ChoirStaff <<
> \new Staff = "v1" {
> \set Staff.instrumentName = "Cantus"
> \set Staff.shortInstrumentName = "C"
> \clef treble
> \new Voice = "v1" {
> \global
> \cantus
> }
> }
> \new Lyrics = "v1"
>
> \context Lyrics="v1" {
> \lyricsto "v1" {
> \textocantus
>
> %<<
> \tcm
>
> %\tcd
> %>>
>
> }
> }
>
> ...
>
> The net result wants to look rather like this:
>
> "... peccata mundi, miserere nobis."
> " dona nobis pacem."
>
> Any suggestions?
>
> Dirk
>
> ___
> 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: Lilypond newbie can't compile
Le samedi 20 mai 2017 à 11:18 -0500, David Wright a écrit : > Stable has more than one meaning. 2.18.2 has been stable for a long > time, and promises to be around a lot longer seeing that Debian's > "stretch" (as yet unreleased) still includes it. Debian Stretch currently does not include any lilypond version (2.18.2 is still in sid). ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Add second set of lyrics part way through a movement
Hi Dirk, > The net result wants to look rather like this: > "... peccata mundi, miserere nobis." > " dona nobis pacem." > Any suggestions? Since the number of syllables is identical, you *could* just put columns for each of those lyrics. But the better overall attack would be to write each set of lyrics out, using variables and/or skips as necessary, and then layer them in as two Lyric contexts. Hope this helps! Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Add second set of lyrics part way through a movement
I am trying to set a Victoria mass's Agnus Dei. Most of the words are
the same, but there are two endings, basically "miserere nobis" and
"dona nobis pacem".
textocantus=\lyricmode{
A -- gnus De -- _ _ i,
A -- gnus __ _
De -- _ _ _ _ i,
A -- gnus De -- _ _ _ _ _ _ _ i,
qui tol -- lis pec -- ca -- ta mun -- _ _ _ _ _ _ di,
qui tol -- lis pec -- ca -- ta mun -- _ _ di,
pec -- ca -- ta mun -- _ _ _ _ _ _ _ _ di, __
pec -- ca -- ta mun -- _ _ _ _ _ _ di,
}
tcm=\lyricmode {
mi -- se -- re -- re no -- _ _ bis,
mi -- se -- re -- re no -- _ _ _ _ _ _ bis,
mi -- se -- re -- re no -- bis,
mi -- se -- re -- re no -- _ _ _ _ _ bis,
mi -- se -- re -- re no -- _ bis.
}
tcd=\lyricmode{
do -- _ na no -- bis pa -- _ _ _ cem,
do -- na no -- bis pa -- _ _ _ _ _ _ cem,
do -- na no -- bis pa -- cem,
do -- na no -- bis pa -- _ _ _ _ _ cem,
do -- na no -- bis pa -- _ _ cem.
}
The first part would look something like this:
\score {
\new ChoirStaff <<
\new Staff = "v1" {
\set Staff.instrumentName = "Cantus"
\set Staff.shortInstrumentName = "C"
\clef treble
\new Voice = "v1" {
\global
\cantus
}
}
\new Lyrics = "v1"
\context Lyrics="v1" {
\lyricsto "v1" {
\textocantus
%<<
\tcm
%\tcd
%>>
}
}
...
The net result wants to look rather like this:
"... peccata mundi, miserere nobis."
" dona nobis pacem."
Any suggestions?
Dirk
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond newbie can't compile
On Sat 20 May 2017 at 18:38:24 (+1000), Andrew Bernard wrote:
> I have used the development versions full time 8 hours plus a day for the
> last few years, with only two trivial crashing bugs, on massively complex
> scores.
Stable has more than one meaning. 2.18.2 has been stable for a long
time, and promises to be around a lot longer seeing that Debian's
"stretch" (as yet unreleased) still includes it.
For five minutes of mental exercise this Saturday morning, I cobbled
a line of shell¹ to see how many development versions of LP were talked
about here over the last year. There are rather a lot, and you've
quite probably tracked them all.
I think that if "ordinary people" are encouraged to use development
versions, then there needs to be another level introduced on the web
page between bleeding-edge and stable; perhaps "trailing-edge".
These would be the development versions (only one need be offered at
any one time) that over time have shown they don't contain egregious
mistakes (eg like broken lyric extenders).
I hope 2.19.49 (the version I currently use) is one of these.
I run LP regularly on three different machines and don't want
to be perpetually downloading and installing new versions even
though it's only two lines to do so (two more for the docs).
When preparing several pieces over the course of a few weeks,
even the smallest change can destabilise, say, the pagination,
which is most inconvenient.
> Here the OP is using the so called stable version and it has
> crashed straight up.
If the reported diagnosis is correct (locked output file), this
is not a function of stable/unstable LP, but a property of the
OS being used. A "kiosk" computer user (eg ATM) is constrained
to do one thing at a time. Anyone else has to understand the
properties of the OS they use.
With linux-type OSes, you get used to what happens when you,
say, refresh a PDF that's being written to. When it matters,
eg email clients, there are file-locking methods that are used
to prevent file corruption.
On Windows, it's different. Most processes lock files that are
being written to, and even files that are only being read can
have problems with being shared.
> On 20 May 2017 at 18:11, Richard Shann wrote:
> >
> > The harm is that users assume the problem is with their code and spend a
> > lot of time trying to find what they have done wrong.
Agreed.
Cheers,
David.
¹
$ grep '\<2\.19\.[0-9]' ~/Mail-alum/lilypond-user | sed -e
's/.*\(2\.19\.[0-9]\{1,2\}\).*$/\1/' | lcount.py | sort -n | tail -n 28 | sort
-k 2
192 2.19.0
140 2.19.15
87 2.19.22
50 2.19.35
173 2.19.36
59 2.19.37
87 2.19.38
121 2.19.39
223 2.19.40
82 2.19.41
246 2.19.42
124 2.19.43
468 2.19.44
242 2.19.45
329 2.19.46
330 2.19.47
452 2.19.48
542 2.19.49
241 2.19.50
92 2.19.51
518 2.19.52
196 2.19.53
200 2.19.54
277 2.19.55
219 2.19.56
125 2.19.57
191 2.19.58
231 2.19.59
$
"Talked about", so the counts include quotations as well as OPs.
No control for multipart email duplicates, nor omissions through encoding.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How exactly does "\transpose" work?
Hi all,
> Most of my scores finish with something like:
>
> \score {
> \transpose f g
+1
>> But it seems that some really weird things happen
>> if, as I did recently, one screws up the order has:
>>
>> theNotes = \relative c'' \transpose c d''{ {
>> some notes
>> }
>> }
Yet another reason why I strongly advocate for absolute note entry.
Cheers,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How exactly does "\transpose" work?
On Sat 20 May 2017 at 17:28:57 (+1000), Don Gingrich wrote:
> I had the idea that all that I needed to
> do to convert a score from, for example, F to G,
> was to wrap a \transpose f g { } around the
> \relative block where I had entered the notes in
> F. And that is actually correct.
Most of my scores finish with something like:
\score {
\transpose f g
\new GrandStaff <<
\new Staff <<
\new Voice { \clef treble \global }
\new Voice { \sopranoi }
\addlyrics { \textsopranoi }
>>
[... other parts ...]
>>
\layout { }
}
so it's easy to produce in any suitable key at a moment's notice.
> But it seems that some really weird things happen
> if, as I did recently, one screws up the order and
> has:
>
> theNotes = \relative c'' \transpose c d''{ {
> some notes
> }
> }
>
> I'm noting this it the hope that it may save someone else
> the agro that I experienced with notes jumping
> all over the place.
>
> The order is *critical* to having transpose work as
> expected.
>
> This is sort-of a solution in search of a problem but
> it may save someone else some frustration.
You have to think about what \relative { … } means.
Given *raw* notes in its argument, it transforms them into
absolute pitches by a simple rule (up to a fourth, and
fifths or greater; you know this rule). There's no
"second chance"; it's an input method. The octavation
is baked in, so the expression
\relative { … }
placed anywhere else is now absolute music.
The expression \transpose X Y { … } is already absolute
so \relative can't do anything to it. OTOH
\transpose X Y { … \relative { raw notes } … }
is a useful, well-formed expression.
If you nest \relative expressions, the inner ones are baked
first, then the outer ones are evaluated, hopping over the
inner, now baked, expressions.
Cheers,
David.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new voice with cluster changes horizontal spacing
Hi Harm, Thomas Morley-2 wrote > \newSpacingSection > %% the value 1.68 was found by try and error > \override Score.SpacingSpanner.spacing-increment = #1.68 > Thanks for your suggestion. Unfortunately, I'm looking for a solution that works automatically, as I'm trying to build a function: https://raw.githubusercontent.com/openlilylib/analysis/connected-noteheads/connected-noteheads/test.ly Anybody here with some knowledge about clusters? They seem to be written in c as they don't appear in any of the *.scm files. Cheers, Klaus -- View this message in context: http://lilypond.1069038.n5.nabble.com/new-voice-with-cluster-changes-horizontal-spacing-tp203189p203205.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond newbie can't compile
Ok I have made this experience, e.g. the grace-problem. Sometimes it seemed to me that I stumbled over every known Lilypond-bug ;-) and blamed it on me. As a newbie you think it is your fault, that does not depend on the Lilypond-Version. On the other hand you learn much about using Lilypond. Anyway, I think William's problem is solved now, :-) greetings Manuela 2017-05-20 10:11 GMT+02:00 Richard Shann : > On Sat, 2017-05-20 at 10:05 +0200, Manuela Gößnitzer wrote: > > Hi Andrew, > > > > > > well, I think the Lilypond-Homepage should be updated so that the > > latest "developer"-version is strongly recommanded. Compiling a > > sourcefile is a batchjob, so where is the harm done when it crashes? > > > The harm is that users assume the problem is with their code and spend a > lot of time trying to find what they have done wrong. > > Richard > > > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond newbie can't compile
Hi Robin, Would't it be great if instead of saying 'failed(1)' we could have a message saying 'unable to write to output file - file locked'. Especially since newbies are not generally able to read and remember all the details in the references, even though these may be obvious to old hands. Gosh, even I did not see that line in the instructions, even though it is clearly there. Perception is a fuzzy thing when beginning a new subject. Andrew On 20 May 2017 at 18:39, Robin Bannister wrote: You are using a pdf viewer such as Adobe Reader > which locks the file it is displaying. > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond newbie can't compile
William Zeitler wrote: It fails to compile: Processing `C:/Users/william/Documents/Untitled.ly' Parsing... Interpreting music... Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `Untitled.ps'... Converting to `./Untitled.pdf'... warning: `(gs -q -dNOSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./Untitled.pdf -c.setpdfwrite -fUntitled.ps)' failed (1) fatal error: failed files: "Untitled.ly" This is a newbie problem. You are using a pdf viewer such as Adobe Reader which locks the file it is displaying. In the above log, LilyPond compiles successfully, producing a .ps. But the subsequent ghostscript conversion from .ps to .pdf fails, because Adobe Reader won't let it write to the .pdf. The .ps file is partly readable; the gibberish parts are the fonts. Your case is mentioned at the bottom of this page: http://lilypond.org/doc/v2.18/Documentation/web/windows The same page is in the Learning Manual (required reading) at http://lilypond.org/doc/v2.18/Documentation/learning/windows So always terminate Adobe Reader before recompiling. Or use a non-blocking viewer such as SumatraPDF. Cheers, Robin ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond newbie can't compile
Hi Richard, I have used the development versions full time 8 hours plus a day for the last few years, with only two trivial crashing bugs, on massively complex scores. Here the OP is using the so called stable version and it has crashed straight up. Andrew On 20 May 2017 at 18:11, Richard Shann wrote: > > The harm is that users assume the problem is with their code and spend a > lot of time trying to find what they have done wrong. > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond newbie can't compile
On Sat, 2017-05-20 at 10:05 +0200, Manuela Gößnitzer wrote: > Hi Andrew, > > > well, I think the Lilypond-Homepage should be updated so that the > latest "developer"-version is strongly recommanded. Compiling a > sourcefile is a batchjob, so where is the harm done when it crashes? > The harm is that users assume the problem is with their code and spend a lot of time trying to find what they have done wrong. Richard ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How exactly does "\transpose" work?
I tried this code
\version "2.19.42"
someNotes= { c d e f a }
theNotes = \relative c' \transpose c d' {
{
\someNotes
}
}
#'()
\theNotes
\transpose e f \theNotes
which produced nothing unexpected on my system even when transposed again.
Could you add an example for notes?
Greetings,
Manuela
2017-05-20 9:28 GMT+02:00 Don Gingrich :
> I had the idea that all that I needed to
> do to convert a score from, for example, F to G,
> was to wrap a \transpose f g { } around the
> \relative block where I had entered the notes in
> F. And that is actually correct.
>
> But it seems that some really weird things happen
> if, as I did recently, one screws up the order and
> has:
>
> theNotes = \relative c'' \transpose c d''{ {
> some notes
> }
> }
>
> I'm noting this it the hope that it may save someone else
> the agro that I experienced with notes jumping
> all over the place.
>
> The order is *critical* to having transpose work as
> expected.
>
> This is sort-of a solution in search of a problem but
> it may save someone else some frustration.
>
> Cheers,
>
> -Don
> --
> Don Gingrich
>
>
> ___
> 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: Lilypond newbie can't compile
Hi Manuela, The emphasis in my mail was on 7, not Windows. I wonder if there is an incompatibility with ghostscript and Windows 7, that being rather dated now? Andrew On 20 May 2017 at 18:05, Manuela Gößnitzer wrote: > Hi Andrew, > > well, I think the Lilypond-Homepage should be updated so that the latest > "developer"-version is strongly recommanded. Compiling a sourcefile is a > batchjob, so where is the harm done when it crashes? > > I use windows myself for several reasons (there is software that works on > windows only e.g.) so I don't ask that question. > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond newbie can't compile
Hi Andrew, well, I think the Lilypond-Homepage should be updated so that the latest "developer"-version is strongly recommanded. Compiling a sourcefile is a batchjob, so where is the harm done when it crashes? I use windows myself for several reasons (there is software that works on windows only e.g.) so I don't ask that question. I am considering changing to Linux but did not do this step until now, it is a big change of habits. The good news is that younger users seem to prefer Linux, both my kids use it. Greetings, Manuela 2017-05-20 9:00 GMT+02:00 Andrew Bernard : > Hi Manuela, > > Well I think the reason newcomers use 2.18.2 is because the download page > strongly asserts that this is the latest stable version. > > More experienced users find the development versions very stable, of > course, but newcomers don't know that. > > The question that arises in my mind is why the OP is using Windows 7. :-) > > Andrew > > > > On 20 May 2017 at 15:55, Manuela Gößnitzer > wrote: > >> Is there any particular reason why you use 2.18 and not 2.19? Don't be >> afraid of the term "unstable version", it works fine :-). >> >> > ___ > 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
How exactly does "\transpose" work?
I had the idea that all that I needed to
do to convert a score from, for example, F to G,
was to wrap a \transpose f g { } around the
\relative block where I had entered the notes in
F. And that is actually correct.
But it seems that some really weird things happen
if, as I did recently, one screws up the order and
has:
theNotes = \relative c'' \transpose c d''{ {
some notes
}
}
I'm noting this it the hope that it may save someone else
the agro that I experienced with notes jumping
all over the place.
The order is *critical* to having transpose work as
expected.
This is sort-of a solution in search of a problem but
it may save someone else some frustration.
Cheers,
-Don
--
Don Gingrich
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond newbie can't compile
Hi Manuela, Well I think the reason newcomers use 2.18.2 is because the download page strongly asserts that this is the latest stable version. More experienced users find the development versions very stable, of course, but newcomers don't know that. The question that arises in my mind is why the OP is using Windows 7. :-) Andrew On 20 May 2017 at 15:55, Manuela Gößnitzer wrote: > Is there any particular reason why you use 2.18 and not 2.19? Don't be > afraid of the term "unstable version", it works fine :-). > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
