Re: Typo about LilyDev image size
Abraham Lee writes: > Documentation Writers, > > I was just reading through the 2.19.31 contributors "Quick Start" guide > (Section 2.1) and it says this: > > *"The LilyDev disk image can also be written to a USB device or ‘burnt’ to > a DVD – it is approximately 900 GB in size – and installed just like any > standard GNU/Linux distribution."* > > Now, I don't know about anyone else, but I don't think I've ever seen a > Linux distribution that required 900 GB ;-) I'm pretty sure it should say > "900 *M*B" instead. Yes, I already corrected this in a patch about to be uploaded for a review. Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: quarter tones in tablature - FretBoards
d...@faithful.be writes: > On 2015-10-31 12:49, pls wrote: >> d...@faithful.be writes: >> >>> On 2015-10-31 11:39, pls wrote: >>>> Thomas Morley writes: >>>>> Personally, I don't like any of those and lean towards excluding >>>>> quarter-tones from FretBoards at all and let output the warning >>>>> about >>>>> "Missing fret for pitch ~a on string ~a" as before. >>>>> Letting only TabStaff display quarter-tones. >>>> >>>> I'm of the same opinion as it doesn't/shouldn't really matter >>>> pitchwise where exactly you >>>> place your finger within a fret space on a fretted instrument. >>> >>> I'm no guitarist, but don't they sometimes pull sideways on the string >>> or use a mechanical attachment to sharpen a note? >> >> Yes, pull-offs are quite common but it's rather a technique to pluck >> the >> string with your fretting hand. With "mechanical attachment" you're >> probably alluding to a capo. It acts like a sort of artificial >> "barre". It fits around the neck of the guitar and raises the pitch of >> all (or only some of the) strings. LilyPond already displays capo >> indications as a thick bar >> in fret diagrams. Bottlenecks are also used to sharpen or lower a >> note. It works like some sort of a "movable fret". >> But I've never seen quarter tone indications in fret diagrams. >> >> Cheers, >> Patrick > > I was thinking of things like these: > https://en.wikipedia.org/wiki/Vibrato_systems_for_guitar Yes, electric guitars can be equipped with a whammy bar. Those effects usually have their own symbols in traditional notation and tablature but not in fret diagrams (see attachment). > >> BTW: Did you deliberately not reply to the list? > > No. I'm stuck using an unfamiliar web-mail interface while my main > computer is being repaired; I must have hit the wrong button. Thanks > for noticing. You're welcome! Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: quarter tones in tablature - FretBoards
Thomas Morley writes: > Personally, I don't like any of those and lean towards excluding > quarter-tones from FretBoards at all and let output the warning about > "Missing fret for pitch ~a on string ~a" as before. > Letting only TabStaff display quarter-tones. I'm of the same opinion as it doesn't/shouldn't really matter pitchwise where exactly you place your finger within a fret space on a fretted instrument. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
On 20.05.2015, at 20:19, Werner LEMBERG wrote: > >> Except you're doing a ghoti Bernard Shaw on our sentence structure. >> German declines its articles, so you can tell subject and object by >> article, in English we have to do it by position *relative to the >> verb*. Schweine fressen die Menschen! Which one’s the subject and which one’s the object? Well, it depends! ;) > > German has other niceties, like > > der gefangene Flohthe prisoned flea > der Gefangene flohthe prisoner escaped > > look at the case :-) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
On 06.05.2015, at 20:43, David Kastrup wrote:
> Werner LEMBERG writes:
>
>>> Probably the best name is \octave, which was used for something
>>> similar
>>> until version 0.1.19
>>>
>>>\octave c'' {c4 e g c e g c'1}
>>
>> Sounds OK for me.
>
> Huh. I like the contrast \relative/\absolute better. Particularly,
> I like a sensible default when one leaves off the pitch.
>
> Neither \octave { bes, c d e f } nor \octave c { c' bes as g } or
> \octave c'' { c' bes as g } seem particularly convincing. I like
> \absolute { bes, c d e f } \absolute c { c; bes as g } \absolute c'' {
> c' bes as g } better.
Me too! I don’t see the need for an additional \octave-command. We change
octave positions in relative mode as well as in absolute mode by adding octave
marks. In my opinion it wouldn’t alter the “absoluteness” of absolute mode if
it were possible to change the octave position for the whole expression (e.g.
\absolute c’’ {c’}). It would just be another handy shortcut for
transposing/octavating expressions in absolute mode (instead of having to
add/remove individual octave marks).
patrick
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Guitar right-hand fingering
On 17.03.2015, at 11:24, Thomas Morley wrote: > 2015-03-17 11:00 GMT+01:00 Peter Bjuhr : > >> Hi, >> >> I just noticed that in the documentation about right-hand fingerings in >> the common notation for fretted strings: http://www.lilypond.org/doc/ >> v2.19/Documentation/notation/common-notation-for-fretted- >> strings#right_002dhand-fingerings the fifth finger isn't mentioned. >> >> I also tried|\rightHandFinger #5| and an 'x' was printed. As I understand >> it 'x' is printed for all non supported numbers. > > > No. 'x' _is_ the sign for the 5th finger in LilyPond > > >> But although perhaps not so common the fifth finger is used (with the >> letter 'c'): >> >> 1 = p = pulgar, 2 = i = índice, 3 = m = mayor, 4 = a = >> anular,5 = c = chiquito >> > > I slightly disagree. > In printed editions I've found: 'c', 'x', 'e' and even 'μ' (from a greek > editor) > LilyPond should default to the most common usage, imho. > > Though, I've no clue which that might be. > Speaking only for me, I most often see 'x', but that's only me. > In some of my flamenco books “q” is used for the little finger (meñique). ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: fixing German's Wikipedia entry of LilyPond
On 12.01.2014, at 19:31, Phil Holmes wrote: > - Original Message - From: "Phil Holmes" > To: "Carl Sorensen" ; "James" ; > "Werner LEMBERG" ; "Devel" > Sent: Sunday, January 12, 2014 6:24 PM > Subject: Re: fixing German's Wikipedia entry of LilyPond > > >> - Original Message - From: "Phil Holmes" >> To: "Carl Sorensen" ; "James" ; >> "Werner LEMBERG" ; "Devel" >> Sent: Sunday, January 12, 2014 3:19 PM >> Subject: Re: fixing German's Wikipedia entry of LilyPond >> >> >>> - Original Message - From: "Carl Sorensen" >>> Is there any reason not to put the tuplet brackets on the upper staff in bar 2 *below* the staff? It seems to me they would be clearer that way. Thanks, Carl >>> >>> If the version on YouTube is original (see attachment), then this has the >>> tuplet markings over the staff. >>> >>> It's also got a modern time signature style. Anyone any idea how to do >>> this? >>> >>> -- >>> Phil Holmes >>> >> >> Latest version is attached. Needs dotted tuplet brackets, a bit of tidying >> of positioning, alternative time signature format, move of clef in LH of 2nd >> bar and I think it's done. >> >> Can anyone help with any of these? > > > Dotted tuplet brackets and positions tweaked. Think this is good to go for > now? According to http://www.youtube.com/watch?v=BE2cMxY91rU a couple of dynamics are still missing: -) in LH 1st bar there should be one \f above and one below the staff -) in LH 2nd bar there should be a \mf under the e# ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: fixing German's Wikipedia entry of LilyPond
On 12.01.2014, at 19:31, Phil Holmes wrote:
> - Original Message - From: "Phil Holmes"
> To: "Carl Sorensen" ; "James" ;
> "Werner LEMBERG" ; "Devel"
> Sent: Sunday, January 12, 2014 6:24 PM
> Subject: Re: fixing German's Wikipedia entry of LilyPond
>
>
>> - Original Message - From: "Phil Holmes"
>> To: "Carl Sorensen" ; "James" ;
>> "Werner LEMBERG" ; "Devel"
>> Sent: Sunday, January 12, 2014 3:19 PM
>> Subject: Re: fixing German's Wikipedia entry of LilyPond
>>
>>
>>> - Original Message - From: "Carl Sorensen"
>>>
Is there any reason not to put the tuplet brackets on the upper staff in
bar 2 *below* the staff? It seems to me they would be clearer that way.
Thanks,
Carl
>>>
>>> If the version on YouTube is original (see attachment), then this has the
>>> tuplet markings over the staff.
>>>
>>> It's also got a modern time signature style. Anyone any idea how to do
>>> this?
>>>
>>> --
>>> Phil Holmes
>>>
>>
>> Latest version is attached. Needs dotted tuplet brackets, a bit of tidying
>> of positioning, alternative time signature format, move of clef in LH of 2nd
>> bar and I think it's done.
>>
>> Can anyone help with any of these?
>
>
> Dotted tuplet brackets and positions tweaked. Think this is good to go for
> now?
Looks good!
Here is a proposal for the positioning of the time signature:
\version "2.18.0"
\relative c'' {
\override Staff.TimeSignature #'font-size = #20
\override Staff.TimeSignature #'extra-offset = #'(0 . -20)
\numericTimeSignature
c
}
hth
patrick
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Repeats starting and ending in mid-bar?
On 17.11.2013, at 18:40, Dan Eble wrote: > On Nov 17, 2013, at 10:40 , pls wrote: > >> Gardner shows two examples of repeats starting in mid-bar (p. 226). In one >> of them the thin line of the repeat mark is omitted leaving only the thick >> line and the colon. But he writes that this practice is not recommended. > > I’m curious to know what is recommended. According to him the best plan is to use conventional repeat bars (.|: :|.) when a repetition involves more than two measures – regardless of where they occur. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Repeats starting and ending in mid-bar?
On 17.11.2013, at 15:57, David Kastrup wrote: > > Hi, > > I'm occasionally repondering the barline |: :| issue and I want to know > if anybody's music typesetting theory text or private music library has > examples of repeats starting and/or ending in mid-bar. I seem to > remember that there is some weakened double bar in use for that, > something like ||: :|| instead of the current .|: :|. (according to our > notation). Do I remember right? Gardner shows two examples of repeats starting in mid-bar (p. 226). In one of them the thin line of the repeat mark is omitted leaving only the thick line and the colon. But he writes that this practice is not recommended. hth patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyPond meeting in Waltrop, Germany, 2013-08-16 to 2013-08-20
On 12.08.2013, at 19:51, Thomas Morley wrote: > > I'll arrive Thursday, leave Tuesday, sleeping in my tent. This applies to me, too! See you soon! patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: suggestion: change OctavateEight name to ClefTransposition - opinions?
On 08.04.2013, at 10:58, pls wrote: > On 08.04.2013, at 09:56, David Kastrup wrote: > >> Thomas Morley writes: >> >>> 2013/4/7 David Kastrup : >>> >>>> A digital camera does not produce even lighting, but for simple >>>> demonstrations it is better than nothing. >>> >>> I don't have a digital camera, too. >>> Though, my girl friends mobile phone camera worked. >> >> Actually, it's not just the clef where I am without a clue how to play >> this, or on what instrument… > Is this piece supposed to be played on a baritone guitar (tuned a perfect > fifth lower than standard guitar tuning)? In this case 12 would be more appropriate than 5?! >> >> -- >> David Kastrup >> >> ___ >> lilypond-devel mailing list >> lilypond-devel@gnu.org >> https://lists.gnu.org/mailman/listinfo/lilypond-devel > > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: suggestion: change OctavateEight name to ClefTransposition - opinions?
On 08.04.2013, at 09:56, David Kastrup wrote: > Thomas Morley writes: > >> 2013/4/7 David Kastrup : >> >>> A digital camera does not produce even lighting, but for simple >>> demonstrations it is better than nothing. >> >> I don't have a digital camera, too. >> Though, my girl friends mobile phone camera worked. > > Actually, it's not just the clef where I am without a clue how to play > this, or on what instrument… Is this piece supposed to be played on a baritone guitar (tuned a perfect fifth lower than standard guitar tuning)? > > -- > David Kastrup > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: suggestion: change OctavateEight name to ClefTransposition - opinions?
Am 07.04.2013 um 10:14 schrieb Marc Hohl : > Am 06.04.2013 23:44, schrieb David Kastrup: >> Marc Hohl writes: >> >>> Am 05.04.2013 23:02, schrieb Janek Warchoł: Hi, The name "OctavateEight" doesn't have any sense - it doesn't show that this grob is related to the clef, and anyway the clef can be "transposed" by any amount, not just an octave. I suggest to rename this grob to ClefTransposition or something similar (since this is not strictly transposition, it may be best to use a slightly different name... ClefShift? At any rate, ClefOctavation would make much more sense than OctavateEight). We can also change names of some related context properties, for example clefOctavation, clefOctavationStyle etc. My only worry is that they may become too similar (clefTransposition and ClefTransposition). Thoughts? >>> >>> +1 >>> >>> I'd prefer ClefTransposition over ClefShift, since the latter >>> implies some shift relative to the clef's default position. >> >> I think I'd like ClefModifier. Something like I'd prefer ClefOctavation (or maybe ClefOctaveShift) to ClefModifier because it's clearer / more intuitive (at least to me). ClefModifier could be misunderstood to refer to the shape of the symbol. > > +1 > >> >> `clefOctavation' (integer) >> Add this much extra octavation. Values of 7 and -7 are >> common. >> >> does not make sense. Transposition is not really accurate since the >> number is in steps rather than diatonic. It is a bit disconcerting that >> values of 7, -7, 14 and -14 lead to numbers 8, 8, 15 and 15. >> >> I don't find "shift" all too bad: one can talk about pitch shifting >> after all, and for spatial displacements we tend to use "offset". >> > > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: How to extract PDF of translated documentation?
Am 13.01.2013 um 15:01 schrieb David Kastrup : > pls writes: > >> Am 13.01.2013 um 11:24 schrieb David Kastrup : >> >>> an old lady I had visited in Switzerland asked me to provide her for >>> examples of input for LilyPond, and she has no computer. Now it turns >>> out that the web site has >>> >>> File: lilypond-web.info, Node: Text input, Next: Easier editing, >>> Prev: Reviews, Up: Introduction >>> >>> which is quite nice as an introduction. make doc apparently also builds >>> a PDF version of it which is fine for that purpose. However, it >>> apparently does not build a PDF of the German (or any) translation. >>> >>> Anybody have a quick suggestion how to do this manually? After all, it >>> is a bit intricate with having to run Lilypond-book, specifying paths, >>> include paths, and other stuff. >> >> I just did a local make doc and all PDFs are in >> lilypond-git/build/Documentation/de/out-www. > > Well, I won't make the experiment (quite computationally expensive) > without asking back: does this include web.pdf or its equivalent? > Namely not any manual, but rather the PDF version of our website? > > That's what I was looking for, and I did not find it when I tried last > time round. Sorry for the noise. Of course it's not the translated version. it's not there. > > -- > David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: How to extract PDF of translated documentation?
Am 13.01.2013 um 15:01 schrieb David Kastrup : > pls writes: > >> Am 13.01.2013 um 11:24 schrieb David Kastrup : >> >>> an old lady I had visited in Switzerland asked me to provide her for >>> examples of input for LilyPond, and she has no computer. Now it turns >>> out that the web site has >>> >>> File: lilypond-web.info, Node: Text input, Next: Easier editing, >>> Prev: Reviews, Up: Introduction >>> >>> which is quite nice as an introduction. make doc apparently also builds >>> a PDF version of it which is fine for that purpose. However, it >>> apparently does not build a PDF of the German (or any) translation. >>> >>> Anybody have a quick suggestion how to do this manually? After all, it >>> is a bit intricate with having to run Lilypond-book, specifying paths, >>> include paths, and other stuff. >> >> I just did a local make doc and all PDFs are in >> lilypond-git/build/Documentation/de/out-www. > > Well, I won't make the experiment (quite computationally expensive) > without asking back: does this include web.pdf or its equivalent? > Namely not any manual, but rather the PDF version of our website? > > That's what I was looking for, and I did not find it when I tried last > time round. I finally found web.pdf here: lilypond-git/build/Documentation/out-www. Do you want me to send you a dropbox-link to it? hth patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: How to extract PDF of translated documentation?
Am 13.01.2013 um 11:24 schrieb David Kastrup : > > Hi, > > an old lady I had visited in Switzerland asked me to provide her for > examples of input for LilyPond, and she has no computer. Now it turns > out that the web site has > > File: lilypond-web.info, Node: Text input, Next: Easier editing, Prev: > Reviews, Up: Introduction > > which is quite nice as an introduction. make doc apparently also builds > a PDF version of it which is fine for that purpose. However, it > apparently does not build a PDF of the German (or any) translation. > > Anybody have a quick suggestion how to do this manually? After all, it > is a bit intricate with having to run Lilypond-book, specifying paths, > include paths, and other stuff. I just did a local make doc and all PDFs are in lilypond-git/build/Documentation/de/out-www. hth patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
musicxml2ly
Hey all,we have been working on solutions for old musicxml2ly-bugs and some new functions. We have published our efforts on https://github.com/Philomelos/lilypond-musicxml2ly-dev. We will continue working on musicxml2ly but there are far more bugs than we could ever handle on our own. So if no one minds we will send a lot of musicxml2ly related reports to the bug list in the near future.hthpatrickHere is a list of new commits and some test files:1) https://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/f22cb84f93dc968322abd6bc0a89371ddf54Test files:https://github.com/Philomelos/lilypond-musicxml2ly-dev/blob/master/MusicXML-TestSuite/midi-block-single-part.xml (MIDI-Bug fixed: monophonic pieces were converted without a midi-block. Now all scores are exported in a \score{} containing a \midi-Block)https://github.com/Philomelos/lilypond-musicxml2ly-dev/blob/master/MusicXML-TestSuite/placement-musical-directions.xml (placement attributes for musical directions now work for dynamics, hairpins, textspans and ligature brackets)https://github.com/Philomelos/lilypond-musicxml2ly-dev/blob/master/MusicXML-TestSuite/wavy-line.xml (wavy-line bug fixed (Issue: 2316))https://github.com/Philomelos/lilypond-musicxml2ly-dev/blob/master/MusicXML-TestSuite/barre.xml ((curved) barre-indications are now included in fret diagrams)
powerchordsymbol.xml
Description: XML document
(The symbol for powerchords is now "C5" instead of "C")https://github.com/Philomelos/lilypond-musicxml2ly-dev/blob/master/MusicXML-TestSuite/new%20functions/transpose/scale.xml (new transpose function to be able to transpose .xml-files via command line)2) https://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/f6e50496a56a38d7ec0ec333df8b03257aa1bb7chttps://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/32f8dda4c3e2302a0e755a3e1fb3aebb2cd30fcehttps://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/ed9e55034f154fb219cfaabdf8f5cfe2df356cb7Test file:https://github.com/Philomelos/lilypond-musicxml2ly-dev/blob/master/MusicXML-TestSuite/sound.xml (added sound tempo recognition for midi output)3) https://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/5501d9562ba245697ec7273fe0eaa6952eebbffdhttps://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/91eee40736e923690f39d735a5d301704f3a7a35https://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/9576bfa0996829c24ee0f1759d16dac8ac57ec40https://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/dc077b4611400e1b9e77b0aa625a3debe68af29fWith e.g. --shift-meter 2/2 you can change the length|duration of notes as a function of a given time signature to make the score look faster or slower, (eg. '4/4' or '2/2')4) https://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/0747e5ce34f8d3a6128302ec0363a8f5f91ce3fdTest file:https://github.com/Philomelos/lilypond-musicxml2ly-dev/blob/master/MusicXML-TestSuite/stem.xmlimplemented recognition of stem values "up" and "down" (and neutral)5) https://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/6b45d133394dbea0a28eaf36a1c474dd9835cb1chttps://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/21580656ca819099e7dcc6e9f9b44f19cd32ca77Test file:
fretboardvoice.xml
Description: XML document
command line option:--fb --fretboards converts '' events to a separate FretBoards voice instead of markupsThis helps to align the fretboards vertically. fretboards in markups tend to go up and down. 6) https://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/a5b7a919cf26700c51b8aa5a43099a291d65b3adhttps://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/13e97f8d56492afc4adfc1eee3f112879c92ae55Test file:
tabclef.xml
Description: XML document
command line option:--tc --tab-clef=TABCLEFNAME switch between two versions of tab clefs ("tab" and "moderntab")7) https://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/a534b4c446fc807019d87c8cffd4184095a3159dTest file:
string-numbers.xml
Description: XML document
command line option:--sn --string-numbers=t[rue]/f[alse] deactivate string number stencil with --string-numbers f[alse]. Default is t[rue]8) https://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/68f3f2c8bf2084496777ba96603fbfc79351946dhttps://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/33957a48cbde9d5b30e24aefa324d14154e19a19Test file:https://github.com/Philomelos/lilypond-musicxml2ly-dev/blob/master/MusicXML-TestSuite/frame.xmlIf a is not defined (or commented out) in an .xml-file musicxml2ly converts it as an unplayed (muted) string.___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: new mailing list: lilypond-syntax-explorations
Am 07.09.2012 um 02:14 schrieb Graham Percival: > On Mon, Sep 03, 2012 at 08:15:27PM +0100, Graham Percival wrote: >> For the past 6 days, we've performed an experiment: can we have a >> On Thursday, I will create a new mailing list, with the tentative >> name "lilypond-syntax-explorations". Alternate name suggestions >> are welcome. > > I'm re-thinking the name. It's not ideal to pinpoint "syntax" in > the list name, since this could be a useful venue to discuss other > ideas[1]. I'm now leaning towards: > lilypond-loony-bin > > Other possibilities are: > lilypond-free-discussion > lilypond-random-discussion > lilypond-explorations > lilypond-loonies % Canadian joke: our $1 coin is a loonie > % http://en.wikipedia.org/wiki/Loonie > > > [1] for example, having closer ties with Mutopia, doing something > with kickstarter, online web editors, critical editions of > scores... basically, any of the "random discussions" we had at > Waltrop. These straddle the boundary between users and > developers. To re-iterate, none of the discussions will be taken > as a direct proposal; any actual proposals that arise from those > unstructured discussions will be brought to -devel. > > - Graham It's not meant to be disrespectful but how about * lilypond-croaking * lilypond-croaks * lilypond-quacks * lilypond-quack-pack (* lilypond-quackery) ;) > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: slides-in-tablature.ly snippets: string numbers of hided notes are visible
Am 01.09.2012 um 22:22 schrieb David Kastrup:
> pls writes:
>
>> There must have been a change in default with regards to the
>> visibility of string numbers between 2.15.20 and the current
>> version. In 2.15.20 it was still possible to add string numbers to
>> notes (e.g. c'4\4) without them showing up in the score.
>
> But they showed up when writing , so this was more a convenient
> bug than anything else.
>
>> This was very handy in order to automatically specify the appropriate
>> fret on the right string in tablature. One could decide whether to
>> output individual string numbers via 4 or not to engrave them
>> via c'4\4.
>
> And what would you do when _wanting_ a chord with more than a single
> note but no string numbers?
I used to use \5\4\3. Quite a convenient bug, indeed! ;)
>
>> Now it seems that this behavior can only be achieved by constantly
>> overriding the string number stencil...
>
> Not that bad:
>
> n=#(define-event-function (parser location e) (ly:event?)
> #{ \tweak #'stencil ##f $e #})
>
> { c'\4 c'\n\4 }
>
> --
> David Kastrup
>
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: slides-in-tablature.ly snippets: string numbers of hided notes are visible
There must have been a change in default with regards to the visibility of
string numbers between 2.15.20 and the current version. In 2.15.20 it was still
possible to add string numbers to notes (e.g. c'4\4) without them showing up in
the score. This was very handy in order to automatically specify the
appropriate fret on the right string in tablature. One could decide whether to
output individual string numbers via 4 or not to engrave them via c'4\4.
Now it seems that this behavior can only be achieved by constantly overriding
the string number stencil...
Am 01.09.2012 um 17:40 schrieb Federico Bruni:
> I've just realized that in this snippet the hidden notes, used to make the
> grace slides, have a string number which is printed (and it shouldn't).
> I think that we should just remove /3 from the notes in the grace blocks (see
> file attached).
>
> All the examples in the doc using Staff + TabStaff show the string numbers. I
> don't know if it's desirable, but removing all the string numbers in this
> example putting this in a \layout block wouldn't be consistent with the rest
> of the doc:
>
> \context {
> \Staff
> \override StringNumber #'stencil = ##f
> }
>
> Can a LSR editor fix it?
> Thanks
> --
> Federico
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: MusicXML and GuileV2
Hi David, thanks for the hint. We'll keep it in mind. For now we extended John's stub a little bit. See https://github.com/Philomelos/lilypond-ly2musicxml. Cheers, patrick Am 30.08.2012 um 19:04 schrieb David Kastrup: > > Looking in the GuileV2 manual, I find > > File: guile-2.0.info, Node: Standard Library, Next: GOOPS, Prev: Guile > Modules, Up: Top > > 8 Standard Library > ** > > * Menu: > > * statprof:: Statistical profiler > * sxml apply-templates:: A more XSLT-like approach to SXML transformations > * sxml fold::Fold-based SXML transformation operators > * sxml simple:: Convenient XML parsing and serializing > * sxml ssax::Functional-style XML parsing for Scheme > * sxml ssax input-parse:: The SSAX tokenizer, optimized for Guile > * sxml transform:: A higher-order SXML transformation operator, > `pre-post-order' > * sxml xpath:: XPath for SXML > * texinfo:: Parse texinfo files or fragments into `stexi', a > scheme representation > * texinfo docbook:: Transform a subset of docbook into `stexi' > * texinfo html:: Transform `stexi' into HTML > * texinfo indexing:: Extract an index from a piece of `stexi' > * texinfo string-utils:: String utility functions used by the texinfo > processor > * texinfo plain-text:: Render `stexi' as plain text > * texinfo serialize::Render `stexi' as texinfo > * texinfo reflection:: Enable texinfo across Guile's help system > > Considering that for MusicXML export we want to write valid XML, perhaps > manipulate it, it would appear to make sense to not develop an > independent implementation of XML input/output but rather make use of > the existing work. > > So it is another reason to speedily move to Guilev2 now that 2.17 has > been started. > > This would also seem to form an excellent starting point for having > LilyPond interpret MusicXML directly, bypassing converters as well as > the ly parser. While this would not offer the full tweaking power and > expressivity of ly, it would certainly be a good way of interfacing in a > machine-readable manner. If one wanted to wax poetic, one could view > the ly/MusicXML pairing as a variation on the full/stripped theme that > PostScript/PDF provides as input to Ghostscript: one a full, > human-writable programming language, one a content-focused collection of > elements. > > -- > David Kastrup > > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: The currently still assembled part of the team in Waltrop
Philo más o menos! ;) It was nice to meet you all in person! I enjoyed it very much and hope to see you and the rest of the gang again, soon! Thanks for everything! patrick Am 27.08.2012 um 22:35 schrieb David Kastrup: > Thomas Morley writes: > >> 2012/8/27 David Kastrup : >>> Han-Wen Nienhuys writes: >>> Everyone with eyes closed for lack of sleep? >>> >>> I was sitting on a couch discussing MusicXML exports with the guys from >>> Philomenos (sp?) with Janek snoring right beside us. >> >> Philomelos >> -> http://philomelos.net/intro > > So much for myself being awake... Thanks! > > -- > David Kastrup > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Waltrop meeting outline
Thanks, I'm almost on the way! Am 26.08.2012 um 02:07 schrieb David Kastrup: > pls writes: > >> I'll try to be in Brambauer at 11:09. If you haven't ordered food yet >> I'd take the Broccoli al Forno. Otherwise: no problem. > > If possible, call when you are in the subway. 02309-782756 landline, > probably less reliable fallback 016092087547. I'll call the cook in the > morning (probably getting the answering machine, but that should > suffice). > > -- > David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Waltrop meeting outline
I'll try to be in Brambauer at 11:09. If you haven't ordered food yet I'd take the Broccoli al Forno. Otherwise: no problem. See you. p Am 25.08.2012 um 13:46 schrieb David Kastrup: > pls writes: > >> Sleeping space is not an issue. I have a sleeping bag, a pad and a >> tent. But as I almost live in commuting distance I might go back home >> in the evening. >> >> When will you start tomorrow morning? > > I suppose that sometimes around 10:00 we'll gravitate from breakfast to > the meeting room. I was going to order food for tomorrow, the outlet > does Indian, Italian, Chinese, and German (Google finds them as > http://www.lieferheld.de/datteln/journal/>, but I am not sure this > is the best link. It does seem to show the menu.). > > So check out what you want to get from there. > > See you > > -- > David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Waltrop meeting outline
Sleeping space is not an issue. I have a sleeping bag, a pad and a tent. But as I almost live in commuting distance I might go back home in the evening. When will you start tomorrow morning? I'm looking forward to meet you all! patrick Am 25.08.2012 um 11:05 schrieb David Kastrup: > pls writes: > >> Hey all, >> >> does anybody mind me joining you tomorrow? We've been working on some >> improvements of musicxml2ly. Our efforts are published on >> https://github.com/Philomelos/lilypond-musicxml2ly-dev. There is more >> to come... We have also developed a basic scm2xml-export (no export of >> the layout). We are looking for a way to contribute it to LilyPond. >> >> So I hope to see you tomorrow?! > > Sleeping space will be a bit cramped unless you can camp here. Just now > across the room Jan Nieuwenhuizen has revived some work of his from a > year ago with Rodolfo in the area of MusicXML export, so we obviously > have some interest in that area, and it would seem interesting to share > views and experience. > > > > -- > David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Waltrop meeting outline
Hey all,
does anybody mind me joining you tomorrow? We've been working on some
improvements of musicxml2ly. Our efforts are published on
https://github.com/Philomelos/lilypond-musicxml2ly-dev. There is more to
come... We have also developed a basic scm2xml-export (no export of the
layout). We are looking for a way to contribute it to LilyPond.
So I hope to see you tomorrow?!
Cheers
patrick
Am 19.08.2012 um 15:02 schrieb David Kastrup:
>
> Details are still somewhat fuzzy since I don't have all that much
> feedback concerning who will arrive when and leave, but there are some
> corner points.
>
> Apparently Janek will be arriving in advance. No details yet as to his
> exact travel time and accommodation wishes: like anybody else not having
> mentioned anything, I count on him bringing sleeping bag or other
> bedcloths.
>
> Marc mentioned coming as well as Rodolfo. Rodolfo wanted to talk about
> using LilyPond in a professional print environment, as they are starting
> a new series of printed music books ("Musik aus Schweizer Klöstern").
>
> As Marc was not able to work the stock instrument I can offer here, he
> was thinking of bringing his left-handed guitar. I have no precise idea
> about the exact dates of those two participants and whether it might
> make sense for them to organize sharing a car part of the trip (Munich
> and Zurich, IIRC).
>
> Harm/Thomas Morley intended to come on Saturday, stay probably until
> Monday and camp on the premises.
>
> John and Graham will be there essentially the whole time, John bringing
> a sleeping bag. We'll find a bed for Graham since he does not own a
> sleeping bag and arrives by plane. Mike arrives on Saturday noonish and
> will leave on Tuesday noonish.
>
> I'll dig out suitable connections for people arriving at Düsseldorf by
> flight/high speed train later.
>
> The schedule would focus on stable release work and criteria on Friday,
> with the goal of getting most participants hands-on experience or at
> least exposure to GUB work. Coursework goal is the release of 2.16, and
> getting the computing facilities up and running.
>
> Saturday and Sunday are focused on programming courses. Nils Gey asked
> for the best single day to come and talk about Laborejo and likely also
> music production in general, and I considered Sunday to be likely best
> fit. We'll probably put pure/unpure and other backend programming stuff
> from user level on Saturday, also general Scheme programming and
> frontend syntax stuff.
>
> On the weekend, I would like to squeeze in at least some entry-level
> "garbage-collection and other Guile/C++ interaction" and possibly some
> "what kind of syntax can be achieved and debugged at the C++ level with
> reasonable effort" discussion, with the more heavy-handed stuff being
> put on Monday.
>
> In case of "let's see what kind of release work we can get done", 2.17.0
> might be possible on Sunday or Monday. We should at least arrive at a
> good agreement about how to tackle the humongous 2148 merge which is
> definitely called for post-2.17.0.
>
> --
> David Kastrup
>
> ___
> lilypond-user mailing list
> lilypond-u...@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: musicxml2ly
It's not a regression. It has never been officially fixed. A while ago I posted a bug report and a minimal example: http://old.nabble.com/musicxml2ly%3A-chordnames-placement-bug-td33309393.html. Here is a solution for the chord symbol bug: http://codereview.appspot.com/5697059/. I still haven't found the time to tidy up the patch. But it works! Am 16.05.2012 um 10:18 schrieb Colin Hall: > On Wed, May 16, 2012 at 09:33:09AM +0200, Martin Tarenskeen wrote: > The good news is that in many cases only a little editing of > the .ly file is required to turn a bad conversion into a good > one. For example, all lead sheets from Wikifonia that I have > tried have the Chords printed below instead of above the > staff. I remember this had been fixed in one of the previous lilypond 2.15.x versions, but with musicxml2ly from Lilypond 2.15.37 I am still (again?) having this problem. >>> >>> Same with 2.15.38 >> >> I did not see a reaction to this question, so I try again. What >> happened with this musicxml2ly bug ? First chords were printed below >> the staff, then I think it was fixed, and now the chords are below >> the staff again. Regression? > > That must be very frustrating for you. Sorry that I can't help you, as > I'm not familiar with musicxml2ly. It appears to be central to > Patrick's project so I would imagine he or his colleagues are working > hard on this. > > http://www.philomelos.net/en/about > > There are a number of issue trackers relating to musicxml2ly but I see > no issue tracker for this bug, Martin. > > I'd like to at least record the bug. We can create a tracker if you > supply these details: > > 1. A version of lilypond/musicxml2ly and a specific lead sheet from Wikifonia > in MusicXML format that together exhibit the bug. > > 2. A version of lilypond/musicxml2ly from the 2.15.x series which does not > exhibit the bug. > > Cheers, > Colin. > > -- > > Colin Hall > > ___ > bug-lilypond mailing list > bug-lilyp...@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Dictionary for musical terms in Lilypond
http://www.lilypond.org/doc/v2.15/Documentation/music-glossary/index.html Am 29.04.2012 um 12:55 schrieb Łukasz Czerwiński: > Hi, > > Recently my Polish speaking friend told me that it's a problem for him to > look something in Lilypond documentation, because first of all he must > translate the musical term he needs to English, which is quite a hard task, > because there are several words that might express the same musical element. > > I came to an idea - what about creating a small dictionary of musical terms > used in Lilypond and in Lilypond documentation? > > It might be just a separate page for each language with pairs: word - > translated word. > > What do you think? As I guess, I will have too include that into > documentation which is available in git repository? > > > Łukasz > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: musicxml2ly
Hi Martin, yes, we are currently working on the musicxml2ly scripts and we have solved e.g. the issue concerning the chord symbols you mentioned. I haven't had time to work on the patch James pointed to but it works as it is. We use it on www.philomelos.net. Philomelos is a new community site for free and editable sheet music. The private beta version includes the ability to read and share MusicXML files that are displayed online using LilyPond technology. If someone wants to be invited: drop me a line offlist. We will share all improvements on musicxml2ly but we could also need some help! We are planning to add a blog/wiki to our website so that philomelos can be used to test MusicXML files and to share music sheets and knowledge concerning MusicXML, conversions between musical notation codes... Cheers, patrick Am 08.04.2012 um 19:13 schrieb James: > Hello, > > On 8 April 2012 17:47, Martin Tarenskeen wrote: > ... >> Or are many >> problems already known? > > http://code.google.com/p/lilypond/issues/list?can=2&q=musicxml&sort=priority&colspec=ID&x=type&y=priority&mode=grid&cells=tiles > > There is also this recent - seemingly unfinished patch > > http://codereview.appspot.com/5697059/ > > And see > > http://lists.gnu.org/archive/html/lilypond-devel/2011-12/msg00025.html > > http://lists.gnu.org/archive/html/lilypond-user/2011-11/msg00280.html > > This will give you an idea of the current issues and the effort still > required. > > James > > ___ > lilypond-user mailing list > lilypond-u...@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Google Summer of Code - Ideas List, please discuss
Am 21.02.2012 um 22:04 schrieb Janek Warchoł: > On Thu, Feb 16, 2012 at 1:56 PM, pls wrote: >> >> Am 16.02.2012 um 13:02 schrieb Han-Wen Nienhuys >>> What happens if you take a fully formatted file from Finale and load >>> it into Sibelius via the musicxml route, and the reverse? Is anyone >>> able to post the before and after PDFs of such a transition? >> I can't really say what happens when you interchange a fully formatted >> MusicXML generated by Finale but this is what I did to test the different >> output: >> >> * engraved a piece with LilyPond >> * converted it to MusicXML using PDFtoMusic Pro v1.3.0d >> * manually corrected the .xml-file (surprise, surprise: PDFtoMusic Pro' OCR >> is not »perfect« ;-)) >> * reconverted the file to LilyPond using musicxml2ly >> * opened the .xml-file with Finale NotePad 2012, Finale 2011 Demo, Sibelius >> 6 Demo, MuseScore v1.1 >> >> And these are the results (first page only): > > Thank you for doing this test! The results are valuable; i'd say that > it works reasonably. (however it would also be good to test a more > complicated piece - could you try it with first pages of attached > scores?) > From what i undestand, the most important comparison is between first > and last file (IMSLP74045-PMLP148535-256-16_pls.png and > IMSLP74045-PMLP148535-256-16_pls_p2mp_pls.png) - the first one is the > original LilyPond engraving, and the second one is what you got after > converting to musicXML and back to .ly? Yes, you're right. But I'd say the other results are also interesting because they show that the same .xml-file is represented differently by different notation softwares (e.g. concerning page breaks , lyrics...) I could try it again with a more complicated piece if you want. Any suggestions? hth, patrick P.S.: I don't think I will find time to do some more testing before the next weekend, though. Sorry. > > thanks, > Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Google Summer of Code - Ideas List, please discuss
Am 16.02.2012 um 13:25 schrieb catch...@philholmes.me.uk: > Quoting Han-Wen Nienhuys : > >> What happens if you take a fully formatted file from Finale and load >> it into Sibelius via the musicxml route, and the reverse? Is anyone >> able to post the before and after PDFs of such a transition? Sorry, my first mail didn't get through because of the size of the attached files. I can't really say what happens when you interchange a fully formatted MusicXML generated by Finale but this is what I did to test the different output: * engraved a piece with LilyPond * converted it to MusicXML using PDFtoMusic Pro v1.3.0d * manually corrected the .xml-file (surprise, surprise: PDFtoMusic Pro's OCR is not »perfect« ;-)) * reconverted the file to LilyPond using musicxml2ly * opened the .xml-file with Finale NotePad 2012, Finale 2011 Demo, Sibelius 6 Demo, MuseScore v1.1 And here are the results (first page only): http://dl.dropbox.com/u/21383326/png.zip ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Thinking about putting together a grant to support development onLilyPond
Am 09.02.2012 um 17:26 schrieb Phil Holmes: > - Original Message - From: "Han-Wen Nienhuys" > To: "Carl Sorensen" > >>> C) Development of score_ocr2ly, which would take a score pdf and turn it >>> into .ly files matching the lilypond scoring standard >> >> Heh. This is a known problem, and the OCR part is very, very >> difficult. It also has nothing to do with lilypond. > > > There are a number of commercial products that, given a perfect > representation of a score, convert it to perfect musicXML - so it can't be > that hard. Hm, could you name some, please? I haven't come across such a product, yet. > It may simply be that the OS community do not generally have these skills. > > -- > Phil Holmes > > ___ > lilypond-user mailing list > lilypond-u...@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)
Hi Janek, done! Thanks patrick BTW: http://codereview.appspot.com/5303063/ is still open and hasn't been pushed. Am 16.01.2012 um 00:07 schrieb Janek Warchoł: > Hi Patrick, > > your patch was pushed when i was absent; now i see that Rietveld issue > is still opened. Could you close it please? > > http://codereview.appspot.com/5096050/ > > Janek > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
