Re: lilypond-user Digest, Vol 121, Issue 70

Thanks Joram and others On 2012 Dec 14, at 04:18 , Joram wrote: > A few remarks to your notes: > - The last [ should probably be opened after the fisis32. Harm caught that. Something happened in my editing in my mail program where I messed that up. > - The 32 is necessary only once I know, bu

Likely bug in 2.16.1: Changing document fonts messes lots of things up…

[Trying again: for some reason this message was ignored by the list, so I'm trying without any attachments.] OK, one more issue (possible bug?) has arisen that I cannot diagnose. (Lilypond 2.16.1, Mac OS X 10.8.2) I have followed instructions on how to change document fonts, as outlined at htt

Re: Forced double accidental

David Nalesnik writes: > On Thu, Dec 13, 2012 at 9:30 PM, David Nalesnik > wrote: >> >> I notice that you haven't added the $ sign before offsets in the LSR >> snippet as Harm and I advised. Try that and I see no reason the >> snippet shouldn't work.. >> > > Ah, no, I see. You did add it, but n

Re: Likely bug in 2.16.1: Changing document fonts messes lots of things up…

On 14 déc. 2012, at 09:31, Arle Lommel wrote: > [Trying again: for some reason this message was ignored by the list, so I'm > trying without any attachments.] > > OK, one more issue (possible bug?) has arisen that I cannot diagnose. > (Lilypond 2.16.1, Mac OS X 10.8.2) > Dear Arle, Please s

Re: Likely bug in 2.16.1: Changing document fonts messes lots of things up…

MS, Thanks. I wanted to confirm that it is a bug before submitting. I've tracked down the cause (but not the solution) and will submit there. -Arle On 2012 Dec 14, at 10:07 , "m...@mikesolomon.org" wrote: > On 14 déc. 2012, at 09:31, Arle Lommel wrote: > >> [Trying again: for some reason th

Re: Likely bug in 2.16.1: Changing document fonts messes lots of things up…

I found the cause. I had changed the global staff size to 16. As long as the global staff size stays at the default value of 20, things are fine. If it goes smaller or larger, the scaling goes off. Unfortunately the commands for changing fonts are not size independent, which seems like a very od

Re: Likely bug in 2.16.1: Changing document fonts messes lots of things up…

Arle Lommel Friday, December 14, 2012 8:31 AM > I have followed instructions on how to change document fonts, as outlined at > http://lilypond.org/doc/v2.16/Documentation/notation/fonts > > But I find when I change the fonts that there are some undesirable side > effects in *other* areas: Basic

Likely bug in 2.16.1: Changing document fonts messes lots of things up…

OK, one more issue (possible bug?) has arisen that I cannot diagnose. (Lilypond 2.16.1, Mac OS X 10.8.2)I have followed instructions on how to change document fonts, as outlined at http://lilypond.org/doc/v2.16/Documentation/notation/fontsBut I find when I change the fonts that there are some undes

Re: Likely bug in 2.16.1: Changing document fonts messes lots of things up…

Hi Trevor, I see you answered before I posted that I'd found the cause, and I think the discovery of the cause shows that your answer is really to a different problem. There is a real problem with font handling here and taking the approach in the documentation sections you point to to fix it wo

Re: Likely bug in 2.16.1: Changing document fonts messes lots of things up…

Hi all, I've finally figured the workaround for this issue. I think this should be contributed to the documentation until a better (i.e., scale-independent) solution is implemented. The example can stay the same: \paper { myStaffSize = #20 #(define fonts (make-pango-font-tree "Times Ne

Re: Likely bug in 2.16.1: Changing document fonts messes lots of things up…

On 14 déc. 2012, at 10:13, Arle Lommel wrote: > MS, > > Thanks. I wanted to confirm that it is a bug before submitting. I've tracked > down the cause (but not the solution) and will submit there. > > -Arle > > On 2012 Dec 14, at 10:07 , "m...@mikesolomon.org" > wrote: > >> On 14 déc. 2012,

Re: \crossStaff and \stemDown

Hi Eluze, thanks for your reply. Eluze wrote > well - I think originally the idea was to display chords over two staves > (and nothing more)! That is what I want to do, but with stems down. Stems up seem to work well. I have tried with the documentation sample, but same problem: \layout { \c

Re: \crossStaff and \stemDown

ornello wrote > > Eluze wrote >> well - I think originally the idea was to display chords over two staves >> (and nothing more)! > That is what I want to do, but with stems down. Stems up seem to work > well. I have tried with the documentation sample, but same problem: I think the \crossStaff co

brainstorming a really smart system engraver

Hello all, Like many people on this list, I engrave a number of choral works using Lilypond. Like a smaller subset of those people, I engrave a number of large and very large works (musicals, operas, extended choral works, etc.), which require multiple editions (full score, pianovocal score, vo

markup baselines

Hello all, What would be required to change all markups so that the baseline is the reference point, and extenders and descenders are ignored (or maybe assumed) for skyline calculations? At least for markups that often should be on the same baseline (e.g., MetronomeMark), it is somewhat frustr

RE: Re:Lyrics (David Kastrup)

Hi David, you wrote: > > You are aware that you don't _need_ to use \lyricsto or \addlyrics? > Just specify the duration you want in the text itself like > > \new Lyrics \lyricsmode { "And there were"1 "shepherds in"2. the4 field. } > > If you go "one lyric per bar", then you should just need the

Re: Lyrics (David Kastrup)

"Maarten de Keijzer" writes: > Hi David, you wrote: > >> >> You are aware that you don't _need_ to use \lyricsto or \addlyrics? >> Just specify the duration you want in the text itself like >> >> \new Lyrics \lyricsmode { "And there were"1 "shepherds in"2. the4 field. } >> >> If you go "one lyri

brackets

I get it: the bracket comes after the first note to be bracketed: a( b c[ d e)] Not like in algebra. Christopher Brooks violinist 925 Virginia Avenue Lancaster, PA 17603 717-291-9123 cbro...@orpheus-acoustics.com ___ lilypond-user mai

editing

I have found that if I edit in Microsoft Wordpad, I can undo much farther back than in the lilypond editor. This is a help for stumblers such as myself. Christopher Brooks violinist 925 Virginia Avenue Lancaster, PA 17603 717-291-9123 cbro...@orpheus-acoustics.com _

Re: \crossStaff and \stemDown

Eluze wrote > I think the \crossStaff command (and the \autoBeamOn/Off) have to be set > in the voice (or staff) where the stem originates, i.e. in the upper staff > if you set \voiceTwo or \stemDown. Ah, excellent suggestion! This is indeed symmetrical, and working: \layout { \context { \P

what's the most "efficient" way of doing this?

Hello all, Let's say I've got a series of RehearsalMark and MetronomeMark objects. I want them to appear at (e.g.) three places in my score: 1. Above the top staff of my score, at "full size"; 2. Above the string StaffGroup (about 2/3 of the way down the score), at "3/4 size"; and, 3. Below the

Re: brainstorming a really smart system engraver

Hello again! I think I have the PERFECT solution to this problem, if only \quoteDuring did the following two things: 1. Quoted lyrics. 2. Observed \RemoveEmptyStaves as if the quoted portion was empty (i.e., if the quoted material did NOT stop a hara-kiri action). Then, I could simply wri

Re: Neal Morse songbook done with LilyPond

Thank you, Stjepan! I have yet to see it printed, but the book should arrive at my house in the coming days. -- Peter Crighton | Musician & Music Engraver based in Mainz, Germany http://www.petercrighton.de 2012/12/13 Stjepan Horvat : > Hey Peter..The sample looks great! > > On Wed, Dec 12, 2012

Fast generation of png files

Hi! I would like to ask how to generate a png file in a minimal time. I tried to use " -dpreview -dno-print-pages " options, but from "test.ly" file, it produced "test.pdf"," test..preview.pdf" and "test.preview.png" files. I think if I could skip the pdf files, the generating time could be shorter

Re: editing

On 15/12/12 01:49, Christopher Brooks wrote: I have found that if I edit in Microsoft Wordpad, I can undo much farther back than in the lilypond editor. This is a help for stumblers such as myself. There are much better editors to assist with writing lilypond code. See http://lilypond.org

lyqi link from LP web site not valid

The link to lyqi at http://lilypond.org/doc/v2.17/Documentation/web/easier-editing is not valid (the page http://nicolas.sceaux.free.fr/lilypond/lyqi.html doesn't exist. The correct link now appears to be http://github.com/nsceaux/lyqi . Nick

beams

When I write this, it puts the beams in another place, places a beam for the first group, but not the second. This is mystifying 16~ [g'32 aes64 g fis g des b c fis,32] [g e'16 d c64 b c16] c16. [cid:image001.png@01CDD9DE.97A1E8B0] Christopher Brooks LEED(r) AP Senior consultant ACOUSTIC

Re: beams

On 15/12/12 01:37, Christopher Brooks wrote: 16~ [g'32 aes64 g fis g des b c fis,32] [g e'16 d c64 b c16] c16. Put the second "[" after the g, not before. 16~ [g'32 aes64 g fis g des b c fis,32] g[ e'16 d c64 b c16] c16. ___ lilypond-user ma

Re: \crossStaff and \stemDown

ornello wrote > So the problem of my original fragment seems to be related to adding > another voice in one of the staves. Here is another example: > > { > \new PianoStaff << > \new Staff << > \new Voice { > \voiceOne > g''4 > } > \new Voice { > \voi

Re: \crossStaff and \stemDown

2012/12/14 Eluze : > ornello wrote >> So the problem of my original fragment seems to be related to adding >> another voice in one of the staves. Here is another example: >> >> { >> \new PianoStaff << >> \new Staff << >> \new Voice { >> \voiceOne >> g''4 >> } >>

Re: \crossStaff and \stemDown

Thomas Morley wrote > Because \voiceThree has \shiftOn enabled. exactly - so another solution is (keeping the "natural" order of voices): \new PianoStaff << \new Staff << \new Voice { \voiceOne \shiftOn g''4 } \new Voice { \voiceThree \shiftOff < b d'>8 [ <

Manually aligning notes

I need to move the last d in this snippet to the *right* to avoid it colliding with the fis4 in the other voice. Inserting something like "\once \override NoteColumn #'force-hshift = #2" after the tie doesn't move it at all. Is there a way of moving it? << { \stemDown fis2 _~ fis4 e } \\ { d2

RE: Full bar rests in single-staff polyphony

No answer... should I send this to the bug list as a feature request? Here's an example: \version "2.16.1" \new Staff << \new Voice { \time 3/4 \voiceOne e' e' e' } \new Voice { \voiceTwo R1*3/4 } >> DR -Original Message- From: Daniel Rosen Sent: Thursday, December 13, 2012

Re: Manually aligning notes

Hilary Snaden wrote Friday, December 14, 2012 10:12 PM >I need to move the last d in this snippet to the *right* to avoid it > colliding with the fis4 in the other voice. Inserting something like > "\once \override NoteColumn #'force-hshift = #2" after the tie doesn't > move it at all. Is ther

Re: Manually aligning notes

Hilary Snaden wrote > I need to move the last d in this snippet to the *right* to avoid it > colliding with the fis4 in the other voice. Inserting something like > "\once \override NoteColumn #'force-hshift = #2" after the tie doesn't > move it at all. Is there a way of moving it? > > << { \ste

Re: Manually aligning notes

2012/12/14 Hilary Snaden : > I need to move the last d in this snippet to the *right* to avoid it > colliding with the fis4 in the other voice. Inserting something like "\once > \override NoteColumn #'force-hshift = #2" after the tie doesn't move it at > all. Is there a way of moving it? > > << { \

RE: Harmonic Analysis

Mr. Kastrup: Following your suggestion, the code for "/rN.ly" was included in the coding of the piece for which I was doing the harmonic analysis. It work easily. And its inclusion brought up two additional questions. I wanted to query the contributor, "MS," yet the e-mail address was withheld. 1

Writing to the console (debug info)

Hi all, Is there a way to write text to the console in LilyPond? I'd like to display the file currently processed to keep track of problems on a 60 part etude. Best regards, Olivier ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gn

Re: Fast generation of png files

Piotr Tokarski wrote > Hi! > I would like to ask how to generate a png file in a minimal time. I > tried to use " -dpreview -dno-print-pages " options, but from > "test.ly" file, it produced "test.pdf"," test..preview.pdf" and > "test.preview.png" files. I think if I could skip the pdf files, the >

Re: Harmonic Analysis

Hi Mark, On Fri, Dec 14, 2012 at 5:01 PM, Mark Stephen Mrotek wrote: > Mr. Kastrup: > > Following your suggestion, the code for "/rN.ly" was included in the coding > of the piece for which I was doing the harmonic analysis. I think you mean me, David Nalesnik. > It work easily. > And its inclus

Re: Writing to the console (debug info)

On Dec 14, 2012, at 17:05, Olivier Biot wrote: > Hi all, > > Is there a way to write text to the console in LilyPond? > > I'd like to display the file currently processed to keep track of problems on > a 60 part etude Use a "-v" flag when running it in Terminal.

Re: Displaying string number above fingering

On Wed, Dec 12, 2012 at 10:25 AM, David Kastrup wrote: > Keith OHara writes: > > > Eluze gmail.com> writes: > > > >> maybe this could be merged into > >> https://code.google.com/p/lilypond/issues/detail?id=2830 > > > > That issue is about fingering and string numbers inside chord brackets > <>,

Re: Displaying string number above fingering

shutterfreak wrote > Hi all, > > How can I display the string number above fingerings in all cases? > > Here's a small snippet that will semi randomly arrange fingerings and > string numbers: > > %%% BEGIN snippet > \version "2.16.1" > > theMusic = \new Staff \with {midiInstrument = #"cello"} {

Re: Writing to the console (debug info)

On Sat, Dec 15, 2012 at 12:20 AM, Eric Pancer wrote: > On Dec 14, 2012, at 17:05, Olivier Biot wrote: > > > Hi all, > > > > Is there a way to write text to the console in LilyPond? > > > > I'd like to display the file currently processed to keep track of > problems on a 60 part etude > > > Use a

Re: \crossStaff and \stemDown

Investigating \crossStaff further, I noticed a buggy behaviour, if the stem-direction changes. http://lilypond.1069038.n5.nabble.com/crossStaff-breaks-if-stem-direction-changes-td137717.html -Harm ___ lilypond-user mailing list lilypond-user@gnu.org ht

Re: what's the most "efficient" way of doing this?

> B. > B1. Put the RehearsalMark and MetronomeMark objects in the main global > variable (which also includes \time, \bar, etc.). > B2. Create a MarksOnly custom context, which only has the engravers > necessary to show RehearsalMark and MetronomeMarks, and let it "filter out" > everythi

Re: unhiding a hidden staff at the NEXT line break (instead of previous line break)

gmail.com> writes: > > Anyone know how I can get Lilypond to unhide a staff at the NEXT line break? No. It looks like you have a part for a cello section with the form unison |A| simple-divisi |B| complex-divisi where the complex-divisi music demands a separate staff for each part. If

Re: Writing to the console (debug info)

You can do that with Scheme. I don't know if there's a LilyPond command for it. #(display ) will display what you give it, either a plain string or an expression. The results aren't always totally useful (give it a \paper{} block, for example, and it will just say #) but that's a start. #(newline

Re: Full bar rests in single-staff polyphony

Daniel Rosen gmail.com> writes: > "So far, there's no automatic support in LilyPond to avoid collisions between > multi-measure rests and other objects." > > Is this still the case? Yes. > If so, is there a reason that this feature can't be added? I think that part of reason full-measure re

Re: minimal-breaking page breaking algorithm fails

Kieren MacMillan sympatico.ca> writes: > > Is there anything you use a lot in your score that could sometimes > > force staves further apart, > > depending on how the note-spacing comes out ? > > My score is frenched, so the estimates could be based on system extents > BEFORE the empty ones ar