Re: Persian accidentals
Hans Aberg wrote: On 1 Feb 2009, at 13:07, Graham Breed wrote: You can use any glyph, or string of glyphs, you have in a font. I haven't seen a mention here of such a font being available. Didn't you work with MicroABC? A quick search gave this page http://anamnese.online.fr/site2/index.php?page=abc_perse (Click on the "English version" button to see the text.) I've done a bit with it. That link isn't MicroABC, it's a different tool for use with abcm2ps. But it'll likely be compatible with Lilypond as both use PostScript. I think that koron and sori may not be in Unicode, which LilyPond uses for fonts. So some special implementation might be needed. There'll be a code point in the font file. You can get it using FontForge (which I had to use for Sagittal because the Unicode mapping is wrong for some reason I may have been told about but forgot). Another thing Hudson Lacerda (the author of MicroABC) told me is that you can get PostScript code for a glyph from FontForge. That might be useful as some of the hacks in this thread have involved coding PostScript directly. If you're designing a Unicode font there's a private use area for characters without an official code point. Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Lilypondtool 2.12-r2 and UTF-8
I updated to this version of LPT a few days ago. It fixes the problem with jPedal and jEdit locking up if jPedal is not showing the first page of the PDF when rebuilding the ly file, but although I have the default file encoding in jEdit set to UTF-8, it still insists on saving ly files as UTF-8Y. This only happens with ly files: I can open or create other types of file using UTF-8 encoding and they remain UTF-8 on saving. Nick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fitting as many lines as possible on a page
On Sun, 2009-02-01 at 20:00 +0100, Reinhold Kainhofer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Sonntag, 1. Februar 2009 19:49:05 Joe Neeman wrote: > > On Sat, 2009-01-31 at 12:13 +0100, Reinhold Kainhofer wrote: > > > On Samstag, 31. Januar 2009 02:06:38 Joe Neeman wrote: > > > > On Sat, 2009-01-31 at 00:53 +0100, Reinhold Kainhofer wrote: > > > > > On Freitag, 30. Januar 2009 23:37:28 Tim Yang wrote: > > > > > > It doesn't work. I set the page-count as 2 and Lilypond still uses > > > > > > 3 pages. I think it is because somehow Lilypond thinks these lines > > > > > > don't fit in 2 pages but in fact there is a lot of space left. > > > > > > > > > > Yes, currently the vertical page layouting algorithm of lilypond is > > > > > sub- optimal. Lilypond reserves 10% of the total space to make sure > > > > > it does not overprint staves. This means that 10% of the page will > > > > > always be wasted... Unfortunately, there is no easy way around this > > > > > for now, until someone starts working on the vertical staff layouting > > > > > seriously... > > > > > > > > This is only the case for the stretching of systems, AFAICR. It > > > > shouldn't affect single-staff music. > > > > > > Isn't stretch-and-draw-page called for all pages, even for single-staff > > > systems? > > > > Right, but it only uses the 10% buffer to decide how much to stretch the > > systems. The actual layout of the systems, once they've been stretched, > > is done in space-systems, which uses the full printable extent of the > > page. > > Exactly. However, the 10% buffer is used when calculating how many systems to > put on a page, so even if e.g. 10 systems would fit on a page, only 9 are > placed there... Or am I misunderstanding the code? Either you are or I am misremembering it. The stretch-and-draw-page function is called after the page breaks have been decided (in Optimal_page_breaking::solve, by default) to do the stretching and to actually position the systems on the page. Within the page-breaking calculation, there is no 10% buffer. Joe ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Persian musical koron and sori
PS The symbols for koron and sori were introduced by Vaziri (1888-1980). His quartertone theory didn't last but his symbols have. Millions of pages of printed Persian music are around, with the koron and sori always obviously handwritten. Hopefully we (I) can typeset them in lilypond very soon. Kees - Original Message - From: Behnam Date: Sunday, February 1, 2009 3:16 pm Subject: Re: Persian musical koron and sori To: Kees van den Doel Cc: Hans Aberg , Unicode Mailing List , LilyPond users list , Graham Breed > Thanks Kees. > Is this for tuning a key or marking a specific note? or both? > Behnam > On 1-Feb-09, at 6:07 PM, Kees van den Doel wrote: > > > Here's an example from a Persian music book. > > Kees > > > > - Original Message - > > From: Hans Aberg > > Date: Sunday, February 1, 2009 2:14 pm > > Subject: Re: Persian musical koron and sori > > To: Behnam > > Cc: Unicode Mailing List , LilyPond > users list > > , Graham Breed > , Kees van > > den Doel > > > >> On 1 Feb 2009, at 22:35, Behnam wrote: > >> > LilyPond now has the capability to typeset these, if one can > >> get > hold of glyphs, and produce correctly tuned MIDI files. > >>> > >>> I may be able to produce the glyph (with some additional > >> studies) > >>> but I can only support you in getting the code for it. > >> > >> It would be great - I searched for that on the Internet and > >> could not > >> find it. > >> > >> Graham Breed or Kees van den Doel on the LilyPond list may know > >> better > >> exactly what might be needed. > >> > >> Hans > >> > >> > >> > >> > > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: changing notehead color within a chord
Thanks very much Jon, for your quick reply. Works great
Best
Nick
Jonathan Kulp wrote:
Nick Didkovsky wrote:
Hello
I am changing notehead color with ...
\override NoteHead #'color = #'(1.0 0.7 0.0)
... which works fine.
But how can I change the notehead color within a chord?
Thanks
Nick Didkovsky
You want the \tweak command to affect individual items inside a chord:
\relative c' {
4
}
Jon
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: changing notehead color within a chord
Nick Didkovsky wrote:
Hello
I am changing notehead color with ...
\override NoteHead #'color = #'(1.0 0.7 0.0)
... which works fine.
But how can I change the notehead color within a chord?
Thanks
Nick Didkovsky
You want the \tweak command to affect individual items inside a chord:
\relative c' {
4
}
Jon
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
changing notehead color within a chord
Hello I am changing notehead color with ... \override NoteHead #'color = #'(1.0 0.7 0.0) ... which works fine. But how can I change the notehead color within a chord? Thanks Nick Didkovsky ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: phrasing slur continued through a repeat?
Well, \repeatTie doesn't take you very far into the ensuing phrase.
And it doesn't swoop properly.
A fairly easy way in this case is to add a hidden grace note:
{ \hideNotes \grace b16\( \unHideNotes c8 g8 c8 \) | }
And you can use the grace pitch to adjust the starting height.
This is usually necessary if you want to make the trailing fragment
appear any way related to the (both-times) leading section.
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Persian musical koron and sori
> Is this for tuning a key or marking a specific note? or both? Both. They are used exactly as normal accidentals. Kees > Behnam > On 1-Feb-09, at 6:07 PM, Kees van den Doel wrote: > > > Here's an example from a Persian music book. > > Kees > > > > - Original Message - > > From: Hans Aberg > > Date: Sunday, February 1, 2009 2:14 pm > > Subject: Re: Persian musical koron and sori > > To: Behnam > > Cc: Unicode Mailing List , LilyPond > users list > > , Graham Breed > , Kees van > > den Doel > > > >> On 1 Feb 2009, at 22:35, Behnam wrote: > >> > LilyPond now has the capability to typeset these, if one can > >> get > hold of glyphs, and produce correctly tuned MIDI files. > >>> > >>> I may be able to produce the glyph (with some additional > >> studies) > >>> but I can only support you in getting the code for it. > >> > >> It would be great - I searched for that on the Internet and > >> could not > >> find it. > >> > >> Graham Breed or Kees van den Doel on the LilyPond list may know > >> better > >> exactly what might be needed. > >> > >> Hans > >> > >> > >> > >> > > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Persian musical koron and sori
Here's an example from a Persian music book. Kees - Original Message - From: Hans Aberg Date: Sunday, February 1, 2009 2:14 pm Subject: Re: Persian musical koron and sori To: Behnam Cc: Unicode Mailing List , LilyPond users list , Graham Breed , Kees van den Doel > On 1 Feb 2009, at 22:35, Behnam wrote: > > >> LilyPond now has the capability to typeset these, if one can > get > >> hold of glyphs, and produce correctly tuned MIDI files. > > > > I may be able to produce the glyph (with some additional > studies) > > but I can only support you in getting the code for it. > > It would be great - I searched for that on the Internet and > could not > find it. > > Graham Breed or Kees van den Doel on the LilyPond list may know > better > exactly what might be needed. > > Hans > > > <>___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Persian musical koron and sori
On 1 Feb 2009, at 22:35, Behnam wrote: LilyPond now has the capability to typeset these, if one can get hold of glyphs, and produce correctly tuned MIDI files. I may be able to produce the glyph (with some additional studies) but I can only support you in getting the code for it. It would be great - I searched for that on the Internet and could not find it. Graham Breed or Kees van den Doel on the LilyPond list may know better exactly what might be needed. Hans ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Persian accidentals
> > Is there any way to print the koron (60cents flat) and sori > (40 cent sharp)? > I am curious where you got those figures. The values in > Hormoz > Farhat's thesis suggest one should use E53 with koron lowering > 3 > commas and sori raising 2 commas (E53 tonesteps). He describes > the > Persian pitch system using a minor (resp. major) second m (resp. > M) > plus a neutral second n. In E53 they are m = 4, M = 9, n = 6. > > Then I wanted to retune m, M into E12. There is a suggestion > that n > can be set to the rational interval 27/25, which is close to > Farhat's > values, and also sound good in Scala. If I fix n at that value, > a > close approximation is E36, or if you so like, in E12 let (koron > resp. > sori) lower 2/3 (resp. raise 1/3) of an E12 tonestep. > > Now, this is very close to your suggestion, making me curious > about > the motivation for those setting those. Hormoz Farhat was not a practicing musician, so I would not rely too much on his thesis and book. For sources and details of Persian tuning please see my website http://members.shaw.ca/persianney section techinque-fingering and tuning. In terms of lilypond support for Persian music the koron and sori glyphs are all that's needed for notation, but for midi rendering we'd need also at least the 20 cent flat note, which is not notated but considered part of tuning. Also the minor second is often small up to 10 cent. Kees ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Persian accidentals
> >> Is there any way to print the koron (60cents flat) and sori > (40 cent > >> sharp)? > > > > Check with Graham Breed - it might be possible now. > > You can use any glyph, or string of glyphs, you have in a > font. OK, my question then is: how? Assume I edit the font svg files emmentaler-??.svg and put in the koron and sori code and put in something called accidentals.koron. Or even just overwriting accidentals.mirroredflat. How do I then compile these changes? > haven't seen a mention here of such a font being available It is available in an abc variant, but can only be printed above the notes. Thanks, Kees ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Good luck, Valentin
Jonathan Kulp a écrit : Francisco Vila wrote: Cross fingers, today is the premiere of Valentin's "the LilyPond Opera" in Montpellier. Success! The name is "Affaire étrangère"; how would you translate it, Valentin? :-) All right! Can't wait to hear how it goes. Good luck! IIRC it should have started at 15.00 CET, so the premiere is most probably finished. I hope this was a great success and the two other will go well too. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cross Staff Argeggio Question (v2.6.5)
On 2/1/09 1:06 PM, "Ed Ardzinski" wrote: > > Thanks Mats! > > arpeggioUp = \override PianoStaff.Arpeggio #'arpeggio-direction = #UP > > Did the trick. > > As for what I'm missinng...it's hard to know since I'm still using an > "ancient" version. So far I've still yet to exhaust the potential of 2.6.5. > And frankly, I'm a little apprehensive tying to make a jump of about 6 > versions - I'm guessing it will take a bit of effort. It's actually only 3 versions. 2.6, 2.8, 2.10, 2.12. The odd-numbered versions are all development versions. I think you ought to at least take a shot at it; I think you'll find that 2.12 is way ahead of 2.6. One way that it's vastly improved is the documentation. And much of the excellent docs for 2.12 won't apply to 2.6, because of differences in the syntax. It's going to be harder and harder as time goes on to get help for 2.6, because there will be fewer and fewer people who have any experience with it. Regards, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Good luck, Valentin
Francisco Vila wrote: Cross fingers, today is the premiere of Valentin's "the LilyPond Opera" in Montpellier. Success! All right! Can't wait to hear how it goes. Good luck! Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Cross Staff Argeggio Question (v2.6.5)
Thanks Mats! arpeggioUp = \override PianoStaff.Arpeggio #'arpeggio-direction = #UP Did the trick. As for what I'm missinng...it's hard to know since I'm still using an "ancient" version. So far I've still yet to exhaust the potential of 2.6.5. And frankly, I'm a little apprehensive tying to make a jump of about 6 versions - I'm guessing it will take a bit of effort. When I do have the time to devote to writing music I'd rathrr write than fight with converting code. I am aware of several newer features that I am missing - word wrap in markups and not having to invoke chord name exceptions all the time seem like nice features. But for my style of writing I'm pretty satisfied where I am. Thanks again!> Ed Ardzinski wrote:> > Yes, I'm still using v2.6.5...> I hope you realize what you miss!> See http://lists.gnu.org/archive/html/lilypond-user/2006-10/msg00193.html> for a solution that should apply also to your ancient version.> You may have to look through all emails in that thread to get the> full story.> > /Mats _ Windows Live™ Hotmail®…more than just e-mail. http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_hm_justgotbetter_howitworks_012009___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Good luck, Valentin
Cross fingers, today is the premiere of Valentin's "the LilyPond Opera" in Montpellier. Success! -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: phrasing slur continued through a repeat?
One solution is \repeatTie, see http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Writing-rhythms#Ties /Mats Ed Ravin wrote: I'm using LilyPond Version 2.10.29-1 on a PPC MacOS 10.4 (Tiger). I'm trying to typeset a piece that has phrasing slurs and repeats. One of the phrasing slurs starts in the repeated section, and it ends in the alternative section. The attached file "slurme.ly.txt" shows the problem. It compiles without errors, and the phrasing slur is rendered properly in the first alternative, but it is not drawn at all in the 2nd alternative (the final measure). Any ideas? Do I need to draw the phrasing slur in the 2nd alternative "by hand"? Thanks, -- Ed ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing School of Electrical Engineering Royal Institute of Technology (KTH) SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: mats.bengts...@ee.kth.se WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cross Staff Argeggio Question (v2.6.5)
Ed Ardzinski wrote:
Yes, I'm still using v2.6.5...
I hope you realize what you miss!
I'm trying to get a cross staff arpeggio with a directional head. I'm
wondering if that's possible or not, since it seems no matter what I
do the arpeggio comes out with no direction indicator.
See http://lists.gnu.org/archive/html/lilypond-user/2006-10/msg00193.html
for a solution that should apply also to your ancient version.
You may have to look through all emails in that thread to get the
full story.
/Mats
Here's a condensation of the code. Thanks in advance!
\version "2.6.5"
#(ly:set-option 'point-and-click #f)
\header
{
title = "Cross Staff Apeggio Test"
}
upper =
{
\clef treble
\set PianoStaff.connectArpeggios = ##t
\arpeggioUp
1\arpeggio
}
lower =
{
\clef bass
1\arpeggio
}
\score
{
\context PianoStaff
<<
\context Staff = upper \upper
\context Staff = lower \lower
>>
\layout{}
}
Windows Live™: E-mail. Chat. Share. Get more ways to connect. Check it
out.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: mats.bengts...@ee.kth.se
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Make eighth looks like quarter note
Nick Payne wrote: You can use \override Stem #'flag-style = #'no-flag c8 c That's a complicated solution to obtain the same as c4*1/2, read about "scaling durations" in the manual. However, James Bailey has provided a much better solution for this specific application. /Mats and so on to remove the flag on eighth or shorter notes. Nick *From:* lilypond-user-bounces+nick.payne=internode.on@gnu.org [mailto:lilypond-user-bounces+nick.payne=internode.on@gnu.org] *On Behalf Of *Manolo Padron Martinez *Sent:* Saturday, 31 January 2009 11:34 PM *To:* lilypond-user@gnu.org *Subject:* Make eighth looks like quarter note Hi: I'm really newbie with lilypond. I've been looking in google about how to change the look of the eighth note to appear like a quarter note. I only want to change how the note is draw into the pdf but I don't want to make it a quarter note. In drum partiture looks like better in that way but I need that the note sounds (when I get the midi file) like a eighth note. I attach a screenshot to ilustrate why I want to do that. Thanks in advance Manolo Padrón Martínez No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.233 / Virus Database: 270.10.16/1926 - Release Date: 01/30/09 17:31:00 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing School of Electrical Engineering Royal Institute of Technology (KTH) SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: mats.bengts...@ee.kth.se WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fitting as many lines as possible on a page
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sonntag, 1. Februar 2009 19:49:05 Joe Neeman wrote: > On Sat, 2009-01-31 at 12:13 +0100, Reinhold Kainhofer wrote: > > On Samstag, 31. Januar 2009 02:06:38 Joe Neeman wrote: > > > On Sat, 2009-01-31 at 00:53 +0100, Reinhold Kainhofer wrote: > > > > On Freitag, 30. Januar 2009 23:37:28 Tim Yang wrote: > > > > > It doesn't work. I set the page-count as 2 and Lilypond still uses > > > > > 3 pages. I think it is because somehow Lilypond thinks these lines > > > > > don't fit in 2 pages but in fact there is a lot of space left. > > > > > > > > Yes, currently the vertical page layouting algorithm of lilypond is > > > > sub- optimal. Lilypond reserves 10% of the total space to make sure > > > > it does not overprint staves. This means that 10% of the page will > > > > always be wasted... Unfortunately, there is no easy way around this > > > > for now, until someone starts working on the vertical staff layouting > > > > seriously... > > > > > > This is only the case for the stretching of systems, AFAICR. It > > > shouldn't affect single-staff music. > > > > Isn't stretch-and-draw-page called for all pages, even for single-staff > > systems? > > Right, but it only uses the 10% buffer to decide how much to stretch the > systems. The actual layout of the systems, once they've been stretched, > is done in space-systems, which uses the full printable extent of the > page. Exactly. However, the 10% buffer is used when calculating how many systems to put on a page, so even if e.g. 10 systems would fit on a page, only 9 are placed there... Or am I misunderstanding the code? Cheers, Reinhold - -- - -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJhfFeTqjEwhXvPN0RAmfHAKCVTq3LdN1N2wCfWYO3DHml0qBDwQCgnigr 9Bw5QvsbQCiknds+i6Kq2Fs= =gGDG -END PGP SIGNATURE- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fitting as many lines as possible on a page
On Sat, 2009-01-31 at 12:13 +0100, Reinhold Kainhofer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Samstag, 31. Januar 2009 02:06:38 Joe Neeman wrote: > > On Sat, 2009-01-31 at 00:53 +0100, Reinhold Kainhofer wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA1 > > > > > > On Freitag, 30. Januar 2009 23:37:28 Tim Yang wrote: > > > > It doesn't work. I set the page-count as 2 and Lilypond still uses 3 > > > > pages. I think it is because somehow Lilypond thinks these lines don't > > > > fit in 2 pages but in fact there is a lot of space left. > > > > > > Yes, currently the vertical page layouting algorithm of lilypond is sub- > > > optimal. Lilypond reserves 10% of the total space to make sure it does > > > not overprint staves. This means that 10% of the page will always be > > > wasted... Unfortunately, there is no easy way around this for now, until > > > someone starts working on the vertical staff layouting seriously... > > > > This is only the case for the stretching of systems, AFAICR. It > > shouldn't affect single-staff music. > > Isn't stretch-and-draw-page called for all pages, even for single-staff > systems? Right, but it only uses the 10% buffer to decide how much to stretch the systems. The actual layout of the systems, once they've been stretched, is done in space-systems, which uses the full printable extent of the page. Joe ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staff collision because of a postscript line
Stefan Thomas wrote: What does this \with-dimensions-command exactly do? Is it explained in the manual? It is mentioned right at the end of NR B.8.6. I think that by "dimensions" you are meant to understand the X-extent and Y-extent [1] of the markup that follows. I suppose that if the markup involves text, Lilypond can use the font information to calculate these dimensions, but if it involves just Postscript, Lilypond doesn't try. [1] as described for "ly:make-stencil" in NR B.15. Also mentioned in NR 5.5.1, second paragraph. Cheers, Robin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Cross Staff Argeggio Question (v2.6.5)
Yes, I'm still using v2.6.5...
I'm trying to get a cross staff arpeggio with a directional head. I'm
wondering if that's possible or not, since it seems no matter what I do the
arpeggio comes out with no direction indicator.
Here's a condensation of the code. Thanks in advance!
\version "2.6.5"
#(ly:set-option 'point-and-click #f)
\header
{
title = "Cross Staff Apeggio Test"
}
upper =
{
\clef treble
\set PianoStaff.connectArpeggios = ##t
\arpeggioUp
1\arpeggio
}
lower =
{
\clef bass
1\arpeggio
}
\score
{
\context PianoStaff
<<
\context Staff = upper \upper
\context Staff = lower \lower
>>
\layout{}
}
_
Windows Live™: E-mail. Chat. Share. Get more ways to connect.
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t2_allup_explore_012009___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Persian accidentals
On 1 Feb 2009, at 13:07, Graham Breed wrote: You can use any glyph, or string of glyphs, you have in a font. I haven't seen a mention here of such a font being available. I netsearched for "koron sori font", and worked through all entries and found no font. So I figure they must be drawn. However, the link http://www.chrysalis-foundation.org/Al-Farabi's_'Uds.htm contained the glyphs in picture format: <><> Hans ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \crescTextCresc... 2.10 vs 2.12
Ahh, I see Carl's note didn't make it to the list. I'll forward it. Trevor - Original Message - From: "Graham Percival" To: "Trevor Daniels" Cc: ; "Carl D. Sorensen" Sent: Sunday, February 01, 2009 12:06 PM Subject: Re: \crescTextCresc... 2.10 vs 2.12 On Sun, Feb 01, 2009 at 08:35:47AM -, Trevor Daniels wrote: Graham Percival wrote Sunday, February 01, 2009 3:27 AM Rather, \cresc and \dim should finally be removed. See the message in ly/spanner-init.ly No. There was a long discussion on -user at the end of October last year Ok, I stand corrected. But the change was not completed. As often happens, no one took up the baton and it was forgotten. Now we have frogs it can be easily done. Carl has already set out a very sensible programme of work. Do you mean "Carl is organizing the Frogs", or do you mean "Carl knows exactly what needs to be done for this issue, and has already assigned and explained the work?" Because unless you mean the latter, there's a very good chance that this will get forgotten again. Unless it's already in the Issue tracker and I just missed finding it. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Persian accidentals
On 1 Feb 2009, at 13:07, Graham Breed wrote: You can use any glyph, or string of glyphs, you have in a font. I haven't seen a mention here of such a font being available. Didn't you work with MicroABC? A quick search gave this page http://anamnese.online.fr/site2/index.php?page=abc_perse (Click on the "English version" button to see the text.) I think that koron and sori may not be in Unicode, which LilyPond uses for fonts. So some special implementation might be needed. Hans ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Persian accidentals
2009/2/1 Hans Aberg : > > On 30 Jan 2009, at 03:34, Kees van den Doel wrote: > >> Is there any way to print the koron (60cents flat) and sori (40 cent >> sharp)? > > Check with Graham Breed - it might be possible now. You can use any glyph, or string of glyphs, you have in a font. I haven't seen a mention here of such a font being available. Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \crescTextCresc... 2.10 vs 2.12
On Sun, Feb 01, 2009 at 08:35:47AM -, Trevor Daniels wrote: > > Graham Percival wrote Sunday, February 01, 2009 3:27 AM > >> Rather, \cresc and \dim should finally be removed. See the >> message in ly/spanner-init.ly > > No. There was a long discussion on -user at the end > of October last year Ok, I stand corrected. > But the change was not completed. As often happens, no > one took up the baton and it was forgotten. Now we have > frogs it can be easily done. Carl has already set out > a very sensible programme of work. Do you mean "Carl is organizing the Frogs", or do you mean "Carl knows exactly what needs to be done for this issue, and has already assigned and explained the work?" Because unless you mean the latter, there's a very good chance that this will get forgotten again. Unless it's already in the Issue tracker and I just missed finding it. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Persian accidentals
On 30 Jan 2009, at 03:34, Kees van den Doel wrote: Is there any way to print the koron (60cents flat) and sori (40 cent sharp)? Check with Graham Breed - it might be possible now. I've defined these pitch alterations by modifying makam.ly but they should really be printed according to the Persian notation. I am curious where you got those figures. The values in Hormoz Farhat's thesis suggest one should use E53 with koron lowering 3 commas and sori raising 2 commas (E53 tonesteps). He describes the Persian pitch system using a minor (resp. major) second m (resp. M) plus a neutral second n. In E53 they are m = 4, M = 9, n = 6. Then I wanted to retune m, M into E12. There is a suggestion that n can be set to the rational interval 27/25, which is close to Farhat's values, and also sound good in Scala. If I fix n at that value, a close approximation is E36, or if you so like, in E12 let (koron resp. sori) lower 2/3 (resp. raise 1/3) of an E12 tonestep. Now, this is very close to your suggestion, making me curious about the motivation for those setting those. koron = upside down flat, with a triangular body like |> sori = like sharp but with the two horizontal lines angled to form a '>' sign. In Scala, and some other places when only ASCII is available, one uses koron p sori > Any suggestions appreciated, I'm prepared to do some hacking if required. I think this should now be possible. Hans ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staff collision because of a postscript line
Stefan
You could invert the order of the pedal
indication and dynamics with 'outside-staff-priority
and then move the dynamics grobs with 'extra-offset
so the beat indicator falls in the gap.
E.g.
\once \override Staff.SustainPedalLineSpanner #'outside-staff-priority =
#200
\once \override DynamicText #'extra-offset = #'(-1.5 . 0)
etc
but it's a bit messy. I don't think there is any
automatic way of avoiding collisions with postscript
objects.
Trevor
- Original Message -
From: "Stefan Thomas"
To: "lilypond-user"
Sent: Sunday, February 01, 2009 8:33 AM
Subject: staff collision because of a postscript line
Dear Lilypond-users,
in the below quoted snippet I get a collision between the two staves.
Is there a possibilitie to avoid automatically this collision, without
increasing the distace between the two staves generally?
Here is the snippet:
\version "2.12.0"
%%some definitions
onBeat = \markup { \postscript #"
0.1 setlinewidth
0.5 4 moveto
0.5 0 lineto
0.2 0.6 lineto
0.5 0 moveto
0.8 0.6 lineto
0.5 4 moveto
3.5 4 lineto
stroke
"}
standardped = { \override Staff.PianoPedalBracket #'style =
#'bracket \set Staff.pedalSustainStyle = #'mixed }
smaller = {\set fontSize = #-3 \override DynamicText #'font-size =
#+3 \override TextSpanner
#'font-size = #+3 } %noten so schnell wie moeglich; Dynamik und
TextSpanner normale Groesse
% das habe ich bisher noch nicht benutzt
normal = {\unset fontSize \revert DynamicText #'font-size
\revert TextSpanner #'font-size } % Noten und Dynamik normale Groesse!
% the music itself
%%
UpStaff = \new Staff \relative c {
\clef bass \scaleDurations #'(32 . 35) { \standardped
\smaller f32[\f\>^\onBeat \sustainOn g e] \normal dis1
\sustainOff \p } }
DownStaff = \new Staff \relative c { \clef bass
\scaleDurations #'(32 . 36) { \standardped
\smaller a32 [ \sustainOn \f \>^\onBeat c cis d ] \normal es1
\sustainOff } }
\score { << \UpStaff
\DownStaff >> }
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staff collision because of a postscript line
Dear Robin, excellent! It works now! What does this \with-dimensions-command exactly do? Is it explained in the manual? 2009/2/1 Robin Bannister : > Stefan Thomas wrote: >> >> Is there a possibilitie to avoid automatically this collision > > The eyeglasses example in NR B.8.3. uses the \with-dimensions command for > this. > \with-dimensions #'(0 . 3.5) #'(0 . 4) for your case? > > Cheers, > Robin > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staff collision because of a postscript line
Stefan Thomas wrote: Is there a possibilitie to avoid automatically this collision The eyeglasses example in NR B.8.3. uses the \with-dimensions command for this. \with-dimensions #'(0 . 3.5) #'(0 . 4) for your case? Cheers, Robin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \crescTextCresc... 2.10 vs 2.12
Graham Percival wrote Sunday, February 01, 2009 3:27 AM On Sat, Jan 31, 2009 at 08:11:11PM -, Trevor Daniels wrote: The docs for 2.12 don't mention \cresc or \dim. This could (should) be fixed now. Rather, \cresc and \dim should finally be removed. See the message in ly/spanner-init.ly No. There was a long discussion on -user at the end of October last year (What to do when \> and \< produce text) during which I, Reinhold, Till, Risto, Mats and Valentin all supported the retention of \cresc and \dim. There was no dissention then. None. At all. The need comes from choral music which often mixes text cresc with no extender (\cresc) and hairpins (\<). Turning the text style on and off with \crescTextCresc and \crescHairpin is far too laborious. But the change was not completed. As often happens, no one took up the baton and it was forgotten. Now we have frogs it can be easily done. Carl has already set out a very sensible programme of work. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
staff collision because of a postscript line
Dear Lilypond-users,
in the below quoted snippet I get a collision between the two staves.
Is there a possibilitie to avoid automatically this collision, without
increasing the distace between the two staves generally?
Here is the snippet:
\version "2.12.0"
%%some definitions
onBeat = \markup { \postscript #"
0.1 setlinewidth
0.5 4 moveto
0.5 0 lineto
0.2 0.6 lineto
0.5 0 moveto
0.8 0.6 lineto
0.5 4 moveto
3.5 4 lineto
stroke
"}
standardped = { \override Staff.PianoPedalBracket #'style =
#'bracket \set Staff.pedalSustainStyle = #'mixed }
smaller = {\set fontSize = #-3 \override DynamicText #'font-size =
#+3 \override TextSpanner
#'font-size = #+3 } %noten so schnell wie moeglich; Dynamik und
TextSpanner normale Groesse
% das habe ich bisher noch nicht benutzt
normal = {\unset fontSize \revert DynamicText #'font-size
\revert TextSpanner #'font-size } % Noten und Dynamik normale Groesse!
% the music itself
%%
UpStaff = \new Staff \relative c {
\clef bass \scaleDurations #'(32 . 35) { \standardped
\smaller f32[\f\>^\onBeat \sustainOn g e] \normal dis1
\sustainOff \p } }
DownStaff = \new Staff \relative c { \clef bass
\scaleDurations #'(32 . 36) { \standardped
\smaller a32 [ \sustainOn \f \>^\onBeat c cis d ] \normal es1
\sustainOff } }
\score { << \UpStaff
\DownStaff >> }
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
