Re: \dim and avoid-slur

Simon, you wrote Sunday, June 14, 2015 12:20 AM > I stand corrected. And thanks for spelling out that explanation :-) I Happy to help; sorry for sounding a little irritated. > And I just noticed that, with outside-staff-priority being > unset for both (or rather, all three), avoid-slur doesn’

Re: \dim and avoid-slur

"Trevor Daniels" writes: > Simon, you wrote Sunday, June 14, 2015 12:20 AM > >> I stand corrected. And thanks for spelling out that explanation :-) I > > Happy to help; sorry for sounding a little irritated. > >> And I just noticed that, with outside-staff-priority being >> unset for both (or r

Re: \dim and avoid-slur

David Kastrup wrote Sunday, June 14, 2015 10:05 AM > "Trevor Daniels" writes: > >> Simon, you wrote Sunday, June 14, 2015 12:20 AM >> >>> And I just noticed that, with outside-staff-priority being >>> unset for both (or rather, all three), avoid-slur doesn’t have the >>> desired effect, they

avoid merging stems

Hello, I'd like to avoid "stem-merging" in measure 13 between the upper g2. and the first lower g4. Additionally I'd like to hide the stem of the first lower g4 in m.13 (should be no problem, if the stems don't merge). I tried a couple of things to achieve this, but unfortunately I don't find

Re: avoid merging stems

2015-06-14 13:16 GMT+02:00 musicus : > Hello, > > I'd like to avoid "stem-merging" in measure 13 between the upper g2. and the > first lower g4. > Additionally I'd like to hide the stem of the first lower g4 in m.13 (should > be no problem, if the stems don't merge). > I tried a couple of things to

Re[2]: avoid merging stems

Sorry, forgot the minimal example... See attached -- Originalnachricht -- Von: "Thomas Morley" An: "musicus" Cc: "lilypond-user" Gesendet: 14.06.2015 13:37:57 Betreff: Re: avoid merging stems 2015-06-14 13:16 GMT+02:00 musicus : Hello, I'd like to avoid "stem-merging" in measure

Re: avoid merging stems

musicus wrote Sunday, June 14, 2015 12:16 PM > I'd like to avoid "stem-merging" in measure 13 between the upper g2. and the > first lower g4. > Additionally I'd like to hide the stem of the first lower g4 in m.13 (should > be no problem, if the stems don't merge). > I tried a couple of things

Re[2]: avoid merging stems

Yes, I want to leave the first g4 with no stem. (a specialty with string instruments: If you have to play the same pitch with two different strings simultaneously, there are two identical noteheads with one stem between) Thank you very much for "\override Slur.details.accidental-collision"!

Re: \dim and avoid-slur

Am 14.06.2015 um 12:19 schrieb Trevor Daniels: David Kastrup wrote Sunday, June 14, 2015 10:05 AM "Trevor Daniels" writes: Simon, you wrote Sunday, June 14, 2015 12:20 AM And I just noticed that, with outside-staff-priority being unset for both (or rather, all three), avoid-slur doesn’t have

Re: avoid merging stems

Am 14.06.2015 um 15:04 schrieb musicus: Yes, I want to leave the first g4 with no stem. (a specialty with string instruments: If you have to play the same pitch with two different strings simultaneously, there are two identical noteheads with one stem between) No need for acrobatics here: {

Re[2]: avoid merging stems

This helps indeed a lot. On the other hand I'd be interested how to avoid stem merging... NoteHeads are controllable with "\mergeDifferentlyHeadedOn" etc. Is there any similar function to do the same with stems? Am 14.06.2015 um 15:04 schrieb musicus: Yes, I want to leave the first g4 with no

Half flat or sharp

Hello! I have one question. Can I entered a half flat and half sharps to the Lilypond? Thank You! Marco Oros ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Half flat or sharp

See: http://www.lilypond.org/doc/v2.18/Documentation/source/Documentation/notation/writing-pitches#index-microtones - Original Message - > From: "Marco Oros" > To: lilypond-user@gnu.org > Sent: Sunday, June 14, 2015 2:05:59 PM > Subject: Half flat or sharp > > Hello! > I have one questi

Re: Half flat or sharp

Marco Oros writes: > Hello! > I have one question. Can I entered a half flat and half sharps to the > Lilypond? http://lilypond.org/doc/v2.18/Documentation/notation/writing-pitches#index-quarter-tones> -- David Kastrup ___ lilypond-user mailing list

Help with Horizontal Compression!

Hello, I recently started to typeset Shostakovich's first violin concerto and i entered the first 7 bars into lilypond, only to find that the notes have been spaced at some comically large space, rather than compressing into a readable size. If the score was to continue at this rate then reading

Re: Help with Horizontal Compression!

Hello, Perhaps it won't help but documentation from fonts.openlilylib.org tells that the staff height factor has to be set to 20. Is there a reason why you set it to 22 ? Philippe -- View this message in context: http://lilypond.1069038.n5.nabble.com/Help-with-Horizontal-Compression-tp177855p

Re: avoid merging stems

Am 14.06.2015 um 15:32 schrieb musicus: This helps indeed a lot. On the other hand I'd be interested how to avoid stem merging... NoteHeads are controllable with "\mergeDifferentlyHeadedOn" etc. Is there any similar function to do the same with stems? There’s no such thing like stem merging. Ei

Re: Help with Horizontal Compression!

Hello, some remarks: 1. Are you aware that it’s illegal what you’re doing? All of the works of Shostakovich are under copyright (almost?) everywhere on the world, see the note on . So there is little point in typesetting his music, unless yo

Re: avoid merging stems

2015-06-14 20:20 GMT+02:00 Simon Albrecht : > Am 14.06.2015 um 15:32 schrieb musicus: >> >> This helps indeed a lot. >> On the other hand I'd be interested how to avoid stem merging... NoteHeads >> are controllable with "\mergeDifferentlyHeadedOn" etc. >> Is there any similar function to do the sam

Re: Help with Horizontal Compression!

Simon Albrecht writes: > Hello, > > some remarks: > 1. Are you aware that it’s illegal what you’re doing? All of the works > of Shostakovich are under copyright (almost?) everywhere on the world, > see the note on > . So? That does not preclu

Re[2]: avoid merging stems

so \voiceXxx should work, or not? Why doesn't the stem of "\voiceOne g" go up as intended? Sure, it's a quite rare usecase, but i hope you can see my point. I don't want to merge the \voiceOne and \voiceTwo stems and if you try to hide/ omit one of both stems, both disappear! That's why I'm ask

Re: Help with Horizontal Compression!

Am 14.06.2015 um 22:42 schrieb David Kastrup: >> 3. If the problem should persist nevertheless, have a look at >> > . > In general, LilyPond tends to take up sizeable more space than scores by > experienced human

Re: Help with Horizontal Compression!

2015-06-14 22:42 GMT+02:00 David Kastrup : > Simon Albrecht writes: > >> Hello, >> >> some remarks: >> 1. Are you aware that it’s illegal what you’re doing? All of the works >> of Shostakovich are under copyright (almost?) everywhere on the world, >> see the note on >>

Re: avoid merging stems

musicus writes: > so \voiceXxx should work, or not? > Why doesn't the stem of "\voiceOne g" go up as intended? Sure, it's a > quite rare usecase, but i hope you can see my point. > I don't want to merge the \voiceOne and \voiceTwo stems and if you try > to hide/ omit one of both stems, both disap

Re: avoid merging stems

Am 14.06.2015 um 23:00 schrieb musicus: so \voiceXxx should work, or not? Why doesn't the stem of "\voiceOne g" go up as intended? I didn’t figure the exact reason, but generally it’s because of the nested << \\ >>. The following works perfectly fine: \version "2.19.17" { << \clef bass

Re[2]: avoid merging stems

Ok, this sounds indeed very interesting. I understand your explenation regarding nesting of <<>> in following way: << {"layerOne"} \\ << {"layerOne"} \\ {"layerTwo"} >> >> which leads to the problem: \version "2.19.17" << {a' a' a' a'} \\ { b b << {c