Re: lilypond mensural notation
Hello, 2011/3/10 Carl Sorensen c_soren...@byu.edu If you could get a closer shot of the desired clefs, I'd be happy to have a discussion with you about how much you're willing to pay for the clefs. Here it is: http://gregoriana.sk/gg/wp-content/uploads/c-clef1.png http://gregoriana.sk/gg/wp-content/uploads/c-clef2.png http://gregoriana.sk/gg/wp-content/uploads/c-clef3.png http://gregoriana.sk/gg/wp-content/uploads/g-clef1.png http://gregoriana.sk/gg/wp-content/uploads/g-clef2.png http://gregoriana.sk/gg/wp-content/uploads/g-clef3.png Thanks in advance! Marek ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Map voices to channels in MIDI output
Neil Puttock schreef op do 10-03-2011 om 21:41 [+]: On 10 March 2011 21:04, Jan Nieuwenhuizen jann...@gnu.org wrote: Doesn't that still fall foul of the lack of synchronization between Staff_performer instances though? For example, if I have two staves with one voice each, both voices will still be allocated the same channel Why would that be a problem? They're in different tracks. (and so will the instruments, if set) unless channel_map_ is static. Are you saying that the instrument of channel 0 of track 1 is somehow linked to the instrument of channel 0 of track 2? Greetings, Jan. -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Map voices to channels in MIDI output
Keith OHara schreef op do 10-03-2011 om 18:15 [-0800]: It works for me, [...] Oh! Thanks for checking. I'll post a report on the bug list with the (very tiny) midi files and see if it's just my midi players (timidity and WMP) Thanks. Note that I now found that if there are two voices on one staff, taking track 1 channels 0 and 1, only channel 0's instrument is set, so the second voice sounds as the default piano. It would be nice to have a test for that to check when it's fixed. Long term, though, I don't see how your approach can handle orchestral scores, where there usually are more than 16 voices. I hope this new solution is better than the previous one: that had a maximum of 15 staffs + 1 percussion and would wrap around after 16 different staffs/instruments. Now, we have an unlimited number of staffs, and 15 voices per staff (or one percussion). I hope. Greetings, Jan. -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: The usage of -dtrace-scheme-coverage in Lilypond
On Fri, Mar 11, 2011 at 12:21 AM, zhangxy zhangxy290626...@gmail.com wrote: Dear hanwen, Now I want to analyze the test coverage of Lilypond. I find the option -dtrace-scheme-coverage. It says that the option can record coverage of Scheme files in `FILE.cov'. Then I do the following lilypond -dtrace-scheme-coverage test.ly But it gives me the error throw from within critical section. trace-scheme-coverage relies on a hack in the GUILE evaluator that I added in 2007, which records a symbol's source location the moment that symbol is looked up. The glue on the lilypond side is in scm/coverage.scm. This feature was removed in 2010, when the GUILE folks rewrote the evaluator, before ever seeing the light in a GUILE release. Apparently there is a new mechanism for finding coverage. See https://www.gnu.org/software/guile/manual/html_node/Code-Coverage.html - perhaps you can work out a way with the guile folks to resurrect lilypond's test coverage code. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Potential fix for issue 1504. (issue4237057)
On Thu, Mar 10, 2011 at 5:04 AM, mts...@gmail.com wrote: this looks wrong - different broken pieces cannot ever share a commonx. Odd - it gets correct results for some reason (I honestly don't know how...). Lily tries not to crash, and things may just work in this case, but better not rely on it. The correct way is to use each beam's System() as a reference point, as the System always is the ultimate parent in both X and Y directions. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
RE: using \sans on Windows gives 'gs' error (2.13.53) fails to compile
Hello,
)-Original Message-
)From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
)[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org] On
)Behalf Of James Lowe
)Sent: 10 March 2011 17:54
)To: 'Phil Holmes'; '-Eluze'; 'lilypond-devel@gnu.org'
)Subject: RE: using \sans on Windows gives 'gs' error (2.13.53) fails to
)compile
)
)Hello
)
))-Original Message-
))From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
))[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org]
)On )Behalf Of Phil Holmes
))Sent: 10 March 2011 16:41
))To: -Eluze; lilypond-devel@gnu.org
))Subject: Re: using \sans on Windows gives 'gs' error (2.13.53) fails to
))compile
))
))- Original Message -
))From: -Eluze elu...@gmail.com
))To: lilypond-devel@gnu.org
))Sent: Thursday, March 10, 2011 3:13 PM
)) no problem over here (windows vista. lp-version 2.13.53)!
))
))
))Ditto. Vista. Possibly a problem with which fonts are installed?
)
)I also don't get the problem on XP.
)
):(
)
)So either this is specific to my own desktop or Windows 7.
)
)Until I can use another Windows 7 machine I have no comparison.
)
)James
)
I have tried this on a different windows 7 machine with 2.13.52
Same error
# -*-compilation-*-
Processing `C:/Users/jlowe.DCSW/Desktop/untitled.ly'
Parsing...
C:/Users/jlowe.DCSW/Desktop/untitled.ly:0: warning: no \version statement
found, please add
\version 2.13.52
for future compatibility
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `/Users/jlowe.DCSW/Desktop/untitled.ps'...
Converting to `/Users/jlowe.DCSW/Desktop/untitled.pdf'...
`(gs -q -dNOSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89
-dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
-sOutputFile=/Users/jlowe.DCSW/Desktop/untitled.pdf -c.setpdfwrite
-f/Users/jlowe.DCSW/Desktop/untitled.ps)' failed (1)
error: failed files: C:\\Users\\jlowe.DCSW\\Desktop\\untitled.ly
Only when \sans is used
i.e.
{c1^ markup { \sans hello}
is used.
---
Does anyone understand the error?
Could it be permission related for instance?
I don't think I have an older version of LP but I seem to remember being able
to use 2.13.20-something.
I also remember some GS changes were made or something related to stop the CMD
window popping up. Could this be related?
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Implements the 2nd of 5 legs of getting footnotes up and running. (issue4254055)
Hi Mike, can fix the below points before continuing with pushing stuff for this patch series? On Sun, Mar 6, 2011 at 8:46 PM, mts...@gmail.com wrote: +// ugh...code dup...hopefully can be consolidated w/ above one day can you make a priority to do this right now? If it's not done directly, 'one day' usually does not happen at all. + int pos = orig-spanned_rank_interval ()[LEFT]; + Real spanner_placement = min (1.0, + max (robust_scm2double (me-get_property (spanner-placement), -1.0), + -1.0)); + + spanner_placement = (spanner_placement + 1.0) / 2.0; + int rpos = orig-spanned_rank_interval ()[RIGHT]; + pos = (int)((rpos - pos) * spanner_placement + pos + 0.5); + + if (pos me-spanned_rank_interval () [LEFT]) + return SCM_EOL; Can you rethink this? The rank numbers are not good measures of anything. In particular, adding a new voice/staff with different rhythmic texture will cause these numbers to fluctuate, and mess up your positioning. I still think this is a overall bad idea, and would love to see examples where users need placement of footnotes, but placement so inexact that they do not want to use per-item positioning. One possibility is to use column-when() as a measure, as it is least somewhat invariant, but preferably I'd like to scrap this (especially given the code dup and overall ugliness) until we have proof that it's really needed. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
RE: using \sans on Windows gives 'gs' error (2.13.53) fails tocompile
Hello,
)-Original Message-
)From: Phil Holmes [mailto:m...@philholmes.net]
)Sent: 11 March 2011 15:50
)To: James Lowe; '-Eluze'; lilypond-devel@gnu.org
)Subject: Re: using \sans on Windows gives 'gs' error (2.13.53) fails
)tocompile
)
)James,
)
)Try adding the line:
)
)#(ly:set-option 'delete-intermediate-files #f)
)
)to your LilyPond source, then have a look at the PostScript file and see
)what fonts it's trying to use.
Thanks, I set the option and ran the file.
I got the same error in the logs
I also opened the .PS file in Acrobat distiller and got the message
%%[ Error: typecheck; OffendingCommand: readonly ]%%
Stack:
/glyph
/glyph
-dict-
/CharStrings
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
---
Opening the .PS (in word) I get
%!PS-Adobe-3.0
%%Creator: LilyPond 2.13.52
%%Pages: 1
%%PageOrder: Ascend
%%Orientation: Portrait
%%DocumentMedia: a4 595.28 841.89 80 () ()
%%DocumentSuppliedResources: font CenturySchL-Bold
%%DocumentSuppliedResources: font CenturySchL-Roma
%%DocumentSuppliedResources: font Emmentaler-20
%%DocumentSuppliedResources: font Verdana
%%EndComments
%%BeginProlog
/lilypond-datadir where {pop} {userdict /lilypond-datadir (C:/Program
Files/LilyPond/usr/share/lilypond/current) put } ifelse
%%BeginFont: CenturySchL-Bold
%%BeginResource: font CenturySchL-Bold
%!PS-Adobe-3.0 Resource-FontSet
%%DocumentNeededResources: ProcSet (FontSetInit)
%%Title: (FontSet/CenturySchL-Bold)
%%Version: 0
%%EndComments
%%IncludeResource: ProcSet (FontSetInit)
%%BeginResource: FontSet (CenturySchL-Bold)
/FontSetInit /ProcSet findresource begin
%%BeginData: 64206 Binary Bytes
/CenturySchL-Bold 64172 StartData CenturySchL-Bold ùË ùÌ ùÍ ùÎ ø
$
then the binary stuff.
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Map voices to channels in MIDI output
On Fri, 11 Mar 2011 01:32:39 -0800, Jan Nieuwenhuizen jan...@gnu.org wrote: Neil Puttock schreef op do 10-03-2011 om 21:41 [+]: both voices will still be allocated the same channel Why would that be a problem? They're in different tracks. Are you saying that the instrument of channel 0 of track 1 is somehow linked to the instrument of channel 0 of track 2? Yes. The player should remember the instrument assigned to each channel, regardless of which track set the instrument. The physical model is a midi cable, where the receiver sees only the messages, not the track structure. Tracks and Channels are orthogonal organizations. Tracks organize the file; channels distinguish data streams down the (real or virtual) cable. The structure that *can* contain several channels is a Port, separate Ports corresponding to separate cables in the hardware. One can optionally specify a different Port for each Track (making Tracks and Channels no longer purely orthogonal) http://www.somascape.org/midi/tech/mfile.html#meta but I have no reason to expect a software midi player to support multiple ports. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
RE: using \sans on Windows gives 'gs' error (2.13.53) fails tocompile
Hello, )-Original Message- )From: Phil Holmes [mailto:m...@philholmes.net] )Sent: 11 March 2011 15:50 )To: James Lowe; '-Eluze'; lilypond-devel@gnu.org )Subject: Re: using \sans on Windows gives 'gs' error (2.13.53) fails )tocompile ) )James, ) )Try adding the line: ) )#(ly:set-option 'delete-intermediate-files #f) ) )to your LilyPond source, then have a look at the PostScript file and see )what fonts it's trying to use. ) )-- Also I forgot to add that one of my large scores will not compile - get the same error and this has no \sans in it. But if I create a new file *only* \sans switch causes the problem. James attachment: winmail.dat___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: using \sans on Windows gives 'gs' error (2.13.53) fails tocompile
[snip again]
OK - it's a bit blind leading the blind here, but perhaps a font-person will
step in at some point.
You can get all the fonts on your system with the following command:
lilypond -dshow-available-fonts x fonts.txt 21
It'll redirect the output to fonts.txt and you can view it in your favourite
file editor.
The PostScript file is clearly calling for 4 fonts:
%%DocumentSuppliedResources: font CenturySchL-Bold
%%DocumentSuppliedResources: font CenturySchL-Roma
%%DocumentSuppliedResources: font Emmentaler-20
%%DocumentSuppliedResources: font Verdana
My guess is that you don't have one of them on your system.
You can mess around with using different fonts with:
\paper {
myStaffSize = #20
#(define fonts
(make-pango-font-tree Times New Roman
Arial
Courier New
(/ myStaffSize 20)))
}
(as you probably know). I would try using, say Arial, as your Sans font and
see what happens with your .PS file.
--
Phil Holmes
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
RE: using \sans on Windows gives 'gs' error (2.13.53) fails tocompile
Phil,
One step back two steps forward (yes I did say that right)
)-Original Message-
)From: Phil Holmes [mailto:m...@philholmes.net]
)Sent: 11 March 2011 17:41
)To: James Lowe; '-Eluze'; lilypond-devel@gnu.org
)Subject: Re: using \sans on Windows gives 'gs' error (2.13.53) fails
)tocompile
)
)[snip again]
)
)OK - it's a bit blind leading the blind here, but perhaps a font-person will
)step in at some point.
)
)You can get all the fonts on your system with the following command:
)
)lilypond -dshow-available-fonts x fonts.txt 21
Thanks, I couldn't for the life of me remember where that command was. I have
used it before.
)
)It'll redirect the output to fonts.txt and you can view it in your favourite
)file editor.
)
)The PostScript file is clearly calling for 4 fonts:
)
)%%DocumentSuppliedResources: font CenturySchL-Bold
)%%DocumentSuppliedResources: font CenturySchL-Roma
)%%DocumentSuppliedResources: font Emmentaler-20
)%%DocumentSuppliedResources: font Verdana
)
)My guess is that you don't have one of them on your system.
Hmm..I don't have CentruryS*...however neither does my XP system where it does
compile. So o! but not !.
)
)You can mess around with using different fonts with:
)
)\paper {
)myStaffSize = #20
)#(define fonts
)(make-pango-font-tree Times New Roman
)Arial
)Courier New
)(/ myStaffSize 20)))
)}
)
)(as you probably know).
I do :( but I've moved on from that issue for now.
)I would try using, say Arial, as your Sans font and
)see what happens with your .PS file.
I cut and paste this directly in my file that wouldn't compile and
now it does!
;)
So it is a 'font' thing, but it isn't clear what because XP which doesn't
contain CenturyS* still compiles fine. Can you check on your XP install (I
assume that is what you use generally) and see if YOU have CenturyS* in case I
have missed this.
Thanks for the path..not so much' the blind leading the blind' but the
'partially sighted leading the not looking in the right place'
?
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: using \sans on Windows gives 'gs' error (2.13.53) fails tocompile
[snip] You said: I don't have CentruryS* I assume this is a typo in the mail, and you were searching for the right family? FWIW I use Vista, and I did install some other fonts a month or so ago. If I use your original file (no font substitution) I get %%DocumentSuppliedResources: font CenturySchL-Roma %%DocumentSuppliedResources: font DejaVuSans %%DocumentSuppliedResources: font Emmentaler-20 With a completely vanilla XP virtual machine, same file, I get: %%DocumentSuppliedResources: font CenturySchL-Roma %%DocumentSuppliedResources: font Emmentaler-20 %%DocumentSuppliedResources: font Verdana so it looks like the default sans font is verdana, which makes sense. You got that on your W7 machine? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Map voices to channels in MIDI output
Keith OHara schreef op vr 11-03-2011 om 09:16 [-0800]: On Fri, 11 Mar 2011 01:32:39 -0800, Jan Nieuwenhuizen jan...@gnu.org wrote: The structure that *can* contain several channels is a Port, separate Ports corresponding to separate cables in the hardware. One can optionally specify a different Port for each Track (making Tracks and Channels no longer purely orthogonal) http://www.somascape.org/midi/tech/mfile.html#meta but I have no reason to expect a software midi player to support multiple ports. So if we put track 0 to port 0, track 1 to port 1 etc., we would technically be correct? Midi players would have the option to ignore ports, as long as they do not lump together channel 0 of track 0 and channel 0 of track 1 -- a midi player does see the tracks after all. Technical correctness probably has little merit if no player supports it, but it is worth a try. Setting ports should be quite easy and if major players support this, we're safe. Jan. -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Map voices to channels in MIDI output
On Fri, 11 Mar 2011 10:12:59 -0800, Jan Nieuwenhuizen jann...@gnu.org wrote: Technical correctness probably has little merit if no player supports it, but it is worth a try. Setting ports should be quite easy and if major players support this, we're safe. I know nothing about this, but some other people with similar goals are http://www.classicalmidiconnection.com/2port.htm Remember, without this hack, midi2ly cannot recreate it's own midi files if they use voices. With the fixes in the above commits, even wtk1-fugue2.ly (one of the nice test examples that was removed and not put back) can be nicely recreated by midi2ly. To preserve more organizational information, use more Tracks. There can be up to 65535 Tracks in a midi file. The correspondence could be: single Port Staff_performer - Channel Voice - Track midi2ly puts each track on its own staff by default (which is probably safest, and not a problem because re-arranging the variables in staves is one of the easier things to do in LilyPond). To associate several Tracks with one staff, you could write a staff-association into Track Name ( event 0xFF03 ). ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: shortened flags affair, part 5 - length of notes extending far from staff
Hmm, i raised this issue because it looked to me as if it was overlooked by developers, but engraving books seem to be clear here and LilyPond is in fact doing the right job. While personally i dislike current looks of the output, i won't argue with authorities here. Let's leave it as it is now. 2011/3/10 Werner LEMBERG w...@gnu.org Again - makes no difference, once the note mean is below a single ledger line. ??? As written earlier, I see absolutely no reason why the stems for the beamed 128th must be that long. IMHO, they could be moved down one staff space. Am I missing something? Maybe it's done in order to visually separate beams with staff symbol. 128th beam consists of five lines, so it could blend with staff undesireably. cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyPond speed. Idea for Schikkers list
2011/3/10 Graham Percival gra...@percival-music.ca:
On Thu, Mar 10, 2011 at 12:42:11AM +0100, Janek Warchoł wrote:
2011/3/9 Han-Wen Nienhuys hanw...@gmail.com
You can easily try this out yourself. Just set ragged-right=##t and
set linelength to 100 meters (or something). You may need to remove
some internal sanity checks on distances.
Maybe i should've explained why i ask this question. My idea for
shikkers list is this: it would show a user only a rough preview of
music,
This has been proposed a few times in the past, but nobody has yet
seriously investigated it.
I think the first step would be to do exactly what Han-Wen
suggests -- hey, it'll only take 5 minutes!
I did it.
(assuming that you
choose a very large score to test with?)
I tried one horn concerto from mutopia (45 pages, ~300 measures).
Results are interesting: compiling it with regular settings took 2
minutes. After adding
\paper
{
ragged-last-bottom = ##t
ragged-bottom = ##t
ragged-right = ##t
paper-width = 1000 \cm
}
It compiles for 15 minutes now and still didn't finish.
2 days ago I tried much smaller score (4 pages) and normally it
compiled in 12 seconds, while using this 'infinite' paper size it took
about twice as long.
Perhaps something in line breaking algorythm isn't working as we expect at all?
If you see a
significant increase, then clearly it's worth investigating more.
But that other investigation will probably require modifying the
C++ code.
I would see a significant increase only if calculating line-breaks was
a significant part of score compiling (computational-wise), but right
from the start I didn't suppose that was the case.
I hoped that some experienced developer could give an estimate based
on intuition, but maybe that's impossible.
As for me this idea is postponed indefinately then.
cheers,
Janek
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: PATCH - DOC: Added @knownissue to NR for fingering
Hello, -Original Message- From: David Kastrup d...@gnu.org Organization: Organization?!? Date: Thu, 10 Mar 2011 23:47:41 +0100 To: Lilypond Dev lilypond-devel@gnu.org Subject: Re: PATCH - DOC: Added @knownissue to NR for fingering James Lowe james.l...@datacore.com writes: http://codereview.appspot.com/4248081/ Doc: Added @knownissue to NR for fingering By default double-digit fingering (i.e. 9) is not possible using normal fingering markups. There is an LSR that has been posted for approval at the time of this patch, and will be included in the snippet link in the @seealso already in this section. Tidied up some grammar and minor punctuation changes. --- Came out of http://article.gmane.org/gmane.comp.gnu.lilypond.general/62604 Stupid question: since I can see no use for following a fingering with a digit, why don't we just change the parser appropriately? _If_ there is some use for numbers greater than 10 (apart from the current situation, button accordion fingerings may need to be underlined in order to indicate helper rows, and one could likely just put something in the engraver which does this for numbers greater 10, deducting 10 in the process), rather than making yet-another-LSR-snippet, we could just allow larger numbers. Any reason not to? Well there's no rush for this specific patch, so it can wait for a while in case anyone wants to chime in/add some code change. I agree that another LSR is not ideal, but we need to do something I think. James ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
adding issues to the tracker
Just a reminder that any developer is more than welcome to add issues directly to the tracker. If you're confident that you've identified a bug -- or even if you're not confident in that itself, but at least you're confident that you're more familiar with the topic than the bug squad volunteers -- then by all means add the bug directly. This is particularly relevant with us being 1 critical issue (I think? officially, at least) away from having another release candidate. If your google account doesn't have permission to add issues, then ask Phil to add you to the list. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Internals: untranslated and huge
On Thu, Mar 10, 2011 at 06:25:45PM +0100, Francisco Vila wrote: 2011/3/10 Francisco Vila paconet@gmail.com: I'm wondering if we really need translated html pages for Internals Reference, which contain only untranslated material. No, those should be cleaned up. Thanks, added as; http://code.google.com/p/lilypond/issues/detail?id=1556 Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Added @knownissue to NR for fingering (issue4248081)
LGTM, go ahead and push after fixing Neil's thing. http://codereview.appspot.com/4248081/ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: PATCH - DOC: Added @knownissue to NR for fingering
On Fri, Mar 11, 2011 at 11:00:27PM +, James Lowe wrote: Hello, -Original Message- Stupid question: since I can see no use for following a fingering with a digit, why don't we just change the parser appropriately? _If_ there is some use for numbers greater than 10 (apart from the current situation, button accordion fingerings may need to be underlined in order to indicate helper rows, and one could likely just put something in the engraver which does this for numbers greater 10, deducting 10 in the process), rather than making yet-another-LSR-snippet, we could just allow larger numbers. Sounds good to me! Well there's no rush for this specific patch, so it can wait for a while in case anyone wants to chime in/add some code change. I agree that another LSR is not ideal, but we need to do something I think. I don't think we need a LSR snippet; let's just add the @knownissue now. Unless David thinks he can make a patch in a few days...? Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
RE: Indexing the new spacing properties
Hello From: Trevor Daniels [t.dani...@treda.co.uk] Sent: 11 March 2011 20:43 To: James Lowe Cc: Lily-Devel List Subject: Indexing the new spacing properties Hi James I just noticed that none of the new spacing properties in spacing.itely have @funindex entries. These are needed so people can follow-up error messages like staff-affinities should only decrease Do you fancy adding them, or shall I do it? Pushed as 94e86f88b7d4c3461876f72583f5e00c2d0e2a51 Hope this is enough? James ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Scheme Tweak Help: Highlighting a Staff in a StaffGroup
This works perfectly!
Thanks ever so much.
If anyone is curious to see how this looks, I have a sight-singing blog,
http://moveabledo.com Moveable Do , that I'm putting together using Lilypond
and some other resources.
Best,
- Eugene
Neil Puttock wrote:
On 7 March 2011 21:11, emw ewal...@weisswalden.com wrote:
If anyone can help me write a Scheme tweak for this, I'd appreciate it.
Even
pointing me to a tweak that does some of the same things would be helpful
(i.e. tweaking output across an entire Staff in a StaffGroup, etc).
Each Staff context contains a grouping object (a VerticalAxisGroup)
which carries all the elements on the stave. You can extract the
bounding box for this and print a solid coloured box as its stencil
(which is usually unset):
\version 2.12.3
highlight = {
\override Staff.VerticalAxisGroup #'layer = #-1
\override Staff.VerticalAxisGroup #'stencil =
#(lambda (grob)
(let ((x-ext (ly:grob-property grob 'X-extent))
(y-ext (ly:grob-property grob 'Y-extent)))
(grob-interpret-markup grob
(markup #:with-color yellow
#:filled-box x-ext y-ext 0
}
\new StaffGroup
\new Staff \relative c' {
c1
}
\new Staff \relative c' {
\highlight
c1
}
If you're running 2.13, defining \highlight as a context modification
makes it easier to add to other contexts such as Lyrics:
\version 2.13.53
highlight = \with {
\override VerticalAxisGroup #'layer = #-1
\override VerticalAxisGroup #'stencil =
#(lambda (grob)
(let ((x-ext (ly:grob-property grob 'X-extent))
(y-ext (ly:grob-property grob 'Y-extent)))
(grob-interpret-markup grob
(markup #:with-color yellow
#:filled-box x-ext y-ext 0
}
\new StaffGroup
\new Staff \new Voice = melody \relative c' {
c1
}
\new Lyrics \highlight \lyricsto melody {
foo
}
\new Staff \relative c' {
c1
}
\new Staff \highlight \relative c' {
c1
}
Cheers,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
View this message in context:
http://old.nabble.com/Scheme-Tweak-Help%3A-Highlighting-a-Staff-in-a-StaffGroup-tp31091731p31130224.html
Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: shortened flags affair, part 5 - length of notes extending far from staff
As written earlier, I see absolutely no reason why the stems for the beamed 128th must be that long. IMHO, they could be moved down one staff space. Am I missing something? Maybe it's done in order to visually separate beams with staff symbol. 128th beam consists of five lines, so it could blend with staff undesireably. I rather believe that noone has specifically considered this case. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
