Tuplet Bracket and \fermataMarkup

Hello Jeremy, did you try "padding" instead of "outside-staff-priority"? \version "2.18.2" \relative c { \omit Staff.TimeSignature << { \hideNotes \once \override TupletNumber.text = "~ 25 sec." \once \set tupletFullLength = ##t \once \set tupletFullLengthNote

\breakDynamicSpan in a Dynamics context?

Hi Dominic, i already had to deal with this particular prolem in many cases and don't know of any reasonable workaround. As others have mentioned, you can use either Y-offset in the Dynamics context or attach the dynamic signs to particular staves/ notes. Both ways have annoying side effects

Re[2]: \breakDynamicSpan in a Dynamics context?

gine a way of positioning objects relative to any other object. (this feature could be a nice workaround solution for most positioning bugs) In terms of dynamics you could group any number of dynamics and position the entire group between staves/ skylines... Best, musicus Hi, Both ways have

Re[2]: \breakDynamicSpan in a Dynamics context?

d the layout tweaks of the default output via edition-engraver I hope my thoughts are not too bad explained :) Please excuse my mistakes with scheme and so on...i guess i have some syntax errors here (in this theoretical consideration). Best regards, musicus Hi all, musicus wrote: +1 fo

new Staff staff-staff-spacing (down AND up) regarding only one single system

. But I don't find a solution for adjusting the distance to the upper one. Of course, I don't want to change the standard vertical spacing, when only the two main staves are used. Any suggestions or workarounds? Thank you for your help, musicus\version "2.19.34" \paper {

Fw: Solution for: new Staff staff-staff-spacing (down AND up) regarding only one single system

-- Weitergeleitete Nachricht -- Von: "musicus" An: kieren_macmil...@sympatico.ca Gesendet: 16.01.2016 21:43:55 Betreff: Solution for: new Staff staff-staff-spacing (down AND up) regarding only one single system Hi all, After i tried Kieren's suggestion (absolute sys

simplifying chromatic scale notation

as and can present one, which is IMO good to read. See attached. Comments, suggestions are very welcome ;) Best regards musicus\version "2.19.34" chrom = #(define-music-function (offset music)(number? ly:music?) #{ \once \override NoteHead.stencil = #ly:text-interface::print

Re[2]: simplifying chromatic scale notation

tes for orientation should be enough to solve this problem. The omission of many distractions (accidentals, "false" notehead position) weighs more, IMO. musicus ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: simplifying chromatic scale notation

Dear Paul, I really admire the effort and courage of alternative notation systems, but I cannot see a reasonable improvement in this case. I don't think it's a good idea to remove all great advantages, which our standard notation system has. IMO, there are only a few problems to be solved - c

Re: simplifying chromatic scale notation

Dear Sharon, "This last bit made me laugh out loud. Well I guess some musicians do not really feel like focusing on every single note. The good ones do though." I'd like to contradict on this one. Of course a good musician needs to focus on every detail, but only the "bad" ones neglect the

Re: digital music editions - is Lilypond a suitable tool for it?

Dear Urs, I recently learned about MEI and "Beethovens Werkstatt" (and as an example http://zolaemil.github.io/meiView/#pg=1), but I must say that this direction has IMO too many drawbacks/ misleadings. I didn't know http://beethovens-werkstatt.de/demo, so many thanks for it. IMO coloring and

Fw: Re: digital music editions - is Lilypond a suitable tool for it?

Sorry, didn't know that an attached html file does'nt work... Please change the attached file to ".html" JavaScript_Test3.html.rename Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/li

Re: Fw: Re: digital music editions - is Lilypond a suitable tool forit?

> I don't understand. The only difference between your two attachments > appears to be that the second one has DOS-style line endings. > What does that affect? My browser didn't show the first one as attachement, but displayed the content as an image and the javascript button did not work. Appare

ossia staff without SystemStartBar / Bracket / Brace

> I'm not top posting. Is there an easier way to get an ossia Staff without SystemStart than following code? I'm thinking of something like SystemStartBar #'allow-span-bar = ##f \version "2.19.17" << \new Staff = "ossia" \with { \remove "Time_signature_engraver" \hide Clef

coloring voices vs systemStartDelimiterHierarchy

Dear LilyPonders, I wanted to use a great coloring function by Urs Liska, but ran into a problem with using systemStartDelimiterHierarchy. If I color a music section, the SystemStart of the next system after that section isn't displayed properly. Anybody an idea how to solve this? Attached an

Fw: Re[2]: coloring voices vs systemStartDelimiterHierarchy

Hi Klaus, unfortunately I have to use \startStaff \stopStaff, because I want to set ossia variations above the original score. I'll attach the complete score, so you can see my problem. musicus -- Originalnachricht -- Von: "Klaus Blum" An: lilypond-user@gnu.org Gesen

Re[2]: Fw: Re[2]: coloring voices vs systemStartDelimiterHierarchy

Ok, the "\stopStaff \startStaff" in the colorMusic function is only necessary, if you want to color clefs, for example. In my case there aren't any "clef-changes", so the coloring function can work without it. It would be nice however, if music with clefs could be colored as well. I tried to put

avoid merging stems

restrict the shaping of slurs to a limit?) musicus\version "2.19.17" \language "deutsch" %\include "general-tools/clip-regions/definitions.ily" %\include "custom-music-fonts/smufl/definitions.ily" % Define a list with original page breaks (barnumbers) %origin

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

Re[2]: avoid merging stems

ision"! That helps a lot... I checked the details list for Slurs and wondered, if there are any settings, which can provide a better output than attached... Slurs seem to be very tricky! musicus -- Originalnachricht -- Von: "Trevor Daniels" An: "musicus" ;

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 th

Re[2]: avoid merging stems

isappear! That's why I'm asking... Anyway, in this case the chord syntax {4 bes g} does work perfectly. Thanks for help, musicus \version "2.19.17" { << \clef bass \time 3/4 \relative c' {\voiceOne g2.} \\

Re[2]: avoid merging stems

ot; in nested "<<>>"? Following by default (without needing \new Voice) seems to be much more understandable. << {"layerOne} \\ << {"layerTwo"} \\ {"layerThree"} >> >> Regards, musicus -- Originalnachr

Re[2]: Control which voice if shifted left

Attached another example, where changing the shift direction could be helpful... -- Originalnachricht -- Von: "Keith OHara" An: lilypond-user@gnu.org Gesendet: 16.06.2015 06:11:40 Betreff: Re: Control which voice if shifted left Simon Albrecht mail.de> writes: Am 15.06.2015 um 16:

Re[2]: Control which voice if shifted left

borious to find the proper h-shift value for each case. Yours, musicus -- Originalnachricht -- Von: "Simon Albrecht" An: "musicus" ; "Keith OHara" ; lilypond-user@gnu.org Gesendet: 16.06.2015 15:03:14 Betreff: Re: Control which voice if shifted left Am

\shape curves relative to NoteHead etc.

Slur.control-points = #'(NoteHead 0 . 0)(StartPoint rotated 0 . 0)(EndPoint standard 0 . 0)(Stem 0 . 0)) Probably I need some help with the scheme code for this function What do you think of this idea? Yours, musicus<> ___ lilypon

Re[3]: \shape curves relative to NoteHead etc.

It seems to happen at the end of a line... -- Originalnachricht -- Von: "musicus" An: "Urs Liska" ; lilypond-user@gnu.org Gesendet: 23.06.2015 20:24:35 Betreff: Re[2]: \shape curves relative to NoteHead etc. Hi Urs, thanks for the \shapeII link! I think it's

centering dynamics - robust vertical aligning

eating multiple independent Dynamics contexts - interrupting DynamicLineSpanner via \stopStaff \startStaff Y-offsets in the Dynamics context are working well, but only if line breaking doesn't change. Yours, musicus \version "2.19.22" \header { tagline = ##f } \paper { page-br

additional clef at start

Dear all, I have a probably not so difficult question, but cannot find the solution by myself: How to get a second clef at the beginning of a piece? See attached... Thank you all, musicus___ lilypond-user mailing list lilypond-user@gnu.org https://l

Re: additional clef at start

forgot the attachement... Dear all, I have a probably not so difficult question, but cannot find the solution by myself: How to get a second clef at the beginning of a piece? See attached... Thank you all, musicus<> ___ lilypond-user m

clef spacing problem with staff scaling

Dear all, I have a problem with spacing a small snippet of music. Of course I could manually add some extra space each time after the Clef, but I wonder if there is a better solution. In my opinion, this spacing behaviour should clearly adapt to the staff size... Cheers, musicus\version

Re: OT: high-precision tuner app

f 1/100 cent. Maybe it is better to specify Beats/second. (tempered quint vs pure quint = 1/2 B/s) Best regards, musicus ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user