Re: Lyrics and Punctuations Alignment Issue?
2013/5/6 Jun Wang : > > Since this issue is so common, I wonder if we could add this feature to the > lilypond code base? Definitely. This was already reported: http://code.google.com/p/lilypond/issues/detail?id=2451 And (after a long wait) much of the work is already done; now it's waiting for the rewrite of self-alignment interface (issue http://code.google.com/p/lilypond/issues/detail?id=3239, which in turn waits until new stable is released). So, i'm sorry that someone is duplicating my work :( But according to my knowledge, these things should really happen in this order (1. stable -> 2. issue 3239 -> 3. lyrics punctuation). best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: publish music book
Hi Jim, On 22/04/13 20:17, Jim Tisdall wrote: > I'm preparing a book for publication. > > Lilypond has several methods to combine text and examples. One is > lilypond-book, but due to the many examples in my chapters, I find > that is too slow, so I'm deciding on other ways to include the > graphics. No problem since everything is made possible, especially > for a programmer. Probably some combo of lilypond with make. > > Peace, Jim One possibility may be to use OpenOffice/LibreOffice with the OOOLilyPond extension to and then translate that to lilypondbook + snippets. Cheers, Ian Hulin ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: publish music book
Ian Hulin writes: > Hi Jim, > On 22/04/13 20:17, Jim Tisdall wrote: >> I'm preparing a book for publication. >> > >> Lilypond has several methods to combine text and examples. One is >> lilypond-book, but due to the many examples in my chapters, I find >> that is too slow, so I'm deciding on other ways to include the >> graphics. No problem since everything is made possible, especially >> for a programmer. Probably some combo of lilypond with make. >> > >> Peace, Jim > One possibility may be to use OpenOffice/LibreOffice with the > OOOLilyPond extension I have found it impossible to have OOOLilyPond include anything but bitmaps into the document. It does not work with any vector rendition of LilyPond output, so expect many more rasterization artifacts. Partly that is the fault of OpenOffice/LibreOffice for not being able to import _any_ free vector image format reliably. > to and then translate that to lilypondbook + snippets. Not sure how that is supposed to work. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re:scheme function help
This conversation is throwing much light on the difficulty that even the computer literate face when trying to learn the Lilypond Scheme interface. In this case the simple addition of a mark is seen to be very complex with procedures and arguments that are counter intuitive (or at least nowhere near intuitive). Nor are they and their uses fully defined in the manuals (I'm sure it is obvious to a developer but confusing to an outsider). Secondly there are apparently several ways to skin the cat and contexts that are not immediately obvious. Guidance at the gateway would be a very productive way to spread the use of Lilypond beyond highly qualified developers into the more mundane world of the everyday user. None of this is criticism of the project which is a remarkable achievment - more a cry from the wilderness for a helping hand to newcomers. Actually not so much a helping hand more an appreciation of the misconceptions and misunderstandings that plague the tyro. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: scheme function help
"Peter Gentry" writes:
> This conversation is throwing much light on the difficulty that even
> the computer literate face when trying to learn the Lilypond
> Scheme interface.
By using documentation from 5 years ago with a current version of
LilyPond. Preceding my work on usability.
I don't consider it fair to judge LilyPond and the work that has been
invested into it in that area on that base.
> In this case the simple addition of a mark is seen to be very complex
> with procedures and arguments that are counter intuitive (or at least
> nowhere near intuitive). Nor are they and their uses fully defined in
> the manuals (I'm sure it is obvious to a developer but confusing to an
> outsider).
Get real. define-music-function is explained pretty well, and the
function is
addmarkup =
#(define-markup-function (parser location mark music)
(markup? ly:music?)
#{ \mark #mark #music #})
which is a dead-simple wrapper not really involving any Scheme
programming, and the obvious way to do this once you have read the
documentation. If you also want to allow for
\addmarkup \default { c'd' e' f' }, this becomes
#(define-markup-function (parser location mark music)
((markup?) ly:music?)
(if mark
#{ \mark #mark #music #}
#{ \mark \default #music #}))
which is more intricate but still a very basic wrapper once you bother
looking up \default and/or optional function arguments.
> Secondly there are apparently several ways to skin the cat and
> contexts that are not immediately obvious.
If you try doing things in a complex manner unnecessarily, possibly
triggered by very old documentation, you can expect complex problems.
> Guidance at the gateway would be a very productive way to spread the
> use of Lilypond beyond highly qualified developers into the more
> mundane world of the everyday user.
So what do you think I have been doing for the last two years?
> None of this is criticism of the project which is a remarkable
> achievment - more a cry from the wilderness for a helping hand to
> newcomers. Actually not so much a helping hand more an appreciation of
> the misconceptions and misunderstandings that plague the tyro.
Try starting with the documentation corresponding to the version you are
using. The above examples are for the current version, but 2.16 works
almost the same except for requiring $music instead of #music in the
expressions.
And yes, the documentation goes to a lot of effort in order to explain
the details. And yes, this was awfully documented and awful to use in
2.12, the documentation that the original poster chose to consult.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: repeated time signatures
Hi David,
unfortunately your engraver does _not_ work as expected (and as I had
stated):
Obviously the 'previous' time signature may also be the one in a
'previous' staff at the same musical moment. So when using the engraver
the time signature is only printed in the top-most staff :-(
I guess one can update the condition so that is true if the time
signature of 'elem' is equal to the time signature of 'prev' _and_ if
their musical moments differ.
But unfortunately I don't have any clue on how to achieve that :-(
Any help (new version or even better: hint) would be very welcome
Urs
Am Montag, den 29.04.2013, 09:15 -0500 schrieb David Nalesnik:
> Hi Urs,
>
>
> On Mon, Apr 29, 2013 at 9:02 AM, Urs Liska wrote:
> The NR (1.2.3 "Displaying Rhythms") states that time
> signatures "are printed at the beginning of a piece and
> whenever the time signature changes."
>
> But if I write
>
> music = {
> \time 3/4
> R2.*4
> \time 3/4
> R2.
> }
>
> the time signature is printed a second time although it
> doesn't change (to my understanding)
>
> a) Is this intended behaviour? And if yes, shouldn't it be
> documented?
>
>
> I would think that you should need to tell LilyPond to force the
> unusual situation of a redundant time signature as it's not typical
> practice. It shouldn't be possible to do something unusual like this
> through oversight.
>
> b) How can I achieve that the time signature is only printed
> if it is actually different from the one currently in use?
>
>
> This question came up here:
> http://www.mail-archive.com/lilypond-user@gnu.org/msg72613.html
>
>
> Hopefully the engraver (see second version) still works!
>
>
> c) How can I achieve the same (only displaying if really
> changed) for key signatures and clefs?
>
>
> Possibly that engraver can be adapted. (I can't try now as my job is
> calling).
>
>
> Best,
> David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: repeated time signatures
Hi Urs, On Tue, May 7, 2013 at 6:02 AM, Urs Liska wrote: > Hi David, > > unfortunately your engraver does _not_ work as expected (and as I had > stated): > Obviously the 'previous' time signature may also be the one in a > 'previous' staff at the same musical moment. So when using the engraver > the time signature is only printed in the top-most staff :-( > The immediate problem is solved by keeping the engraver in the Staff context. Of course it would be nice if the behavior you describe didn't happen if the engraver is moved to StaffGroup or PianoStaff or whatever. > > I guess one can update the condition so that is true if the time > signature of 'elem' is equal to the time signature of 'prev' _and_ if > their musical moments differ. > But unfortunately I don't have any clue on how to achieve that :-( > > Any help (new version or even better: hint) would be very welcome > > You've described how I would tackle the problem. Getting the timing of the signatures is the part I'm not sure of right now. (It could be stored with the time signatures as they are acknowledged, but maybe there's a better way. I'll look into this. Sorry I don't have a ready hint/solution.) -David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics and Punctuations Alignment Issue?
Hi Janek, On Tue, May 7, 2013 at 4:29 AM, Janek Warchoł wrote: > So, i'm sorry that someone is duplicating my work :( > But according to my knowledge, these things should really happen in > this order (1. stable -> 2. issue 3239 -> 3. lyrics punctuation). > Just a workaround, for the time being :) Thanks for your work on these issues! BTW, will the enhancement be able to handle multi-byte characters? --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics and Punctuations Alignment Issue?
Hi David, 2013/5/7 David Nalesnik : > Just a workaround, for the time being :) Well, the issue is not that complicated, and a real fix will (conceptually) be quite similar to yours. > Thanks for your work on these issues! Don't thank until the code isn't in the official repository ;-) > BTW, will the enhancement be able to handle multi-byte characters? That's not done yet, but i will try until it will handle them. best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: repeated time signatures
Hi David, thanks for that. Sometimes I have the impression I don't see the forest for the trees as soon as Scheme is involved. Even if the actual problem isn't a Scheme one as in the current case ... Moving the engraver to Staff seems to be enough for my score problem. Urs Am Dienstag, den 07.05.2013, 07:38 -0500 schrieb David Nalesnik: > Hi Urs, > > > On Tue, May 7, 2013 at 6:02 AM, Urs Liska wrote: > Hi David, > > unfortunately your engraver does _not_ work as expected (and > as I had > stated): > Obviously the 'previous' time signature may also be the one in > a > 'previous' staff at the same musical moment. So when using the > engraver > the time signature is only printed in the top-most staff :-( > > > The immediate problem is solved by keeping the engraver in the Staff > context. Of course it would be nice if the behavior you describe > didn't happen if the engraver is moved to StaffGroup or PianoStaff or > whatever. > > > I guess one can update the condition so that is true if the > time > signature of 'elem' is equal to the time signature of 'prev' > _and_ if > their musical moments differ. > But unfortunately I don't have any clue on how to achieve > that :-( > > Any help (new version or even better: hint) would be very > welcome > > > > > You've described how I would tackle the problem. Getting the timing > of the signatures is the part I'm not sure of right now. (It could be > stored with the time signatures as they are acknowledged, but maybe > there's a better way. I'll look into this. Sorry I don't have a > ready hint/solution.) > > > -David > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
[OT?] Roman Numeral Analysis Fonts
Hi, I've released two fonts for "Roman Numeral" Analysis... as the music symbols (sharps, flats, double sharps, doubles flats) are based on Emmentaler, I've thought that would be nice to distribute also among LilyPonders.. There is a PT and an EN version. I use them to prepare music analysis of IMSLP scores or images in LibreOffice (yes, I'm aware that LilyPond has features to do Roman Numeral analysis, but my fonts...). The font use is somewhat tricky. In a macbook US International - PC layout one can notate things with simple keys (note names and grades/uppercase/lowercase), alt+keys (columns of numbers/intervals), shift+keys (alterations) and alt+shift+keys (Np, Fr, etc.). As an example, to notate something like I64 one can type it, with this layout, like that "1" / space / [alt+6] / [alt+r] / [space or tab] Hope it works well in other OSes in some layout (some feedback would be nice). You find the fonts here: http://zepadovani.info/etc.html As some parts of the font come from Emmentaler I've released them in the same license (GPLv3 with exception that derived documents can be released with any license). I'm not an expert in these license issues, so if someone find any failure regarding this, please tell me... Number, letters and other symbols are based in DejaVu Sans, and it may be usefull to use it to write other annotations... Well... the font is not really "professional", but it is helping me a lot to prepare music materials to my students. Maybe in the future I will write a guide about how to use it and a second font family, to make Functional Harmony analysis. cheers, josé ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics and Punctuations Alignment Issue?
Janek Warchoł writes: > Hi David, > > 2013/5/7 David Nalesnik : >> Just a workaround, for the time being :) > > Well, the issue is not that complicated, and a real fix will > (conceptually) be quite similar to yours. > >> Thanks for your work on these issues! > > Don't thank until the code isn't in the official repository ;-) > >> BTW, will the enhancement be able to handle multi-byte characters? > > That's not done yet, but i will try until it will handle them. It would likely make more sense to invest the time into Guile 2 migration as Guile 2 has Unicode characters in its strings. Which means that the problems will be elsewhere entirely and any handling of them with the Guile 1 code will be a complete waste of effort. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics and Punctuations Alignment Issue?
2013/5/7 David Kastrup : > Janek Warchoł writes: > >> 2013/5/7 David Nalesnik : >>> BTW, will the enhancement be able to handle multi-byte characters? >> >> That's not done yet, but i will try until it will handle them. > > It would likely make more sense to invest the time into Guile 2 > migration as Guile 2 has Unicode characters in its strings. Which means > that the problems will be elsewhere entirely and any handling of them > with the Guile 1 code will be a complete waste of effort. I intended to tackle this issue on C++ level, so i suppose that Guile is irrelevant? Or am i missing something? (it's been a while since i wrote the part that i have) Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics and Punctuations Alignment Issue?
Janek Warchoł writes: > 2013/5/7 David Kastrup : >> Janek Warchoł writes: >> >>> 2013/5/7 David Nalesnik : BTW, will the enhancement be able to handle multi-byte characters? >>> >>> That's not done yet, but i will try until it will handle them. >> >> It would likely make more sense to invest the time into Guile 2 >> migration as Guile 2 has Unicode characters in its strings. Which means >> that the problems will be elsewhere entirely and any handling of them >> with the Guile 1 code will be a complete waste of effort. > > I intended to tackle this issue on C++ level, so i suppose that Guile > is irrelevant? Or am i missing something? (it's been a while since i > wrote the part that i have) A string is an array of characters in GUILE and I don't think it makes sense treating it separate from GUILE strings in C++. That's just duplicated work and an additional source of problems. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: scheme function help
I did not mean to criticize anyone but to learn how to use the software
completely. And that was my fault as I did not watch which documentation I
read, ie the version. I'm sorry. I think lilypond has a great community and
i did't have to wait more that 12h to get at least a response. This is very
fast in my opinion. Meny people care and i appreciated that. But to start
for scratch is hard and help is always encouraging.
On Tue, May 7, 2013 at 12:09 PM, David Kastrup wrote:
> "Peter Gentry" writes:
>
> > This conversation is throwing much light on the difficulty that even
> > the computer literate face when trying to learn the Lilypond
> > Scheme interface.
>
> By using documentation from 5 years ago with a current version of
> LilyPond. Preceding my work on usability.
>
> I don't consider it fair to judge LilyPond and the work that has been
> invested into it in that area on that base.
>
> > In this case the simple addition of a mark is seen to be very complex
> > with procedures and arguments that are counter intuitive (or at least
> > nowhere near intuitive). Nor are they and their uses fully defined in
> > the manuals (I'm sure it is obvious to a developer but confusing to an
> > outsider).
>
> Get real. define-music-function is explained pretty well, and the
> function is
>
> addmarkup =
> #(define-markup-function (parser location mark music)
> (markup? ly:music?)
> #{ \mark #mark #music #})
>
> which is a dead-simple wrapper not really involving any Scheme
> programming, and the obvious way to do this once you have read the
> documentation. If you also want to allow for
> \addmarkup \default { c'd' e' f' }, this becomes
>
> #(define-markup-function (parser location mark music)
> ((markup?) ly:music?)
> (if mark
> #{ \mark #mark #music #}
> #{ \mark \default #music #}))
>
> which is more intricate but still a very basic wrapper once you bother
> looking up \default and/or optional function arguments.
>
> > Secondly there are apparently several ways to skin the cat and
> > contexts that are not immediately obvious.
>
> If you try doing things in a complex manner unnecessarily, possibly
> triggered by very old documentation, you can expect complex problems.
>
> > Guidance at the gateway would be a very productive way to spread the
> > use of Lilypond beyond highly qualified developers into the more
> > mundane world of the everyday user.
>
> So what do you think I have been doing for the last two years?
>
> > None of this is criticism of the project which is a remarkable
> > achievment - more a cry from the wilderness for a helping hand to
> > newcomers. Actually not so much a helping hand more an appreciation of
> > the misconceptions and misunderstandings that plague the tyro.
>
> Try starting with the documentation corresponding to the version you are
> using. The above examples are for the current version, but 2.16 works
> almost the same except for requiring $music instead of #music in the
> expressions.
>
> And yes, the documentation goes to a lot of effort in order to explain
> the details. And yes, this was awfully documented and awful to use in
> 2.12, the documentation that the original poster chose to consult.
>
> --
> David Kastrup
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
--
*Nesmotren govori kao da mačem probada, a jezik je mudrih iscjeljenje.
Izreke 12:18*
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: scheme function help
Stjepan Horvat writes: > I did not mean to criticize anyone but to learn how to use the > software completely. And that was my fault as I did not watch which > documentation I read, ie the version. I'm sorry. I was no annoyed at you making a mistake, but rather that Peter used that in order to paint a bleak general picture of LilyPond. You actually have managed to get pretty far considering the discrepancy between documentation and actually used version. And if you scour the developer mailing lists around the time of 2.12 you'll likely find a lot of choice words of mine about the state of the documentation even at a time when it still _did_ correspond with the current version. And that version was so awfully inconsistent that it turned out easier to first bring it into a state where you'd not have to wash out your hands with soap after writing documentation for it. Actually, you might want to look at http://news.lilynet.net/?The-LilyPond-Report-23#feature_story_prelude_1_in_scheme> which I mentioned elsewhere in this thread. And compare the approach there to the older, 2.12 style version of it that Nicolas Sceaux has on his website. > I think lilypond has a great community and i did't have to wait more > that 12h to get at least a response. Well, I definitely proud myself on facilitating one of the fastest PTF times for active projects (PTF = posting to flamewar). > This is very fast in my opinion. Yes. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
writing percussion notes
Ok. I'v never seen percussion music so I don't even know how to looks. I have to in this final assignment write for 3 timponies, 1 player playing them, a bass drum and symbol, one player playing them and a snare. I know there are to be 3 percussion lines, but in the case of the timpani's how do I indicate which ones they need, or should I? and in the case of the non pitched instruments how do I indicate those notes, or rhythms that is? Sorry if I'm not making sense. I'm not a band nerd. lol! should I do new staff groups? or is it all 3 lines on 1 staff? if so yuck! Take care. and thanks all. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
