Re: key signatures and partcombine
Hi Kieren,
Many thanks, ah... i copied music from another file, where time, key, cleff,
etc... music are put into the staff and put together in score.
Best,
Eby.
--- On Fri, 3/26/10, Kieren MacMillan kieren_macmil...@sympatico.ca wrote:
From: Kieren MacMillan kieren_macmil...@sympatico.ca
Subject: Re: key signatures and partcombine
To: Eby Mani eby...@yahoo.com
Cc: lilypond-user@gnu.org
Date: Friday, March 26, 2010, 2:00 PM
Hi Eby,
What should i do to show key signatures when using
\partcombine ? you can see it doesn't render any key
signature when \partcombine is used.
Yes it does -- you haven't put the \global (with the key
signature) into your partcombine-d staff:
\new Staff \with { printPartCombineTexts = ##f
}{ \partcombine \OrganRHOne \OrganRHTwo }
;)
Hope this helps!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
repeatTie question
Is it possible to specify minimum length for it so the repeatTie appears to
connect the previous note on another voice.
e.g.
vOne = { ees4. ees8 c'4 aes }
vTwo = { d4 c ees2 \repeatTie }
I've tried vTwo = { d4 c4 \hideNote ees~ \unHideNotes ees2 }, but this
will hide both c4 and ees, leaving the tie visible. And ees2-\tweak
#'minimum-length #10 \repeatTie doesn't have any effect. Any suggestions ?.
Thanks.
Eby
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Force clef visibility
Siska Ádám-3 wrote: Hello List, how can I force a clef appearing even in case the clef doesn't change actually? I'm thinking about something like this: \clef treble c' \bar | s \clef treble d' How can I force the drawing of the second clef? 1.1.3 in the NR -- Clef -- Selected Snippets -- View this message in context: http://old.nabble.com/Force-clef-visibility-tp28049912p28050878.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: all must do a new clone - new git repository with fixed history
The git repository at savannah has been updated, everyone should do a fresh clone. I can only use the http server because I cannot get outside my firewall using the git protocol. I was using http://git.sv.gnu.org/r/lilypond.git before. I have tried http://git.savannah.gnu.org/r/lilypond.git and it seems to work. Is it the right address to use? Frédérci ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: all must do a new clone - new git repository with fixed history
Op zaterdag 27-03-2010 om 09:34 uur [tijdzone +0100], schreef Frédéric Bron: The git repository at savannah has been updated, everyone should do a fresh clone. I can only use the http server because I cannot get outside my firewall using the git protocol. I was using http://git.sv.gnu.org/r/lilypond.git before. I have tried http://git.savannah.gnu.org/r/lilypond.git and it seems to work. Is it the right address to use? According to http://git.savannah.gnu.org/gitweb/?p=lilypond.git it is. Jan. -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond - The music typesetter Avatar®: http://AvatarAcademy.nl| http://lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Force clef visibility
Hello List, how can I force a clef appearing even in case the clef doesn't change actually? I'm thinking about something like this: \clef treble c' \bar | s \clef treble d' How can I force the drawing of the second clef? 1.1.3 in the NR -- Clef -- Selected Snippets Hi, maybe I'm missing something obvious. I read the manual at least three times, but I still don't find a way to force a clef to appear in case it doesn't change. Can you post a short example? Thanks, Adam ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staff-space doesn't seem to work as documented
The user error was actually in the quoting in my email: I'd tried both #'1.5
and #1.5 and neither had worked. Thanks to those who pointed out the
requirement for white space between the font size specification and the
curly brace: #'1.5 } and #1.5 } both work. #1.5} doesn't work, and I'd not
picked this up from the documentation since I tend to put commands of this
sort on a single line, which the documentation doesn't.
--
Phil Holmes
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: Phil Holmes em...@philholmes.net
Cc: LilyPond User Group lilypond-user@gnu.org
Sent: Friday, March 26, 2010 6:42 PM
Subject: Re: staff-space doesn't seem to work as documented
There's a difference between
#'1.5
and
#1.5}
This is a user error, not a documentation problem.
- Graham
On Fri, Mar 26, 2010 at 4:22 PM, Phil Holmes em...@philholmes.net wrote:
In the PDF documentation for 2.12.3 and the online documentation for
2.13.16
it gives the syntax for reducing staff spacing as:
\override StaffSymbol #'staff-space = #1.5
If I use this syntax, I get an error:
error: syntax error, unexpected '{'
\new Staff \with {\override StaffSymbol #'staff-space = #'1.5}
{ c'' c'' c''
c'' }
If I use a syntax with parentheses (guessed by trial and error):
\override StaffSymbol #'staff-space = #'( . 1.5)
I compiles and runs successfully.
Code snippets are available if required.
Is this a bug in the documentation?
--
Phil Holmes
___
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
glissando between two notes not joint
Need a glissando between two notes not joint ? add in lsr : http://lsr.dsi.unimi.it/LSR/Item?u=1id=662 voili -- Martial ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Force clef visibility
Try this: \clef treble c' \bar | s \set Staff.forceClef = ##t \clef treble d' -- Phil Holmes - Original Message - From: Siska Ádám szad...@gmail.com To: lilypond-user@gnu.org Sent: Saturday, March 27, 2010 10:26 AM Subject: Re: Force clef visibility Hello List, how can I force a clef appearing even in case the clef doesn't change actually? I'm thinking about something like this: \clef treble c' \bar | s \clef treble d' How can I force the drawing of the second clef? 1.1.3 in the NR -- Clef -- Selected Snippets Hi, maybe I'm missing something obvious. I read the manual at least three times, but I still don't find a way to force a clef to appear in case it doesn't change. Can you post a short example? Thanks, Adam ___ 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-space doesn't seem to work as documented
Phil Holmes wrote Saturday, March 27, 2010 10:37 AM The user error was actually in the quoting in my email: I'd tried both #'1.5 and #1.5 and neither had worked. Thanks to those who pointed out the requirement for white space between the font size specification and the curly brace: #'1.5 } and #1.5 } both work. #1.5} doesn't work, and I'd not picked this up from the documentation since I tend to put commands of this sort on a single line, which the documentation doesn't. There's a big warning about this right at the beginning of the Learning Manual. Section 1.1.1 Entering input says ... braces should also be surrounded by a space unless they are at the beginning or end of a line to avoid ambiguities. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staff-space doesn't seem to work as documented
Thanks. Must sit down and read it soon, rather than dipping in to try to find what I need. Won't make that mistake again, anyway! -- Phil Holmes - Original Message - From: Trevor Daniels t.dani...@treda.co.uk To: Phil Holmes em...@philholmes.net; Graham Percival gra...@percival-music.ca Cc: LilyPond User Group lilypond-user@gnu.org Sent: Saturday, March 27, 2010 11:27 AM Subject: Re: staff-space doesn't seem to work as documented Phil Holmes wrote Saturday, March 27, 2010 10:37 AM The user error was actually in the quoting in my email: I'd tried both #'1.5 and #1.5 and neither had worked. Thanks to those who pointed out the requirement for white space between the font size specification and the curly brace: #'1.5 } and #1.5 } both work. #1.5} doesn't work, and I'd not picked this up from the documentation since I tend to put commands of this sort on a single line, which the documentation doesn't. There's a big warning about this right at the beginning of the Learning Manual. Section 1.1.1 Entering input says ... braces should also be surrounded by a space unless they are at the beginning or end of a line to avoid ambiguities. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Chords
On 3/26/10 4:41 PM, David Stocker dstoc...@notesettersinc.com wrote: I have some questions/concerns about display of chords in LilyPond: * Is there a way to make LilyPond center the entire chord symbol (root and suffix) on its rhythmic axis? Right now, LilyPond is only centering the root on the rhythmic axis, with the suffix extending on the right. As far as I know, there is not. I have noticed this problem, and hope to work on it sometime in the near future. * Does someone on the list have a set of modern custom chord definitions? A very large list of chord exceptions that can be effectively used has been posted on the list. I'd try searching the archives for exceptions. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: all must do a new clone - new git repository with fixed history
According to http://git.savannah.gnu.org/gitweb/?p=lilypond.git it is. I am a bit lost: should it be git.sv or git.savannah? Maybe this does not matter. Frédéric ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Chords
David Stocker wrote: center the entire chord symbol (root and suffix) on its rhythmic axis? #(define (centerCN grob) (ly:stencil-aligned-to (ly:text-interface::print grob) X CENTER )) and then apply as \override ChordNames.ChordName #'stencil = #centerCN Cheers, Robin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: all must do a new clone - new git repository with fixed history
2010/3/27 Frédéric Bron frederic.b...@m4x.org: According to http://git.savannah.gnu.org/gitweb/?p=lilypond.git it is. I am a bit lost: should it be git.sv or git.savannah? Maybe this does not matter. Type in your browser sv.gnu.org and you'll be redirected to savannah.gnu.org -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Converting from a really old version - how far can I jump?
I've been chided before about still using 2.6.5, and I still find that I learn more and more, and feel satisfied with what I do with it...but it nags me I'm so far behind the discussion on this list. My biggest con against upgrading is I don't have the time to upgrade 30 or more pieces (not to mention test/templates). The biggest pro is that I'm having to do this already as I learn how to do better with 2.6.5 I am starting to revisit old files...and reduce the size of my final output PDF from 14 pages to 6...it takes time to rework the old files. Possibly the same time it would take to get used to a new version and revise the old files? So - is it possible to run the old (2.6.5) and the newest stable branch (a 2.12 version I think?) simultaneously on a WinXP box? Or do I have to try and use my laptop (Win7 machine) for the new (or old versions), and just struggle using both machines (I really don't like to use my laptop...)? I imagine that a lot of my music notation (the actual notes and durations and rests and beamings) can be copied over to a newer version, but my techniques in using score and contexts might need updating? Well, I'm actually facing that now with 2.6.5 - as I had been warned (year or so ago?) by Mats - as it's hard to get/find advice, and seeing that 2.10 had the issue simplified...and I wonder, do I want to chase down the code fix for how I'm writing now in 2.6.5 or do I try to make the big leap? And if the answer is to go stepwise through 2.8 - 2.10 - then 2.12 then I have to say sorry boys, I'm staying in the paleozoic! I just don't have the time to do that... I would appreciate any advice - suggestions. Thanks! _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. http://clk.atdmt.com/GBL/go/210850552/direct/01/___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Converting from a really old version - how far can I jump?
You might want to try reading the documentation about upgrading from older versions. In 2.13, this is in the Usage manual. Cheers, - Graham On Sat, Mar 27, 2010 at 10:25 PM, Ed Ardzinski ed_ardzin...@hotmail.com wrote: I've been chided before about still using 2.6.5, and I still find that I learn more and more, and feel satisfied with what I do with it...but it nags me I'm so far behind the discussion on this list. My biggest con against upgrading is I don't have the time to upgrade 30 or more pieces (not to mention test/templates). The biggest pro is that I'm having to do this already as I learn how to do better with 2.6.5 I am starting to revisit old files...and reduce the size of my final output PDF from 14 pages to 6...it takes time to rework the old files. Possibly the same time it would take to get used to a new version and revise the old files? So - is it possible to run the old (2.6.5) and the newest stable branch (a 2.12 version I think?) simultaneously on a WinXP box? Or do I have to try and use my laptop (Win7 machine) for the new (or old versions), and just struggle using both machines (I really don't like to use my laptop...)? I imagine that a lot of my music notation (the actual notes and durations and rests and beamings) can be copied over to a newer version, but my techniques in using score and contexts might need updating? Well, I'm actually facing that now with 2.6.5 - as I had been warned (year or so ago?) by Mats - as it's hard to get/find advice, and seeing that 2.10 had the issue simplified...and I wonder, do I want to chase down the code fix for how I'm writing now in 2.6.5 or do I try to make the big leap? And if the answer is to go stepwise through 2.8 - 2.10 - then 2.12 then I have to say sorry boys, I'm staying in the paleozoic! I just don't have the time to do that... I would appreciate any advice - suggestions. Thanks! Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up now. ___ 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
hairpins in above ossia staff collide with main staff
Hi folks, I created a 21 page score with only one staff but at some place, an ossia staff appears above the main staff. Everything was fine up to the point where I needed to move the bar number engraver from the score context to the staff context because I wanted the bar numbers to be below text spanners. After doing this, hairpins of the ossia staff started to collide with the below staff. I noticed that if I do not use \override VerticalAlignment #'max-stretch = #ly:align-interface::calc-max-stretch no collision arises. Also it works fine if I use \override VerticalAxisGroup #'minimum-Y-extent = #'(-5 . 5) in the main staff context but with (-4 . 4) it is awfull. Why such a yield effect? Does anyone understand anything? I tried to make the example minimum so I put some \break and \noBreak to mimic the original 21 page score. Frédéric hairpin-staff-collision.ly Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: Frescobaldi 1.0.0 released
Two Frescobaldi editing problems I haven't been able to solve, and which I see on all three versions I've tried (1.0.0, 1.0.2, and 1.1.0): 1. Regardless of whether I check or uncheck the editing option Insert spaces instead of tabulators, I always get spaces and not tabs in my source file, whether from auto-indentation or from explicitly hitting the tab key. 2. Regardless of the value I set for indentation width, I always get a width of two characters. I'm running on Ubuntu 9.10 x86. I'm using Gnome desktop, so have minimal KDE to support Frescobaldi installed. I haven't tried it on a Kububtu installation to see if the problem is the same there. Nick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
