|
From: | Ed Ardzinski |
Subject: | RE: Odd Stem Lengths |
Date: | Sat, 16 Apr 2011 12:29:59 +0000 |
The issue I have with convenrting is the massive projecy involved getting 50 or more pieces up to speed...but I suppose it's probably time. I also have to update the editor I wrote, but that really should not be too hard. I usually write in a pretty simple coding style, so maybe I've been afraid of something that's not too big? The definitions in the variables are pretty simple: hpianoII = { \times 4/5 {<g' g''>4 <e' e''> <cis' cis''> <c' c''> <b b'>} } hpianoIIb = { \times 4/5 {<g' g''>8 [<e' e''>] ~ <e' e''>4 <cis' cis''> <c' c''> <b b'>} } hpianoIIa = { \times 4/5 {<e'' e'''>4 <gis' gis''> <fis' fis''> <f' f''> <e' e''>} } Thanks! > From: address@hidden > Date: Sat, 16 Apr 2011 10:51:14 +0200 > Subject: Re: Odd Stem Lengths > To: address@hidden > CC: address@hidden > > On 16 April 2011 00:23, Ed Ardzinski <address@hidden> wrote: > > > > I have a sections with quints in my piece, and in 2 different blocks of the > > piece the PDF output varies. > > > > I've attached pictures of the output - the same exact code produces each > > part...same variable and transpositions. I am in an old version (2.6.5) but > > I'm never run into this without having chord names creating spacing. This > > is a fairly simple file, with just a RH and LH part for a piano, but not > > using a piano staff. The first instance happens in the II part, it has the > > bad stem lengths. THe second instance is in the II part, and outputs > > looking good. The > > > > \transpose c c' \hpianoIIb > > \hpianoIIb > > > > part is in other parts of the piece and outputs fine. Any ideas would be > > helpful. Thanks! > > Could you send a *compilable* code? > > We do not have the definitions of all your variables: "hpianoI", > "hpianoII", "hpianoIVb", etc. > > Also you are using a very old version of LilyPond. > Current stable version is 2.12.3 and the new stable 2.14 is about to > be released (in a few weeks). > > Please upgrade to 2.12.3 at least, the result should be really better > (many bugfixes compared to 2.6.5) and people could help you better. > Syntax changes should not be a problem if you use "basic" commands. > And you can upgrade your files very easily using convert-ly . > > Please note that in current development version (2.13.59, aka pre-2.14) > the "beam collision stuff" has been improved a lot, even compared to > 2.12! > > Cheers, > Xavier > > -- > Xavier Scheuer <address@hidden> |
[Prev in Thread] | Current Thread | [Next in Thread] |