Re: Don't engrave measure symbol, actually now Browser differences
Thomas Morley writes: > I wrote too early. > Now Firefox saves the file and _then_ opens it with gedit. > > Not what I wanted. I have a hard time imagining how to open the text editor on a file that has not been saved. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Don't engrave measure symbol, actually now Browser differences
2013/2/21 Thomas Morley : > 2013/2/21 Nick Payne : >> On 21/02/13 11:59, Andrew Bernard wrote: >>> >>> Using Safari or Chrome, clicking lilypond documentation illustrations >>> displays the lilypond code used to produce them. Using Firefox or Opera, >>> these browsers offer to save the file. >>> >>> The browser behaviour is different regarding how they deal with an anchor >>> which is an image. It's not really a lilypond matter. >>> >>> I have a look into how we can make this cross-browser compliant. The >>> behaviour where the browser directly shows the code seems to be preferable. >> >> >> It's the same problem the other way around for the Lilypond installer shell >> scripts. Click on the download link for one of them in Firefox and it >> defaults to saving the script, which is the wanted behaviour. Click on the >> same link in Chrome and it defaults to opening the script in the browser >> window, which is not what is wanted. >> >> Nick > > To be more precise: I use Firefox on Ubuntu 10.04 > There must have been a change with some of the latest Firefox-updates. > > I was used to open clickable images from our documentation with gedit, > but recently noticed that it didn't work any more. > Although, I can click on images from > http://kainhofer.com/~lilypond/Documentation/notation-big-page.html#index > and Firefox still shows the code. > > After some research I managed to get back my old preferences: > > In Firefox: Edit->Preferences->Applications I found _two_ entries for > Lilypond: > LilyPond-Notenblatt (text/lilypond-source) > and > LilyPond-Notenblatt (text/x-lilypond) > > Setting `Action´ for _both_ to `Use gedit` restored the old behaviour. > > > Thanks, > Harm I wrote too early. Now Firefox saves the file and _then_ opens it with gedit. Not what I wanted. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Don't engrave measure symbol, actually now Browser differences
2013/2/21 Nick Payne : > On 21/02/13 11:59, Andrew Bernard wrote: >> >> Using Safari or Chrome, clicking lilypond documentation illustrations >> displays the lilypond code used to produce them. Using Firefox or Opera, >> these browsers offer to save the file. >> >> The browser behaviour is different regarding how they deal with an anchor >> which is an image. It's not really a lilypond matter. >> >> I have a look into how we can make this cross-browser compliant. The >> behaviour where the browser directly shows the code seems to be preferable. > > > It's the same problem the other way around for the Lilypond installer shell > scripts. Click on the download link for one of them in Firefox and it > defaults to saving the script, which is the wanted behaviour. Click on the > same link in Chrome and it defaults to opening the script in the browser > window, which is not what is wanted. > > Nick To be more precise: I use Firefox on Ubuntu 10.04 There must have been a change with some of the latest Firefox-updates. I was used to open clickable images from our documentation with gedit, but recently noticed that it didn't work any more. Although, I can click on images from http://kainhofer.com/~lilypond/Documentation/notation-big-page.html#index and Firefox still shows the code. After some research I managed to get back my old preferences: In Firefox: Edit->Preferences->Applications I found _two_ entries for Lilypond: LilyPond-Notenblatt (text/lilypond-source) and LilyPond-Notenblatt (text/x-lilypond) Setting `Action´ for _both_ to `Use gedit` restored the old behaviour. Thanks, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Don't engrave measure symbol, actually now Browser differences
On 21/02/13 11:59, Andrew Bernard wrote: Using Safari or Chrome, clicking lilypond documentation illustrations displays the lilypond code used to produce them. Using Firefox or Opera, these browsers offer to save the file. The browser behaviour is different regarding how they deal with an anchor which is an image. It's not really a lilypond matter. I have a look into how we can make this cross-browser compliant. The behaviour where the browser directly shows the code seems to be preferable. It's the same problem the other way around for the Lilypond installer shell scripts. Click on the download link for one of them in Firefox and it defaults to saving the script, which is the wanted behaviour. Click on the same link in Chrome and it defaults to opening the script in the browser window, which is not what is wanted. Nick ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [bug] \acciaccatura breaks a preceding tie in MIDI
On Feb 20, 2013 10:57 PM, "Jay Anderson" wrote: > > On Wed, Feb 20, 2013 at 7:28 AM, James Harkins wrote: > > I'm unsure if this is a known issue, or a new one. > > http://code.google.com/p/lilypond/issues/detail?id=3091 > > This probably won't be fixed in 2.16. That's fine. It isn't critical for me; it was just an odd behavior that seemed worth reporting. Thanks! hjh ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Don't engrave measure symbol
On 21/02/13 10:25, Thomas Morley wrote: 2013/2/20 Robert Schmaus : So, if you would like to use a certain example from the documentation, click on it and check out that code. BTW, for me this doesn't work no longer with our official documentation. At least, it doesn't work out of the box. Though, it works with http://kainhofer.com/~lilypond/Documentation/notation-big-page.html Can someone confirm? Works ok for me with Chrome on Linux. Clicking on any of the musical examples loads the ly code for the example. Nick ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Don't engrave measure symbol, actually now Browser differences
Using Safari or Chrome, clicking lilypond documentation illustrations displays the lilypond code used to produce them. Using Firefox or Opera, these browsers offer to save the file. The browser behaviour is different regarding how they deal with an anchor which is an image. It's not really a lilypond matter. I have a look into how we can make this cross-browser compliant. The behaviour where the browser directly shows the code seems to be preferable. How amusing life would be if we had browsers that were standards compliant. Andrew On 21/02/13 10:25 AM, Thomas Morley wrote: 2013/2/20 Robert Schmaus : So, if you would like to use a certain example from the documentation, click on it and check out that code. BTW, for me this doesn't work no longer with our official documentation. At least, it doesn't work out of the box. Though, it works with http://kainhofer.com/~lilypond/Documentation/notation-big-page.html Can someone confirm? Did we change something? -Harm ___ 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: Console warning "rhythmic head is not part of a rhythmic column"
Am 19.02.2013 07:46, schrieb Robert Schmaus: please always answer to the list, so everybody can follow what's going on! I know - and I usually do (that's why I've re-sent my answer to the list right away). I seem to belong to that fraction of list contributors who struggle with the concept of "clicking 'Reply' replies to the sender only". I know I'm not alone ... for me only nabble acts correctly (or if I answer from a mailer) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Don't engrave measure symbol
Thomas Morley wrote > 2013/2/20 Robert Schmaus < > robert.schmaus@ > >: >> So, if you would like to use a certain example from the >> documentation, click on it and check out that code. > > BTW, for me this doesn't work no longer with our official documentation. > At least, it doesn't work out of the box. > Though, it works with > http://kainhofer.com/~lilypond/Documentation/notation-big-page.html > > Can someone confirm? > Did we change something? for me it does - I'm not always happy with the choice: save or run… sometimes it just displays the code in opera (which I'd prefer) but I'm not sure if this is because of my browser settings or if LilyPond only proposes these actions Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Don-t-engrave-measure-symbol-tp141212p141227.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: cadenzaOn / Off don't work
David Kastrup wrote > Eluze < > eluzew@ > > writes: >> >> /beams/ are removed > > Hardly. Autobeaming is switched off, so you get only beams for manual > beaming. But that does not mean that the beams are "removed": rather > you get the default flags which are also used on isolated notes. I was addressing the possibility that Sávio Ramos might have confounded stems and beams (and I didn't want to go into technical details) - if so he got a hint otherwise he will/can specify what he meant specifically. Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/cadenzaOn-Off-don-t-work-tp141213p141226.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: Don't engrave measure symbol
2013/2/20 Robert Schmaus : > So, if you would like to use a certain example from the > documentation, click on it and check out that code. BTW, for me this doesn't work no longer with our official documentation. At least, it doesn't work out of the box. Though, it works with http://kainhofer.com/~lilypond/Documentation/notation-big-page.html Can someone confirm? Did we change something? -Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cadenzaOn / Off don't work
Eluze writes: > Nathan wrote >> On Wed, Feb 20, 2013 at 9:11 AM, Sávio Ramos < > >> savio.debian@ > >> > wrote: >> >>> Hello, >>> >>> The command \cadenzaOn \cadenzaOff don't remove stem. >>> >>> >> They shouldn't. They only affect timing, not the appearance of notes. >> >> To hide stems, use >> >> \override Stem #'stencil = ##f > > /beams/ are removed Hardly. Autobeaming is switched off, so you get only beams for manual beaming. But that does not mean that the beams are "removed": rather you get the default flags which are also used on isolated notes. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cadenzaOn / Off don't work
Nathan wrote > On Wed, Feb 20, 2013 at 9:11 AM, Sávio Ramos < > savio.debian@ > > wrote: > >> Hello, >> >> The command \cadenzaOn \cadenzaOff don't remove stem. >> >> > They shouldn't. They only affect timing, not the appearance of notes. > > To hide stems, use > > \override Stem #'stencil = ##f /beams/ are removed Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/cadenzaOn-Off-don-t-work-tp141213p141219.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: Vertical spacing between verses
Szász Károly-Zsolt wrote > Hello, > please help me adjust the space between the verses. My problem is that > there's a well seeing difference between the white space after the 1st and > the white space after the 2nd verse. How can I change the distance between > the verses equally, no matter what kind of letters I use? > Here's the code I use: > > \override VerticalAxisGroup #'nonstaff-nonstaff-spacing = > #'((basic-distance . 0.6 ) > (minimum-distance . 0.6 ) > (padding . 0.6 ) > (stretchability . 0)) what's wrong with using the default settings of LilyPond? (also for the other override of VerticalAxisGroup) Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Vertical-spacing-between-verses-tp141187p141218.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: cadenzaOn / Off don't work
On Wed, Feb 20, 2013 at 9:11 AM, Sávio Ramos wrote: > Hello, > > The command \cadenzaOn \cadenzaOff don't remove stem. > > They shouldn't. They only affect timing, not the appearance of notes. To hide stems, use \override Stem #'stencil = ##f Regards, Nathan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Don't engrave measure symbol
I want to do a staff without the measure symbol like above: http://www.lilypond.org/doc/v2.15/Documentation/source/Documentation/essay/building-software#music-representation I am using 2.14 lilypond. Hi Savio, those examples in the documentation can be clicked - they will then reveal their source code. So, if you would like to use a certain example from the documentation, click on it and check out that code. Best way to learn, too! Just make sure that you are either using a documentation that either belongs to your Lilypond version or (even better) upgrade to the latest stable version. Best, Robert ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cadenzaOn / Off don't work
Sávio Ramos writes: > Hello, > > The command \cadenzaOn \cadenzaOff don't remove stem. Is there a reason they should? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
cadenzaOn / Off don't work
Hello,
The command \cadenzaOn \cadenzaOff don't remove stem.
\version "2.14.2"
\header{
title = "Voz Tenor"
}
\score{
\new Staff \with { \remove "Time_signature_engraver" }
{
\time 4/4
\key c \major
\clef bass
\cadenzaOn
bes,4 d1 \glissando g' c''4
\cadenzaOff
}
\layout{ \context {\Score}}
\midi{}
}
--
Sávio M Ramos
Arquiteto, Rio, RJ
Só uso Linux desde 2000
www.debian.org
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Don't engrave measure symbol
Hello, I want to do a staff without the measure symbol like above: http://www.lilypond.org/doc/v2.15/Documentation/source/Documentation/essay/building-software#music-representation I am using 2.14 lilypond. Thanks. -- Sávio M Ramos Arquiteto, Rio, RJ Só uso Linux desde 2000 www.debian.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [bug] \acciaccatura breaks a preceding tie in MIDI
On Wed, Feb 20, 2013 at 7:28 AM, James Harkins wrote: > I'm unsure if this is a known issue, or a new one. http://code.google.com/p/lilypond/issues/detail?id=3091 This probably won't be fixed in 2.16. -Jay ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \slashedGrace forces a downward slur?
James Harkins writes:
> Another question: Is it possible to begin a slur on a slashedGrace,
> and change the slur's direction to be upward?
>
> \slurUp has no effect. The printed score here looks funny, since most
> of the notes under the slur have downward stems -- so I'd expect the
> slur to be above.
>
> \version "2.16.1"
> \relative c'' { \slurUp d4. \slashedGrace e16 ( d8 b4 d4 ) }
\version "2.16.1"
\relative c'' { d4. \slashedGrace e16^( d8 b4 d4 ) }
works fine here.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
\slashedGrace forces a downward slur?
Another question: Is it possible to begin a slur on a slashedGrace,
and change the slur's direction to be upward?
\slurUp has no effect. The printed score here looks funny, since most
of the notes under the slur have downward stems -- so I'd expect the
slur to be above.
\version "2.16.1"
\relative c'' { \slurUp d4. \slashedGrace e16 ( d8 b4 d4 ) }
Hm, I wonder what that would do to a multi-voice example. Probably ugly.
hjh
--
James Harkins /// dewdrop world
jamshar...@dewdrop-world.net
http://www.dewdrop-world.net
"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
[bug] \acciaccatura breaks a preceding tie in MIDI
I'm unsure if this is a known issue, or a new one.
If an \acciaccatura immediately follows a tie, the printed score looks
right, but MIDI renders without the tie.
\version "2.16.1"
\score {
\new Staff \relative c'' { g4 g4 ~ g8 \acciaccatura b16 a8 g4 }
\layout {}
\midi {}
}
Examining the MIDI using SuperCollider (+ wslib extensions):
m = SimpleMIDIFile.read("/home/dlm/Documents/ly/tests/13-02-20-bugs.midi");
// .select removes note-off events, i.e., notes with velocity == 0
m.noteOnEvents(0, 1).select({ |ev| ev.last > 0 }).do(_.postln); ""
[ 1, 0, noteOn, 0, 67, 90 ]
[ 1, 384, noteOn, 0, 67, 90 ]
[ 1, 768, noteOn, 0, 67, 90 ]<<-- this is the ~g8 -- it shouldn't be here
[ 1, 938, noteOn, 0, 71, 90 ]
[ 1, 960, noteOn, 0, 69, 90 ]
[ 1, 1152, noteOn, 0, 67, 90 ]
hjh
--
James Harkins /// dewdrop world
jamshar...@dewdrop-world.net
http://www.dewdrop-world.net
"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problems with download.linuxaudio.org?
On Feb 20, 2013, at 9:22 AM, David Kastrup wrote: > James Harkins writes: > >> What I did to get to this point: >> >> 1. Cloned the repository. Checked out the tag release/2.16.2-1, and >> then "git checkout -b hjh2.16.2" (because I don't like staying >> somewhere earlier than the head of a branch for too long). >> >> 2. sudo apt-get build-dep lilypond >> >> 3. ./autogen.sh --noconfigure >> >> 4. mkdir build/ && cd build/ >> >> 5. mkdir ../myinstall >> >> 6. ../configure --prefix=$HOME/share/lilypond/myinstall > > You are missing "make" here, and while I have not checked, I'd be > somewhat surprised if the --prefix option worked reliably: I don't think > people test it much. --prefix works perfectily fine for me on OSX ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fwd: Problems with download.linuxaudio.org?
David Kastrup gnu.org> writes: > First make, then make install. Quite right -- "make install" did actually compile some of it, though, so I thought it was OK. I'll remember that for next time. "make" on its own did complete successfully, thanks. > > 6. ../configure --prefix=$HOME/share/lilypond/myinstall > > You are missing "make" here, and while I have not checked, I'd be > somewhat surprised if the --prefix option worked reliably: I don't think > people test it much. The prefix seems promising so far, but I'll be alert for problems. Thanks! hjh $ cd ../myinstall/bin $ ls abc2ly etf2lylilypond lilypond-invoke-editor midi2ly convert-ly lilymidi lilypond-book lilysongmusicxml2ly $ ./lilypond --version GNU LilyPond 2.16.1 Copyright (c) 1996--2012 by Han-Wen Nienhuys Jan Nieuwenhuizen and others. This program is free software. It is covered by the GNU General Public License and you are welcome to change it and/or distribute copies of it under certain conditions. Invoke as `lilypond --warranty' for more information. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problems with download.linuxaudio.org?
James Harkins writes: > I just tried to download this: > > http://download.linuxaudio.org/lilypond/binaries/linux-64/lilypond-2.16.2-1.linux-64.sh > > But download.linuxaudio.org is almost totally unresponsive. After a > few minutes of watching the estimated time remaining climb from 18 > hours to *4 days*, I gave up. The linuxaudio site went down on 5th January this year, reported by Francesco here: http://lists.gnu.org/archive/html/bug-lilypond/2013-01/msg00036.html It was back up again a few hours later. Cheers, Colin. -- Colin Hall ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 19th-cent. accidental notation
Am 20.02.2013 11:22, schrieb Nick Payne: On 20/02/13 20:33, Urs Liska wrote: [...] There actually _are_ such ideas and attempts. At least the Reger Edition has already started publishing digital editions. And there is more research going on. I also once read about a huge project (sponsored by HP I think) to make all works of Mozart digitally available for anybody (I think it is targeted at ca. 2020 ...), but I don't know if they are thinking in such categories or if they merely want to provide scans of existing editions). The Mozart works are here: http://dme.mozarteum.at/DME/main/index.php?l= Ah, thanks for this reminder. English version is http://dme.mozarteum.at/DME/main/index.php?l=2 Looks like they are going to do exactly what we were talking about here. ___ 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
Changing the SpanBar for a single staff
Dear LilyPond users,
I am trying to add an analysis staff above a PianoStaff group to which
its bar lines are connected with a dotted SpanBar. Since the SpanBar
appears to only live in a context for staffgroups (PianoStaff,
ChoirStaff etc) there appears to be no way to add one to a lone staff.
My best attempt is to include the PianoStaff inside a StaffGroup and set
different SpanBars for each one, but the result is that the PianoStaff
prints both SpanBars on top of eachother (the code for this is at the
bottom of the email). My various attempts to alter the SpanBar for a
single staff have no effect. I would appreciate any help!
\version "2.16.1"
\score {
\new StaffGroup \with {
\remove "System_start_delimiter_engraver"
\override SpanBar #'glyph-name = #":"
}
<<
\new Staff { c'1 }
\new PianoStaff \with {
\override SpanBar #'glyph-name = #"|" }
<<
\new Staff { c' }
\new Staff { c' }
>>
>>
}
Regards,
Kevin Barry
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Vertical spacing between verses
Hello,
please help me adjust the space between the verses. My problem is that
there's a well seeing difference between the white space after the 1st and
the white space after the 2nd verse. How can I change the distance between
the verses equally, no matter what kind of letters I use?
Here's the code I use:
\override VerticalAxisGroup #'nonstaff-nonstaff-spacing =
#'((basic-distance . 0.6 )
(minimum-distance . 0.6 )
(padding . 0.6 )
(stretchability . 0))
And here is the content of the *.ly file:
\version "2.12.3"
strofaI= \lyricmode {
\set stanza = "1."
El -- ső vers -- szak el -- ső vers -- szak el -- ső vers -- szak el -- ső
vers -- szak el -- ső vers -- szak el -- ső vers -- szakel -- ső vers --
szak
}
strofaII= \lyricmode {
\set stanza = "2."
Má -- so -- dik, itt már jé és gé is van, eb -- ben már jé és gé is van,
eb -- ben már jé és gé is van, eb -- ben már jé és gé is van,
}
strofaIII= \lyricmode {
\set stanza = "3."
Itt a hi -- ba, mert Ő is, Ő is, Ő is van benne, Ő is, Ő is, Ő is van
benne, Ő is, Ő is, Ő is van benne, Ő is, Ő is, Ő is van benne,
}
strofaIV= \lyricmode {
\set stanza = "4."
A vers -- sza -- kok köz -- ti tá -- vol -- ság így már nem egy -- for -- ma
így már nem egy -- for -- ma így már nem egy -- for -- ma
}
partitura = \new ChoirStaff {
<< \new Staff { \numericTimeSignature \set Staff.midiInstrument="choir aahs"
\clef treble
\time 3/4
\key es \major
<< \context Voice = "Soprana" \transpose d es { \relative c' { \voiceOne
\override Script #'padding = #0.5
\override Score.BarNumber #'break-visibility = #all-invisible
d4
fis e d( a') g fis4. e8 fis[ g] fis4 e a4\rest
e4 a cis \break
d4. b8 cis[ a] e4( cis') b a2 a4\rest d,4 fis e d( a') g \break
\bar "|."
} }
\context Voice = "Alto" \transpose d es { \relative c' { \voiceTwo
d d cis d2 e4 d4. cis8 d[ e] d4 cis s4 cis e e
d4. e8 e[ e] cis4( e) d cis2 s4 d d cis d2 e4
} }
>>
}
\context Lyrics = "lmelodySATLI" { c }
\override VerticalAxisGroup
#'nonstaff-relatedstaff-spacing =
#'((basic-distance . 2 )
(minimum-distance . 1 )
(padding . 1 )
(stretchability . 8 ))
\context Lyrics = "lmelodySATLII" { d }
\context Lyrics = "lmelodySATLIII" { e }
\context Lyrics = "lmelodySATLIV" { f }
\new Staff { \set Staff.midiInstrument="choir aahs" \numericTimeSignature
\clef bass
\key es \major
<< \context Voice = "Tenor" \transpose d es { \relative c { \voiceOne
fis4 a g fis2 a4 a4. a8 a[ b] a4 a c,4\rest a'4 a a
fis8[( e)] fis([ gis)] a8 a a2 gis4 e2 c4\rest fis4 a g
fis2 a4
} }
\context Voice = "Bass" \transpose d es { \relative c { \voiceTwo
\override Script #'padding = #0.5
d4 d a d2 cis4 d8[( e)] fis([ g]) fis[ e] a4 a, s4 a cis a
b4. e8 a,[ cis] e2 e4 a,2 s4 d4 d a d2 cis4
} } >>
}
>>
}
\score { << \partitura
\context Lyrics = "lmelodySATLI" \lyricmode { \lyricsto
"Soprana"
\strofaI }
\context Lyrics = "lmelodySATLII" \lyricmode { \lyricsto
"Soprana"
\strofaII }
\context Lyrics = "lmelodySATLIII" \lyricmode { \lyricsto
"Soprana"
\strofaIII }
\context Lyrics = "lmelodySATLIV" \lyricmode { \lyricsto
"Soprana" \strofaIV }
>>
\midi { }
\layout { indent = 0\mm
\context { \Lyrics \override VerticalAxisGroup
#'nonstaff-nonstaff-spacing
=
#'((basic-distance . 0.6 )
(minimum-distance . 0.6 )
(padding . 0.6 )
(stretchability . 0))
\override LyricSpace #'minimum-distance = #0.5 } }
\header {
}
}
\paper { }
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Vertical-spacing-between-verses-tp141187.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: 19th-cent. accidental notation
On 20/02/13 20:33, Urs Liska wrote: [...] There actually _are_ such ideas and attempts. At least the Reger Edition has already started publishing digital editions. And there is more research going on. I also once read about a huge project (sponsored by HP I think) to make all works of Mozart digitally available for anybody (I think it is targeted at ca. 2020 ...), but I don't know if they are thinking in such categories or if they merely want to provide scans of existing editions). The Mozart works are here: http://dme.mozarteum.at/DME/main/index.php?l= ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 19th-cent. accidental notation
Am 19.02.2013 18:58, schrieb Luca Rossetto Casel: Il 19/02/2013 15:13, Urs Liska ha scritto: But OTOH it is impossible to make a perfect edition. [...] Again, in cases of similar complexity I find quite necessary to acclude a critical report to the score. Yes, but it really isn't possible to make it perfect in the sense that it suits every possible use case. First: There are nearly always aspects in the material that are just one step more detailed than you would want to deal with. Just one example: It is often important to determine the order of writing in the manuscript, especially when it comes to corrections (e.g. to state that a changed pitch is just an immediately corrected typo and not a change applied later (which could indicate that it's a change rather than a fix)). You usually do this by noticing different used inks/pencils or sometimes thanks to different character of the handwriting (e.g. hasty/accurate). You just _can't_ document everything that leads to your conclusion in each and every case. Second: If you try very hard to document everything you will get an edition that is so complex that the information is actually buried within an intransparent bunch of comments. The Schoenberg Edtion for example tries to be as precise and exhaustive as possible in its critical reports, but it really isn't nice to work with them ... I find the approach of the Schubert Edition quite useful (in general). They have a foreword in each volume. There you can find general information on the works and also comments on the situation of the sources, if they are of some general interest. At the end of each volume (or in a 'b' volume) there is a section 'sources and versions (Lesarten)' that states in detail which sources have been used and gives information on editorial decisions - but only those that the editors thought to be of interest for the average user. Finally there is the Critical Report which should document _everything_ short of found fingerprints on the manuscripts ;-). The Critical Report originally wasn't part of the regular edition that you can buy or subscribe to, but by now you can also buy them separately. Now to the editorial problem (we are talking about): Of course the New Edition marks all editor's addition typographically. But a) printing staccato dots and accents smaller than normal is a quite unnoticeable style. And b) (much more important) the New Edition takes the manuscript and the original edition as its main sources. So additions by the original engraver are taken as _original material_ and thus not marked in the New Edition. While I realized (through the study of the manuscript) that the original edition presumably made a lot of problematic additions this isn't visible in the New Edition at all. I can only hope that this fact is described in the Critical Report (which I haven't inspected yet). But as the Critical Report isn't actually part of the books and only available in some libraries, the information in it is really buried quite far away. THe approach you describe here is the one I personally chose for my edition. By the way, I also managed - I think - to print smaller, but distinguable, scripts quite well! I slightly increased their distance from the noteheads to give the scripts a clearly, more visible appearence; I also adopted a quite large spacing to make all as clear as possible, even with a quite small font. Would you mind sending me a screenshot of an example? Regarding the problem of the Critica Report, I can see it's somehow not immediately visible - or even note immediately reachable, as you point out. But I think it's anyway the better compromise... in a printed score. Providing the edition in a digital format, as an interactive pdf (or other), it would be possible display the variants of all the adopted sources on our score, making every change visible. It's becoming a common practice in literarature studies, why not apply to music philology? As an example, see this project related to Metastasio's works: http://www.progettometastasio.it/pietrometastasio/ There actually _are_ such ideas and attempts. At least the Reger Edition has already started publishing digital editions. And there is more research going on. I also once read about a huge project (sponsored by HP I think) to make all works of Mozart digitally available for anybody (I think it is targeted at ca. 2020 ...), but I don't know if they are thinking in such categories or if they merely want to provide scans of existing editions). [...] While I'm quite happy with the solutions and know that we don't change the musical text, I can't know if the (originally used) reminder accidentals might become meaningful to someone who later studies the edition. On the other hand we decided to mark the accidentals that we identified as musically wrong by parentheses. (BTW any idea how one could highlight the _emendation_ of an accidental (or any
Re: Fwd: Problems with download.linuxaudio.org?
James Harkins writes: > What I did to get to this point: > > 1. Cloned the repository. Checked out the tag release/2.16.2-1, and > then "git checkout -b hjh2.16.2" (because I don't like staying > somewhere earlier than the head of a branch for too long). > > 2. sudo apt-get build-dep lilypond > > 3. ./autogen.sh --noconfigure > > 4. mkdir build/ && cd build/ > > 5. mkdir ../myinstall > > 6. ../configure --prefix=$HOME/share/lilypond/myinstall You are missing "make" here, and while I have not checked, I'd be somewhat surprised if the --prefix option worked reliably: I don't think people test it much. > 7. make install First make, then make install. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
