Re: 64-bit Mac build of 2.20 is now available!

Glad my feedback seems to be useful. [cutting a bit here] > Thanks, this makes sense. I should be able to set the variables correctly > (and actually, the lilypond "binary" in the app bundle is already a script > that sets a few variables and calls the real executable, so putting a few >

Re: LilyPond 2.19.84 installer on MacOS 10.15 (Hans Åberg)

Hans, Thank you for providing this. It works great, except for one bug I found. It seems that when it’s installed it expects the file system to be using ISO Latin 1 rather than UTF-8. When I ran it on file names with non-ASCII characters in UTF-8, it returned fatal errors like this: Warnung:

Re: Grace notes in the first measure mess up the layout

Thanks much. I *hunted* all over for something like this, but clearly didn’t have the right search string as I thought this was a problem with the *first* measure in a piece. This helps. > On Feb 3, 2020, at 22:14, Daniel Rosen wrote: > >> From: Arle Lommel [mailto:fene.

Grace notes in the first measure mess up the layout

I’m running into a major layout fault when I have a grace note in the first measure of a piece. Measures with a grace note look as expected, but all other staves are *really* ugly. I’m assuming this is *not* the intended behavior and conjecture it is happening because Lilypond sees the grace

Re: license question

> From: David Nalesnik > > Subject: license question > > Hi all, > > I have a question concerning the GPL. Is it permissible for an app > under a GPL-incompatible license to provide output in LilyPond code? > For example, could Finale provide a Finale->LilyPond

Re: SVG in \markup Block?

> Took some time to refactor things and add functionality. I believe I have > managed to support all SVG path commands, except for elliptic arcs (A/a). Holy Hannah, that is going *far* above and beyond any reasonable (or even unreasonable) expectations I might have had for assistance. I

Re: Unusual cross-staff stem in Bartók

a function. Arle -- Misit de iPhone meo. > On Jan 20, 2020, at 06:00, Simon Albrecht wrote: > > On 14.01.20 18:15, Arle Lommel wrote: >> Why Bartók didn’t simply show the bottom D in the treble clef is an >> interesting question. I think he was trying to keep the

Re: SVG in \markup Block?

>

SVG in \markup Block?

I’ve got some SVG images I would like to embed in \markup blocks. I’ve been searching the documentation and the archives for information on how to do this, but without success. If it’s been discussed before, the results are getting lost in all of the discussion about SVG output, so I’m not

Re: Scheme question

> Since you have a variable, you would need the quasi-quote feature if you > wanted the shorthand: `(,padding . 0) But, (cons padding 0) should > work. > > > -- Aaron Hill Thank you, Aaron. The quasi-quote version did it. Is that feature explained anywhere in the documentation? I don’t

Re: Three short questions from Bartók around fingering, about 90% there

> On Jan 14, 2020, at 18:05, Mark Stephen Mrotek wrote: > > Arle, > > Add these before the b! > > \once \override Accidental.extra-offset = #'(3 . 0) > \once \override NoteColumn.force-hshift = #2.5 > > Mark Thanks. I’m finding I have to play around with the numbers a bit and add an

Scheme question

I am a total neophyte to Scheme, but not to coding. I’ve written a simple function, but it does not work (I’ve reduced it to just the problematic lines. Can anyone tell me how to write the line indicated below? shifter = #(define-music-function (parser location padding) (number?) #{

Re: Unusual cross-staff stem in Bartók

> The more things interact unnecessarily, the harder it becomes doing > things reliably. The more we manage to get LilyPond to behave to naive > expectations, the more useable power the average user has at their > convenience. > > So we should not try overexercising the "music is complex, so

Re: Unusual cross-staff stem in Bartók

> Hope that helps more! > Kieren. Thanks much. One of the challenging things for folks like me who dip in and out is keeping track of all the different ways that things can be done and how all the elements interact. But that is inherent to this: Music notation is orders of magnitude more

Re: Unusual cross-staff stem in Bartók

Írta Kieren: > p.s. Maybe this helps? That did indeed help. It got me 90% of the way there. When I actually applied it in the piece I’m setting, I found that the length of the overridden stem was pushing the other staff away. It didn’t do this in the example you made, so I’m not sure what

Re: Lyric misalignment solved. Was Re: Lyric misalignment and beaming?

So schrieb David: > Either way is acting as it should. > > The manual has an index entry "beam, with lyrics" for the chapter > "Setting automatic beam behavior" but there is no usable reference > whatsoever in that chapter. I actually find rather little elsewhere > either, there are mostly just

Re: Unusual cross-staff stem in Bartók

Thank you. This seems to do it nicely. I’d not submitted a MWE because I didn’t have anything I was confident was even the right sort of starting point and was looking for a pointer where to even start. Fortunately (for me), you filled the gap very nicely with this. I’ll need to adapt it for

Re: lilypond-user Digest, Vol 206, Issue 45

Sic scripsit Aaron Hill: > In your larger document, do you use \autoBeamOff? This was the problem. I did’t recall turning autoBeam off so I didn’t think to check for it. Sic scripsit Kieran MacMillan: > Well, that would follow "traditional" (meaning pre-1900) engraving rules for > vocal

Lyric misalignment solved. Was Re: Lyric misalignment and beaming?

Thanks very much to Carl Sorenson for a response that got me to start paring things down even more and led me to find the problem in my score where I didn’t previously look. Took a while Basically, if autoBeam is off (somehow I’d turned it off outside a variable where I was defining things),

Lyric misalignment and beaming?

Got a head scratcher here. Using 2.19.83, I’ve run into a problem where I *cannot* create a minimal example: The minimal example works exactly as it should and it is only in context where things fail, but I have no idea what actually makes them fail, so I have no idea how to make a minimal

Re: lilypond-user Digest, Vol 186, Issue 108

Thank you Ben. See below: > \version "2.19.80" > > %% http://lsr.di.unimi.it/LSR/Item?id=272 > Don’t know how I didn’t find this, but I thought I’d gone through all of the time signature-related snippets. Clearly not… The snippet is almost right, but

Re:Single-measure time signatures with raised numbers

Apologies for forgetting to change the subject line on my last mail… -Arle ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Font caching problems on the Mac

A while back I mentioned very long start-up times for Lilypond on the Mac and someone suggested that the problem is with font caching. Today I was able to confirm that as the case. I installed a number of new fonts (Noto from Google) and suddenly Lilypond was facing extremely long load times

Re: Lilypond slow to start up on the Mac

, but I'll do so later. Thanks for the pointer. Arle -- Misit de iPhone meo. > On Apr 23, 2018, at 14:13, David Wright <lily...@lionunicorn.co.uk> wrote: > >> On Mon 23 Apr 2018 at 11:40:46 (-0400), Arle Lommel wrote: >> I’ve noticed on the Mac for some time that

Lilypond slow to start up on the Mac

I’ve noticed on the Mac for some time that the first time I invoke Lilypond from an external application after a reboot, it can take quite a while for it to respond. Normally this is something like a 40–60 second delay, after which Lilypond behaves normally. But a few days ago, after I updated

Re: Double ties: Can't tweak both ties.

Found a solution, in this: \override TieColumn.tie-configuration = #'((3.5 . 1) (5.5 . 1)) It’s not as precise as I’d like to be, but it gives me this, which is clear: I’d prefer to have the direct control, but as that appears to be buggy (and not just counter-intuitive), this will

Re: Double ties: Can't tweak both ties.

Thank you for looking at what I sent earlier, Carl. Turns out that it *doesn’t* actually work like I thought it did. Here is a real tiny example of the problem: \version "2.18.2" \relative c'' { \tieUp 2 2 ~ |

Re: Double ties: Can't tweak both ties.

gt; wrote: > > > > From: Arle Lommel <arle.lom...@gmail.com <mailto:arle.lom...@gmail.com>> > Date: Monday, March 12, 2018 at 10:55 AM > To: <lilypond-user@gnu.org <mailto:lilypond-user@gnu.org>> > Subject: Double ties: Can't tweak both ties

Double ties: Can't tweak both ties.

[I hope this doesn’t turn up twice. I’h having trouble sending from another email address and it doesn’t seem that my previous attempt to send this worked. So apologies if it does come through twice from different addresses.] Hoping someone can help me on this, as I have not found any way to

Double ties: Can't tweak both ties.

Hoping someone can help me on this, as I have not found any way to fix this problem, despite trying all sorts of things and searching for anything similar. I have some polyphonic music where some double ties are crashing with notes in another voice. It looks like this: The relevant code

Re: Resolving cannot resolve rest collision: rest direction not set warnings

out a lot, cognitively, in finding real issues. -Arle On 2012 Dec 19, at 09:45 , Jim Long lilyp...@umpquanet.com wrote: On Wed, Dec 19, 2012 at 08:44:29AM +0100, Arle Lommel wrote: Hi all, I am working on the same score that spawned discussion about stem lengths and now have another

Re: Resolving cannot resolve rest collision: rest direction not set warnings

: On Wed, Dec 19, 2012 at 08:44:29AM +0100, Arle Lommel wrote: Hi all, I am working on the same score that spawned discussion about stem lengths and now have another, hopefully less controversial, question. I keep getting warnings like the following when I run Lilypond: warning: cannot

Re: Resolving cannot resolve rest collision: rest direction not setwarnings

Here is a minimal (real) example of one measure that generates four warnings. As you can see the rests in the third voice are simply invoked as r4 while the ones in the second voice are given explicit locations (which, again, I want to do in this case). (I realize the notation convention here

Re: Resolving cannot resolve rest collision: rest direction notsetwarnings

Thanks much. This is what I was missing. I had thought, somehow, from reading that portion (a number of times) that the voiceOne and voiceTwo bits were automatically and implicitly assigned and did not realize that they have to be explicitly invoked. Earliest suggestions got me part of the way

Re: Resolving cannot resolve rest collision: rest direction notsetwarnings

Just realized another issue. Is there a way to tell Lilypond where in the staff a voice’s rests should go? While Phil’s guidance to use \voiceOne and \voiceTwo took care of the warnings, it also means that the rests from one of the voices that had previously been centered in the staff now sit

Re: Resolving cannot resolve rest collision: rest direction notsetwarnings

Thanks. The (probably deserved) chastisement aside, finding things in the documentation does require knowing how to find them. Finding even obvious things in the documentation isn't always easy if you don't already know what to look for. As I had spent some time earlier looking for this and

Re: Resolving cannot resolve rest collision: rest direction notsetwarnings

David, Sorry for the long response, but maybe it will be useful for project insiders to see how someone mostly on the outside experiences the documentation and the ways for finding things. I think part of the problem is the sheer volume and being able to recognize what is directly relevant.

Re: Resolving cannot resolve rest collision: rest direction notsetwarnings

Reinhold, The position there is a perfect example of where the search probably should be for the main documentation. The way you have it actively encourages use. The way the main site has it discourages use unless someone has a big enough screen to spot it. Does an AJAX search field

Re: Short stems [ATTENTION: INLINE IMAGES]

testament to its design. Best, Arle -- Arle Lommel Berlin, Germany Skype: arle_lommel Phone (US): +1 707 709 8650 Sent from a mobile device. Please excuse any typos. On Dec 18, 2012, at 9:03, Werner LEMBERG w...@gnu.org wrote: LilyPond tries to mimick traditional engraving. There are bugs

Re: Short stems [ATTENTION: INLINE IMAGES]

…how can you be so sure that the LilyPond output wrong? I'm not at all sure it is wrong, but as Werner points out, there were non-German traditions that Lilypond does not address. Since this comes from one of those and I am trying to represent the score in a nicer format that is still true to

Re: Short stems

No worries at all. If most people were “impolite” in the same way (offering solutions and helping) the world would be better off. Since you've helped me before, I didn't take it personally in any way. Arle I apologize having been impolite. ___

Re: Best practices in lyric typesetting

MS, Putting aside the impossibility of the attached exercise, you'll see that the lyrics stay shifted way down for the part of the attached example that moves to D major. I ran into the reverse problem with pedal markings the other day: they were *not* aligned (and in fact seemed to behave

Resolving cannot resolve rest collision: rest direction not set warnings

Hi all, I am working on the same score that spawned discussion about stem lengths and now have another, hopefully less controversial, question. I keep getting warnings like the following when I run Lilypond: warning: cannot resolve rest collision: rest direction not set They appear from

Short stems

I have run into an odd little aesthetic issue. I'm finding that some eighth (or shorter) notes get stems that are too short when they stick out from the staff.For instance, I find the stem here awfully short because it makes the flag on the eighth note run into the note heads:But the measure

A question of list etiquette and images. (Was Re: Short stems)

First off, thanks very much, Harm, for taking the time to review my issue and provide a detailed response, despite the complaint about images. I will work with it and see how it works out. Now please forgive me for diverting from Lilypond-related matters to issues of the list etiquette. My

Re: Short stems

then you might comment on the recommendation for improvement here http://code.google.com/p/lilypond/issues/detail?id=2724 which will probably prompt some action. I will look at that. See my note below: I think the default values are a problem. LilyPond's default is the list I typed above :

Re: Improving alignment of pedal marks

Thanks. This works beautifully, once I figured out how to get the right pedal style (because I'd changed it for a staff context earlier I had to update that bit, and then it worked and the alignment looks great! -Arle On 2012 Dec 15, at 23:55 , Nathan when.possi...@gmail.com wrote: You can

Moving a staff closer to another one

Hi all, I have a piece with the following overall structure: \score { \new StaffGroup \new PianoStaff \new Staff = RH { \relative c' { \righthand } } \new Staff = LH { \relative c { \lefthand } }

Re: Moving a staff closer to another one

I've moved sustain pedal articulations to a separate voice using spacers because they did not fit cleanly on the other voices. If I put the pedal voice in the left-hand it forces all the rests in the left-hand voice to sit a fifth higher. In addition the marks end up aligned all over the place,

Re: Moving a staff closer to another one

Great. That takes care of the issue with the rests, but not with the vertical alignment of the pedal brackets, which move all over the place to accommodate other objects. But knowing this about voices helps me a ton. I've learned Lilypond on an ad hoc, as needed basis, so there is still a lot

Improving alignment of pedal marks

Thanks to Phil Holmes’ suggestion to learn move about using explicit voices I resolved one of my major problems with the piece I'm working on. Thanks much.The second problem remains. How can I improve the vertical alignment of pedal marks? The piece I am working on has a lot of situations like the

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, but

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

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 m...@mikesolomon.org wrote: On 14 déc. 2012, at 09:31, Arle Lommel fene...@gmail.com wrote

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

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 athttp://lilypond.org/doc/v2.16/Documentation/notation/fontsBut I find when I change the fonts that there are some

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

bug… Best, Arle On 2012 Dec 14, at 10:18 , Trevor Daniels t.dani...@treda.co.uk wrote: 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

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

Re: Forced double accidental

, Arle On 2012 Dec 13, at 12:50 , Thomas Morley thomasmorle...@googlemail.com wrote: 2012/12/13 Arle Lommel fene...@gmail.com: One more question: I need a way to force a note to show a cancellation natural (from a double sharp) followed by a sharp sign. Lilypond doesn't want to do this in my

Missing 8s

Just thought I would share a strange little bug that I can't explain (Lilypond 2.16.1 on Mac OS X 10.8.2). I've switched the document font for a document to use Adobe Brioso Pro. It works well for the piece and everything is beautiful except one thing: in the bar numbers any “8” disappears. So

Removing bar lines between piano staff and ossia and making space between consecutive ossias

Thanks to everyone for recent help. I've been truly impressed by how helpful people have been for my requests.Now I have one more problem with the piano piece I am working on. I am using a pianoStaff, which works fine, except that I now have a portion with a bunch of ossia parts (almost one a

Re: Removing bar lines between piano staff and ossia and making space between consecutive ossias

explanation :-) Best, Arle On 2012 Dec 13, at 00:19 , Thomas Morley thomasmorle...@googlemail.com wrote: Hi Arle, 2012/12/12 Arle Lommel fene...@gmail.com Thanks to everyone for recent help. I've been truly impressed by how helpful people have been for my requests. Now I have one more

Tweaking notehead direction in chords

I've been looking for how to tweak the direction of noteheads within chords. I've got a few instances where Lilypond’s default isn't as clear as when I flip the direction of some of the noteheads. I've searched the repository and tried various tweaks using direction, but nothing seems to

Re: Tweaking notehead direction in chords

Arle, On Dec 11, 2012, at 2:37 PM, Arle Lommel fene...@gmail.com wrote: I've been looking for how to tweak the direction of noteheads within chords. I've got a few instances where Lilypond’s default isn't as clear as when I flip the direction of some of the noteheads. I've searched

Re: How to cross-staff beam different length notes in a chord.

As a follow-up, I managed to mostly solve the problem with this example (relevant additions in bold):top = { \change Staff = "top" }bottom = { \change Staff = "bottom" }staffPiano = \new PianoStaff { \set PianoStaff.instrumentName = #"Piano" \time 3/4 \context Staff = "top" { \clef treble

Apologies

Not sure what my mail program did, so sorry for all the base64 crap dumped in the list just now, and please ignore the earlier messages, which was sent from the wrong address and shouldn't have even gone through. -Arle ___ lilypond-user mailing list

Trying once more…

Hopefully this won't puke on the list. What is the best way to handle something like this:Where the notes in a "chord" are of unequal length.I've tried using polyphony and forcing the stem direction, but I've gotten problems with very small misalignments in the stems, and in this case it would be

Re: Trying once more.

Between Phil's suggestion, which prompted me to add a missing: \context { \PianoStaff \consists #Span_stem_engraver } in the layout {} block (which made cross-staff beaming possible), and Thomas’ suggestion to use \tweak #'duration-log #, I've got this working nicely. The

Simple hymn question

Hello all, I've got what should be a simple question, but one which is giving me no end of trouble. I'm attempting to set a carol for homophonic choir, so I do *not* need independent voices, but I do need the lyrics between the staves. All of the examples I have found online are considerably

Re: Changing quarter tone notation

regards, Arle On Sep 5, 2012, at 11:44 PM, Keith OHara k-ohara5...@oco.net wrote: On Wed, 05 Sep 2012 06:37:38 -0700, Arle Lommel fene...@gmail.com wrote: If the arrows were independent of the sharp and flat signs (which would derive as normal from the key signature plus accidentals

Re: lilypond-user Digest, Vol 118, Issue 20

Hi Keith,Thanks for this answer and my apologies for taking a while to acknowledge it. For some reason I missed it at the time and only today found it.The bit there is a different system then what I need in that it puts arrows on the accidentals. The system I'm looking for puts the arrows above or

Re: Changing quarter tone notation

[apologies for reposting, but I had the wrong subject heading, which means nobody would have read this before.]Hi Keith,Thanks for this answer and my apologies for taking a while to acknowledge it. For some reason I missed it at the time and only today found it.The bit there is a different system

Lyrics help

Hello all, I've got a pretty basic question, but looking through the manuals and trying things out hasn't seemed to help me get closer to a solution. I'm transcribing some songs I collected in the field and I need to have a volta repeat in the music where the lyrics for two verses are listed

Changing quarter tone notation

As a separate question from the last, does anyone know of a simple way to override the quarter-tone notation in Lilypond? In particular, I want to replace half sharps with an upward arrow over the note, which is the de facto standard in the particular ethnomusicological area I work in. While the

Re: Lyrics help

Thanks Trevor, Thanks for pointing me in the right direction. My mistake was to look in lyrics, not repeats, I guess. I just tried it and it worked well, so I'm set. As you say, not trivially obvious, but I can see the logic behind the syntax (even if I would never have guessed it in a hundred

Re: Lyrics help

Actually, as I look, I'm not sure how I missed this. But I did search for quite a while, so thank you again Trevor for the help. Best, Arle ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

PDF preview in jEdit

Hi all, Just started using jEdit and lilypondtool today on Mac OS X because I liked the idea of the PDF Preview and the integration between it and the editor. However, in trying it out, I find that once I first invoke the preview function it won't update for me, so I can't see any changes: it

Re: PDF preview in jEdit

Thank you Patrick, but I should have made it clear, *that* was the item that kept serving me up the old version of the file as a preview, even after saving and making changes. Running the “Run Lilypond” botton, per Bert’s suggestion, however, seems to take care of the issue. -Arle On Jan 17,

Re: Complex time signature

Ralph, look here: http://www.fam.tuwien.ac.at/~reinhold/temp/time_sigs.ly I've used this, with some adjustment in the 2.13 development versions, and I think it works unaltered in 2.12. It should do exactly what you want. In some of the later 2.13 versions you have to manually control beaming

Re:Complex time signature

Even if that is perfect for your needs, you might want to take a look at Reinhold’s code anyway. It provides the proper Bartókian output (3+3+2/8), while the LSR code can only produce 3/8 + 3/8 + 2/8 type output. I prefer the former as cleaner and easier to read. -Arle Thank you, James -

Re: Complex time signature

| } } On Jan 14, 2011, at 12:51 , Hans Aberg wrote: On 14 Jan 2011, at 18:28, Arle Lommel wrote: Even if that is perfect for your needs, you might want to take a look at Reinhold’s code anyway. It provides the proper Bartókian output (3+3+2/8), while the LSR code can only produce 3/8 + 3/8

Re: Complex time signature

Somebody in this list used the notation of writing just the number in the staff, and the '+' decomposition above it and the staff within parenthesis in smaller size. That seems me to be a good idea. The '+' is not needed if the decomposition can be seen from the beaming. Seems like a good

Re: Complex time signature

Reinhold, Thanks for the changes. I wasn't aware of the new version and I'm glad to see it in LSR. -Arle ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

OT: Discussion with developer on documentation

Apologies for a question not directly related to Lilypond, but is there anyone who works with the documentation for Lilypond on this list with whom I could interact privately? I am working on a totally unrelated open-source project and we we are faced with about 500 pages of legacy

Re: Possible bug in lyrics mode

I’ve gone ahead and submitted the lyric mode spacing issue to the gmane lilypond bugs list. This is the first time I've submitted a bug and as I look at the other postings, so I'll askhere if I need to do anything beyond posting it there to get the bug actually listed?For what it's worth, I've

Re:Possible bug in lyrics mode

Just after I posted the additional example, Urs confirmed that it was posted to the bug list and given medium priority. So please disregard the question about if I needed to do anything else. The example I included may be useful though. Best, Arle

Possible bug in lyrics mode

Hi all, Just thought I'd mention something I believe to be a bug in lyrics mode, but thought I'd ask if there is a rationale for it before I submit. I found this a few weeks ago and got a workaround thanks to the list, but it was a bit of a pain and I can't help but think this is a bug. Line

Re: invisible rest that takes no horizontal space

On 6/18/10 12:32 PM, Dmytro O. Redchuk wrote: Why not: % [...] d4. e8 fis4 e | \partial 2 d2 \bar :|: fis2 g | % [...] Yes. That would be the solution if I could start from scratch. The problem is that I have more than 1000 melodies in which the invisible rest is used instead

Alternative polymetric representation

(Sorry for the lengthy post, but a couple of issues came up when I tried to work with an older file I did some time ago.) About 18 months ago Reinhold helped me figure out how to display time signatures like (3+3+4)/16 in which there is a complex upper portion of the time signature over a

Re: Alternative polymetric representation

Thanks to Alexander for the quick fix. I hadn't found that bit (obviously), in part because I wasn't thinking about it in the context of beams, but rather in the context of polymetric time signatures and that problem. Had I thought to look in the semi-obvious place, I suppose I would have found

Problem with complete lack of spacing between stanzas

and the stanzas stay stubbornly stuck together and ugly. I include an abbreviated version of my file below (four stanzas are deleted for the sake of brevity). I would appreciate any working suggestions for how to control these spacing issues on a per stanza basis. Best, Arle Lommel \version

Specialist staff for Hungarian bagipe

regards, Arle Lommel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Specialist staff for Hungarian bagipe

Thanks for the most helpful response. Somehow I missed that portion of the documentation, even though I do recall looking at it earlier. My guess is that if I can define the right line positions and limit the number to two, I'll be there. Now I have a starting point. Best, Arle On Jun 9,