A reminder maybe?
I hope I didn't miss this, but has the automatic further shortening of downward stems on very low notes and of upward stems on very high notes been implemented? (There was discussion of this back in the Cretaceous.) Regards, daveA -- For beginners: very easy guitar music, solos, duets, exercises. Early intermediate guitar solos. One best scale set for all guitarists. http://www.openguitar.com/scalescomparison.html ::: plus new and better chord and arpeggio exercises. http://www.openguitar.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Major version: LilyPond 2.14.0 released!
On Fri, Apr 02, 2010 at 01:57:07AM +0200, Reinhold Kainhofer wrote: > Am Freitag, 2. April 2010 01:11:29 schrieb Graham Percival: > > On Thu, Apr 01, 2010 at 04:15:18PM +0200, Nils Gey wrote: > > > It seems the real joke is "Release Early, Release Often" in the > > > same sentence as lilypond. > > > > In the past 5 months, we've had an > > average of one release every 2 weeks. > > I suppose what Nils meant was not that we have 2.13.x *unstable* *developer* > releases every fortnight, but rather that we have stable releases about every > two years (of course, not counting the minor releases, which mainly backport > fixes to serious problems)... "Release early, release often" is specifically aimed at developers -- get the code out there, let people play around with it, let them help find+fix bugs. That phrase as **nothing** to do with stable releases for normal users. If people want a stable release, they can take a look at the 15 critical issues. Once those are down, we can announce a beta and find approximately 5 more critical issues. Then we'll have a second beta, and probably discover 2 more issues. Then we'll have a third beta, find no more critical issues within two weeks, and then release 2.14.0. But this whole process doesn't get off the ground until the current crop of release-critical issues are fixed. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Major version: LilyPond 2.14.0 released!
Am Freitag, 2. April 2010 01:11:29 schrieb Graham Percival: > On Thu, Apr 01, 2010 at 04:15:18PM +0200, Nils Gey wrote: > > It seems the real joke is "Release Early, Release Often" in the > > same sentence as lilypond. > > In the past 5 months, we've had an > average of one release every 2 weeks. Are you seriously > complaining that we should have had more releases than that? I suppose what Nils meant was not that we have 2.13.x *unstable* *developer* releases every fortnight, but rather that we have stable releases about every two years (of course, not counting the minor releases, which mainly backport fixes to serious problems)... 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 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Major version: LilyPond 2.14.0 released!
On Thu, Apr 01, 2010 at 04:15:18PM +0200, Nils Gey wrote: > It seems the real joke is "Release Early, Release Often" in the > same sentence as lilypond. Yeah, well, screw you too. In the past 5 months, we've had an average of one release every 2 weeks. Are you seriously complaining that we should have had more releases than that? If so, what are you willing to do in order to make the extra releases make sense? Are you offering to fix a bug every 2 days, or add new features at a similar rate? That would justify having a release every week. There's no point making a new release if we've only fixed a few typos in the docs. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pedal markings at the end of a piece of music
This looks like a bug to me. My minimal example:
\version "2.13.16"
{
\set Staff.pedalSustainStyle = #'text
c''1\sustainOn
}
If the pedalSustainStyle is set to #'mixed or #'bracket then the
bracket indicates the sustain up at the end of the piece. With #'text
style there is no sustain up mark.
Andrew
On Thu, Apr 1, 2010 at 8:58 AM, Phil Holmes wrote:
> I am trying to recreate a piece of music as shown in the attached .png. As
> you see, it has a pedal down marking on the dotted minims in the left hand.
> The pedal stays down as the arpeggiated dotted crochets are played in the
> right hand, and then comes off right at the end of the music. It's easy to
> notate the pedal down mark, but is there any way to notate pedal up? The
> notation reference says "Pedalling to the final bar line is indicated by
> omitting the final pedal up command" which presumably works for the bracket
> style of pedal marks, but does not seem to place a final pedal up mark when
> using the text style.
>
> Any advice appreciated.
>
> --
> 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
Pedal markings at the end of a piece of music
I am trying to recreate a piece of music as shown in the attached .png. As you see, it has a pedal down marking on the dotted minims in the left hand. The pedal stays down as the arpeggiated dotted crochets are played in the right hand, and then comes off right at the end of the music. It's easy to notate the pedal down mark, but is there any way to notate pedal up? The notation reference says "Pedalling to the final bar line is indicated by omitting the final pedal up command" which presumably works for the bracket style of pedal marks, but does not seem to place a final pedal up mark when using the text style. Any advice appreciated. -- Phil Holmes <>___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book with LilyPond, community of professionals
Rodolfo, Rodolfo Zitellini wrote: Apart from layout and co. I am also curious if anyone has experience in making printer proofs and printing lilypond output with high res offset printers, ad this will likley be the publisher's output. Having worked for an offset-litho printers for many, many years the PDFs that LilyPond outputs should be enough. Most printers will take PDFs and use their own layout software to position etc. If you are intending on using spot colour then it maybe simpler to just give them black and white output and let them sort that out. Always try to provide some kind of 'mock up' (i.e. what you want the finished product to look like with any specific margin or colour instruction written on) so that they can make sure their pagination is correct before printing and they have a good idea of what the finished project needs to be, oh, and always ask for proofs to sign off before you start printing. ;) James ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book with LilyPond, community of professionals
On Wed, Mar 31, 2010 at 7:41 PM, Aaron Dalton wrote:
> My master's thesis is a modern edition of a book of 16th-century madrigals.
> It is comprised of two parts: the first is all the discursive stuff, and
> then the second is the text, scores, and apparatus. I simply have a single
> .lytex file with entries like the following for each madrigal:
>
> \clearpage
> \addcontentsline{toc}{subsection}{1. Amor, che sol dei cor leggiadri ha
> cura}
> \label{madrigal01}
> \lilypondfile{/home/aaron/svn/scores/out/01-3-01.ly}
>
> In my case all the scores are in one place, so I simply \input this file
> wherever I wish it to appear in the larger document. As you can see, you
> can quite simply put a few madrigals in, then add some text, then do some
> more scores, and back again. This is producing excellent results for me.
>
Thanks to all for the tips. I did not think of using lilypond-book for
a complete score sice I used it only for snippets in the text. I will
try it right away!
Apart from layout and co. I am also curious if anyone has experience
in making printer proofs and printing lilypond output with high res
offset printers, ad this will likley be the publisher's output.
Cheers,
Rodolfo
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Publishing a book with lilypond
On Wed, Mar 31, 2010 at 9:57 PM, Karl Hammar wrote: > Rodolfo: > ... >> So I am wondering: has anyone experience in publishing his works >> trough a professional publisher? > > I'm my own publisher. > I think this simplifies thing a bit, since you don't have to adapt to someone else's (still unknown..) workflow :) > I like a "little smaller than a4" format for choirbooks. I grabbed the > dimensions from a Bärenreiter choirbook. I hope the final print will be a little bigger than a4, since I think it is better for keyboard music. Ciao, Rodolfo ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book with LilyPond, community of professionals
On 01/04/2010 2:58 AM, Dmytro O. Redchuk wrote:
> У ср, 2010-03-31 у 13:41 -0400, Aaron Dalton пише:
>> \clearpage
>> \addcontentsline{toc}{subsection}{1. Amor, che sol dei cor leggiadri ha cura}
>> \label{madrigal01}
>> \lilypondfile{/home/aaron/svn/scores/out/01-3-01.ly}
>>
>> In my case all the scores are in one place, so I simply \input this file
>> wherever I wish it to appear in the larger document.
> By the way, since all the scores are in one place, you can do this like
> this:
>
> % first, include files by filenames, no pathes:
> \lilypondfile{01-3-01.ly}
>
> and then, i believe, process like this:
> $ lilypond-book --process='lilypond -I/home/aaron/svn/scores/out/' book.lytex
>
> This will allow relocate easily .)
>
> If needed.
>
Ooo, I never noticed lilypond-book had an -I switch! Thanks!
Aaron
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: glissando between two notes not joint
Hi Eluze There's a fair bit on fiddling with glissando lines in Section 5.4.6 of the Notation Reference under Using the line spanner interface. If you've not seen this maybe it will help. Trevor - Original Message - From: "-Eluze" To: Sent: Thursday, April 01, 2010 1:45 PM Subject: Re: glissando between two notes not joint Martial-3 wrote: Need a glissando between two notes not joint ? add in lsr : http://lsr.dsi.unimi.it/LSR/Item?u=1&id=662 good idea! but after tweaking around for hours to get the glissando not to clash with the notes - which of the parameters allows to shorten the glissando line on the left/right - or to shift the line up to make the glissando on the fingering or string numbers i started looking for another solution; why should not lilypond make that work!? lilypond can: (see attached files) http://old.nabble.com/file/p28107783/gliss3.ly glissando between nonadjacent notes ly http://old.nabble.com/file/p28107783/gliss3.png glissando between nonadjacent notes png -- View this message in context: http://old.nabble.com/glissando-between-two-notes-not-joint-tp28051494p28107783.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 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: glissando between two notes not joint
Martial-3 wrote: > > Need a glissando between two notes not joint ? > > add in lsr : http://lsr.dsi.unimi.it/LSR/Item?u=1&id=662 > > good idea! but after tweaking around for hours to get the glissando not to clash with the notes - which of the parameters allows to shorten the glissando line on the left/right - or to shift the line up to make the glissando on the fingering or string numbers i started looking for another solution; why should not lilypond make that work!? lilypond can: (see attached files) http://old.nabble.com/file/p28107783/gliss3.ly glissando between nonadjacent notes ly http://old.nabble.com/file/p28107783/gliss3.png glissando between nonadjacent notes png -- View this message in context: http://old.nabble.com/glissando-between-two-notes-not-joint-tp28051494p28107783.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: Major version: LilyPond 2.14.0 released!
:-D Graham Percival-3 wrote: > > GLASGOW, Scotland -- April 1, 2010 -- The LilyPond development > team is proud to announce LilyPond 2.14, the latest stable release > of our award-winning music engraver. "Music notation for > everyone" has never looked better! > http://lilypond.org > [...] > -- View this message in context: http://old.nabble.com/Major-version%3A-LilyPond-2.14.0-released%21-tp28105610p28107780.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: Major version: LilyPond 2.14.0 released!
Am Donnerstag, 1. April 2010 13:03:43 schrieb Jonathan Kulp: > Awesome! Props to all the contributors! > > But...I don't see 2.14 on the download page. Is this an April Fools joke? If you look at the list of incredibly important features (eyeglasses markup, using colored letters in tablatures (huh?!?!?), and some internal function call details), that should be pretty clear. Add to this the urge to use a version with regressions on production systems, plus the ascii-art list of contributors, then there can be no doubt that this is just a April Fools joke... 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 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Major version: LilyPond 2.14.0 released!
On Thursday 01 Apr 2010 08:50:36 Graham Percival wrote: > * in tablature, fets can be indicated with colored letters > instead of numbers. I think working in an EE dept has finally got to you Graham! Is there similar support for bipolar transistors? :) Very well done on the release! Looking forward to using it. Nick/. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book with LilyPond, community of professionals
У ср, 2010-03-31 у 13:41 -0400, Aaron Dalton пише:
> \clearpage
> \addcontentsline{toc}{subsection}{1. Amor, che sol dei cor leggiadri ha cura}
> \label{madrigal01}
> \lilypondfile{/home/aaron/svn/scores/out/01-3-01.ly}
>
> In my case all the scores are in one place, so I simply \input this file
> wherever I wish it to appear in the larger document.
By the way, since all the scores are in one place, you can do this like
this:
% first, include files by filenames, no pathes:
\lilypondfile{01-3-01.ly}
and then, i believe, process like this:
$ lilypond-book --process='lilypond -I/home/aaron/svn/scores/out/' book.lytex
This will allow relocate easily .)
If needed.
>
> HTH!
> Aaron
--
Dmytro O. Redchuk
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Major version: LilyPond 2.14.0 released!
GLASGOW, Scotland -- April 1, 2010 -- The LilyPond development team is proud to announce LilyPond 2.14, the latest stable release of our award-winning music engraver. "Music notation for everyone" has never looked better! http://lilypond.org Following the open-source motto of "release early, release often", we are making 2.14 available now. There are still a few regression bugs compared to 2.12, but we urge everybody to download 2.14.0 from the lilypond website when it becomes available and use it in their production systems. Let us know if anything doesn't work; we love getting feedback! We have introduced a new "bug voting" system on our website to allow us to better direct programmer effort: http://lilypond.org/website/bug-reports.html Other major new features include: * eyeglass markup, to remind musicians to watch the conductor at critical moments. * in tablature, fets can be indicated with colored letters instead of numbers. * The Unicode Bidirectional Algorithm is now fully supported for single-line markup due to enhanced integration with Pango, and we now use FT_Error in the prototype for freetype_error_string(). The full list of new features is online here: http://lilypond.org/doc/v2.13/Documentation/changes/index.html Having music engraving! Patrick McCarty - SVG guru, text handler Nicolas Sceaux - Schemer extraordinaire Reinhold Kainhofer - musicxml2ly bloke Werner Lemberg - Fonts, bugz squasher Jan Nieuwenhuizen - Core development Han-Wen Nienhuys - Core development John Mandereau - Translation swain Trevor Daniels - Asst. doc editor Jonathan Kulp - Asst. doc editor Mark Polesky - Code cleanup-er Mats Bengtsson - Support guru Valentin Villenave - Web 2.0 Carl Sorensen - Frog master Francisco Vila - ES writer Joe Neeman - Spacing guru Dmytro O. Redchuk - Bugs James Lowe - Doc gopher Colin Campbell - Ditto Marc Hohl - Bug nuker Graham Percival - me -- This email is best viewed with a fixed-width font in a screen size of 80x25 characters. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Grace notes and Lyrics
On Fri, 19 Mar 2010 20:05:18 +0200, Mika Kuuskankare wrote: > Hi, > > Can't you put Lyrics (a syllable) on a grace note? Hi, I had the same problem and started to work on a patch. You might want to have a look at http://www.mail-archive.com/lilypond-de...@gnu.org/msg28324.html if you are willing to work with the lilypond sources. The patch is not yet finished but it works already for my case. It would surely be great if you could provide some test case(s). Cheers, Richard ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
