Manual repeat and line break.

Well... after sending this I started thinking about a different question I had asked a while back and realized I could leverage that to get what I need.   it's not really ideal but it will work. Refer to code below and the screen shot. Once i get the structure laid out I'll work on making it p

Manual repeat and line break.

bit of struggle I have not gotten anything to really work well using the built in repeat structures.  The only thing I have really gotten to work is to just use manual repeats combined with markup for the segno markers.  I have this 95% working but am having a problem with line breaks.  Below are

Re: Manual page-breaking

On Tue, 2024-09-24 at 22:07 +0200, Xavier Scheuer wrote: > On Tue, 24 Sept 2024 at 16:41, David Sumbler > wrote: > > > > The best solution I have come up with is adding \autoPageBreaksOff > at the start of each Score block, and adding \noPageBreak between > markup items etc. which come outside o

Re: Manual page-breaking

On Tue, 24 Sept 2024 at 16:41, David Sumbler wrote: > > The best solution I have come up with is adding \autoPageBreaksOff at the start of each Score block, and adding \noPageBreak between markup items etc. which come outside of the Score block. So far, this seems to be working. Hello, You coul

Re: Manual page-breaking

On Mon, 2024-09-23 at 10:05 +0100, David Sumbler wrote: > Is there a way that I can take *total* control of page breaking? Thanks to those who responded to my question.  Judging from these responses, the answer to my question is "No" -- at least they don't seem to be readily applicable to the case

Re: Manual page-breaking

evitable that I'd end up wanting to override the decisions manually. But the original request for an ability to specify manual page breaks and not have Lilypond add any others, seems like more of bite-sized thing. We can already do something similar with line breaks. -- Matthew S

Re: Manual page-breaking

>> Is there a way that I can take *total* control of page breaking? > > I don't have a solution to offer but will comment that this is an > issue I also ran into recently while trying to engrave parts for > piano four hands. See https://gitlab.com/lilypond/lilypond/-/issues/902 Werner

Re: Manual page-breaking

On Mon, Sep 23, 2024 at 2:06 AM David Sumbler wrote: > Is there a way that I can take *total* control of page breaking? > > Here's what I do when I want to take total control of line and page breaking (this is for 3/4 time): %%% forceBreaks = { % page 1 \repeat unfold 3 { s2.\noBreak } s2.\b

Re: Manual page-breaking

t, only between the two sides of a single two-page spread. And it's not particularly necessary for the line breaks to match between the two sides, only the page breaks and number of systems on facing pages. I found it helped to add manual line breaks on one side or the other, as well as t

Manual page-breaking

Is there a way that I can take *total* control of page breaking? I have a file in the form: \version "2.24.3" \include "file1" \noPageBreak \include "file2" \pageBreak % lots more lines like the above \include "fileN" and individual files such as: % file1 \score {   \autoPageBreaksOff   %music

Re: manual vertical alternative marks

Add the || bar type to the list of bar symbols that require a volta hook with #(allow-volta-hook "||") at the top level of the ly file. On 04/06/2024 20:12, Paul Scott wrote: I have tried several variations of (volta #f) and end-repeat with the following code: \version "2.25.16" xDS = \mar

manual vertical alternative marks

I have tried several variations of (volta #f) and end-repeat with the following code: \version "2.25.16" xDS = \markup{\fontsize #4 \line{D.S. al Fine }} xFine = \markup{\fontsize #4 Fine} music = \fixed c' {   g1   \segnoMark 1   f 4 g a b   \set Score.repeatCommands = #`((volta ,xDS) )   g4

Re: manual repeat mark syntax question

Thank you! Paul On 5/16/24 11:42, Jean Abou Samra wrote:    \set Score.repeatCommands = #'((volta ,voltaOpt)) ^^^ This should be ` not ' .

Re: manual repeat mark syntax question

>    \set Score.repeatCommands = #'((volta ,voltaOpt)) ^^^ This should be ` not ' . signature.asc Description: This is a digitally signed message part

manual repeat mark syntax question

What is wrong with the following code that gives: programming error: Trying to interpret a non-markup object: (unquote voltaOpt) If it isn't clear, I'm trying to create a 3rd optional ending. \version "2.25.16" voltaOpt = \markup{Optional} \fixed c' {   a1   \repeat segno 2 {     g1     \vo

Bracket to indicate organ manual changes

Hi, I've been trying to make a bracket to indicate a change of manuals for an organ piece, and have succeeded in getting Lilypond to generate what I want (code below) for a particular instance. However, I have three questions: 1) Why does this particular format work? I'm not understanding why rem

Re: HTH w RTFM (Reading The Full Manual)

Jeff Olson writes: > On 1/5/2023 6:26 AM, David Kastrup wrote: >> I wonder whether something like this might help motivate work on lagging >> translations? > > Hmm, lags over what kind of time scale? > > I've only been comparing major releases, 2.24.0 vs 2.22.2. > Did translations for 2.24.0 feat

Re: HTH w RTFM (Reading The Full Manual)

On 1/5/2023 6:26 AM, David Kastrup wrote: I wonder whether something like this might help motivate work on lagging translations? Hmm, lags over what kind of time scale? I've only been comparing major releases, 2.24.0 vs 2.22.2. Did translations for 2.24.0 features not make it into that release

Re: HTH w RTFM (Reading The Full Manual)

ion can be translated Starting translation in a new language 5.9.2 Documentation translation details Files to be translated Translating the Web site and other Texinfo documentation Adding a Texinfo manual 5.9.3 Docu

Re: HTH w RTFM (Reading The Full Manual)

Jeff Olson writes: > Here we are:  with a new release, a new year.  Do I hear any resolutions? > > I've been impressed by how this community helps each other by > referencing just the right section of a manual, and that, lately, > those sections seem better writte

Re: HTH w RTFM (Reading The Full Manual)

Thanks Jeff, this really helps! MT Op woensdag 4 januari 2023 om 22:24:09 -0700 schreef Jeff Olson : Here we are: with a new release, a new year. Do I hear any resolutions? I've been impressed by how this community helps each other by referencing just the right section of a manual

Re: Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

On Fri, Oct 29, 2021 at 4:53 PM Lukas-Fabian Moser wrote: > > I'll probably keep the \noBeam rather than the \autoBeamOff, since I'm > > trying to faithfully reproduce the original, as much as I can. > Non sequitur (I think). > > Consider: > > \version "2.22" > \language "english" > > \relative

Re: Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

Again, much thanks. I would not have known this without your post. The Documentation page you reference clearly shows use of the "older" type of temporary polyphonic context and in the text explicitly mentions its use for lyric continuation. Yet doing so does require the use of \skip1 in lyrics

Re: Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

On Fri, Oct 29, 2021 at 3:51 PM Lukas-Fabian Moser wrote: > > Hi Kevin, > > Am 29.10.21 um 21:03 schrieb Kevin Cole: > > First, I'm using LilyPond v. 2.20.0. (I often seem to end up at 2.18 > > and 2.21 when searching for documentation -- though explicitly > > changing the URL to 2.20 works.) > Ye

Re: Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

I'll probably keep the \noBeam rather than the \autoBeamOff, since I'm trying to faithfully reproduce the original, as much as I can. Non sequitur (I think). Consider: \version "2.22" \language "english" \relative {   \time 3/4   \key d \major   d'8\noBeam d e16( fs) g8\noBeam a\noBeam fs

Re: Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

Whoa! What is this magic you're doing Master Moser?? - I made sure that the bf4. on "days" stays in the voice called melody. There are various ways to do this; I chose a "modern" way using \voices and \\ inside << >> which allows to automatically add a "second" voice This is a techni

Re: Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

Am 29.10.21 um 22:14 schrieb Guy Stalnaker: Whoa! What is this magic you're doing Master Moser?? - I made sure that the bf4. on "days" stays in the voice called melody. There are various ways to do this; I chose a "modern" way using \voices and \\ inside << >> which allows to autom

Re: Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

On Fri, Oct 29, 2021 at 3:37 PM Guy Stalnaker wrote: > Kevin, > > You're encountering an known situation with polyphonic contexts like this > one. A change in 2.20.x modified how lyrics are calculated in these > polyphonic contexts. You need to manually add to the *lyrics* \skip1 to > position

Re: Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

Hi Kevin, Am 29.10.21 um 21:03 schrieb Kevin Cole: First, I'm using LilyPond v. 2.20.0. (I often seem to end up at 2.18 and 2.21 when searching for documentation -- though explicitly changing the URL to 2.20 works.) Yes, that's a bit of a nuisance. Second, I guess I'm not sure what you mean by

Re: Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

er; When    | %   4 } Regards. On 10/29/21 1:17 PM, Kevin Cole wrote: So. I have a piece with a few sections where there are two "voices" as I understand things. And according to the manual, the solution, which works fine is: melody = { \relative { \global \n

Re: Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

easure should be > > "days of old, Ere her" with "days" taking up everything except the > last five notes, > > as shown on the bottom right of: > > https://archive.org/details/the-celtic-song-book/page/n22/mode/1up > > I see that the manual page I was lo

Re: Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

ve notes, as shown on the bottom right of: https://archive.org/details/the-celtic-song-book/page/n22/mode/1up I see that the manual page I was looking at says I cannot do things the way previous pages taught me to do things with \addlyrics. Is that enough info to let you know where I'm struggling?

Re: Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

Hi Kevin, Am 29.10.21 um 20:17 schrieb Kevin Cole: So. I have a piece with a few sections where there are two "voices" as I understand things. And according to the manual, the solution, which works fine is: Could you please post a compilable example? (Preferably as short as possib

Trying to get the hang of "Polyphony with Shared Lyrics" section of the manual.

So. I have a piece with a few sections where there are two "voices" as I understand things. And according to the manual, the solution, which works fine is: melody = { \relative { \global \new Voice = "melody" { \partial 4 bf4^\f

Re: Putting finger substitution in the LilyPond manual

Cc: Mark Stephen Mrotek ; lilypond-user@gnu.org Subject: Re: Putting finger substitution in the LilyPond manual On Sun, Oct 24, 2021 at 10:22 AM Carl Sorensen wrote: > > I think this should be a snippet, rather than text in a section. Rather than > telling, just show (and one can s

Re: Putting finger substitution in the LilyPond manual

On Sun, Oct 24, 2021 at 10:22 AM Carl Sorensen wrote: > > I think this should be a snippet, rather than text in a section. Rather than > telling, just show (and one can show three different methods in one snippet). > > The snippet could be as simple as: > > \version "2.21" > > \header { > lsrt

Re: Putting finger substitution in the LilyPond manual

On 10/24/21, 10:33 AM, "lilypond-user on behalf of Knute Snortum" wrote: On Sun, Oct 24, 2021 at 8:46 AM Mark Stephen Mrotek wrote: > > Knute, > > Some instructions are here > https://lilypond.org/doc/v2.22/Documentation/notation/inside-the-staff#fingering-instruc

Re: Putting finger substitution in the LilyPond manual

Actually the discussed solutions here are arguably better than the documentation example, because that one simply uses a markup event instead of a fingering event, which will cause problems in positioning. Cheers, Valentin 24.10.2021 18:32:32 Knute Snortum : > On Sun, Oct 24, 2021 at 8:46 AM M

Re: Putting finger substitution in the LilyPond manual

On Sun, Oct 24, 2021 at 8:46 AM Mark Stephen Mrotek wrote: > > Knute, > > Some instructions are here > https://lilypond.org/doc/v2.22/Documentation/notation/inside-the-staff#fingering-instructions > although it refers mainly to stringed instrument. Thank you Mark. So no need for a new section, b

RE: Putting finger substitution in the LilyPond manual

Behalf Of Knute Snortum Sent: Sunday, October 24, 2021 7:36 AM To: lilypond-user@gnu.org Subject: Putting finger substitution in the LilyPond manual In this thread (1) we discussed how to notate the piano technique of holding down one note and changing fingers without releasing the note. Wikipedia

Re: Putting finger substitution in the LilyPond manual

> Any thoughts on this? Just provide a patch on the development repository at this point. It is easier to discuss specifics with concrete material. The contributor's guide has all you need to know, and feel free to ask for assistance with Git, Texinfo or anything. Thanks in advance. Jean

Putting finger substitution in the LilyPond manual

In this thread (1) we discussed how to notate the piano technique of holding down one note and changing fingers without releasing the note. Wikipedia calls this "substitution." (2) I would like to put a section in the manual that explains how to notate this. It seems to be a fairly co

Re: tremolo question; don't understand how to apply the manual to my situation

Thank you, Harm! Now I have to place this with the examples in the manual and try to understand how to generalize this for the next time. Many times these things really make my head hurt :-) Thanks, Ken On Thu, Sep 16, 2021 at 4:40 PM Thomas Morley wrote: > > Am Fr., 17. Sept. 2021 um

Re: tremolo question; don't understand how to apply the manual to my situation

tand the tremolo repeat section in the manual, and > definitely not when it comes to this situation. See attached > screenshot. > > Here's my code (without the tremolo) for this measure (bass clef only): > > << > { e,2 e | } % tremolo?? > \\ >

tremolo question; don't understand how to apply the manual to my situation

Hi; I have a tremolo question. 4/4 time bass clef (piano part) polyphony apparently required two half notes, the first half note is in both voices I don't understand the tremolo repeat section in the manual, and definitely not when it comes to this situation. See att

Re: Manual

Le 17/04/2021 à 13:48, Mario Moles a écrit : Hi! Thanks! But ... it is very big... Is there anything simpler? I haven't found any. Thanks If you are talking about the \path command, it is explained here: http://lilypond.org/doc/v2.22/Documentation/notation/graphic (scroll down to \path).

Re: Manual

Hi! Thanks! But ... it is very big... Is there anything simpler? I haven't found any. Thanks Il 15/04/21 08:36, Helge Kruse ha scritto: On 15.04.2021 08:13, Mario Moles wrote: Hi! You know the manual for moveto, lineto etc ? Thanks. Sounds like you ask for PostScript commands. Would

Re: Manual

On 15.04.2021 08:13, Mario Moles wrote: Hi! You know the manual for moveto, lineto etc ? Thanks. Sounds like you ask for PostScript commands. Would this help? https://www.adobe.com/jp/print/postscript/pdfs/PLRM.pdf Regards, Helge

Manual

Hi! You know the manual for moveto, lineto etc ? Thanks.

Re: manual alternative endings

On 2/4/21 2:59 AM, Aaron Hill wrote: On 2021-02-04 1:13 am, Paul Scott wrote: The code below gives me what I want but gives me a warning. warning: already have a volta spanner, ending that one prematurely I'm thinking I need to add (volta #f) to the 2nd repeatCommands string but If so my sch

Re: manual alternative endings

On 2021-02-04 1:13 am, Paul Scott wrote: The code below gives me what I want but gives me a warning. warning: already have a volta spanner, ending that one prematurely I'm thinking I need to add (volta #f) to the 2nd repeatCommands string but If so my scheme is weak enough that I don't know how

manual alternative endings

The code below gives me what I want but gives me a warning. warning: already have a volta spanner, ending that one prematurely I'm thinking I need to add (volta #f) to the 2nd repeatCommands string but If so my scheme is weak enough that I don't know how to add it. TIA for any help with this,

Re: Problems with Internals manual

On 2020-06-17 5:53 am, David Kastrup wrote: Aaron Hill writes: On 2020-06-17 1:35 am, Peter Toye wrote: Robin, Thanks. Fair enough. I guessed and experimented and got the result that I wanted. But I'm not quite sure how I managed it! A problem I had with minimum-X-extent is that it's a pair,

Re: Problems with Internals manual

Aaron Hill writes: > On 2020-06-17 1:35 am, Peter Toye wrote: >> Robin, >> Thanks. Fair enough. I guessed and experimented and got the result >> that I wanted. But I'm not quite sure how I managed it! >> A problem I had with minimum-X-extent is that it's a pair, but the >> description describes i

Re: Problems with Internals manual

On 2020-06-17 1:35 am, Peter Toye wrote: Robin, Thanks. Fair enough. I guessed and experimented and got the result that I wanted. But I'm not quite sure how I managed it! A problem I had with minimum-X-extent is that it's a pair, but the description describes it as a distance, which I'd have th

Re: Problems with Internals manual

! Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.com - Tuesday, June 16, 2020, 7:55:50 PM, Robin Bannister wrote: > Peter Toye wrote: >> I'm trying to work out what the properties of a LyricHyphen are, but the >> Internals manual for that obj

Re: Problems with Internals manual

Peter Toye wrote: I'm trying to work out what the properties of a LyricHyphen are, but the Internals manual for that object keeps referring to rests, notes. beams. stems, See, for example, the minimum-distance property. None of these, to my mind, have much to do with lyrics or hyphens

Problems with Internals manual

I'm trying to work out what the properties of a LyricHyphen are, but the Internals manual for that object keeps referring to rests, notes. beams. stems, See, for example, the minimum-distance property. None of these, to my mind, have much to do with lyrics or hyphens. Has some text from an

Re: Manual in the terminal

On 4/17/20, foxfanfare wrote: > I know you can access to the manual page inside a terminal with "info > lilypond", but I was wondering if there was also a similar option available > to access the "internal documentation" Well, I suspect what you want is `info lil

Manual in the terminal

Hi all, I know you can access to the manual page inside a terminal with "info lilypond", but I was wondering if there was also a similar option available to access the "internal documentation", without having an access to the internet and without having to download the pdf

Extending manual (was Re: metronome-mark-alignment)

tual level, might be helpful for someone like me. I don't know if such an overview exists, or whether anyone has the time and ability to write one; and, moreover, depending on how much basic computer science it would need to cover, it might be outside the scope of this community---I

Section 2.9.6 of the Reference Manual: Combining Ancient Notation with Modern?

Hi, Weird scenario, and unfortunately I can't hate on the composersince it's my work and my misbehavior! ;-) So I have a section of a piece for tenor and orchestra that is in 4/4 but the singer has cadenza figures for sections, while the orchestra is resting. So the structure is 4/4 Orchestra

Re: Error compiling markup fret diagram example from manual

On 1/16/19, 11:49 AM, "David Kastrup" wrote: > > Obviously, it compiled properly for the documentation. Which is not 2.19.80 but 2.19.82. And 2.19.81 contains commit 6d588f7a85113cc9a6b6efcc1d254558e0a85998 Author: David Kastrup Date: Thu Oct 5 11:28:18 201

Re: Error compiling markup fret diagram example from manual

Carl Sorensen writes: > I'm on Mac OSX Sierra. Using Frescobaldi and LilyPond 2.19.80 > > I'm trying to compile the exampler from Fret diagram markups, NR 2.4.1: > > << > \new ChordNames { > \chordmode { > c1 d:m > } > } > \new Staff { > \clef "treble_8" > 1^\markup {

Error compiling markup fret diagram example from manual

I'm on Mac OSX Sierra. Using Frescobaldi and LilyPond 2.19.80 I'm trying to compile the exampler from Fret diagram markups, NR 2.4.1: << \new ChordNames { \chordmode { c1 d:m } } \new Staff { \clef "treble_8" 1^\markup { \fret-diagram "6-x;5-3;4-2;3-o;2-1;1-o;"

Re: tie with manual repeat

It works! Thank you Aaron! g. On Fri, 5 Oct 2018 at 11:08, Aaron Hill wrote: > On 2018-10-05 2:03 am, Gianmaria Lari wrote: > > I have the following code > > > > \version "2.19.82" > > \fixed c' { > > a1~ > > \set Score.repeatCommands = #'((volta "1")) a2 b2 \set > > Score.repeatCommands = #

Re: tie with manual repeat

On 2018-10-05 2:03 am, Gianmaria Lari wrote: I have the following code \version "2.19.82" \fixed c' { a1~ \set Score.repeatCommands = #'((volta "1")) a2 b2 \set Score.repeatCommands = #'((volta #f)) \set Score.repeatCommands = #'((volta "2")) a1^"Fine" \set Score.repeatCommands = #'((volta

tie with manual repeat

I have the following code \version "2.19.82" \fixed c' { a1~ \set Score.repeatCommands = #'((volta "1")) a2 b2 \set Score.repeatCommands = #'((volta #f)) \set Score.repeatCommands = #'((volta "2")) a1^"Fine" \set Score.repeatCommands = #'((volta #f)) \bar "|." c1 _"Da capo al Fine" \bar ":

Re: Follow up: using a bracket or brace to indicate an organ manual change

Joseph Srednicki wrote > I have just encountered the situation where the manual-change bracket is > colliding with an accidental. See the example included below. > > Do any members of this list have any suggestions to resolve this > situation? Hi Joe, The manual-change bracket i

Follow up: using a bracket or brace to indicate an organ manual change

Hello: Last I asked the members of the mailing list about how to add a brace or bracket to indicate a change of manuals in an organ score. See the following thread for the messages about this issue: http://lilypond.1069038.n5.nabble.com/Adding-a-brace-or-bracket-to-indicate-an-organ-manual

Re: Figured Bass discrepancy with Manual Lilypond & lyLuaTeX

-11 00:40, Brian Barker wrote: At 00:09 11/08/2018 -0400, Nobody Noname wrote: From the Lilypond manual, "http://lilypond.org/doc/v2.19/Documentation/notation/figured-bass";  I use the following code for figured bass. (The code is 3-steps above "Predefined commands" at th

Re: Figured Bass discrepancy with Manual Lilypond & lyLuaTeX

Thanks. I assumed it wasnt code and some arbitrary form of quotation. Bad assumption. thanks that settles it. To the other post. Definitely three steps above in my browser. On 2018-08-11 00:40, Brian Barker wrote: At 00:09 11/08/2018 -0400, Nobody Noname wrote: From the Lilypond manual

Re: Figured Bass discrepancy with Manual Lilypond & lyLuaTeX

Please put << Before your code and >> After your code as shown in the example (I actually found it 3 steps below the Predefined commands). HTH, Carl On 8/10/18, 10:09 PM, "liebre...@grossmann-venter.com" wrote: From the Lilypond manual, "ht

Re: Figured Bass discrepancy with Manual Lilypond & lyLuaTeX

At 00:09 11/08/2018 -0400, Nobody Noname wrote: From the Lilypond manual, "http://lilypond.org/doc/v2.19/Documentation/notation/figured-bass"; I use the following code for figured bass. (The code is 3-steps above "Predefined commands" at the end) \new Staff = &qu

Figured Bass discrepancy with Manual Lilypond & lyLuaTeX

From the Lilypond manual, "http://lilypond.org/doc/v2.19/Documentation/notation/figured-bass"; I use the following code for figured bass. (The code is 3-steps above "Predefined commands" at the end) \new Staff = "myStaff" \figuremode { <4>4 <

Re: manual beaming in compound time signatures

eve my aim >> >> Is there a cleaner way to do this ? >> >> Paul >> > > No AFAIK but there is no need to use manual beamings : > > \version "2.18.2" > > \relative c' { > \clef alto > \key ees \major > \time 6/

Re: manual beaming in compound time signatures

Hi Paul, 2018-07-24 3:46 GMT+02:00 B~M : > > I used stemLeftBeamCcount and stemRightBeamcount to achieve my aim > > Is there a cleaner way to do this ? > > Paul > No AFAIK but there is no need to use manual beamings : \version "2.18.2" \relative c' { \cle

manual beaming in compound time signatures

dear All, I have been trying to write clean code to achieve manual beaming in 6/8 time, but my code seems (to me) to be a grubby hack, there must be a cleaner way. In one compounded beat of 6/8 time I have 4 semiquavers (or 16th notes) then in the remaining time value of 2 semiquavers, I have a

Re: please direct to manual; different time signatures for different instruments

On 3/26/2018 1:29 AM, Wols Lists wrote: On 25/03/18 23:39, Ben wrote: On 3/25/2018 6:24 PM, Colin Campbell wrote: On 2018-03-25 12:19 PM, Sam Frybyte wrote: I don't even know what this is called so finding it in the manual has me stymied. I am using version 2.18.2 Thanks in advance

Re: please direct to manual; different time signatures for different instruments

On 25/03/18 23:39, Ben wrote: > On 3/25/2018 6:24 PM, Colin Campbell wrote: >> On 2018-03-25 12:19 PM, Sam Frybyte wrote: >>> I don't even know what this is called so finding it in the manual has >>> me stymied. >>> I am using version 2.18.2 >>&g

Re: please direct to manual; different time signatures for different instruments

On 3/25/2018 6:24 PM, Colin Campbell wrote: On 2018-03-25 12:19 PM, Sam Frybyte wrote: I don't even know what this is called so finding it in the manual has me stymied. I am using version 2.18.2 Thanks in advance. I believe someone has already directed you to polymetric notation, but he

Re: please direct to manual; different time signatures for different instruments

Hi Sam, What you're looking for is probably Polymetric notation All the best, Torsten -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___

please direct to manual; different time signatures for different instruments

I don't even know what this is called so finding it in the manual has me stymied. I am using version 2.18.2 Thanks in advance. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: maximumFretStretch in Manual, tablatures section ?

2018-01-26 0:20 GMT+01:00 Thomas Morley : > 2018-01-26 0:07 GMT+01:00 Carl Sorensen : >> On 1/25/18, 4:05 PM, "Thomas Morley" wrote: >> Thinking of documenting it, I suggest to go for an >> doc-tagged-lsr-snippet. >> WYT? >> >> >> I agree. A doc-tagged snippet would do the trick. > > >

Re: maximumFretStretch in Manual, tablatures section ?

2018-01-26 0:07 GMT+01:00 Carl Sorensen : > On 1/25/18, 4:05 PM, "Thomas Morley" wrote: > > > Seems that we should add maximumFretStretch to the properties read by > Tab_note_heads_engraver. > > > > Carl > I'll put up a patch. https://sourceforge.net/p/testlilyissues/issues/526

Re: maximumFretStretch in Manual, tablatures section ?

On 1/25/18, 4:05 PM, "Thomas Morley" wrote: 2018-01-25 23:48 GMT+01:00 Carl Sorensen : > > > On 1/25/18, 2:57 PM, "Thomas Morley" wrote: > > > Not really. > In the IR you'll find that maximumFretStretch is read by the Fretboard_engraver. > But

Re: maximumFretStretch in Manual, tablatures section ?

2018-01-25 23:48 GMT+01:00 Carl Sorensen : > > > On 1/25/18, 2:57 PM, "Thomas Morley" wrote: > > > Not really. > In the IR you'll find that maximumFretStretch is read by the > Fretboard_engraver. > But it doesn't say it's used in FretBoards-context exclusively. > > You already fo

Re: maximumFretStretch in Manual, tablatures section ?

On 1/25/18, 2:57 PM, "Thomas Morley" wrote: Not really. In the IR you'll find that maximumFretStretch is read by the Fretboard_engraver. But it doesn't say it's used in FretBoards-context exclusively. You already found maximumFretStretch in the determine-frets-proced

Re: maximumFretStretch in Manual, tablatures section ?

by Fretboard_engraver *and* Tab_note_heads_engraver (in TabVoice). > Don't you think that it should be mentionned in the Tablature section of > the manual that, at least, you have to type all the string numbers involved > in a more than default stretch ? > > By the way,

Re: maximumFretStretch in Manual, tablatures section ?

ing to the manuel, the property maximumFretStretch is only belonging to Fretboards context. Don't you think that it should be mentionned in the Tablature section of the manual that, at least, you have to type all the string numbers involved in a more than default stretch ? By the way, is

maximumFretStretch in Manual, tablatures section ?

ds context. Don't you think that it should be mentionned in the Tablature section of the manual that, at least, you have to type all the string numbers involved in a more than default stretch ? By the way, is there a way to override this default, just for a score or a section of it ? (yes,

Re: manual beaming and variables

On 3 September 2017 at 22:34, David Kastrup wrote: > [] > > > Well, you can cheat by going inside of chords like > > > > \version "2.19.60" > > > > nc = c_3 > > nd = d_2 > > ne = e_3 > > nf = f_4 > > > > { > > \fixed c' {<\nc>8 [ <\nd> <\ne> <\nf>]} > > \fixed c' {<\nc>16 [ <\nd> <\ne>

Re: manual beaming and variables

David Kastrup writes: > Gianmaria Lari writes: > >> On 27 August 2017 at 08:57, David Kastrup wrote: >> >>> However, LilyPond does not permit adding "post events" after the fact >>> (never mind their name). You can use >>> >>> { >>> <>[ \note b b b] >>> } >>> >>> to have the beam start event

Re: manual beaming and variables

Gianmaria Lari writes: > On 27 August 2017 at 08:57, David Kastrup wrote: > >> However, LilyPond does not permit adding "post events" after the fact >> (never mind their name). You can use >> >> { >> <>[ \note b b b] >> } >> >> to have the beam start event on an empty chord with duration 0.

Re: manual beaming and variables

On 27 August 2017 at 08:57, David Kastrup wrote: > Gianmaria Lari writes: > [...] if I explicitly set the beaming like this > > > > \version "2.19.60" > > > > note = {a8} > > > > { > > {\note [b b b]} > > } > > > > > > it doesn't compile. Why and how I can fix it? > > You'd have to write > >

Re: manual beaming and variables

gner | asmr artist lilypond video tutorials --> http://bit.ly/bcl-lilypond -- View this message in context: http://lilypond.1069038.n5.nabble.com/manual-beaming-and-variables-tp205289p205294.html Sent from the User mailing list archive at Nabble.com. ___ l

Re: manual beaming and variables

On 27.08.2017 13:50, MING TSANG wrote: Hi Simon: I reply from the user-achieve list. At end of the message there is an instruction "replay email via". I was assuming that it will change the subject line and include the message. Is is possible to set it to reply with re:subject and message ?

Re: manual beaming and variables

to do that. From: Simon Albrecht To: TSANGMING ; "gianmarial...@gmail.com" ; "lilypond-user@gnu.org" Sent: Sunday, August 27, 2017 7:33 AM Subject: Re: manual beaming and variables Hello Ming, sorry to be pedantic, but this list is read by many people as well as arch

Re: manual beaming and variables

Hi Simon,Will remember to do next time. Thank you for letting me know.Ming. From: Simon Albrecht To: TSANGMING ; "gianmarial...@gmail.com" ; "lilypond-user@gnu.org" Sent: Sunday, August 27, 2017 7:33 AM Subject: Re: manual beaming and variables Hello Ming,

Re: manual beaming and variables

Hello Ming, sorry to be pedantic, but this list is read by many people as well as archived. It is important that you write an actual reply to the original e-mail (instead of composing a technically independent e-mail), since the internal In-Reply-To header is needed for correct organisation of

  1   2   3   4   5   6   7   8   >