Re: Mutopia?
Paul Hodges writes: > The variation in content of these mirror sites is sufficiently explained by > this quote from the top of the ca one: > > > All the functionality of the original Mutopia site has been restored, and the > piece count will continue to increase as projects are restored from the > Wayback Archive. Full restoration (~2200 pieces) is anticipated to be > completed in April. New developments will be posted here in this space. Given that the scores' GitHub project is still fully accessible at https://github.com/chrissawer/The-Mutopia-Project.git one has to wonder what they need the Wayback Archive for. -- David Kastrup
Re: Mutopia?
The variation in content of these mirror sites is sufficiently explained by this quote from the top of the ca one: All the functionality of the original Mutopia site has been restored, and the piece count will continue to increase as projects are restored from the Wayback Archive. Full restoration (~2200 pieces) is anticipated to be completed in April. New developments will be posted here in this space. Paul From: Mats Bengtsson To: Cc: Sent: 31/03/2022 15:05 Subject: Re: Mutopia? On 2022-03-31 11:38, Silvain Dupertuis wrote: Would it be that everything is now on this page: https://www.ibiblio.org/mutopia/ Sincerely That seems like an extremely outdated site "Latest additions ... 2010...". Rather, try https://scores.omet.ca/ with the alternative interface https://mutopia.omet.ca/, see https://www.mail-archive.com/mutopia-discuss@mutopiaproject.org/msg00535.html Having written this, I happened to find http://eremita.di.uminho.pt/mutopia/ this is unmaintained but seems to contain contributions up to 2019, whereas https://mutopia.omet.ca/ says "Latest additions ... 2018...". I include a Cc: to the maintainer of https://mutopia.omet.ca/, perhaps it's possible the use the full database from the http://eremita.di.uminho.pt/mutopia/. /Mats
Re: Mutopia?
On 2022-03-31 11:38, Silvain Dupertuis wrote: Would it be that everything is now on this page: https://www.ibiblio.org/mutopia/ Sincerely That seems like an extremely outdated site "Latest additions ... 2010...". Rather, try https://scores.omet.ca/ with the alternative interface https://mutopia.omet.ca/, see https://www.mail-archive.com/mutopia-discuss@mutopiaproject.org/msg00535.html Having written this, I happened to find http://eremita.di.uminho.pt/mutopia/ this is unmaintained but seems to contain contributions up to 2019, whereas https://mutopia.omet.ca/ says "Latest additions ... 2018...". I include a Cc: to the maintainer of https://mutopia.omet.ca/, perhaps it's possible the use the full database from the http://eremita.di.uminho.pt/mutopia/. /Mats
Re: Mutopia?
Would it be that everything is now on this page: *https://www.ibiblio.org/mutopia/* <https://www.ibiblio.org/mutopia/> Sincerely Silvain Le 31.03.22 à 10:20, David Kastrup a écrit : Calvin Ransom writes: Does anyone know what's going on with the mutopia project servers? I haven't been able to access the website recently. I just get a server error message. https://www.mutopiaproject.org Calvin Ransom GitHub page is still there, last commit Oct 31, 2019. <https://github.com/MutopiaProject/MutopiaProject> The last activity of Chris Sawer on GitHub overall was in 2020. His Twitter account athttps://twitter.com/cjsawer however appears still active. Maybe try contacting him via GitHub? -- Silvain Dupertuis Route de Lausanne 335 1293 Bellevue (Switzerland) tél. +41-(0)22-774.20.67 portable +41-(0)79-604.87.52 web: silvain-dupertuis.org <https://perso.silvain-dupertuis.org>
Re: Mutopia?
Calvin Ransom writes: > Does anyone know what's going on with the mutopia project servers? I > haven't been able to access the website recently. I just get a server > error message. > https://www.mutopiaproject.org > > Calvin Ransom GitHub page is still there, last commit Oct 31, 2019. <https://github.com/MutopiaProject/MutopiaProject> The last activity of Chris Sawer on GitHub overall was in 2020. His Twitter account at https://twitter.com/cjsawer however appears still active. Maybe try contacting him via GitHub? -- David Kastrup
Mutopia?
Does anyone know what's going on with the mutopia project servers? I haven't been able to access the website recently. I just get a server error message. https://www.mutopiaproject.org Calvin Ransom
Re: Syntax error encountered while engraving a successfully updated Mutopia ly file
Aaron Hill writes: > convert-ly knows how to fix this: > > > \override Thing #'property #'sub-property = #'value > % ...to... > \override Thing.property.sub-property = #'value > > > It does not however seem to correct: > > > variable #'key = #'value > % ...to... > variable.key = #'value > commit 10df1245877fb5e16410388ef42b71c9aa06a9d9 Author: David Kastrup Date: Mon Mar 30 00:49:14 2020 +0200 Issue 5872: convert-ly rule for 2.19.39 as cleanup for issue 4800 That issue made previously valid and promoted code invalid without proper replacement. Property assignments of the form staffgroup-staff-spacing #'basic-distance = #15 are converted to staffgroup-staff-spacing.basic-distance = #15 for various paper or layout spacing variables. The problem is that this convert-ly rule was done rather late and so you need at least convert-ly from 2.21.0 to get this right. So if you used an older convert-ly for getting your version across 2.19.39, this convert-ly fix will no longer get applied. The good news should be that the given score should work in 2.21.x+ again assuming that you convert it all the way from its ancient version with the new convert-ly. Of course it would also work in 2.20 if you use the latest convert-ly to go just up to 2.20. But who does that? -- David Kastrup
Re: maple leaf rag mutopia
Werner LEMBERG writes: >> Always a bit of a risk to change the call signature of existing >> exported functions. It may be called by more than just >> \unfoldRepeats , with \applyMusic only being a somewhat weird old >> use case. > > Ok. Do you have a better suggestion? Maybe a warning in > `convert-ly`? Frankly, my suggestion would be to make the call-signature of unfold-repeats upwards compatible (optional argument comes last and is actually optional). Of course at the cost of breaking every caller introduced since the change. -- David Kastrup
Re: maple leaf rag mutopia
> Always a bit of a risk to change the call signature of existing > exported functions. It may be called by more than just > \unfoldRepeats , with \applyMusic only being a somewhat weird old > use case. Ok. Do you have a better suggestion? Maybe a warning in `convert-ly`? Werner
Re: maple leaf rag mutopia
Werner LEMBERG writes: > From: David Kastrup > Subject: Re: maple leaf rag mutopia > Date: Tue, 27 Apr 2021 13:31:22 +0200 > >> Werner LEMBERG writes: >> >>>>> Replace \applyMusic #unfold-repeats with \unfoldRepeats ? >>> >>> Missing `convert-ly` rule? >> >> Last examples of \applyMusic #unfold-repeats were removed with [...] >> >> So it's a bit tricky to guess just where to apply a convert-ly rule >> and what it should do. > > Well, after the introduction of `\unfoldRepeats`, is there any other > possibility to use `\applyMusic #unfold-repeats`? Otherwise a rule > for version 2.5.26 might do the trick IMHO. It continued to work until commit ece789bf5f661cb8f16b50f87a248dedd6e1d8d5 Author: Thomas Morley Date: Thu Dec 1 22:38:54 2016 +0100 Issue 5003 unfoldRepeats can be restricted to certain repeat-types It now takes an additional, optional argument. It's a list of symbols representing the repeat-types which should be unfolded. Possible settings are percent, tremolo and volta. The default is an empty list, for which repeated-music is taken, unfolding all. A new regtest is added to cover the new feature. Changes is extended accordingly. Also correcting two small typos in Documentation/notation/staff.itely Always a bit of a risk to change the call signature of existing exported functions. It may be called by more than just \unfoldRepeats , with \applyMusic only being a somewhat weird old use case. -- David Kastrup
Re: maple leaf rag mutopia
From: David Kastrup Subject: Re: maple leaf rag mutopia Date: Tue, 27 Apr 2021 13:31:22 +0200 > Werner LEMBERG writes: > >>>> Replace \applyMusic #unfold-repeats with \unfoldRepeats ? >> >> Missing `convert-ly` rule? > > Last examples of \applyMusic #unfold-repeats were removed with [...] > > So it's a bit tricky to guess just where to apply a convert-ly rule > and what it should do. Well, after the introduction of `\unfoldRepeats`, is there any other possibility to use `\applyMusic #unfold-repeats`? Otherwise a rule for version 2.5.26 might do the trick IMHO. Werner.
Re: maple leaf rag mutopia
Werner LEMBERG writes: >>> Replace \applyMusic #unfold-repeats with \unfoldRepeats ? > > Missing `convert-ly` rule? Last examples of \applyMusic #unfold-repeats were removed with commit 96dbe62b86c3c10d236965730fcbe56571505324 Author: Neil Puttock Date: Thu Apr 8 23:27:59 2010 +0100 Fix #348. * input/regression/repeat-unfold-tremolo.ly: emend snippet to test for single element in braces * scm/music-functions.scm (unfold-repeats): only add extra shift to duration-log if there are two children in 'elements \unfoldRepeats exists since commit 8a7aceb09dd209167281715af1077ec4135fe359 Author: Han-Wen Nienhuys Date: Wed May 25 09:04:08 2005 + * scripts/convert-ly.py (conv): unfoldrepeats -> unfoldRepeats, compressmusic -> compressMusic. * ly/music-functions-init.ly (oldaddlyrics): idem. and before that already was \unfoldrepeats . So it's a bit tricky to guess just where to apply a convert-ly rule and what it should do. -- David Kastrup
Re: maple leaf rag mutopia
>> Replace \applyMusic #unfold-repeats with \unfoldRepeats ? Missing `convert-ly` rule? Werner
Re: maple leaf rag mutopia
> > Replace \applyMusic #unfold-repeats with \unfoldRepeats ? > Yes, now it works fantastically :) Grazie! g.
Re: maple leaf rag mutopia
Gianmaria Lari writes: > Hello, > > I'm trying to engrave Maple Leaf Rag from mutopia. It has been written > with LilyPond, version 2.14.2. > I converted it using "Tools/Update with convert-ly" (in Frescobaldi) but > when I try to engrave it I get this error message: > > Parsing...C:/Program Files > (x86)/LilyPond/usr/share/lilypond/current/ly/music-functions-init.ly:155:4 > <0>: In procedure unfold-repeats in expression (func music): > > C:/Program Files > (x86)/LilyPond/usr/share/lilypond/current/ly/music-functions-init.ly:155:4 > <1>: Wrong number of arguments to # > > > Any suggestions? Replace \applyMusic #unfold-repeats with \unfoldRepeats ? -- David Kastrup
maple leaf rag mutopia
Hello,
I'm trying to engrave Maple Leaf Rag from mutopia. It has been written
with LilyPond, version 2.14.2.
I converted it using "Tools/Update with convert-ly" (in Frescobaldi) but
when I try to engrave it I get this error message:
Parsing...C:/Program Files
(x86)/LilyPond/usr/share/lilypond/current/ly/music-functions-init.ly:155:4
<0>: In procedure unfold-repeats in expression (func music):
C:/Program Files
(x86)/LilyPond/usr/share/lilypond/current/ly/music-functions-init.ly:155:4
<1>: Wrong number of arguments to #
Any suggestions?
Attached the source file.
Thanks, g.
\version "2.23.2"
\header {
title = "Maple Leaf Rag"
composer = "Scott Joplin"
piece = "Tempo di marcia"
mutopiatitle = "Maple Leaf Rag"
mutopiacomposer = "JoplinS"
mutopiainstrument = "Piano"
date = "c. 1899"
style = "Jazz"
copyright = "Public Domain"
source = "Reproduction of original edition (1899)"
maintainer = "Chris Sawer"
maintainerEmail = "ch...@mutopiaproject.org"
maintainerWeb = "http://cjsawer.whitewillow.co.uk/;
footer = "Mutopia-2011/11/13-23"
tagline = \markup { \override #'(box-padding . 1.0) \override #'(baseline-skip . 2.7) \box \center-column { \small \line { Sheet music from \with-url "http://www.MutopiaProject.org; \line { \teeny www. \hspace #-0.5 MutopiaProject \hspace #-0.5 \teeny .org \hspace #0.5 } • \hspace #0.5 \italic Free to download, with the \italic freedom to distribute, modify and perform. } \line { \small \line { Typeset using \with-url "http://www.LilyPond.org; \line { \teeny www. \hspace #-0.5 LilyPond \hspace #-0.5 \teeny .org } by \maintainer \hspace #-0.6 . \hspace #0.5 Reference: \footer } } \line { \teeny \line { This sheet music has been placed in the public domain by the typesetter, for details see: \hspace #-0.5 \with-url "http://creativecommons.org/licenses/publicdomain; http://creativecommons.org/licenses/publicdomain } } } }
}
\paper {
top-margin = 15
bottom-margin = 10
min-systems-per-page = #4
max-systems-per-page = #5
system-system-spacing.padding = #8
}
top = \relative c' {
\override TextScript.padding = #2
\key as \major
\time 2/4
\clef treble
\partial 8
r8 \f |
\repeat volta 2 {
r16 as' as, c 8 g,16 |
16 g, bes ~ 4 |
r16 as, as, c 8 g,16 |
16 g, bes ~ 8 r16 |
r16 as, ces r16 r16 |
r16 as, ces r16 r8 |
\change Staff = "down"
\stemUp r16^\p as,,,-( ces as'-) r as-( ces as'-) \stemNeutral |
\change Staff = "up"
r16 as-( ces as'-) r as-( ces as'-) |
8-\mf \< 16 ~ |
\! es f c es 8 16 ~ |
bes as bes 8 as16 |
as 8 r16 ~ |
8 16 ~ |
es c es 8 16 ~ |
bes as bes 8 as16 |
} \alternative {
{ as 8 r8 }
{ 16 as 8 r8 }
}
\break
\repeat volta 2 {
r16_\markup {\dynamic f \italic "stacc."} g' g, bes 8 g,16 |
g, bes ~ es, es, |
r c c, es 8 c16 |
c, es ~ c 8 |
r16 es bes, des 8 es16 |
bes, des ~ des 8 |
r16 c c, es 8 c16 |
c, es ~ c 8 |
r16 g g, bes 8 g,16 |
g, bes ~ es, es, |
r c c, es 8 c16 |
8|
r16 f, a c f c a f |
r f bes des 8 |
r16 r 8 es,16 |
} \alternative {
{ 8}
{ r16 as, c es 8 r }
}
r16-\f as, as, c 8 g,16 |
16 g, bes ~ 4 |
r16 as, as, c 8 g,16 |
16 g, bes ~ 8 r16 |
r16 as, ces r16 r16 |
r16 as, ces r16 r8 |
\change Staff = "down"
\stemUp r16^\p as,,,-( ces as'-) r as-( ces as'-) \stemNeutral |
\change Staff = "up"
r16 as-( ces as'-) r as-( ces as'-) |
8-\mf \< 16 ~ |
\! es f c es 8 16 ~ |
bes as bes 8 as16 |
as 8 r16 ~ |
8 16 ~ |
es c es 8 16 ~ |
bes as bes 8 as16 |
as 8 |
\key des \major
\repeat volta 2 {
8.^\markup {\large "TRIO"} 16 ~ 16 bes8 |
8. 16 ~ 16 bes |
as, des bes des f as, des f |
bes, des f as, ~ as f' bes, f' |
8. 16 ~ 16 bes8 |
8. 16 ~ 16 bes |
as, des bes des f as, des f |
bes, des f as, ~ as f' a, |
8. 16 ~ 16 c8 |
8. 16 ~ 16 c |
r es es, ges 8 es,16 |
es, ges ~ es, 8 |
|
16 des es ~ bes, 8 |
16 des es ~ c ~ |
} \alternative {
{ 16 8 f16 f f }
{ 16 des f as 8 r }
}
\break
\key as \major
\repeat volta 2 {
|
16 ~ bes as f |
es f8 16 ~ 4 |
r16 es c es 8 c16 |
8 f16 ~ 4 |
r16 des bes, des 8 16 ~ |
es c es 8 16 ~ |
es c es 8 es16 |
8|
16 ~ bes as f |
as8 f es16 as8 16 ~ |
es c es 8 16 ~ |
bes 8 16 ~ |
bes as bes 8 16 ~ |
bes as r 8 es,16 |
} \alternative {
{ 8}
{}
}
\bar "|."
}
bottom = \relative c {
\key as \major
\time 2/4
\clef bass
\partial 8
8 |
\repeat volta 2 {
|
|
|
|
4 8 |
4 8 r |
\stemDown as,, r as' r \stemNeutral |
as' r as' r \clef treble |
|
Re: Syntax error encountered while engraving a successfully updated Mutopia ly file
That works!
Thanks,
Ken
On Sun, Nov 29, 2020 at 1:08 PM Aaron Hill wrote:
>
> On 2020-11-29 12:03 pm, Kenneth Wolcott wrote:
> > Hi;
> >
> > I downloaded a Mutopia Greensleves ly source and successfully
> > converted it to 2.20.0 but get the following error when engraving:
> >
> > ././updated_greensleeves.ly:68:22: error: syntax error, unexpected
> > SCM_TOKEN, expecting ',' or '.' or '='
> > top-markup-spacing
> > #'padding = #10
> >
> > The output from convert was only the version numbers.
> >
> > Please tell me how to fix this.
> >
> > The engraving did succeed as there were pdf and midi files produced.
> >
> > The paper section, below, is where the error occurs:
> >
> > \paper {
> > first-page-number = 2
> > print-first-page-number = ##t
> > top-markup-spacing #'padding = #10
> > markup-system-spacing #'padding = #7
> > system-system-spacing #'basic-distance = #14
> > }
>
> convert-ly knows how to fix this:
>
>
>\override Thing #'property #'sub-property = #'value
> % ...to...
>\override Thing.property.sub-property = #'value
>
>
> It does not however seem to correct:
>
>
>variable #'key = #'value
> % ...to...
>variable.key = #'value
>
>
>
> -- Aaron Hill
>
Re: Syntax error encountered while engraving a successfully updated Mutopia ly file
On 2020-11-29 12:03 pm, Kenneth Wolcott wrote:
Hi;
I downloaded a Mutopia Greensleves ly source and successfully
converted it to 2.20.0 but get the following error when engraving:
././updated_greensleeves.ly:68:22: error: syntax error, unexpected
SCM_TOKEN, expecting ',' or '.' or '='
top-markup-spacing
#'padding = #10
The output from convert was only the version numbers.
Please tell me how to fix this.
The engraving did succeed as there were pdf and midi files produced.
The paper section, below, is where the error occurs:
\paper {
first-page-number = 2
print-first-page-number = ##t
top-markup-spacing #'padding = #10
markup-system-spacing #'padding = #7
system-system-spacing #'basic-distance = #14
}
convert-ly knows how to fix this:
\override Thing #'property #'sub-property = #'value
% ...to...
\override Thing.property.sub-property = #'value
It does not however seem to correct:
variable #'key = #'value
% ...to...
variable.key = #'value
-- Aaron Hill
Syntax error encountered while engraving a successfully updated Mutopia ly file
Hi;
I downloaded a Mutopia Greensleves ly source and successfully
converted it to 2.20.0 but get the following error when engraving:
././updated_greensleeves.ly:68:22: error: syntax error, unexpected
SCM_TOKEN, expecting ',' or '.' or '='
top-markup-spacing
#'padding = #10
The output from convert was only the version numbers.
Please tell me how to fix this.
The engraving did succeed as there were pdf and midi files produced.
The paper section, below, is where the error occurs:
\paper {
first-page-number = 2
print-first-page-number = ##t
top-markup-spacing #'padding = #10
markup-system-spacing #'padding = #7
system-system-spacing #'basic-distance = #14
}
Thanks,
Ken
Re: transpose a score from mutopia
On 01.12.2016 21:06, mj wrote: Thinking about it... it might actually be faster to just transpose from the sheetmusic. It's just two voices and soprano... What Nicolas Sceaux has done here, is one way of coping with a large LilyPond project. On one hand, this makes management much easier _if_ you have all the tools required at hand and are familiar. On the other hand, it reduces accessibility and simplicity. For the latter reason I often try to keep as close to standard methods as I sensibly can. You _can_ get far with intelligently set up structures using \include, but it’s a non-trivial task as well. In your usecase now, I’d figure out where the actual source for the music lies and copy/paste it into a new file of your own. I think that’s the easiest course of action. HTH, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: transpose a score from mutopia
MJ:
...
> Thinking about it... it might actually be faster to just transpose from
> the sheetmusic. It's just two voices and soprano...
...
If you want to do a subset of the work, you can write your own score
file and include the relevant voices.
(cd to top dir of file structure)
The chorus parts have dir. names like Haendel/Oratorio/Messiah/*chorus
The first of wich contains:
$ ls Haendel/Oratorio/Messiah/ADchorus/
bassi.ily lyrics1.ily oboe.ily valto.ily violino1.ily
figures.ily lyrics2.ily parts.ilyvbasso.ily violino2.ily
global.ilylyrics3.ily score.ilyvcanto.ily vocal.ily
keyboard.ily lyrics4.ily silence.ily viola.ily vtenore.ily
global.ily contains \key \time and \tempo
lyrics1.ily could be soprano lyrics (my guess)
vcanto.ily is the soprano notes in absolute mode
so try something like attached file.
Regards,
/Karl Hammar
---
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57
\version "2.19.16"
\header {
copyrightYear = "2009"
composer = "George Frideric Handel"
poet=" "
opus = "HWV 56"
date = "1741"
editions = \markup \column {
\fill-line { \line { Based upon the Deutsche Händelgesellschaft Edition } }
\fill-line { \line { Edited by Frideric Chrysander } }
}
}
\paper {
}
\include "italiano.ly"
pitch_sop = do
pitch_alt = do
pitch_ten = do
pitch_bas = do
mus_sop = {
\autoBeamOff
\clef "treble"
}
mus_alt = {
\autoBeamOff
\clef "treble"
}
mus_ten = {
\autoBeamOff
\clef "treble_8"
}
mus_bas = {
\autoBeamOff
\clef "bass"
}
gbl = {
\key la \major
\time 3/4
% \include "Haendel/Oratorio/Messiah/ADchorus/global.ily"
}
Lsop = \context Lyrics = Lsop \lyricmode {
\include "Haendel/Oratorio/Messiah/ADchorus/lyrics1.ily"
}
Msop = \context Voice = Vsop {
\mus_sop
\include "Haendel/Oratorio/Messiah/ADchorus/vcanto.ily"
}
\score {
\new ChoirStaff <<
\transpose do \pitch_sop
\new Staff << \Msop \gbl >>
\lyricsto Vsop \Lsop
%\transpose do \pitch_alt \new Staff \Malt
%\lyricsto Valt \Lalt
%\transpose do \pitch_ten \new Staff \Mten
%\lyricsto Vten \Lten
%\transpose do \pitch_bas \new Staff \Mbas
%\lyricsto Vbas \Lbas
>>
\layout {
\context {
\Voice
\consists "Ambitus_engraver"
% keySignature = #'()
}
}
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: transpose a score from mutopia
Hi Karl, There is a lot of information in your email, I'll need t bit of time to digest it all. Thinking about it... it might actually be faster to just transpose from the sheetmusic. It's just two voices and soprano... Thanks for your big reply! MJ On 12/01/2016 06:18 PM, k...@aspodata.se wrote: mj: ... Michael: I am trying to transpose a Messiah lilypond file from mutopia: http://www.mutopiaproject.org/ftp/HandelGF/HWV56/Messiah/Messiah-lys.zip However I'm not getting very far, could use a bit of help Extracting the zip gives a folder structure like: |-common |-Haendel |---Oratorio |-Messiah |---AAsinfonia . (many more) |---CGchorus |---CHairSoprano |---CIchorus |---CJchorus |-lilypond-patches |-out |-templates So, looking at this, there is a main.ly in ./Haendel/Oratorio/Messiah which I opened in frescobaldi, but I can't compile it, as all the paths in main.ly look like "\include "Haendel/Oratorio/Messiah/common.ily" The aforementioned include tries to include the file common.ily, which is in the same folder as the main.ly you are trying to convert. Given that there is also a directory ./common which hold a couple of other to-be-included files I'd add the directory that you extracted your ZIP in to frescobaldi's include paths. E.g. the absolute path to your main.ly would be /home/mj/my-lp-scores/from_mutopia/Haendel/Oratorio/Messiah/main.ly then add "/home/mj/my-lp-scores/from_mutopia/" (or ~/my-lp-scores/from_mutopia/) to frescobaldi's include paths. I don't know much about frescobaldi, but unzipping the file and cd Messiah-lys, gives me the folder structure outlined above. There is also a Makefile and: $ make help usage: make score-rule: Build a A4 PDF score -rehearsal Build a A4 PDF score with rehearsal numbers -letterBuild a Letter PDF score -Build a PDF part score -delivery Make archive and move PDFs to delivery directory -all Build all PDF formats and make delivery score: Rameau/Opera/HippolyteEtAricie Couperin/Orgue/MesseCouvents Couperin/Motets Couperin/Clavecin/lArtDeToucherLeClavecin Lully/Ballet/LWV05LaReventeDesHabits Lully/Ballet/LWV08AmourMalade Lully/Fete/LWV22LesPlaisirsDeLIleEnchantee Lully/Comedie/LWV43LeBourgeoisGentilhomme Lully/Opera/LWV56Psyche Lully/Opera/LWV61Phaeton Lully/Opera/LWV71Armide Charpentier/Opera/DavidEtJonathas Haendel/Opera/GiulioCesare Haendel/Oratorio/Messiah PancraceRoyer/PremierLivre which implies that the correct procedure to make the score would be $ make Haendel/Oratorio/Messiah lilypond -ddelete-intermediate-files -o out/Messiah Haendel/Oratorio/Messiah/main.ly GNU LilyPond 2.19.16 ... But since I have a newer lilypond version than the source I expect it to fail, which it does. Source version can be found with: $ find . -type f -name \*.ily -or -name \*.ly | xargs grep version ./common/common.ily:\version "2.13.7" ./common/common.ily:#(ly:export (string-append "version " (lilypond-version))) ./common/music-commands.ily:\version "2.11.57" ./common/test-clef-key.ly:\version "2.11.39" ./common/test-markup.ly:\version "2.11.39" ./common/test-titling.ly:\version "2.11.39" So to proceed forward I suggest you dig up lilypond version 2.13.7. There is also a patch in lilypond-patches/lilypond.patch, and looking through lily/page-turn-page-breaking.cc I can see that that patch is not applied in the git repo. You might need to apply that patch too succeed, who knows. Unfortunately the patch doesn't apply cleanly to neither version 2.11.39 nor 2.13.7. To get version 2.13.7 do: $ git branch release/2.13.7 $ git checkout release/2.13.7 Switched to branch 'release/2.13.7' Then INSTALL.txt in lilypond git covers the compilation process. Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ 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: transpose a score from mutopia
mj: ... > Michael: > >> I am trying to transpose a Messiah lilypond file from mutopia: > >> http://www.mutopiaproject.org/ftp/HandelGF/HWV56/Messiah/Messiah-lys.zip > >> > >> However I'm not getting very far, could use a bit of help > >> > >> Extracting the zip gives a folder structure like: > >> > >> > >> |-common > >> |-Haendel > >> |---Oratorio > >> |-Messiah > >> |---AAsinfonia > >> . (many more) > >> |---CGchorus > >> |---CHairSoprano > >> |---CIchorus > >> |---CJchorus > >> |-lilypond-patches > >> |-out > >> |-templates > >> > >> So, looking at this, there is a main.ly in ./Haendel/Oratorio/Messiah > >> which I opened in frescobaldi, but I can't compile it, as all the paths > >> in main.ly look like "\include "Haendel/Oratorio/Messiah/common.ily" > > > > The aforementioned include tries to include the file common.ily, which is > > in the > > same folder as the main.ly you are trying to convert. > > Given that there is also a directory ./common which hold a couple of other > > to-be-included files I'd add the directory that you extracted your ZIP in to > > frescobaldi's include paths. > > > > E.g. the absolute path to your main.ly would be > > /home/mj/my-lp-scores/from_mutopia/Haendel/Oratorio/Messiah/main.ly > > then add "/home/mj/my-lp-scores/from_mutopia/" (or > > ~/my-lp-scores/from_mutopia/) > > to frescobaldi's include paths. I don't know much about frescobaldi, but unzipping the file and cd Messiah-lys, gives me the folder structure outlined above. There is also a Makefile and: $ make help usage: make score-rule: Build a A4 PDF score -rehearsal Build a A4 PDF score with rehearsal numbers -letterBuild a Letter PDF score -Build a PDF part score -delivery Make archive and move PDFs to delivery directory -all Build all PDF formats and make delivery score: Rameau/Opera/HippolyteEtAricie Couperin/Orgue/MesseCouvents Couperin/Motets Couperin/Clavecin/lArtDeToucherLeClavecin Lully/Ballet/LWV05LaReventeDesHabits Lully/Ballet/LWV08AmourMalade Lully/Fete/LWV22LesPlaisirsDeLIleEnchantee Lully/Comedie/LWV43LeBourgeoisGentilhomme Lully/Opera/LWV56Psyche Lully/Opera/LWV61Phaeton Lully/Opera/LWV71Armide Charpentier/Opera/DavidEtJonathas Haendel/Opera/GiulioCesare Haendel/Oratorio/Messiah PancraceRoyer/PremierLivre which implies that the correct procedure to make the score would be $ make Haendel/Oratorio/Messiah lilypond -ddelete-intermediate-files -o out/Messiah Haendel/Oratorio/Messiah/main.ly GNU LilyPond 2.19.16 ... But since I have a newer lilypond version than the source I expect it to fail, which it does. Source version can be found with: $ find . -type f -name \*.ily -or -name \*.ly | xargs grep version ./common/common.ily:\version "2.13.7" ./common/common.ily:#(ly:export (string-append "version " (lilypond-version))) ./common/music-commands.ily:\version "2.11.57" ./common/test-clef-key.ly:\version "2.11.39" ./common/test-markup.ly:\version "2.11.39" ./common/test-titling.ly:\version "2.11.39" So to proceed forward I suggest you dig up lilypond version 2.13.7. There is also a patch in lilypond-patches/lilypond.patch, and looking through lily/page-turn-page-breaking.cc I can see that that patch is not applied in the git repo. You might need to apply that patch too succeed, who knows. Unfortunately the patch doesn't apply cleanly to neither version 2.11.39 nor 2.13.7. To get version 2.13.7 do: $ git branch release/2.13.7 $ git checkout release/2.13.7 Switched to branch 'release/2.13.7' Then INSTALL.txt in lilypond git covers the compilation process. Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: transpose a score from mutopia
> Hi MJ,
>
> > Thanks for your suggestion, it improves matters a lot, but there are
> > still *MANY* (different kinds) errors. The complete output is here:
> >
> > http://codepad.org/Qc93Rvyu
>
> I see lots of errors. I then had a look at the Messiah ly files and saw most
> of
> them have no \version in them, which is really bad.
> Some have and that's either 2.11.x or 2.13.x (probably not a complete list).
>
> > Are there some basic settings/things that would perhaps help..?
>
> I would throw convert-ly at them. For that to work you'd need to add \version
> statements (or that's my understanding). Quite a task.
Forget that - the --from=versionnumer parameter of convertly takes care of that.
> After that and assuming you're on Linux you could something like
> find . -name "*.*ly" -exec convert-ly --from=2.11 {} ";"
> (I'm not on my linux/LP machine just now, can't test, but the above should
> give
> you the idea)
>
> Or manually go through all directories and issue something like
> convert-ly -e --from=2.11 *.*ly
> You may try 2.13 or something else as well.
>
> This should fix many and if you're lucky most of the errors.
>
> Kind regards,
> Michael
> --
> Michael Gerdau email: m...@qata.de
> GPG-keys available on request or at public keyserver
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
--
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: transpose a score from mutopia
Hi MJ,
> Thanks for your suggestion, it improves matters a lot, but there are
> still *MANY* (different kinds) errors. The complete output is here:
>
> http://codepad.org/Qc93Rvyu
I see lots of errors. I then had a look at the Messiah ly files and saw most of
them have no \version in them, which is really bad.
Some have and that's either 2.11.x or 2.13.x (probably not a complete list).
> Are there some basic settings/things that would perhaps help..?
I would throw convert-ly at them. For that to work you'd need to add \version
statements (or that's my understanding). Quite a task.
After that and assuming you're on Linux you could something like
find . -name "*.*ly" -exec convert-ly --from=2.11 {} ";"
(I'm not on my linux/LP machine just now, can't test, but the above should give
you the idea)
Or manually go through all directories and issue something like
convert-ly -e --from=2.11 *.*ly
You may try 2.13 or something else as well.
This should fix many and if you're lucky most of the errors.
Kind regards,
Michael
--
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: transpose a score from mutopia
Hi Michael, Thanks for your suggestion, it improves matters a lot, but there are still *MANY* (different kinds) errors. The complete output is here: http://codepad.org/Qc93Rvyu Are there some basic settings/things that would perhaps help..? (and generally speaking... would main.ly be the file to open?) (this whole opening-ly-files-from-mutopia business is new to me) MJ On 11/30/2016 11:33 AM, Gerdau, Michael wrote: Hi MJ, I am trying to transpose a Messiah lilypond file from mutopia: http://www.mutopiaproject.org/ftp/HandelGF/HWV56/Messiah/Messiah-lys.zip However I'm not getting very far, could use a bit of help Extracting the zip gives a folder structure like: |-common |-Haendel |---Oratorio |-Messiah |---AAsinfonia . (many more) |---CGchorus |---CHairSoprano |---CIchorus |---CJchorus |-lilypond-patches |-out |-templates So, looking at this, there is a main.ly in ./Haendel/Oratorio/Messiah which I opened in frescobaldi, but I can't compile it, as all the paths in main.ly look like "\include "Haendel/Oratorio/Messiah/common.ily" The aforementioned include tries to include the file common.ily, which is in the same folder as the main.ly you are trying to convert. Given that there is also a directory ./common which hold a couple of other to-be-included files I'd add the directory that you extracted your ZIP in to frescobaldi's include paths. E.g. the absolute path to your main.ly would be /home/mj/my-lp-scores/from_mutopia/Haendel/Oratorio/Messiah/main.ly then add "/home/mj/my-lp-scores/from_mutopia/" (or ~/my-lp-scores/from_mutopia/) to frescobaldi's include paths. Kind regards, Michael -- Michael Gerdau email: m...@qata.de GPG-keys available on request or at public keyserver ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: transpose a score from mutopia
Hi MJ, > I am trying to transpose a Messiah lilypond file from mutopia: > http://www.mutopiaproject.org/ftp/HandelGF/HWV56/Messiah/Messiah-lys.zip > > However I'm not getting very far, could use a bit of help > > Extracting the zip gives a folder structure like: > > > |-common > |-Haendel > |---Oratorio > |-Messiah > |---AAsinfonia > . (many more) > |---CGchorus > |---CHairSoprano > |---CIchorus > |---CJchorus > |-lilypond-patches > |-out > |-templates > > So, looking at this, there is a main.ly in ./Haendel/Oratorio/Messiah > which I opened in frescobaldi, but I can't compile it, as all the paths > in main.ly look like "\include "Haendel/Oratorio/Messiah/common.ily" The aforementioned include tries to include the file common.ily, which is in the same folder as the main.ly you are trying to convert. Given that there is also a directory ./common which hold a couple of other to-be-included files I'd add the directory that you extracted your ZIP in to frescobaldi's include paths. E.g. the absolute path to your main.ly would be /home/mj/my-lp-scores/from_mutopia/Haendel/Oratorio/Messiah/main.ly then add "/home/mj/my-lp-scores/from_mutopia/" (or ~/my-lp-scores/from_mutopia/) to frescobaldi's include paths. Kind regards, Michael -- Michael Gerdau email: m...@qata.de GPG-keys available on request or at public keyserver ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
transpose a score from mutopia
Hi, I am trying to transpose a Messiah lilypond file from mutopia: http://www.mutopiaproject.org/ftp/HandelGF/HWV56/Messiah/Messiah-lys.zip However I'm not getting very far, could use a bit of help Extracting the zip gives a folder structure like: |-common |-Haendel |---Oratorio |-Messiah |---AAsinfonia . (many more) |---CGchorus |---CHairSoprano |---CIchorus |---CJchorus |-lilypond-patches |-out |-templates So, looking at this, there is a main.ly in ./Haendel/Oratorio/Messiah which I opened in frescobaldi, but I can't compile it, as all the paths in main.ly look like "\include "Haendel/Oratorio/Messiah/common.ily" Am I supposed to copy that main.ly to the folder folder above "./Haendel", to make the paths work, or am i approaching this the wrong way? (the ultimate goal here: printing off a transposed version of a particular aria) I hope someone can give me some pointers here. No big hurry, as we still have some time left before christmas :-) MJ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Mutopia [WAS: Re: Add LilyPond incipit on an IMSLP page.]
2014-05-08 16:49 GMT+02:00 Pierre Perol-Schneider pierre.schneider.pa...@gmail.com: Can I ask you why? It's because of the license restrictions (NonCommercial clause is not accepted by Mutopia)? Because I'm no Mutopia user. Now the right question would be why am I not a user ? Well, few years ago I've downloaded one or two files and, as far as I remember : a) None of'em were compilable. b) Copy/paste-ing the notes took me much more time than rewriting the whole score after a facsimile. c) Pdfs look bad (what's the purpose of such footers ??). Yes, the footer looked bad, but it changed recently thanks to the contribution of Noeck (who started contributing to Mutopia after the discussion we had in January on this list). We are also in the process of updating all the files to at least version 2.16 (possibly, 2.18). Glen used to lead this effort, I'll ping him to go on to the next step. I've just take a quick look at the Mutopia site. I'd like to add : a) it is written The Mutopia Project offers sheet music editions of classical music for free download ; which means that it is in direct competition with IMSLP. Does it make sense ? Yes, it does. IMSLP doesn't offer the (lilypond) source used to produce the PDF, so their users cannot modify the scores or re-adapt them in derivative works. b) the composer's pages are not user-friendly ; why not using a wiki system ? Yes, it would be nice if Mutopia had a better interface. OTOH I think that Github may be considered user-friendly, if people knew how to use it :-) (I'd like to write a post on this for lilypondblog.org sooner or later). c) a majority of (all ?) scores are coded relatively ; exept when coding for organ, piano, harp, etc. I never use \relative I see, but most users use \relative and all the snippets in the LilyPond documentation are written in relative mode. So it's no surprise that most of Mutopia pieces are written in relative mode. In Frescobaldi you can easily change the notes from relative to absolute and the other way around. d) there is no coding convention; many Mutopia codes (e.g. http://www.mutopiaproject.org/ftp/BrownCJ/lullaby/lullaby.ly) give me headhaches. If there were too much coding conventions, may a piece written in absolute mode would not be accepted :-) Jokes aside.. I agree with you, Mutopia needs better coding conventions and a general reformatting. e) there are numbers of pretty old version (v2.4 for this one : http://www.mutopiaproject.org/ftp/CarcassiM/O60/carcassi-op60-01/carcassi-op60-01.ly ) Few persons are working on it. I hope to announce in 2014 All Mutopia pieces are updated to 2.16 or 2.18. f)...etc. (too long) I'd like to conclude that Mutopia site remains the same for years, no improvement, no discussion (except you, Federico). So, if nothing changes, I don't see any future for this site. Yes, the site is the same but there's been some discussion and activity on the last months: https://github.com/chrissawer/The-Mutopia-Project/pulls?direction=descpage=1sort=updatedstate=closed I hope that you'll change your mind one day :-) Thanks for your comments ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mutopia [WAS: Re: Add LilyPond incipit on an IMSLP page.]
On Thu, 2014-05-08 at 17:35 +0200, Federico Bruni wrote: Yes, it does. IMSLP doesn't offer the (lilypond) source used to produce the PDF, so their users cannot modify the scores or re-adapt them in derivative works. It does if you upload it; several scores are up there with LilyPond source already. It would be a worthwhile task (for promoting LilyPond) to update mutopia's lilypond sources and upload them ( the pdfs, of course) to IMSLP. I haven't looked to see if there is anything on mutopia for years. Richard ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mutopia [WAS: Re: Add LilyPond incipit on an IMSLP page.]
Le 08/05/2014 17:35, Federico Bruni disait : 2014-05-08 16:49 GMT+02:00 Pierre Perol-Schneider: Can I ask you why? It's because of the license restrictions (NonCommercial clause is not accepted by Mutopia)? Because I'm no Mutopia user. Now the right question would be why am I not a user ? I've just take a quick look at the Mutopia site. I'd like to add : a) it is written The Mutopia Project offers sheet music editions of classical music for free download ; which means that it is in direct competition with IMSLP. Does it make sense ? Yes, it does. IMSLP doesn't offer the (lilypond) source used to produce the PDF, so their users cannot modify the scores or re-adapt them in derivative works. It's up to the typesetter to upload them (what I did for BWV 106 and 246 as well as King Arthur, and will do when I'm finished with Monteverdi's Sanctissimae Virgini Missa and vespers next year). I would add that in some circumstances, page-size (A4 *and* letter) makes a score not acceptable on Mutopia. Cheers, Jean-Charles ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mutopia [WAS: Re: Add LilyPond incipit on an IMSLP page.]
Il 08/mag/2014 18:07 Richard Shann rich...@rshann.plus.com ha scritto: On Thu, 2014-05-08 at 17:35 +0200, Federico Bruni wrote: Yes, it does. IMSLP doesn't offer the (lilypond) source used to produce the PDF, so their users cannot modify the scores or re-adapt them in derivative works. It does if you upload it; several scores are up there with LilyPond source already. Ok, so you can attach any file. But what makes Mutopia different is that any piece _must_ have the source file, otherwise it won't be accepted. The ability to edit a score is not optional, it's the core of Mutopia. The other is quality. It would be a worthwhile task (for promoting LilyPond) to update mutopia's lilypond sources and upload them ( the pdfs, of course) to IMSLP. I haven't looked to see if there is anything on mutopia for years. I'd prefer a search engine which looks up IMSLP, Mutopia and other music libraries and returns the links to the searched piece/author page. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Attribution statements for Mutopia Project works
Greetings all, Are there established practices or examples of how to properly attribute works from the Mutopia Project that are licensed with a Creative Commons license? Say if you make a derivative work based on one? I have made (what I understand to be) derivative works by translating or transcribing some pieces into an alternative music notation system (Clairnote, http://clairnote.org). I came up with the following statement, based on the best practices described here: http://wiki.creativecommons.org/Best_practices_for_attribution Typeset using LilyPond in Clairnote music notation by Paul Morris. This work (© 2014) is a derivative of the Mutopia Project work of the same title, typeset using LilyPond in standard music notation by Nikos Kouremenos (© 2014, Mutopia-2014/03/24-519). Both works are licensed under a Creative Commons Attribution-ShareAlike 4.0 International License — free to distribute, modify, and perform. This statement fits on three lines and would appear in the footer on the first page (just like the current copyright/license statement for Mutopia files). Thanks for any feedback on this, especially from anyone who has experience with this. It would be good to know that these statements are sufficient or if they could be improved. You can see actual examples here: http://clairnote.org/sheet-music/ (see any pdf from that page except Twinkle Twinkle, Swinging on a Gate, or 180 Fiddle Tunes) Thanks, -Paul P.S. For works in the public domain I would use slightly different wording: Typeset using LilyPond in Clairnote music notation by Paul Morris. This work (© 2014) is a derivative of the Mutopia Project work of the same title, typeset using LilyPond in standard music notation and placed in the public domain by Stelios Samelis (Mutopia-2012/12/23-931). This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 License— free to distribute, modify, and perform. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
First Mutopia contribution -- looking for some critique
Hello everyone,
I am typesetting Lied eines Schiffers and die Dioskuren by Franz Schubert
to
contribute to Mutopia. This is my first time tweaking the default output
and it
is also my first time publishing the source.
I am hoping that you can point some (probably present) bad practices or just
plain mistakes. I have the source in a Github repo:
https://github.com/jgnog/schubertdioskuren
You can also find the source attached.
Thank you for your attention,
Gonçalo Nogueira
about.me/goncalonogueira
\version 2.18.0
\header {
title = Lied eines Schiffers and die Dioskuren
composer = F. Schubert
poet = Johann Mayrhofer
opus = D.360, Op. 65, No. 1
% Remove default LilyPond tagline
tagline = ##f
% Mutopia headers
mutopiacomposer = SchubertF
mutopiainstrument = Voice and Piano
source = C.F. Peters, ca. 1910
style = Romantic
copyright = Public Domain
maintainer = Gonçalo Nogueira
maintainerEmail = jgoncalonogueira (at) gmail.com
maintainerWeb = http://about.me/goncalonogueira;
}
\paper {
page-count = #2
ragged-last-bottom = ##f
}
#(set-global-staff-size 18)
global = {
\key as \major
\numericTimeSignature
\time 3/4
\tempo Langsam
}
% Tweaks
smallStem = {
\once \override Stem.length = #4.5
}
changeRight = {
\change Staff = right
}
changeLeft = {
\change Staff = left
}
hideStem = {
\override Stem.stencil = ##f
}
shiftLeft = {
\once \override NoteColumn.horizontal-shift = #1
}
offsetDynamic = {
\once \override DynamicText.X-offset = #-4
}
shapeSlur = {
\shape #'((0 . -0.2) (0 . 0) (0.7 . 0) (0 . -1.2)) Slur
}
shapeSlurA = {
\shape #'((0.7 . 0.8) (0 . 1) (0 . 1) (-0.7 . 0.8)) Slur
}
shapeTie = {
\shape #'((0.8 . -0.3) (0 . -0.3) (0 . -0.3) (0 . -0.3)) Tie
}
tweakDamping = {
\once \override Beam.damping = #0.5
}
dropTies = {
\override Tie.Y-offset = #-0.8
}
dropAccent = {
\once \override Script.Y-offset = #-4.5
}
voice = \relative c'' {
\global
\dynamicUp
\autoBeamOff
% Music follows here.
R2. |
r4 r4 c8. c16 |
c4 aes c8 des |
c4 bes ees8. ees16 |
ees4 c ees8. des16 |
bes4 c r4 |
R2. |
r4 r4 aes8 g |
f4. bes8 aes g |
c4 aes ees'8. ees16 |
ees4 c des8. des16 |
des4 bes c8. bes16 |
bes4 aes c8. bes16 |
bes2. |
aes4 r4 r4 |
r4 r4 c8. c16 |
c4. g8 aes8. f16 |
e4 c des'8. des16 |
des4. f,8 f8. g16 |
aes4 g r4 |
r4 r4 ees'8. ees16 |
ees4. c8 bes aes |
aes4 g ees'8. ees16 |
ees4. c8 bes bes |
d2. |
ees4 r4 r4 |
r4 r4 c8. c16 |
c4 aes c8 des |
c4 bes ees8. ees16 |
ees4 c ees8. des16 |
bes4 c aes8 g |
f4. bes8 aes g |
c4 aes ees'8. ees16 |
ees4. c8 des8. des16 |
des4 bes c8. bes16 |
bes4 aes c8. bes16 |
bes2. |
aes4 r4 r4 |
R2. |
R2. |
\bar |.
}
verse = \lyricmode {
% Lyrics follow here.
Di -- os -- ku -- ren, Zwil -- lings -- ster -- ne,
die ihr leuch -- tet mei -- nem Na -- chen,
mich be -- ru -- hig auf dem Mee -- re eu -- re Mil -- de,
eu -- er Wa -- chen, eu -- re Mil -- de, eu -- er Wa -- chen.
Wer auch fest in sich be -- grün -- det,
un -- ver -- zagt dem Sturm be -- geg -- net,
fühlt sich doch in eu -- ren Strah -- len
dop -- ppelt mu -- tig und ge -- seg -- net.
Die -- ses Ru -- der, das ich schwin -- ge,
Mee -- res -- flu -- ten zu zer -- tei -- len,
hän -- ge ich, so ich ge -- bor -- gen,
auf an eu -- res Tem -- pel Säu -- len,
Di -- os -- ku -- ren, Zwil -- lings -- ster -- ne.
}
right = \relative c' {
\global
% Music follows here.
s2. |
s2. |
\changeLeft
\stemUp
s4 s4 aes c8 bes des |
aes c4 g bes \changeRight c ees8. c ees16 |
c ees2\arpeggio c ees8. bes des16 |
\changeLeft
g bes4 aes c \changeRight c4 |
c4. des8 aes! c g bes |
c ees4 aes c s4 |
c4. des8 aes! c g bes |
c ees4 aes c c ees8( bes c ees) |
a c ees2 bes des8( aes bes des) |
g bes des2 \clef bass \stemDown ees aes c8.\pp( des g bes16) |
des g bes4( c aes') ees aes c8.( des g bes16) |
des ees g bes2.( |
c ees aes4) r4 \stemNeutral \offsetDynamic e g c8.\ff e g c16 |
e g c2 c'8.\f c16 |
c4.( g8 aes8. f16) |
e4 c \offsetDynamic des f bes des8.\ff des f bes des16 |
des f bes des2 f8. g16 |
f aes4( e g8) r8 ees bes'8.\pp ees bes'16 |
ees bes'2 \offsetDynamic ees bes' ees8.\mf ees b' ees16 |
{ \shapeSlur c' ees4.( aes c8 \stemDown \autoBeamOff d, g bes[ f aes]) | } \\ { ees2 s4 | }
d f aes4( ees g) ees bes' ees8.\pp ees b' ees16 |
{ c' ees4.( aes c8 \stemDown \autoBeamOff g bes[ aes bes d]) | } \\ { ees2 s4 | }
{
\stemDown
\shapeTie
bes' f'2.~( |
bes ees2)
}
\\
{
\hideStem
\shiftLeft
\shapeSlurA
aes2.( |
g2)
}
c, ees aes c8. c ees aes c16 |
c ees aes c2 c ees aes c8. c ees aes c16 |
c ees aes c2 aes' c8 f bes des |
aes c4 g bes ees aes c ees8. ees aes c ees16 |
ees aes c ees2
{
c' ees8. bes des16 |
g bes4 aes c s4 |
c4. des8 aes c g bes |
c
Re: First Mutopia contribution -- looking for some critique
Gonçalo Nogueira jgoncalonogue...@gmail.com writes:
hideStem = {
\override Stem.stencil = ##f
}
This one is equivalent to \omit Stem which seems short enough to write.
\hide Stem, in contrast, would be \override Stem.transparency = ##t .
Personally, I'd not write { } around every such command.
g bes4 aes c \changeRight c4 |
c4. des8 aes! c g bes |
c ees4 aes c s4 |
c4. des8 aes! c g bes |
When you find yourself using multiple reminder accidentals, it might be
worth checking whether you can find an \accidentalStyle better matching
the composer's practice.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: First Mutopia contribution -- looking for some critique
Hi Gonçalo, to me it looks nice. Thanks! Some small comments: - The piano dynamics would look better if they were centered between the piano staffs. - The horizontal positioning of dynamics is related: Why do you use this? \once \override DynamicText.X-offset = #-4 Usually dynamics should be centred on the note they belong to (especially for piano music where you can’t increase the volume during the chord, for example mf measure 21). - I would prefer one of №, Nº or No. instead of nº (capital N as the other text is also German) - it should read: doppelt (dop -- pelt), one p too much Thanks for sharing it. Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: First Mutopia contribution -- looking for some critique
As a first pass review: Needs a midi section (I did a quick one with 'choir aahs' for vocals and 'acoustic grand' for the piano, \tempo 4=100, and it sounded quite nice.) You are going to great lengths to keep this to 2 pages. This is fine but Mutopia will want to create both A4 and Letter sizes so your paper variables (2 A4 pages) will be commented out to accommodate this. On letter size your manual breaks also will not do what you need them to do. A suggestion: design for A4 but leave out the set-paper-size command and remove manual line breaks. Remove set-global-staff-size so it defaults to a little larger ( it will go to 2 systems on the 3rd page instead of one.) Request (or add yourself) a Mutopia 'moreinfo' tag in the header with text that the layout was designed for A4 paper size. -glen On Mon, Jan 20, 2014 at 4:00 PM, Gonçalo Nogueira jgoncalonogue...@gmail.com wrote: Hello everyone, I am typesetting Lied eines Schiffers and die Dioskuren by Franz Schubert to contribute to Mutopia. This is my first time tweaking the default output and it is also my first time publishing the source. I am hoping that you can point some (probably present) bad practices or just plain mistakes. I have the source in a Github repo: https://github.com/jgnog/schubertdioskuren You can also find attached the source and the resulting output. Thank you for your attention, Gonçalo Nogueira about.me/goncalonogueira ___ 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: why you don't contribute to Mutopia
The email may be a good alternative, but who is receiving contributions@ emails? Just Chris? I have no idea if people send contributions this way. The last time (1 year ago) I sent an email to the suggested address, I did not get any reply. So I didn’t try again and thought Mutopia is just dead. I have some scores, that I could upload, I could also use them to test any new upload feature. Too bad. Have you checked if your score has been added to Mutopia? Hi Federico, hi all, no, the score has not been added. Did you get any reply from the Mutopia mail address? I wrote to contributi...@mutopiaproject.org again on Jan 4th and didn’t get any answer so far. I also made a pull request to the github repo but there was no reaction, neighter. https://github.com/chrissawer/The-Mutopia-Project/pull/241 I continue to wait, but if anyone has contact to anyone behind those interfaces, I would be interested if some answer can be expected within days or weeks or more like months. Best, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
On 10/01/14 04:57, Noeck wrote: The email may be a good alternative, but who is receiving contributions@ emails? Just Chris? I have no idea if people send contributions this way. The last time (1 year ago) I sent an email to the suggested address, I did not get any reply. So I didn’t try again and thought Mutopia is just dead. I have some scores, that I could upload, I could also use them to test any new upload feature. Too bad. Have you checked if your score has been added to Mutopia? Hi Federico, hi all, no, the score has not been added. Did you get any reply from the Mutopia mail address? I wrote to contributi...@mutopiaproject.org again on Jan 4th and didn’t get any answer so far. I also made a pull request to the github repo but there was no reaction, neighter. https://github.com/chrissawer/The-Mutopia-Project/pull/241 I continue to wait, but if anyone has contact to anyone behind those interfaces, I would be interested if some answer can be expected within days or weeks or more like months. I've submitted corrections to Mutopia two or three times for errors in existing scores on Mutopia, but never received any acknowledgement, and the corrections never made it to the scores on the web site. So I no longer bother. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
From: Nick Payne On 10/01/14 04:57, Noeck wrote: The email may be a good alternative, but who is receiving contributions@ emails? Just Chris? I have no idea if people send contributions this way. The last time (1 year ago) I sent an email to the suggested address, I did not get any reply. So I didn’t try again and thought Mutopia is just dead. I have some scores, that I could upload, I could also use them to test any new upload feature. Too bad. Have you checked if your score has been added to Mutopia? Hi Federico, hi all, no, the score has not been added. Did you get any reply from the Mutopia mail address? I wrote to contributi...@mutopiaproject.org again on Jan 4th and didn’t get any answer so far. I also made a pull request to the github repo but there was no reaction, neighter. https://github.com/chrissawer/The-Mutopia-Project/pull/241 I continue to wait, but if anyone has contact to anyone behind those interfaces, I would be interested if some answer can be expected within days or weeks or more like months. I've submitted corrections to Mutopia two or three times for errors in existing scores on Mutopia, but never received any acknowledgement, and the corrections never made it to the scores on the web site. So I no longer bother. They don't seem completely dead...their home page shows the lastest additions (two so far this year), and Chris Sawer is responding in their mailing list. Phil. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
2014/1/9 Noeck noeck.marb...@gmx.de Too bad. Have you checked if your score has been added to Mutopia? Hi Federico, hi all, no, the score has not been added. Did you get any reply from the Mutopia mail address? I don't know what you mean with Mutopia mail address, but I've received a reply from Chris, mantainer of Mutopia, on mutopia-discuss: http://news.gmane.org/gmane.music.mutopia.discuss He accepted my suggestions and he said that he will update the website. I wrote to contributi...@mutopiaproject.org again on Jan 4th and didn’t get any answer so far. I also made a pull request to the github repo but there was no reaction, neighter. https://github.com/chrissawer/The-Mutopia-Project/pull/241 I also have two pending pull requests (quite easy to review). As you use github,I suggest using pull requests so your contributions are public. I don't know how long it will take to get those pull requests accepted (some were submitted several months ago...). It's evident that the review system of mutopia need a serious change and possibly some contributors who know well Mutopia (like Glen) should have write access to the repository, IMO. If Mutopia doesn't open the doors to the contributions, it will die. I continue to wait, but if anyone has contact to anyone behind those interfaces, I would be interested if some answer can be expected within days or weeks or more like months. The right place to discuss about it is mutopia-discuss: http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
2014/1/9 Nick Payne nick.pa...@internode.on.net I've submitted corrections to Mutopia two or three times for errors in existing scores on Mutopia, but never received any acknowledgement, and the corrections never made it to the scores on the web site. So I no longer bother. I can understand your frustration. You may try sending your corrections to mutopia-discuss: perhaps someone will make a pull request on your behalf. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
2014/1/3 Frédéric Bron frederic.b...@m4x.org I wanted to contribute with the 4th symphony of Schumann which was ready to be submitted. I had spent some time to adjust the page layout for A4 paper format and was not ready to spend more time to target the letter paper format. I still would like to put the symphony but do not find the extra time to do that and also, now the lilypond format is quite old (2.12), I would need to update to 2.18. So, I would say that when time misses, just a minor hurdle can stop the process. Please submit it and you'll add a layout for US letter if/when you'll have time. It doesn't have to be (immediately) perfect :-) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
2014/1/2 Phil Hézaine philippe.heza...@free.fr 2. Licenses Currently Mutopia accepts only transcriptions licensed as public domain, CC By, CC By-Sa: http://www.mutopiaproject.org/legal.html I don't know what led to this decision, but I can imagine that at least CC By-Sa-Nc would be preferred by some. And what about Free Art License which is recommended by the Free Software Foundation. IMHO it's really a Free license. I don't know if it adds much to what the licenses above provide. Simplification is a good principle... ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
2014/1/2 Noeck noeck.marb...@gmx.de 4. Web interface Currently the contributions are handled via github or by email. Github is a good way but it's for geeks only. There are currently only seven contributors: https://github.com/chrissawer/The-Mutopia-Project/graphs/contributors I didn't know that this git repo. I've just asked some website updates on mutopia-discuss. Let's see what happens... The email may be a good alternative, but who is receiving contributions@ emails? Just Chris? I have no idea if people send contributions this way. The last time (1 year ago) I sent an email to the suggested address, I did not get any reply. So I didn’t try again and thought Mutopia is just dead. I have some scores, that I could upload, I could also use them to test any new upload feature. Too bad. Have you checked if your score has been added to Mutopia? A modern web interface may attract more contributions? For several years now, I have sketches and ideas how that could work and look and I always wanted to learn enough web techniques to make a proposal which can be tested. But so far I still don’t have the capabilities to do it. Are you talking about the appearance? I think that what may really change mutopia website requires some programming skill and knowledge of a web framework (django, for example). The last discussion I started about Mutopia ended without changing the website. If there is a chance that things really end up on the website, I would search for the notes I have taken back then and contribute to the discussion (but unfortunately not to realize it, see above). which discussion? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
2. Licenses Currently Mutopia accepts only transcriptions licensed as public domain, CC By, CC By-Sa: http://www.mutopiaproject.org/legal.html I don't know what led to this decision, but I can imagine that at least CC By-Sa-Nc would be preferred by some. BY-SA-NC is not approved as a free cultural license: http://creativecommons.org/freeworks These arguments should be considered. But it is a valid choice and it could also be good to have that option. And the mutopia footer with its varying font sizes is ugly! Yet another license issue: To my understanding the CC licenses (BY-...) require to mention the author somehow. And the license should be linked or be somehow easy to find. The current choice of licenses is lacking both. In addition the newest CC version is 4.0. I would propose something like: © Year Author, License: Creative Commons … 4.0 Where the license points to the cc website (using \with-url) Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
A modern web interface may attract more contributions? For several years now, I have sketches and ideas how that could work and look and I always wanted to learn enough web techniques to make a proposal which can be tested. But so far I still don’t have the capabilities to do it. Are you talking about the appearance? I think that what may really change mutopia website requires some programming skill and knowledge of a web framework (django, for example). Yes, that’s what I meant. The last discussion I started about Mutopia ended without changing the website. If there is a chance that things really end up on the website, I would search for the notes I have taken back then and contribute to the discussion (but unfortunately not to realize it, see above). which discussion? I cannot find it which makes me wondering if this discussion has taken place at all. This is all I found: http://lists.gnu.org/archive/html/lilypond-user/2013-02/msg00570.html But you know it (you replied). Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
Le 04/01/2014 13:27, Federico Bruni a écrit : 2014/1/2 Phil Hézaine philippe.heza...@free.fr 2. Licenses Currently Mutopia accepts only transcriptions licensed as public domain, CC By, CC By-Sa: http://www.mutopiaproject.org/legal.html I don't know what led to this decision, but I can imagine that at least CC By-Sa-Nc would be preferred by some. And what about Free Art License which is recommended by the Free Software Foundation. IMHO it's really a Free license. I don't know if it adds much to what the licenses above provide. Simplification is a good principle... Art Libre a fait le choix du libre; Creative Commons a fait celui du libre choix. The structure of Art Libre is Copyleft. One big difference is the acknowledgement of the Berne's Convention. The Free Art License is effective in all the countries which signed up these agreement. So far it is not the case for CC License (I don't know for CC 4.0). There are also discussions about a compatibility between CC and FAL (or LAL = Licence Art Libre). http://wiki.creativecommons.org/4.0/Compatibility Potential compatible licenses FAL In CC's view, FAL 1.3 is a strong candidate for two-way compatibility with BY-SA 4.0. Discussions are currently underway that we hope will allow remixing between two similarly-spirited but currently separate islands of content. We are working through details of what adjustments may need to be made in order to accomplish this goal. We will be vetting those fully with our communities between now and d3 (draft3). It is possible that some tweaks may needed to be made to our licenses to make that happen, affecting current drafting. In terms of operationalizing such a statement on the CC side either through a reference in the license itself or inclusion on our existing (empty) webpage [link], this is an open question that will be addressed once more progress is made. For now, d2 contains the same compatibility language as 3.0 and maintains the definition of Creative Commons Compatible License and structure. Cheers. Phil. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
Am 03.01.2014 07:56, schrieb Frédéric Bron: I'd like to have some feedback from you. Which change in the Mutopia interface/decisions would make you start contributing or contributing more? I wanted to contribute with the 4th symphony of Schumann which was ready to be submitted. I had spent some time to adjust the page layout for A4 paper format and was not ready to spend more time to target the letter paper format. The requirement to not specify the paper format and have both A4 and letter supported is nice in theory. And it is good that LP has good defaults for both. In practice, for almost every score, the layout settings depend on the paper format to make it really looking good. Therefore, IMHO, both A4 and letter contributions could be accepted by Mutopia without the other. If I (as a user) really want a score which is available as US letter only, I can do the tweaks myself to fit nicely on my A4 paper (and vice versa) and I am better off if it exists in the other format than starting from scratch. Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
Le 01/01/2014 19:01, Federico Bruni a écrit : Dear Lilyponders some recent posts in this list made me think about the weaknesses of Mutopia and why people who may contribute to it are not doing so. I'd like to have some feedback from you. Which change in the Mutopia interface/decisions would make you start contributing or contributing more? I can see these big problems: [snip...] 2. Licenses Currently Mutopia accepts only transcriptions licensed as public domain, CC By, CC By-Sa: http://www.mutopiaproject.org/legal.html I don't know what led to this decision, but I can imagine that at least CC By-Sa-Nc would be preferred by some. And what about Free Art License which is recommended by the Free Software Foundation. IMHO it's really a Free license. Seems like IMSLP has the same problem with this license! It's impossible to tell you what kind of problems are relevant, it's totally esoteric from IMSLP. I don't understand the arguments against this choice, if they exists. Thanks for the feedback. Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
Federico, thanks for writing this. There is a mixture of hope and despair in the responses, as well as an understanding of the complexities in an all-volunteer site. The content in Mutopia is substantial enough to be a great resource and managing this content via volunteers will always be a challenge. There have been a number of updates in the past year -- utf-encoding conversions, project status updates, data consistency repairs -- and these have been good starting points. Much of that effort took place without engaging mutopia-discuss and that was probably a mistake. As long as the content is good (correct, aesthetically pleasing, readable, and using a reasonably current version of LilyPond) I believe the site holds value. It is not as good as it could be. On Wed, Jan 1, 2014 at 10:01 AM, Federico Bruni fedel...@gmail.com wrote: [snip] 3. Requisites for the lilypond files Some people are discouraged by the criteria to get the files accepted. For example, they may create the score with Denemo and then export the lilypond file, but they cannot check the quality of the file. I'd suggest them to try to submit their file to the mutopia-discuss list and see if someone can clean the input. Personally, I'd be glad to contribute this way. As long as the Denemo-based transcriber understands that they may not be able to round-trip their submission. 4. Web interface Currently the contributions are handled via github or by email. Github is a good way but it's for geeks only. There are currently only seven contributors: https://github.com/chrissawer/The-Mutopia-Project/graphs/contributors The email may be a good alternative, but who is receiving contributions@emails? Just Chris? I have no idea if people send contributions this way. A modern web interface may attract more contributions? Probably, but I've come to believe that updating the content is more important. -glen (just an active Mutopia-Project volunteer) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
On Wed, Jan 1, 2014 at 11:11 AM, David Kastrup d...@gnu.org wrote: Federico Bruni fedel...@gmail.com writes: Dear Lilyponders some recent posts in this list made me think about the weaknesses of Mutopia and why people who may contribute to it are not doing so. I'd like to have some feedback from you. Which change in the Mutopia interface/decisions would make you start contributing or contributing more? Mutopia scores tend to be useful as PDF only, the equivalent of dead paper. They usually have been compiled with an ancient version of LilyPond nobody has available any more. As a result, recompilation, transposing, changes of paper format and other things are hard. Mutopia's biggest weakness is not that it is missing new contributions but rather that the existing contributions become unusable. So what's needed is: a) automated run of convert-ly to all following available stable versions b) an interface for people to say PDF for upgraded file looks ok c) an interface for people to fix up files that fail after convert-ly or are unnecessary complex given new LilyPond features. d) grading/voting mechanisms for scores/contributors e) obsoleting files when they have been converted and the version is really outdated (like, beyond Debian Stale from one year ago) f) notification to original transcriber on pending update Time to quantify ancient (which I know is substantial) The only way to achieve a reliable level of automation is to focus on the very old submissions. It is a good goal with or without automation. -glen ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
Glen Larsen glenl@gmail.com writes: 3. Requisites for the lilypond files Some people are discouraged by the criteria to get the files accepted. For example, they may create the score with Denemo and then export the lilypond file, but they cannot check the quality of the file. I'd suggest them to try to submit their file to the mutopia-discuss list and see if someone can clean the input. Personally, I'd be glad to contribute this way. As long as the Denemo-based transcriber understands that they may not be able to round-trip their submission. Perhaps one should offer a way to offer Denemo files as well. The GPL, a key document for the spirit of Free Software, states: 1. Source Code. The source code for a work means the preferred form of the work for making modifications to it. Object code means any non-source form of a work. and requires works to be distributed including source code. For a Denemo score, the preferred form of modification is the Denemo file: offering the export to LilyPond may be nice for LilyPond users, but it's no longer the corresponding source. It's already a derivative like a MIDI file. A modern web interface may attract more contributions? Probably, but I've come to believe that updating the content is more important. If you are counting on surf-by fixings (like Wikipedia does), a web interface is pretty much a necessity. It does not need to be modern (which is often an alias for flashy, clunky, annoying), but it must not make doing a few fast fixes cumbersome. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
I'd like to have some feedback from you. Which change in the Mutopia interface/decisions would make you start contributing or contributing more? I wanted to contribute with the 4th symphony of Schumann which was ready to be submitted. I had spent some time to adjust the page layout for A4 paper format and was not ready to spend more time to target the letter paper format. I still would like to put the symphony but do not find the extra time to do that and also, now the lilypond format is quite old (2.12), I would need to update to 2.18. So, I would say that when time misses, just a minor hurdle can stop the process. Cheers, Frédéric ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
why you don't contribute to Mutopia
Dear Lilyponders some recent posts in this list made me think about the weaknesses of Mutopia and why people who may contribute to it are not doing so. I'd like to have some feedback from you. Which change in the Mutopia interface/decisions would make you start contributing or contributing more? I can see these big problems: 1. Money Recently an user said that he doesn't host his lilypond scores (CC licensed) on Mutopia, because he can't get any money from it; while he can get some money from the advertisements on his website. I don't like advertisements and I'd like to keep them away from Mutopia project. But I believe that other strategies are possible. For example, donations via micropayments: http://en.wikipedia.org/wiki/Micropayment#Recent_micropayment_systems Or crowdfunding for big projects, etc. 2. Licenses Currently Mutopia accepts only transcriptions licensed as public domain, CC By, CC By-Sa: http://www.mutopiaproject.org/legal.html I don't know what led to this decision, but I can imagine that at least CC By-Sa-Nc would be preferred by some. 3. Requisites for the lilypond files Some people are discouraged by the criteria to get the files accepted. For example, they may create the score with Denemo and then export the lilypond file, but they cannot check the quality of the file. I'd suggest them to try to submit their file to the mutopia-discuss list and see if someone can clean the input. Personally, I'd be glad to contribute this way. 4. Web interface Currently the contributions are handled via github or by email. Github is a good way but it's for geeks only. There are currently only seven contributors: https://github.com/chrissawer/The-Mutopia-Project/graphs/contributors The email may be a good alternative, but who is receiving contributions@emails? Just Chris? I have no idea if people send contributions this way. A modern web interface may attract more contributions? X. Other problems/ideas? Thanks for the feedback. Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
On Wed, 2014-01-01 at 19:01 +0100, Federico Bruni wrote:
For example, they may create the score with Denemo and then export the
lilypond file, but they cannot check the quality of the file. I'd
suggest them to try to submit their file to the mutopia-discuss list
and see if someone can clean the input. Personally, I'd be glad to
contribute this way.
Better would be to write a command for Denemo that adds the
mutopia-required headers. A more serious problem would be Denemo users
who have no understanding of the LilyPond output, they will not be using
the \repeat { . } format as it requires placing the first part of
the construct at a place where nothing may appear in the typeset file
(e.g. at the beginning).
So they will generate LilyPond files with
\set Score.repeatCommands = #'((volta 1))
and such like, which make reading the LilyPond output harder. I don't
think there would be a practical way round that.
Richard
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
Federico Bruni fedel...@gmail.com writes: I'd suggest them to try to submit their file to the mutopia-discuss list and see if someone can clean the input. According to Gmane, the last non-SPAM message on the mutopia-discuss list was in April. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
On Wed, 2014-01-01 at 19:01 +0100, Federico Bruni wrote: I'd like to have some feedback from you. Which change in the Mutopia interface/decisions would make you start contributing or contributing more? I can see these big problems: My biggest problem is that I only have the energy to go to one website. I am like the shopper who does not go shopping around. I monitor the recent scores page of IMSLP for things of interest, and re-typeset those that need it. I think a really serious improvement could be made by systematically posting the PDFs of mutopia scores on IMSLP with links to the source files back on Mutopia (where the source files can be checked for malicious code - we don't want people downloading and executing a .ly file only to realize that someone thought it was funny to put rm *.* inside it, it would be *such* bad publicity. I am not trying to give ideas to rival music typesetters here...). Richard ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
Federico Bruni fedel...@gmail.com writes: Dear Lilyponders some recent posts in this list made me think about the weaknesses of Mutopia and why people who may contribute to it are not doing so. I'd like to have some feedback from you. Which change in the Mutopia interface/decisions would make you start contributing or contributing more? Mutopia scores tend to be useful as PDF only, the equivalent of dead paper. They usually have been compiled with an ancient version of LilyPond nobody has available any more. As a result, recompilation, transposing, changes of paper format and other things are hard. Mutopia's biggest weakness is not that it is missing new contributions but rather that the existing contributions become unusable. So what's needed is: a) automated run of convert-ly to all following available stable versions b) an interface for people to say PDF for upgraded file looks ok c) an interface for people to fix up files that fail after convert-ly or are unnecessary complex given new LilyPond features. d) grading/voting mechanisms for scores/contributors e) obsoleting files when they have been converted and the version is really outdated (like, beyond Debian Stale from one year ago) At the current point of time, Mutopia is a large bitrot graveyard. If one makes it easy to crowdsource and/or automate the _maintenance_ of files and make the various versions available, it might become a lot more active. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
David Kastrup d...@gnu.org writes: Mutopia's biggest weakness is not that it is missing new contributions but rather that the existing contributions become unusable. So what's needed is: a) automated run of convert-ly to all following available stable versions b) an interface for people to say PDF for upgraded file looks ok c) an interface for people to fix up files that fail after convert-ly or are unnecessary complex given new LilyPond features. d) grading/voting mechanisms for scores/contributors e) obsoleting files when they have been converted and the version is really outdated (like, beyond Debian Stale from one year ago) At the current point of time, Mutopia is a large bitrot graveyard. If one makes it easy to crowdsource and/or automate the _maintenance_ of files and make the various versions available, it might become a lot more active. Oh, and perhaps let people associate update/entry work with bitcoin and Paypal addresses so that downloaders can easily transfer a suggested fee, and that one can, say, point to an IMSLP source of public domain photocopies and say having them in LilyPond 2.16 would be worth $x to me. Or having this 2.12 source in 2.18 and using the new ??? syntax would be worth $x to me, with the ability of multiple people to pitch in. The success of LilyPond-based projects like SCORA URL:http://www.flanderstoday.eu/innovation/leuven-orchestra-uses-tablet-follow-music-scores ultimately depends on a reasonable availability of workers who are willing to prepare LilyPond scores for a fee. Without that, the projects don't scale. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
Federico Bruni fedelogy at gmail.com writes: 4. Web interface Currently the contributions are handled via github or by email. Github is a good way but it's for geeks only. There are currently only seven contributors: https://github.com/chrissawer/The-Mutopia-Project/graphs/contributors The github is not mentioned on the mutopiaproject contributions page. Pointing to that page might reassure contributors that the project is alive and well. I contribute via email. When I am learning a public-domain piece of music I look for a source on MutopiaProject. Published music often has impossible page-breaks, and revising a LilyPond source is more rewarding than cutting up the paper score. Updating old scores is usually a matter of convert-ly followed by removal of typically very many \overrides that are no longer needed. I wish there was a side-by-side diff for this one: https://github.com/chrissawer/The-Mutopia-Project/ commit/81a588f5d16a3bcb4110bd1e8197dbdc5a08137e Just say 'no' to Scheme. I put just one scheme function, copied from the manual, into a mutopiaproject contribution, and that caused problems almost immediately. http://lists.gnu.org/archive/html/lilypond-devel/2011-11/msg00201.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
Hi, The webpage it self should look more modern. IMSLP is a good example but even small changes could help a lot. 2. Licenses Currently Mutopia accepts only transcriptions licensed as public domain, CC By, CC By-Sa: http://www.mutopiaproject.org/legal.html I don't know what led to this decision, but I can imagine that at least CC By-Sa-Nc would be preferred by some. BY-SA-NC is not approved as a free cultural license: http://creativecommons.org/freeworks These arguments should be considered. But it is a valid choice and it could also be good to have that option. And the mutopia footer with its varying font sizes is ugly! 4. Web interface Currently the contributions are handled via github or by email. Github is a good way but it's for geeks only. There are currently only seven contributors: https://github.com/chrissawer/The-Mutopia-Project/graphs/contributors I didn't know that this git repo. The email may be a good alternative, but who is receiving contributions@ emails? Just Chris? I have no idea if people send contributions this way. The last time (1 year ago) I sent an email to the suggested address, I did not get any reply. So I didn’t try again and thought Mutopia is just dead. I have some scores, that I could upload, I could also use them to test any new upload feature. A modern web interface may attract more contributions? For several years now, I have sketches and ideas how that could work and look and I always wanted to learn enough web techniques to make a proposal which can be tested. But so far I still don’t have the capabilities to do it. The last discussion I started about Mutopia ended without changing the website. If there is a chance that things really end up on the website, I would search for the notes I have taken back then and contribute to the discussion (but unfortunately not to realize it, see above). Updating the current version would also improve it. I could take care of updating some scores. Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Mutopia-discuss] Help with Lilypond
Howdy! There are lots of different ways to do this. Lilypond and the *NIX systems it runs on are very flexible... You may learn something by wading through the files in my source directory tree for my arrangement of Goldberg Variations http://indra2.web.net/~linuxsui/gooeytar.com/public/bwv-988/0.80/ I have tried to organize the build of both a book and individual variations all from the same source files organized in multiple directories It can certainly be improved on, but it seems to work out ok.. -steve Hi Huw I'm CCing lilypond-user because you'll probably get more help from there 2013/4/21 Huw Richards a...@eng.cam.ac.uk Dear All, I have been using Lilypond to transcribe various pieces of music for Mutopia for 2 or 3 years now, but have not yet uploaded anything to Mutopia. I am very happy with typing in the notes, clefs, time signatures etc. but I struggle to know how to produce a complete assembled document with page numbers, cover, text etc. As an example of what I mean, I have produced a set of six viola/ violin duets by Benjamin Blake. I have them as multiple files (- viola file, violin file, score file) for each duet. I would like to be able to combine them elegantly into a book. I think I may have started in the wrong way and perhaps should have understood more about possible file structures before I started. I do not understand how, or if, Lilypond can combine files together to produce a single output. Yes, you can: search \include in the documentation. \include is the same as pasting the content of the file in the point you use it. You should have a good understanding of file structure. If you can provide a minimal example or a link to the files you've written, we'll be able to help you. Anyway, this is the relevant part of the documentation: http://lilypond.org/doc/v2.17/Documentation/notation/input-structure Is there any way / anywhere I can get face-to-face training or help with this in particular and with Lilypond in general? I live in Cambridge, UK. Maybe someone from lilypond-user lives there... 2013/4/21 Huw Richards a...@eng.cam.ac.uk Dear All, I have been using Lilypond to transcribe various pieces of music for Mutopia for 2 or 3 years now, but have not yet uploaded anything to Mutopia. I am very happy with typing in the notes, clefs, time signatures etc. but I struggle to know how to produce a complete assembled document with page numbers, cover, text etc. As an example of what I mean, I have produced a set of six viola/ violin duets by Benjamin Blake. I have them as multiple files (- viola file, violin file, score file) for each duet. I would like to be able to combine them elegantly into a book. I think I may have started in the wrong way and perhaps should have understood more about possible file structures before I started. I do not understand how, or if, Lilypond can combine files together to produce a single output. Is there any way / anywhere I can get face-to-face training or help with this in particular and with Lilypond in general? I live in Cambridge, UK. Huw Richards - a...@eng.cam.ac.uk ___ Mutopia-discuss mailing list mutopia-disc...@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list mutopia-disc...@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Mutopia-discuss] Help with Lilypond
Hi Huw I'm CCing lilypond-user because you'll probably get more help from there 2013/4/21 Huw Richards a...@eng.cam.ac.uk Dear All, I have been using Lilypond to transcribe various pieces of music for Mutopia for 2 or 3 years now, but have not yet uploaded anything to Mutopia. I am very happy with typing in the notes, clefs, time signatures etc. but I struggle to know how to produce a complete assembled document with page numbers, cover, text etc. As an example of what I mean, I have produced a set of six viola/ violin duets by Benjamin Blake. I have them as multiple files (- viola file, violin file, score file) for each duet. I would like to be able to combine them elegantly into a book. I think I may have started in the wrong way and perhaps should have understood more about possible file structures before I started. I do not understand how, or if, Lilypond can combine files together to produce a single output. Yes, you can: search \include in the documentation. \include is the same as pasting the content of the file in the point you use it. You should have a good understanding of file structure. If you can provide a minimal example or a link to the files you've written, we'll be able to help you. Anyway, this is the relevant part of the documentation: http://lilypond.org/doc/v2.17/Documentation/notation/input-structure Is there any way / anywhere I can get face-to-face training or help with this in particular and with Lilypond in general? I live in Cambridge, UK. Maybe someone from lilypond-user lives there... 2013/4/21 Huw Richards a...@eng.cam.ac.uk Dear All, I have been using Lilypond to transcribe various pieces of music for Mutopia for 2 or 3 years now, but have not yet uploaded anything to Mutopia. I am very happy with typing in the notes, clefs, time signatures etc. but I struggle to know how to produce a complete assembled document with page numbers, cover, text etc. As an example of what I mean, I have produced a set of six viola/ violin duets by Benjamin Blake. I have them as multiple files (- viola file, violin file, score file) for each duet. I would like to be able to combine them elegantly into a book. I think I may have started in the wrong way and perhaps should have understood more about possible file structures before I started. I do not understand how, or if, Lilypond can combine files together to produce a single output. Is there any way / anywhere I can get face-to-face training or help with this in particular and with Lilypond in general? I live in Cambridge, UK. Huw Richards - a...@eng.cam.ac.uk ___ Mutopia-discuss mailing list mutopia-disc...@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mutopia
I give free web hosting accounts to lilyponders. You can have your own drupal installation (or whatever), so if you just need a place to host your files, that's an option. M. PS git and viewgit are installed as well On Sat, Feb 23, 2013 at 11:58 AM, Noeck noeck.marb...@gmx.de wrote: Hi, I have some pieces (vocal scores of 3 chorals of Bach's Christmas Oratorio and in future some more) that I would like to share. I got no response from the mutopiaproject. Is there anything new since: http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00300.html What should I do? Upload it to imslp and forget about mutopia? Did someone start an official mutopia-collection-git-repository? Cheers, Joram PS: I would also volunteer to update some scores on Mutopia. Most of them would profit from newer LilyPond versions and sometimes a few additional tweaks would change a lot. But as long as this will not end up online, there is no point in doing so. ___ 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: Mutopia
Il 23/02/2013 20:19, Felix Janda ha scritto: Glen Larsen has described a workflow for updating pieces in the wiki. https://github.com/chrissawer/The-Mutopia-Project/wiki I asked him to announce it when ready but I guess he didn't because it's still a work in progress. I'll try to add some feedback in the wiki -- Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mutopia
Hi, You may upload them to www.cpdl.org (Choral Public Domain Library) and IMSLP. In CPDL you can link the files in your server or directly upload to cpdl server. Remember files should be in Public Domain (atleast in US) Regards, Eby --- On Sat, 2/23/13, Noeck noeck.marb...@gmx.de wrote: From: Noeck noeck.marb...@gmx.de Subject: Mutopia To: lilypond-user lilypond-user@gnu.org Date: Saturday, February 23, 2013, 4:58 PM Hi, I have some pieces (vocal scores of 3 chorals of Bach's Christmas Oratorio and in future some more) that I would like to share. I got no response from the mutopiaproject. Is there anything new since: http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00300.html What should I do? Upload it to imslp and forget about mutopia? Did someone start an official mutopia-collection-git-repository? Cheers, Joram PS: I would also volunteer to update some scores on Mutopia. Most of them would profit from newer LilyPond versions and sometimes a few additional tweaks would change a lot. But as long as this will not end up online, there is no point in doing so. ___ 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
Mutopia
Hi, I have some pieces (vocal scores of 3 chorals of Bach's Christmas Oratorio and in future some more) that I would like to share. I got no response from the mutopiaproject. Is there anything new since: http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00300.html What should I do? Upload it to imslp and forget about mutopia? Did someone start an official mutopia-collection-git-repository? Cheers, Joram PS: I would also volunteer to update some scores on Mutopia. Most of them would profit from newer LilyPond versions and sometimes a few additional tweaks would change a lot. But as long as this will not end up online, there is no point in doing so. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mutopia
Am 23.02.2013 17:58, schrieb Noeck: Hi, I have some pieces (vocal scores of 3 chorals of Bach's Christmas Oratorio and in future some more) that I would like to share. I got no response from the mutopiaproject. Is there anything new since: http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00300.html What should I do? Upload it to imslp and forget about mutopia? Did someone start an official mutopia-collection-git-repository? Cheers, Joram PS: I would also volunteer to update some scores on Mutopia. Most of them would profit from newer LilyPond versions and sometimes a few additional tweaks would change a lot. But as long as this will not end up online, there is no point in doing so. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user I'm not into the regularely visible discussions about Mutopia progress. But Mutopia actually has a Github repository: https://github.com/chrissawer/The-Mutopia-Project And from its commit history it doesn't look dead at all. So it seems that forking this repo and sending a pull request should be a reasonable way to go. But of course one shouldn't do such a thing without asking first. And if you don't get an answer ... Just my thoughts... Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mutopia
New contributions will not be added until such a new team is in place, although I will try to continue to process updates to existing contributions where possible. This is from Chris Sawyer's message (copied below) to the Mutopia discussion list on November 25, 2012, in the thread Mutopia must live! Cheers, -Paul ___ All, Thanks for the various messages during today. As has become rather obvious, Mutopia activity has been almost non-existant for the last few months and the time has come for me to hand over leadership to someone new with the energy and enthusiasm to take the project forward. I have been leading the project since 1999 but unfortunately no longer have the time to put in the hours required to bring the site up to modern standards and co-ordinate the addition and updating of contributions. We attempted to set up a new system for handling contributions around a year ago but unfortunately that wasn't completed for various reasons. I do not want to see Mutopia die due to lack of interest on my part, and am willing to work for several months with a new team to get things going again. However someone needs to volunteer to co-ordinate that team. New contributions will not be added until such a new team is in place, although I will try to continue to process updates to existing contributions where possible. Thanks to all who have supported Mutopia since 1999 and if you are interested in co-ordinating the project from now onwards please contact me by e-mail. If you want to see how things work at present, the source code for the website, scripts and all LilyPond files can be found in github. Of course I will give admin rights to the new co-ordinator so the project can be taken forward. I still believe Mutopia is unique in offering open source sheet music that can be edited, transposed, arranged, etc. all using free software. I really hope that a new team can be found to continue the work. Best regards, Chris ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mutopia
On 02/23/13 at 05:58pm, Noeck wrote: Hi, I have some pieces (vocal scores of 3 chorals of Bach's Christmas Oratorio and in future some more) that I would like to share. I got no response from the mutopiaproject. Is there anything new since: http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00300.html What should I do? Upload it to imslp and forget about mutopia? Did someone start an official mutopia-collection-git-repository? You can find the official git repository at github at http://github.com/chrissawer/The-Mutopia-Project It should be useful to have a look at the issues and the wiki. Some new pieces have been added via github's pull-requests but not many, yet. So fork the repository and file a pull-request. It won't be forgotten, but it might take some time for it to make it into the official repository. Thanks that you also want to help with updating some pieces. Pieces in very old lilypond syntax make it hard for people to tweak scores from Mutopia to their hearts content. Glen Larsen has described a workflow for updating pieces in the wiki. For updates you won't have to wait that long to find them in the main repository. Felix ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Il 24/11/2012 03:34, Keith OHara ha scritto:
You might not have seen that Nick posted a much nicer formatting for
barre indications.
http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00570.html
It avoids taking apart LilyPond's internal data structures, which makes
it better for mutopiaproject.
You can adjust Nick's function to use it as \barre 3 { %{ music %} } and
have it set minimumFret=3 so you don't need so many string number
entries. Scheme can convert to Roman numerals.
barre = #(define-music-function (parser location
strg music) (number? ly:music?)
#{
\set TabStaff.minimumFret = $strg
\set TabStaff.restrainOpenStrings = ##t
\once\override TextSpanner #'(bound-details left text)
= #(format #f B ~@r strg)
%{ ... Nick's other style settings ...%}
\startTextSpan
$music
\stopTextSpan
\unset TabStaff.minimumFret
\unset TabStaff.restrainOpenStrings
#})
I've just realized that it would be better not to specify the context
and let LilyPond use the Voice context, otherwise semi-barré are not
possible in polyphonic music.
See this example:
\version 2.17.9
barreOld =
#(define-music-function (parser location strg music)(number? ly:music?)
#{
\set Staff.minimumFret = $strg
\set Staff.restrainOpenStrings = ##t
\once \override TextSpanner.bound-details.left.text = #(format #f
B ~@r strg)
\once \override TextSpanner.font-shape = #'upright
\once \override TextSpanner.bound-details.left.stencil-align-dir-y
= #CENTER
\once \override TextSpanner.style = #'line
\once \override TextSpanner.bound-details.right.text = \markup
\draw-line #'(0 . -1)
\once \override TextSpanner.to-barline = ##t
\once \override TextSpanner.bound-details.right.padding = #1.5
\startTextSpan
$music
\stopTextSpan
\unset Staff.minimumFret
\unset Staff.restrainOpenStrings
#})
barre =
#(define-music-function (parser location strg music)(number? ly:music?)
#{
\set minimumFret = $strg
\set restrainOpenStrings = ##t
\once \override TextSpanner.bound-details.left.text = #(format #f
B ~@r strg)
\once \override TextSpanner.font-shape = #'upright
\once \override TextSpanner.bound-details.left.stencil-align-dir-y
= #CENTER
\once \override TextSpanner.style = #'line
\once \override TextSpanner.bound-details.right.text = \markup
\draw-line #'(0 . -1)
\once \override TextSpanner.to-barline = ##t
\once \override TextSpanner.bound-details.right.padding = #1.5
\startTextSpan
$music
\stopTextSpan
\unset minimumFret
\unset restrainOpenStrings
#})
first = \relative c {
\barreOld 2 { e a cis4 a cis fis }
\barre 2 { e, a cis4 a cis fis }
}
second = \relative c {
a1 a
}
\score {
\new StaffGroup
\new Staff = guitar
\context Voice = first voice { \clef G_8 \voiceOne \first }
\context Voice = second voice { \clef G_8 \voiceTwo \second }
\new TabStaff = tab
\context TabVoice = tab first voice { \clef moderntab
\voiceOne \first }
\context TabVoice = tab second voice { \clef moderntab
\voiceTwo \second }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
2012/11/26 Nick Payne nick.pa...@internode.on.net:
On 24/11/12 13:34, Keith OHara wrote:
barre = #(define-music-function (parser location
strg music) (number? ly:music?)
#{
\set TabStaff.minimumFret = $strg
\set TabStaff.restrainOpenStrings = ##t
\once\override TextSpanner #'(bound-details left text)
= #(format #f B ~@r strg)
%{ ... Nick's other style settings ...%}
\startTextSpan
$music
\stopTextSpan
\unset TabStaff.minimumFret
\unset TabStaff.restrainOpenStrings
#})
I was testing this barre function without the tabstaff stuff for use with
scores in standard notation, and added a few extra TextSpanner settings to
get the output that I want. One problem that I can't fathom is that if I add
\override TextSpanner.bound-details.right-broken.text = ##f, so that the
small vertical line at the RH end of the spanner is not drawn at the end of
a staff when the barre wraps to the following staff, then the line also
doesn't get drawn if the barre ends at the right hand end of a staff,
without being broken. Why is lilypond thinking that the TextSpanner is
breaking across staves when it isn't? In the example below, the end of the
second TextSpanner is missing the vertical line unless the override of
TextSpanner.bound-details.right-broken.text = ##f is commented out.
\version 2.17.6
% Function contributed by Thomas Morley:
% http://lsr.dsi.unimi.it/LSR/Item?id=857
barre =
#(define-music-function (parser location strg music)(number? ly:music?)
#{
%\set TabStaff.minimumFret = $strg
%\set TabStaff.restrainOpenStrings = ##t
\once\override TextSpanner.bound-details.left.text = #(format #f ~@r
strg)
\once\override TextSpanner.font-shape = #'upright
\once\override TextSpanner.bound-details.left.stencil-align-dir-y =
#CENTER
\once\override TextSpanner.style = #'line
\once\override TextSpanner.bound-details.right.text = \markup \draw-line
#'(0 . -1)
\once\override TextSpanner.to-barline = ##t
\once\override TextSpanner.bound-details.right.padding = #1.5
\once\override TextSpanner.bound-details.right-broken.padding = #0.5
\once\override TextSpanner.bound-details.left-broken.padding = #2
\once\override TextSpanner.bound-details.left-broken.text = ##f
\once\override TextSpanner.bound-details.right-broken.text = ##f
\startTextSpan
$music
\stopTextSpan
%\unset TabStaff.minimumFret
%\unset TabStaff.restrainOpenStrings
#})
\relative c'' {
\key c \major
\barre3 { \repeat unfold 48 { d4 } }
\barre3 { \repeat unfold 20 { d4 } }
\break
\repeat unfold 20 { d4 }
}
Hi Nick,
after some private discussion with Federico it turns out, that
\articulate can't deal with
Wrong false barchecks are returned.
I'd recommend to use s*0 instead.
I raised a bug-report about it.
Best,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
2012/11/28 Nick Payne nick.pa...@internode.on.net:
On 28/11/12 09:35, Thomas Morley wrote:
Although I can confirm your observation, I asked myself: How would I
use a TextSpanner to span a repeat-unfold-expression with pure
LilyPond-syntax?
I couldn't find any reasonable method.
The following doesn't work (ofcourse not):
\relative c {
\clef treble_8
\override TextSpanner #'(bound-details left text) = #B V
\startTextSpan
\repeat unfold 24 { c4 } \stopTextSpan
}
How to do?
My previous example was quite artificial, but here's part of an actual score
where I would want to indicate a barre - it's from a transcription of
Haydn's string quartet Op 2 No 1, transcribed for guitar duet by the 19th
century guitarist François de Fossa. Guitar 2 plays a lot of repeated chords
like this, sometimes the same chord for several bars. Here the console
doesn't indicate any error, but the barre doesn't display.
\version 2.16.0
beamTuplets = \set beamExceptions =
#'((end . (((1 . 24) . (3 3 3 3)
#(define (text-spanner-start-stop mus)
(let ((elts (extract-typed-music mus 'rhythmic-event)))
(for-each
(lambda (sel)
(let ((m (sel elts)))
(set! (ly:music-property m 'articulations)
(cons (make-music 'TextSpanEvent
'span-direction (sel '(-1 1)))
(ly:music-property m 'articulations)
(list last first)))
mus)
barre =
#(define-music-function (parser location strg music)(string? ly:music?)
(let ((arg (string-append B strg)))
#{
\override TextSpanner #'(bound-details left text) = $arg
#(text-spanner-start-stop music)
#}))
\relative c' {
\clef treble_8
\time 2/4
\key d \major
{
\beamTuplets
\set tupletSpannerDuration = #(ly:make-moment 1 8)
\barre II { \times 2/3 { \repeat unfold 12 { a e16 } } }
}
\\
{
\beamTuplets
\set fingeringOrientations = #'(left)
\set tupletSpannerDuration = #(ly:make-moment 1 8)
\times 2/3 { cis,-4 \repeat unfold 11 { cis16 } }
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Nick,
apart from the repeat-unfold-problem there's an additional one, due to
the chord at the end of the TextSpanner.
Compare the output of:
\displayMusic {
\override TextSpanner #'(bound-details left text) = #II
c1\startTextSpan
d f\stopTextSpan
}
\displayMusic {
\barre II {
c1
d f
}
}
and you'll see that
(list (make-music
'TextSpanEvent
'span-direction
1))
is placed differently.
But I doubt I can work on this the next days.
Regards,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
On 29/11/12 12:45, Thomas Morley wrote:
2012/11/28 Nick Payne nick.pa...@internode.on.net:
On 28/11/12 09:35, Thomas Morley wrote:
Although I can confirm your observation, I asked myself: How would I
use a TextSpanner to span a repeat-unfold-expression with pure
LilyPond-syntax?
I couldn't find any reasonable method.
The following doesn't work (ofcourse not):
\relative c {
\clef treble_8
\override TextSpanner #'(bound-details left text) = #B V
\startTextSpan
\repeat unfold 24 { c4 } \stopTextSpan
}
How to do?
My previous example was quite artificial, but here's part of an actual score
where I would want to indicate a barre - it's from a transcription of
Haydn's string quartet Op 2 No 1, transcribed for guitar duet by the 19th
century guitarist François de Fossa. Guitar 2 plays a lot of repeated chords
like this, sometimes the same chord for several bars. Here the console
doesn't indicate any error, but the barre doesn't display.
\version 2.16.0
beamTuplets = \set beamExceptions =
#'((end . (((1 . 24) . (3 3 3 3)
#(define (text-spanner-start-stop mus)
(let ((elts (extract-typed-music mus 'rhythmic-event)))
(for-each
(lambda (sel)
(let ((m (sel elts)))
(set! (ly:music-property m 'articulations)
(cons (make-music 'TextSpanEvent
'span-direction (sel '(-1 1)))
(ly:music-property m 'articulations)
(list last first)))
mus)
barre =
#(define-music-function (parser location strg music)(string? ly:music?)
(let ((arg (string-append B strg)))
#{
\override TextSpanner #'(bound-details left text) = $arg
#(text-spanner-start-stop music)
#}))
\relative c' {
\clef treble_8
\time 2/4
\key d \major
{
\beamTuplets
\set tupletSpannerDuration = #(ly:make-moment 1 8)
\barre II { \times 2/3 { \repeat unfold 12 { a e16 } } }
}
\\
{
\beamTuplets
\set fingeringOrientations = #'(left)
\set tupletSpannerDuration = #(ly:make-moment 1 8)
\times 2/3 { cis,-4 \repeat unfold 11 { cis16 } }
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Nick,
apart from the repeat-unfold-problem there's an additional one, due to
the chord at the end of the TextSpanner.
Compare the output of:
\displayMusic {
\override TextSpanner #'(bound-details left text) = #II
c1\startTextSpan
d f\stopTextSpan
}
\displayMusic {
\barre II {
c1
d f
}
}
and you'll see that
(list (make-music
'TextSpanEvent
'span-direction
1))
is placed differently.
Actually, a chord at the start of the spanner also causes the barre to
not display...
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Thomas Morley thomasmorle...@googlemail.com writes: Hi Nick, apart from the repeat-unfold-problem there's an additional one, due to the chord at the end of the TextSpanner. #(define (text-spanner-start-stop mus) (let ((elts (extract-typed-music mus 'rhythmic-event))) Exchange 'rhythmic-event for '(rhythmic-event event-chord) -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
On 27/11/12 11:52, David Kastrup wrote:
#(define (text-spanner-start-stop mus)
(let ((elts (extract-typed-music mus 'rhythmic-event)))
(for-each
(lambda (sel)
(let ((m (sel elts)))
(set! (ly:music-property m 'articulations)
(cons (make-music 'TextSpanEvent
'span-direction (sel '(-1 1)))
(ly:music-property m 'articulations)
(list last first)))
mus)
Thanks. Substituting that works well except when \repeat unfold is used
inside the braces holding the music for the barre, when the console contains
warning: cannot find start of text spanner
warning: unterminated text spanner.
and the output is not what is desired.
\version 2.16.0
#(define (text-spanner-start-stop mus)
(let ((elts (extract-typed-music mus 'rhythmic-event)))
(for-each
(lambda (sel)
(let ((m (sel elts)))
(set! (ly:music-property m 'articulations)
(cons (make-music 'TextSpanEvent
'span-direction (sel '(-1 1)))
(ly:music-property m 'articulations)
(list last first)))
mus)
barre =
#(define-music-function (parser location strg music)(string? ly:music?)
(let ((arg (string-append B strg)))
#{
\override TextSpanner #'(bound-details left text) = $arg
#(text-spanner-start-stop music)
#}))
\relative c {
\clef treble_8
\barre V { \repeat unfold 24 { c4 } }
}
attachment: test.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
2012/11/27 David Kastrup d...@gnu.org: Probably try something like #(define (text-spanner-start-stop mus) (let ((elts (extract-typed-music mus 'rhythmic-event))) (for-each (lambda (sel) (let ((m (sel elts))) (set! (ly:music-property m 'articulations) (cons (make-music 'TextSpanEvent 'span-direction (sel '(-1 1))) (ly:music-property m 'articulations) (list last first))) mus) Thanks a lot. Works fine. I'll update the LSR-snippet following your suggestion. -Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
2012/11/27 Nick Payne nick.pa...@internode.on.net:
On 27/11/12 11:52, David Kastrup wrote:
#(define (text-spanner-start-stop mus)
(let ((elts (extract-typed-music mus 'rhythmic-event)))
(for-each
(lambda (sel)
(let ((m (sel elts)))
(set! (ly:music-property m 'articulations)
(cons (make-music 'TextSpanEvent
'span-direction (sel '(-1 1)))
(ly:music-property m 'articulations)
(list last first)))
mus)
Thanks. Substituting that works well except when \repeat unfold is used
inside the braces holding the music for the barre, when the console contains
warning: cannot find start of text spanner
warning: unterminated text spanner.
and the output is not what is desired.
\version 2.16.0
#(define (text-spanner-start-stop mus)
(let ((elts (extract-typed-music mus 'rhythmic-event)))
(for-each
(lambda (sel)
(let ((m (sel elts)))
(set! (ly:music-property m 'articulations)
(cons (make-music 'TextSpanEvent
'span-direction (sel '(-1 1)))
(ly:music-property m 'articulations)
(list last first)))
mus)
barre =
#(define-music-function (parser location strg music)(string? ly:music?)
(let ((arg (string-append B strg)))
#{
\override TextSpanner #'(bound-details left text) = $arg
#(text-spanner-start-stop music)
#}))
\relative c {
\clef treble_8
\barre V { \repeat unfold 24 { c4 } }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Although I can confirm your observation, I asked myself: How would I
use a TextSpanner to span a repeat-unfold-expression with pure
LilyPond-syntax?
I couldn't find any reasonable method.
The following doesn't work (ofcourse not):
\relative c {
\clef treble_8
\override TextSpanner #'(bound-details left text) = #B V
\startTextSpan
\repeat unfold 24 { c4 } \stopTextSpan
}
How to do?
-Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
On 28/11/12 09:35, Thomas Morley wrote:
Although I can confirm your observation, I asked myself: How would I
use a TextSpanner to span a repeat-unfold-expression with pure
LilyPond-syntax?
I couldn't find any reasonable method.
The following doesn't work (ofcourse not):
\relative c {
\clef treble_8
\override TextSpanner #'(bound-details left text) = #B V
\startTextSpan
\repeat unfold 24 { c4 } \stopTextSpan
}
How to do?
My previous example was quite artificial, but here's part of an actual
score where I would want to indicate a barre - it's from a
transcription of Haydn's string quartet Op 2 No 1, transcribed for
guitar duet by the 19th century guitarist François de Fossa. Guitar 2
plays a lot of repeated chords like this, sometimes the same chord for
several bars. Here the console doesn't indicate any error, but the barre
doesn't display.
\version 2.16.0
beamTuplets = \set beamExceptions =
#'((end . (((1 . 24) . (3 3 3 3)
#(define (text-spanner-start-stop mus)
(let ((elts (extract-typed-music mus 'rhythmic-event)))
(for-each
(lambda (sel)
(let ((m (sel elts)))
(set! (ly:music-property m 'articulations)
(cons (make-music 'TextSpanEvent
'span-direction (sel '(-1 1)))
(ly:music-property m 'articulations)
(list last first)))
mus)
barre =
#(define-music-function (parser location strg music)(string? ly:music?)
(let ((arg (string-append B strg)))
#{
\override TextSpanner #'(bound-details left text) = $arg
#(text-spanner-start-stop music)
#}))
\relative c' {
\clef treble_8
\time 2/4
\key d \major
{
\beamTuplets
\set tupletSpannerDuration = #(ly:make-moment 1 8)
\barre II { \times 2/3 { \repeat unfold 12 { a e16 } } }
}
\\
{
\beamTuplets
\set fingeringOrientations = #'(left)
\set tupletSpannerDuration = #(ly:make-moment 1 8)
\times 2/3 { cis,-4 \repeat unfold 11 { cis16 } }
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
On 26/11/12 12:37, Keith OHara wrote:
Nick Payne nick.payne at internode.on.net writes:
On 24/11/12 13:34, Keith OHara wrote:
\once\override TextSpanner #'to-barline = ##t
\startTextSpan
$music
\stopTextSpan
Why is lilypond thinking that the
TextSpanner is breaking across staves when it isn't?
This function stops the Text Spanner at the first opportunity /after/
$music so if $music ends on a line-break, the spanner continues to the
first note on the next line. 'to-barline=#t is the option to omit
drawing the short section on the next line.
The other barre function at
% http://lsr.dsi.unimi.it/LSR/Item?id=857
disassembles $music to insert a \stopTextSpan just before the final note.
This assumes that $music is a single sequence, not something like
{...} // {...}
but it would work better with your method of handling line breaks.
Thanks. I had a look at http://lsr.dsi.unimi.it/LSR/Item?id=857.
However, even with a single sequence, in some situations it doesn't
handle braces during the barre - e.g. if you try
\barre V { c4 c c \times 2/3 { c8 c c } }
there's no error indication but the spanner stops too soon at the start
of the tuplet. Interestingly, this problem only happens if the contained
braces terminate at the same point as the barre, as
\barre V { c4 c \times 2/3 { c8 c c } c4 }
continues the spanner to the correct note. I don't know enough about
Scheme to figure out what the problem is.
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
2012/11/26 Nick Payne nick.pa...@internode.on.net:
On 26/11/12 12:37, Keith OHara wrote:
Nick Payne nick.payne at internode.on.net writes:
On 24/11/12 13:34, Keith OHara wrote:
\once\override TextSpanner #'to-barline = ##t
\startTextSpan
$music
\stopTextSpan
Why is lilypond thinking that the
TextSpanner is breaking across staves when it isn't?
This function stops the Text Spanner at the first opportunity /after/
$music so if $music ends on a line-break, the spanner continues to the
first note on the next line. 'to-barline=#t is the option to omit
drawing the short section on the next line.
The other barre function at
% http://lsr.dsi.unimi.it/LSR/Item?id=857
disassembles $music to insert a \stopTextSpan just before the final note.
This assumes that $music is a single sequence, not something like
{...} // {...}
but it would work better with your method of handling line breaks.
Thanks. I had a look at http://lsr.dsi.unimi.it/LSR/Item?id=857. However,
even with a single sequence, in some situations it doesn't handle braces
during the barre - e.g. if you try
\barre V { c4 c c \times 2/3 { c8 c c } }
there's no error indication but the spanner stops too soon at the start of
the tuplet. Interestingly, this problem only happens if the contained braces
terminate at the same point as the barre, as
\barre V { c4 c \times 2/3 { c8 c c } c4 }
continues the spanner to the correct note. I don't know enough about Scheme
to figure out what the problem is.
Nick
Hi Nick,
thanks for testing.
The problem is, that my code inserts the \stopTextSpan-equivalent
before the last of the music-elements. In your example, _before_
starting \times and not before the last note of \times.
Currently I can't see any possibility to fix that code, with reasonable effort.
Perhaps I should delete this snippet.
Best,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Thomas Morley thomasmorle...@googlemail.com writes:
2012/11/26 Nick Payne nick.pa...@internode.on.net:
Thanks. I had a look at http://lsr.dsi.unimi.it/LSR/Item?id=857. However,
even with a single sequence, in some situations it doesn't handle braces
during the barre - e.g. if you try
\barre V { c4 c c \times 2/3 { c8 c c } }
there's no error indication but the spanner stops too soon at the start of
the tuplet. Interestingly, this problem only happens if the contained braces
terminate at the same point as the barre, as
\barre V { c4 c \times 2/3 { c8 c c } c4 }
continues the spanner to the correct note. I don't know enough about Scheme
to figure out what the problem is.
Nick
Hi Nick,
thanks for testing.
The problem is, that my code inserts the \stopTextSpan-equivalent
before the last of the music-elements. In your example, _before_
starting \times and not before the last note of \times.
Probably try something like
#(define (text-spanner-start-stop mus)
(let ((elts (extract-typed-music mus 'rhythmic-event)))
(for-each
(lambda (sel)
(let ((m (sel elts)))
(set! (ly:music-property m 'articulations)
(cons (make-music 'TextSpanEvent
'span-direction (sel '(-1 1)))
(ly:music-property m 'articulations)
(list last first)))
mus)
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Il 24/11/2012 22:53, Nick Payne ha scritto: BTW, given that guitar right-hand fingering in a score is indicated by the letters p, i, m, and a, I think that the source is easier to read if you define P=\rightHandFinger #1 I=\rightHandFinger #2 M=\rightHandFinger #3 A=\rightHandFinger #4 rather than #(define RH rightHandFinger) Yes, it's better. Added, thanks -- Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
On 24/11/12 13:34, Keith OHara wrote:
barre = #(define-music-function (parser location
strg music) (number? ly:music?)
#{
\set TabStaff.minimumFret = $strg
\set TabStaff.restrainOpenStrings = ##t
\once\override TextSpanner #'(bound-details left text)
= #(format #f B ~@r strg)
%{ ... Nick's other style settings ...%}
\startTextSpan
$music
\stopTextSpan
\unset TabStaff.minimumFret
\unset TabStaff.restrainOpenStrings
#})
I was testing this barre function without the tabstaff stuff for use
with scores in standard notation, and added a few extra TextSpanner
settings to get the output that I want. One problem that I can't fathom
is that if I add \override TextSpanner.bound-details.right-broken.text =
##f, so that the small vertical line at the RH end of the spanner is not
drawn at the end of a staff when the barre wraps to the following staff,
then the line also doesn't get drawn if the barre ends at the right hand
end of a staff, without being broken. Why is lilypond thinking that the
TextSpanner is breaking across staves when it isn't? In the example
below, the end of the second TextSpanner is missing the vertical line
unless the override of TextSpanner.bound-details.right-broken.text = ##f
is commented out.
\version 2.17.6
% Function contributed by Thomas Morley:
% http://lsr.dsi.unimi.it/LSR/Item?id=857
barre =
#(define-music-function (parser location strg music)(number? ly:music?)
#{
%\set TabStaff.minimumFret = $strg
%\set TabStaff.restrainOpenStrings = ##t
\once\override TextSpanner.bound-details.left.text = #(format #f
~@r strg)
\once\override TextSpanner.font-shape = #'upright
\once\override TextSpanner.bound-details.left.stencil-align-dir-y =
#CENTER
\once\override TextSpanner.style = #'line
\once\override TextSpanner.bound-details.right.text = \markup
\draw-line #'(0 . -1)
\once\override TextSpanner.to-barline = ##t
\once\override TextSpanner.bound-details.right.padding = #1.5
\once\override TextSpanner.bound-details.right-broken.padding = #0.5
\once\override TextSpanner.bound-details.left-broken.padding = #2
\once\override TextSpanner.bound-details.left-broken.text = ##f
\once\override TextSpanner.bound-details.right-broken.text = ##f
\startTextSpan
$music
\stopTextSpan
%\unset TabStaff.minimumFret
%\unset TabStaff.restrainOpenStrings
#})
\relative c'' {
\key c \major
\barre3 { \repeat unfold 48 { d4 } }
\barre3 { \repeat unfold 20 { d4 } }
\break
\repeat unfold 20 { d4 }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Nick Payne nick.payne at internode.on.net writes:
On 24/11/12 13:34, Keith OHara wrote:
\once\override TextSpanner #'to-barline = ##t
\startTextSpan
$music
\stopTextSpan
Why is lilypond thinking that the
TextSpanner is breaking across staves when it isn't?
This function stops the Text Spanner at the first opportunity /after/
$music so if $music ends on a line-break, the spanner continues to the
first note on the next line. 'to-barline=#t is the option to omit
drawing the short section on the next line.
The other barre function at
% http://lsr.dsi.unimi.it/LSR/Item?id=857
disassembles $music to insert a \stopTextSpan just before the final note.
This assumes that $music is a single sequence, not something like
{...} // {...}
but it would work better with your method of handling line breaks.
I was testing this barre function without the tabstaff stuff
You could instead \set Staff.minimumFret ...
so it works with- or without the Tab Staff
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Il 24/11/2012 03:34, Keith OHara ha scritto:
You might not have seen that Nick posted a much nicer formatting for
barre indications.
http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00570.html
It avoids taking apart LilyPond's internal data structures, which makes
it better for mutopiaproject.
You can adjust Nick's function to use it as \barre 3 { %{ music %} } and
have it set minimumFret=3 so you don't need so many string number
entries. Scheme can convert to Roman numerals.
barre = #(define-music-function (parser location
strg music) (number? ly:music?)
#{
\set TabStaff.minimumFret = $strg
\set TabStaff.restrainOpenStrings = ##t
\once\override TextSpanner #'(bound-details left text)
= #(format #f B ~@r strg)
%{ ... Nick's other style settings ...%}
\startTextSpan
$music
\stopTextSpan
\unset TabStaff.minimumFret
\unset TabStaff.restrainOpenStrings
#})
I've just realized that there's a problem in this command.
I want to comment the TabStaff part of \score, so classical players can
enjoy a clean score while those who can't sight-read music can activate
the tablature.
But if you comment TabStaff the score breaks: a lot of tab staves are
printed,
I see that it's because of the \set TabStaff in the barre command above.
What do you recommend?
Thanks
--
Federico
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Federico Bruni fedel...@gmail.com writes:
Il 24/11/2012 03:34, Keith OHara ha scritto:
You might not have seen that Nick posted a much nicer formatting for
barre indications.
http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00570.html
It avoids taking apart LilyPond's internal data structures, which makes
it better for mutopiaproject.
You can adjust Nick's function to use it as \barre 3 { %{ music %} } and
have it set minimumFret=3 so you don't need so many string number
entries. Scheme can convert to Roman numerals.
barre = #(define-music-function (parser location
strg music) (number? ly:music?)
#{
\set TabStaff.minimumFret = $strg
\set TabStaff.restrainOpenStrings = ##t
\once\override TextSpanner #'(bound-details left text)
= #(format #f B ~@r strg)
%{ ... Nick's other style settings ...%}
\startTextSpan
$music
\stopTextSpan
\unset TabStaff.minimumFret
\unset TabStaff.restrainOpenStrings
#})
I've just realized that there's a problem in this command.
I want to comment the TabStaff part of \score, so classical players
can enjoy a clean score while those who can't sight-read music can
activate the tablature.
But if you comment TabStaff the score breaks: a lot of tab staves are
printed, I see that it's because of the \set TabStaff in the barre
command above. What do you recommend?
You could use \set Staff... instead. The normal staff will likely just
ignore those settings, and within a tabstaff, Staff is aliased to
TabStaff.
The disadvantage is that if you use \barre outside of any staff, it will
create a default Staff rather than a TabStaff.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Federico Bruni fedelogy at gmail.com writes: Il 24/11/2012 03:34, Keith OHara ha scritto: Federico Bruni fedelogy at gmail.com writes: I've updated to 2.16 the following piece of Mutopia: http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=636 Can anyone review it? I've also added the right harmonic (fifth fret of third string) in the last bar: \harmonicByFret #5 g,4.\3\fermata^Octav. I could not figure out what the version currently at mutopiaproject was trying to show. (Guitar harmonic notation confuses me; in bowed strings we use the diamond head to show where the string is touched, and/or a normal head at sounding pitch.) What you wrote seems a quite reasonable interpretation of the original, but the Octav. indication is not needed (and probably was wrong in the original). Touching the open G at the fifth fret divides it into fourths, producing a tone two octaves above the open-string G. The \harmonicByFret creates a diamond-head (apparently following the convention for guitar) at sounding pitch so no need for an extra Octav. But if you comment TabStaff the score breaks: a lot of tab staves are printed, I see that it's because of the \set TabStaff in the barre command above. I was going to suggest \tag #'tab \set ..., but David's suggestion seems much better \set Staff.minimumFret = $strg \unset Staff.minimumFret ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
On 24/11/12 19:02, Federico Bruni wrote: Il 24/11/2012 03:34, Keith OHara ha scritto: Federico Bruni fedelogy at gmail.com writes: I've updated to 2.16 the following piece of Mutopia: http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=636 Can anyone review it? I made one pass through, and made potential-corrections as I went. (attached) Hopefully you can use a 'diff' program to see the changes. Thanks Keith! I see that you've fixed a lot of fingerings, now it makes sense. You just missed a string number in the second voice of bar 15. I've also added the right harmonic (fifth fret of third string) in the last bar: \harmonicByFret #5 g,4.\3\fermata^Octav. The barré formatting is awesome. BTW, given that guitar right-hand fingering in a score is indicated by the letters p, i, m, and a, I think that the source is easier to read if you define P=\rightHandFinger #1 I=\rightHandFinger #2 M=\rightHandFinger #3 A=\rightHandFinger #4 rather than #(define RH rightHandFinger) and then you can use, for example g-\M to indicate the use of m, rather than g-\RH #3 . Upper case is needed because lower case p and a are already used for a dynamic indication and a note name. Nick ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Federico Bruni fedelogy at gmail.com writes:
I've updated to 2.16 the following piece of Mutopia:
http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=636
Can anyone review it?
I made one pass through, and made potential-corrections as I went. (attached)
Hopefully you can use a 'diff' program to see the changes.
You could use \open or -0 to indicate open strings.
Some string numbers were applied to a whole chord (single-note chords
presumably because fingering to the left only works within chords) so they
didn't print. I put string numbers for the bass notes below the staff.
With a few more fingerings to resolve ambiguity, you could leave the string
numbers un-printed. I suppose LilyPond still needs them in the input to
generate tablature.
The more-usual bar numbering for alternatives is available in 2.16
\set Score.alternativeNumberingStyle = #'numbers
You can put the coda on its own line, and ragged-right, with
\bar || \break
%% Coda
%{ ... the music in the coda ... %}
\bar |. \stopStaff s1
You might not have seen that Nick posted a much nicer formatting for barre
indications.
http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00570.html
It avoids taking apart LilyPond's internal data structures, which makes it
better for mutopiaproject.
You can adjust Nick's function to use it as \barre 3 { %{ music %} } and have
it set minimumFret=3 so you don't need so many string number entries. Scheme
can convert to Roman numerals.
barre = #(define-music-function (parser location
strg music) (number? ly:music?)
#{
\set TabStaff.minimumFret = $strg
\set TabStaff.restrainOpenStrings = ##t
\once\override TextSpanner #'(bound-details left text)
= #(format #f B ~@r strg)
%{ ... Nick's other style settings ...%}
\startTextSpan
$music
\stopTextSpan
\unset TabStaff.minimumFret
\unset TabStaff.restrainOpenStrings
#})
guitar.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Federico Bruni fedelogy at gmail.com writes:
I've updated to 2.16 the following piece of Mutopia:
http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=636
Can anyone review it?
I made one pass through, and made potential-corrections as I went. (attached)
Hopefully you can use a 'diff' program to see the changes.
Some string numbers were applied to a whole chord (single-note chords
presumably because fingering to the left only works within chords) so they
didn't print. I put string numbers for the bass notes below the staff.
With a few more fingerings to resolve ambiguity, you could leave the string
numbers un-printed. I suppose LilyPond still needs them in the input to
generate tablature.
The more-usual bar numbering for alternatives is available in 2.16
\set Score.alternativeNumberingStyle = #'numbers
You can put the coda on its own line, and ragged-right, with
\bar || \break
%% Coda
%{ ... the music in the coda ... %}
\bar |. \stopStaff s1
You might not have seen that Nick posted a much nicer formatting for barre
indications.
http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00570.html
It avoids taking apart LilyPond's internal data structures, which makes it
better for mutopiaproject.
You can adjust Nick's function to use it as \barre 3 { %{ music %} } and have
it set minimumFret=3 so you don't need so many string number entries. Scheme
can convert to Roman numerals.
barre = #(define-music-function (parser location
strg music) (number? ly:music?)
#{
\set TabStaff.minimumFret = $strg
\set TabStaff.restrainOpenStrings = ##t
\once\override TextSpanner #'(bound-details left text)
= #(format #f B ~@r strg)
%{ ... Nick's other style settings ...%}
\startTextSpan
$music
\stopTextSpan
\unset TabStaff.minimumFret
\unset TabStaff.restrainOpenStrings
#})
guitar.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Federico Bruni fedelogy at gmail.com writes:
I've updated to 2.16 the following piece of Mutopia:
http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=636
Can anyone review it?
I made one pass through, and made potential-corrections as I went. (attached)
Hopefully you can use a 'diff' program to see the changes.
You could use \open or -0 to indicate open strings.
Some string numbers were applied to a whole chord (single-note chords
presumably because fingering to the left only works within chords) so they
didn't print. I put string numbers for the bass notes below the staff.
With a few more fingerings to resolve ambiguity, you could leave the string
numbers un-printed. I suppose LilyPond still needs them in the input to
generate tablature.
The more-usual bar numbering for alternatives is available in 2.16
\set Score.alternativeNumberingStyle = #'numbers
You can put the coda on its own line, and ragged-right, with
\bar || \break
%% Coda
%{ ... the music in the coda ... %}
\bar |. \stopStaff s1
You might not have seen that Nick posted a much nicer formatting for barre
indications.
http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00570.html
It avoids taking apart LilyPond's internal data structures, which makes it
better for mutopiaproject.
You can adjust Nick's function to use it as \barre 3 { %{ music %} } and have
it set minimumFret=3 so you don't need so many string number entries. Scheme
can convert to Roman numerals.
barre = #(define-music-function (parser location
strg music) (number? ly:music?)
#{
\set TabStaff.minimumFret = $strg
\set TabStaff.restrainOpenStrings = ##t
\once\override TextSpanner #'(bound-details left text)
= #(format #f B ~@r strg)
%{ ... Nick's other style settings ...%}
\startTextSpan
$music
\stopTextSpan
\unset TabStaff.minimumFret
\unset TabStaff.restrainOpenStrings
#})
guitar.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Il 24/11/2012 03:34, Keith OHara ha scritto:
Federico Bruni fedelogy at gmail.com writes:
I've updated to 2.16 the following piece of Mutopia:
http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=636
Can anyone review it?
I made one pass through, and made potential-corrections as I went.
(attached) Hopefully you can use a 'diff' program to see the changes.
Thanks Keith!
I see that you've fixed a lot of fingerings, now it makes sense. You
just missed a string number in the second voice of bar 15.
I've also added the right harmonic (fifth fret of third string) in the
last bar:
\harmonicByFret #5 g,4.\3\fermata^Octav.
The barré formatting is awesome.
\version 2.16.0
#(define RH rightHandFinger)
% Function contributed by Thomas Morley:
% http://lsr.dsi.unimi.it/LSR/Item?id=857
barre =
#(define-music-function (parser location strg music)(number? ly:music?)
#{
\set TabStaff.minimumFret = $strg
\set TabStaff.restrainOpenStrings = ##t
\once\override TextSpanner #'(bound-details left text) = #(format #f B ~@r strg)
\once\override TextSpanner #'font-shape = #'upright
\once\override TextSpanner #'bound-details #'left #'stencil-align-dir-y = #CENTER
\once\override TextSpanner #'style = #'line
\once\override TextSpanner #'bound-details #'right #'text = \markup \draw-line #'(0 . -1)
\once\override TextSpanner #'to-barline = ##t
\once\override TextSpanner #'(bound-details right padding) = #1.5
\startTextSpan
$music
\stopTextSpan
\unset TabStaff.minimumFret
\unset TabStaff.restrainOpenStrings
#})
\header {
title = Sicilienne (Op 78)
composer = Gabriel Fauré
copyright = Domaine Public - Transcription guitare Ludovic Alexandre Morin - revue et doigtée Olivier Flatrès - 20/11/05
mutopiatitle = Sicilienne
mutopiacomposer = FaureG
mutopiaopus = O 78
mutopiainstrument = Guitar
date = 19th Century
source = Transcription
style = Romantic
typesetter = Olivier Flatrs
maintainer = Federico Bruni
lastupdated = \markup {
\simple #(strftime %x (localtime (current-time)))
}
footer = Mutopia-2005/11/25-636
tagline = \markup {
\override #'(box-padding . 1.0) \override #'(baseline-skip . 2.7)
\box \center-column { \small
\line { Sheet music from \with-url #http://www.MutopiaProject.org; \line { \teeny www. MutopiaProject \teeny .org \hspace #0.5 } ⢠\hspace #0.5 \italic Free to download, with the \italic freedom to distribute, modify and perform. }
\line { \small \line { Typeset using \with-url #http://www.LilyPond.org; \line { \teeny www. LilyPond \teeny .org } by \typesetter \hspace #-1.0 ⢠Updated by \maintainer on \lastupdated } }
\line { \teeny \line { This sheet music has been placed in the public domain by the typesetter, for details see: \hspace #-0.5 \with-url #http://creativecommons.org/licenses/publicdomain; http://creativecommons.org/licenses/publicdomain } } }
}
}
global = {
\set Score.alternativeNumberingStyle = #'numbers
\time 6/8
\key bes \major
}
first = \relative c {
\global
\partial 8 d\5-3-\RH #2 8_
\repeat volta 2 {
%\override StringNumber #'padding = #1.5
g-\RH #3 16- d\5-3-\RH #2 g\4-4-\RH #4 d\5 \barre3 { bes'\3-1-\RH #3 - g\4-\RH #2 d'-\RH #3 - f,-\RH #1 bes-\RH #2 d-\RH #3 g-\RH #4 8- } |
bes-1-\RH #3 16- d,\3-3-\RH #2 g\2-4-\RH #4 a- g8\2- \barre3 { a16-4 c,\3 d c\3 d8- } |
\barre1 { d-\RH #3 8.- c-1-\RH #3 16- e8- d8.- c16- e8- } |
d-2-\RH #3 16- fis,-3-\RH #1 a-1-\RH #2 fis a fis d'-\RH #4 8 a-\RH #3 d,\4\open-\RH #2 - |
g16- d\5-3-\RH #2 g\4-\RH #4 d\5 \barre 3 { bes'\3-1-\RH #3 - g\4 d'- f, bes d f8\2- } |
\barre 1 { aes-4-\RH #4 16- aes,-\RH #2 c-\RH #3 g'-3-\RH #4 - f8- } g-2-\RH #4 16- g, b g f'8\2- |
e\open-\RH #4 16- g,\4-4-\RH #1 bes-2-\RH #2 g ees'-3-\RH #4 8- d-2-\RH #4 16- fis,-4 a-1 fis bes-18-^\coda |
}
\alternative {
{ g\3-\RH #3 8- g\4-4-\RH #2 16 d\5-\RH #1 g\4 d\5 g-\RH #3 4- d\5-\RH #2 8- | }
{ g8- g16\4 d\5 g\4 d\5 g4- r8 | }
}
\repeat volta 2 {
\barre 5 { b'-4-\RH #4 16- g,-\RH #1 d'-3-\RH #2 g-4-\RH #3 - a-1-\RH #4 8- bes-3-\RH #3 16- g,-\RH #1 c-\RH #2 c'-4-\RH #3 - cis-4-\RH #4 8- } |
\barre 8 { d-3-\RH #4 16- ees,-\RH #2 a-3-\RH #3 ees-\RH #2 - f-\RH #3 8- } \barre 1 { g-4-\RH #4 16- f,-3-\RH #1 aes-\RH #1 f-3-\RH #1 d'-4-\RH #3 8- } |
bes-4-\RH #3 16- bes,-2-\RH #1 d-\RH #1 g-\RH #3 - a-2-\RH #4 8- \barre 1 { bes-4-\RH #3 16- ees,-\RH #1 bes'-\RH #2 c-\RH #3 - cis-2-\RH #4 8- } |
d-2-\RH #3 16- fis,-3-\RH #1 a-1-\RH #2 e'\open-\RH #3 - fis-1-\RH #4 8- \barre 3 g-\RH #4 d-\RH #3 bes-\RH #2 4- r8 |
}
\break
\repeat volta 2 {
g\2-4-\RH #4 16- a,-1\4-\RH #2 ees'-3\3-\RH #3 a,\4 ees'8\3 \barre 3 { d-1-\RH #4 16 g,-4 bes-1 g bes8 } |
\barre 6 { bes'-1-\RH #4 16- bes,-2-\RH #1 des-1-\RH #2 a'-4-\RH #3 - g-3-\RH #2 8- } \barre 5 { a-1-\RH #4 16- a,-2-\RH #1 c-1-\RH #2 g'-4-\RH #3 - fis-3-\RH
review of a Mutopia file (why TabStaff gives error here?)
Hi LilyPonders,
I've updated to 2.16 the following piece of Mutopia:
http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=636
Can anyone review it?
I had to do a lot of changes...
Also, I have a problem with TabStaff.
When I started to update the input I used also TabStaff, then I
commented it and added other changes. Now if I uncomment it again I get
the following error:
lilypond 2.16.1 [faure-sicilienne.ly] in avvio...
Processing `/home/fede/faure-sicilienne.ly'
Parsing...
Interpreting music...translation-functions.scm: In procedure list-ref in
expression (list-ref tuning (1- string)):
translation-functions.scm: Value out of range 0 to 4294967295: -1
It's a dropped D tuning and I can't see any note out of range.
What I'm missing?
Any suggestion is appreciated.
BTW, for those interested in contributing to Mutopia, check out this thread:
http://www.mail-archive.com/mutopia-discuss@mutopiaproject.org/msg00186.html
It would be nice to promote a Christmas sprint and encourage LilyPond
users to update Mutopia files to latest stable. Well, as soon as a new
team of Mutopia admins is setup.
Thanks
--
Federico
\version 2.16.0
#(define RH rightHandFinger)
% Function contributed by Thomas Morley:
% http://lsr.dsi.unimi.it/LSR/Item?id=857
barre =
#(define-music-function (parser location strg music)(string? ly:music?)
(let ((arg (string-append B strg)))
#{
\override TextSpanner #'(bound-details left text) = $arg
#(let ((elts (ly:music-property music 'elements)))
(make-music 'SequentialMusic 'elements
(append
(list (make-music 'TextSpanEvent 'span-direction -1))
(reverse (cdr (reverse elts)))
(list (make-music 'TextSpanEvent 'span-direction 1))
(list (last elts)
#}))
\header {
title = Sicilienne (Op 78)
composer = Gabriel Fauré
copyright = Domaine Public - Transcription guitare Ludovic Alexandre Morin - revue et doigtée Olivier Flatrès - 20/11/05
mutopiatitle = Sicilienne
mutopiacomposer = FaureG
mutopiaopus = O 78
mutopiainstrument = Guitar
date = 19th Century
source = Transcription
style = Romantic
typesetter = Olivier Flatrs
maintainer = Federico Bruni
lastupdated = \markup {
\simple #(strftime %x (localtime (current-time)))
}
footer = Mutopia-2005/11/25-636
tagline = \markup {
\override #'(box-padding . 1.0) \override #'(baseline-skip . 2.7)
\box \center-column { \small
\line { Sheet music from \with-url #http://www.MutopiaProject.org; \line { \teeny www. MutopiaProject \teeny .org \hspace #0.5 } ⢠\hspace #0.5 \italic Free to download, with the \italic freedom to distribute, modify and perform. }
\line { \small \line { Typeset using \with-url #http://www.LilyPond.org; \line { \teeny www. LilyPond \teeny .org } by \typesetter \hspace #-1.0 ⢠Updated by \maintainer on \lastupdated } }
\line { \teeny \line { This sheet music has been placed in the public domain by the typesetter, for details see: \hspace #-0.5 \with-url #http://creativecommons.org/licenses/publicdomain; http://creativecommons.org/licenses/publicdomain } } }
}
}
global = {
\time 6/8
\key bes \major
}
first = \relative c {
\global
\partial 8 d\5-3-\RH #2 8_
\repeat volta 2 {
%\override StringNumber #'padding = #1.5
g-\RH #3 16- d\5-3-\RH #2 g\4-\RH #4 d\5 \barre III { bes'\3-1-\RH #3 - g\4-\RH #2 d'-\RH #3 - f,-\RH #1 bes-\RH #2 d-\RH #3 g-\RH #4 8- } |
bes-1-\RH #3 16- d,\3-3-\RH #2 g\2-4-\RH #4 a- g8\2- \barre III { a16 c,\3 d c\3 d8- } |
\barre I { d-\RH #3 8.- c-1-\RH #3 16- e8- d8.- c16- e8- } |
d-2-\RH #3 16- fis,-3-\RH #1 a-1-\RH #2 fis a fis d'-\RH #4 8 a-\RH #3 d,\0-\RH #2 - |
g16- d\5-3-\RH #2 g\4-\RH #4 d\5 \barre III { bes'\3-1-\RH #3 - g\4 d'- f, bes d f8\2- } |
\barre I { aes-4-\RH #4 16- aes,-\RH #2 c-\RH #3 g'-3-\RH #4 - f8- } g-2-\RH #4 16- g, b g f'8- |
e-1-\RH #4 16- g,-4-\RH #1 \4 bes-2-\RH #2 g ees'-3-\RH #4 8- d-2-\RH #4 16- fis,-4 a-1 fis bes-18-^\coda |
}
\alternative {
{ g-\RH #3 8\3- g-4-\RH #2 16\4 d-\RH #1 \5 g\4 d\5 g-3-\RH #3 4- d-\RH #2 8\5- | }
{ g8- g16\4 d\5 g\4 d\5 g4- r8 | }
}
\repeat volta 2 {
\barre V { b'-4-\RH #4 16- g,-\RH #1 d'-3-\RH #2 g-4-\RH #3 - a-1-\RH #4 8- bes-3-\RH #3 16- g,-\RH #1 c-\RH #2 c'-4-\RH #3 - cis-4-\RH #4 8- } |
\barre VIII { d-3-\RH #4 16- ees,-\RH #2 a-3-\RH #3 ees-\RH #2 - f-\RH #3 8- } \barre I { g-4-\RH #4 16- f,-3-\RH #1 aes-\RH #1 f-3-\RH #1 d'-4-\RH #3 8- } |
bes-4-\RH #3 16- bes,-2-\RH #1 d-\RH #1 g-\RH #3 - a-2-\RH #4 8- \barre I { bes-4-\RH #3 16- ees,-\RH #1 bes'-\RH #2 c-\RH #3 - cis-2-\RH #4 8- } |
d-2-\RH #3 16- fis,-3-\RH #1 a-1-\RH #2 e'-1-\RH #3 - fis-1-\RH #4 8- g-\RH #4 d-\RH #3 bes-\RH #2 4-^BIII - r8 |
}
\repeat volta 2 {
g-4-\RH #5 16- a,-1-\RH #2 ees'-3-\RH #3 a, ees'8 \barre III { d-1-\RH #4
Re: review of a Mutopia file (why TabStaff gives error here?)
2012/11/22 Federico Bruni fedel...@gmail.com:
Hi LilyPonders,
I've updated to 2.16 the following piece of Mutopia:
http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=636
Can anyone review it?
I had to do a lot of changes...
Also, I have a problem with TabStaff.
When I started to update the input I used also TabStaff, then I commented it
and added other changes. Now if I uncomment it again I get the following
error:
lilypond 2.16.1 [faure-sicilienne.ly] in avvio...
Processing `/home/fede/faure-sicilienne.ly'
Parsing...
Interpreting music...translation-functions.scm: In procedure list-ref in
expression (list-ref tuning (1- string)):
translation-functions.scm: Value out of range 0 to 4294967295: -1
It's a dropped D tuning and I can't see any note out of range.
What I'm missing?
Any suggestion is appreciated.
BTW, for those interested in contributing to Mutopia, check out this thread:
http://www.mail-archive.com/mutopia-discuss@mutopiaproject.org/msg00186.html
It would be nice to promote a Christmas sprint and encourage LilyPond
users to update Mutopia files to latest stable. Well, as soon as a new team
of Mutopia admins is setup.
Thanks
--
Federico
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Federico,
in one case you used \0 as StringNumber-indication. Seems it crashes
when used in a TabStaff.
Try: \new TabStaff { d\0 }
I made a bug-report:
http://lilypond.1069038.n5.nabble.com/Adding-StringNumber-0-in-TabStaff-crashes-td136696.html
Regards,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: review of a Mutopia file (why TabStaff gives error here?)
Il 22/11/2012 01:32, Thomas Morley ha scritto:
Hi Federico,
in one case you used \0 as StringNumber-indication. Seems it crashes
when used in a TabStaff.
Yup, I've removed it and TabStaff compiles.
Now I realize that there are many string numbers missing in the second
part of the piece. I'll play it and check the fingerings.
Try: \new TabStaff {d\0 }
I made a bug-report:
http://lilypond.1069038.n5.nabble.com/Adding-StringNumber-0-in-TabStaff-crashes-td136696.html
Thanks!
--
Federico
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Mutopia contributions [WAS: Version Control and Public Repository]
Il 09/11/2012 21:57, Nick Payne ha scritto: On 10/11/12 03:08, Urs Liska wrote: Re public repositories: Do you know mutopiaproject.org? Is that what you mean? Mutopiaproject seems pretty dead. No scores have appeared there since 12 February, including a couple that I sent them subsequent to that date, and they don't answer their e-mails either... This is unfortunate.. From time to time we discuss in this list about the status of Mutopia and what it needs to make the things work better. AFAIK, main problem is the administrative infrastructure. I've found a discussion on mutopia-discuss (private mailing list) about the need of a bug tracking system. github bug tracking doesn't offer all the features needed and Valentine tried to explore Redmine.. I don't know what he achieved. Also, how does the review process work? Who is responsible for that? Maybe opening the review to all the people subscribed to mutopia-discuss will help to reduce the work load on few persons? Another option: as many users have an account on github, they could fork the mutopia repository and send a pull request when they have a new score to submit. This way the contribution would be public and visible and anyone could comment on it. https://help.github.com/articles/using-pull-requests ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Mutopia
On Tue, May 29, 2012 at 4:20 PM, Nick Payne nick.pa...@internode.on.net wrote: Speaking of which, Mutopia seems to be pretty much moribund. I sent a score to their contributions e-mail address a couple of months ago, which was never acknowledged and hasn't appeared on the web site. Nor did I get a response to a mail pointing out a couple of errors in scores already on the web site, and nothing has appeared there since early February. Personally I have been posting public domain scores to my github account. I think this is a better model than Mutopia. Sites like Mutopia should be aggregators rather than silos. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Status of Mutopia Project
Has the Mutopia Project gone moribund again? There were some new scores being added a few months ago, but nothing new has appeared since early February, and I haven't received any response to a couple of mails I sent about errors in a couple of ly files on the site. Nick ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
