Am Mo., 12. Nov. 2018 um 20:30 Uhr schrieb David Kastrup :
>
> Torsten Hämmerle writes:
>
> > David Kastrup wrote
> >> If you want a Staff, create it rather than rely on somebody else doing
> >> that, maybe.
> >
> > That is basically what I thought (and wrote), too.
> > But, admittedly, these
Am Mo., 12. Nov. 2018 um 05:36 Uhr schrieb Rohan Srinivasan
:
>
> Friendly bump.
Hi,
this was asnwered already:
http://lilypond.1069038.n5.nabble.com/Combining-lyric-verses-onto-one-line-tt217186.html#none
Didn't you get the replies?
Cheers,
Harm
Am So., 11. Nov. 2018 um 11:57 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Use \voiceTwo instead of \stemDown, then LilyPond will place the rest
> > correctly and the warning disappears.
>
> Sometimes I think we should undocument \stemUp/\stemDown.
Am So., 11. Nov. 2018 um 01:39 Uhr schrieb Joseph Srednicki
:
>
> Hello:
>
> The following measure causes Lilypond to issue a warning about too many
> colliding rests.
>
> Is there a way that I can code this measure to avoid the warning?
>
> I checked the online mail archive. I found a message
Am Mi., 27. Juni 2018 um 22:31 Uhr schrieb David Kastrup :
>
>
> Hi folks,
>
> I've been afraid of looking at my bank account for the past months but
> finally had to do so. For the last three months, the payments from
> LilyPond users were stable: one paying €100 monthly, one paying €75
>
Am Do., 8. Nov. 2018 um 21:00 Uhr schrieb Jérôme Plût :
>
>
> #(begin
> ; after http://lsr.di.unimi.it/LSR/Snippet?id=969
> (define-markup-command (with-background layout props color arg) (color?
> markup?)
>(let* ((stencil (interpret-markup layout props arg))
> (X-ext
Am Do., 8. Nov. 2018 um 10:10 Uhr schrieb David Kastrup :
>
> Jérôme Plût writes:
>
> > I would like to *read*, from within a Scheme function
> > (define-music-function), the values of variables such as
> > Score.currentBarNumber or Score.alternativeNumberingStyle.
> >
> > I can have a guess that
Am Mo., 5. Nov. 2018 um 13:24 Uhr schrieb David Sumbler :
>
> My subject line only partially describes the problem.
>
> I find that a tie is not shown after a line-break if the following
> conditions are all true:
> 1. There is a line-break (as stated)
> 2. There is a new time signature
> 3. There
Am Mo., 5. Nov. 2018 um 03:07 Uhr schrieb Aaron Hill :
>
> On 2018-11-04 2:12 pm, Rohan Srinivasan wrote:
> > Hi list,
> >
> > I have the following code for a short song I'm engraving:
> >
> > [ . . . ]
> >
> > Since all 3 verses have "That's" at the end of the line, I would like
> > to
> >
Am So., 4. Nov. 2018 um 16:38 Uhr schrieb pablocordal :
>
> Hi Urs and Torsten,
>
> This snippet is exactly what I need. I'm trying to test it, but when I copy
> your code in Frescobaldi (which uses Lilypond underneath) and try to compile
> it I receive this error:
>
> error: syntax error,
Am So., 4. Nov. 2018 um 01:30 Uhr schrieb David Nalesnik
:
>
> On Sat, Nov 3, 2018 at 7:24 PM David Nalesnik
> wrote:
> >
> > On Sat, Nov 3, 2018 at 7:23 PM Andrew Bernard
> > wrote:
> > >
> > > Hi David,
> > >
> > > Isn't Lilypond open source? Cant you make your code open source? I am not
>
Am Sa., 3. Nov. 2018 um 16:16 Uhr schrieb Thomas Morley
:
>
> Am Do., 1. Nov. 2018 um 16:21 Uhr schrieb Thomas Morley
> :
>
> > Furthermore, compiling your code with my guilev2-setup fails right
> > from the beginning with:
> > error: GUILE signaled an error for
Am Sa., 3. Nov. 2018 um 21:36 Uhr schrieb Ben :
>
> On 11/3/2018 4:25 PM, David Nalesnik wrote:
>
> On Sat, Nov 3, 2018 at 3:21 PM Ben wrote:
>
> On 11/3/2018 4:16 PM, David Nalesnik wrote:
>
> On Sat, Nov 3, 2018 at 2:57 PM Ben wrote:
>
> On 11/3/2018 2:54 PM, m...@opus11.net wrote:
>
> Just
Am Do., 1. Nov. 2018 um 16:21 Uhr schrieb Thomas Morley
:
> Furthermore, compiling your code with my guilev2-setup fails right
> from the beginning with:
> error: GUILE signaled an error for the expression beginning here
> #
> (load "motif.scm")
> Unable to find fil
Am Sa., 3. Nov. 2018 um 13:16 Uhr schrieb Sven Axelsson
:
>
> I want to auto generate a collection of short tunes by \include-ing the
> existing files. If there is room for it, I want to put several tunes on the
> same page, but I only want page breaks between tunes, never in the middle of
> a
Am Sa., 3. Nov. 2018 um 13:12 Uhr schrieb Thomas Morley
:
>
> Am Sa., 3. Nov. 2018 um 12:27 Uhr schrieb Federico Bruni :
>
> > The second staff at the bottom will be cropped.
> > This seems to happen (at least with above file) only with TabStaff,
> > DrumStaff, Rhyt
Am Sa., 3. Nov. 2018 um 12:27 Uhr schrieb Federico Bruni :
> The second staff at the bottom will be cropped.
> This seems to happen (at least with above file) only with TabStaff,
> DrumStaff, RhythmicStaff and VaticanaStaff, while other kinds of Staff
> works fine. Is this a good clue to
Am Do., 1. Nov. 2018 um 19:37 Uhr schrieb Jérôme Plût :
>
> Kalendis Novembribus MMXVIII scripsit Thomas Morley :
> > Part of the problem is you use 'structure as a music-property without
> > declaring it. As a consequence using the option -dcheck-internal-types
> > ma
Am Mo., 29. Okt. 2018 um 15:30 Uhr schrieb Jérôme Plût :
>
> I have a few questions about using Scheme to build Lilypond data.
>
> 1. I have some Scheme code that builds custom articulations (more
> precisely, it attaches metadata to NoteEvents, and the only way I found
> to make this possible is
Am Do., 1. Nov. 2018 um 16:24 Uhr schrieb Kieren MacMillan
:
>
> Hi Werner,
>
> > +1. I've *never* seen an ambitus except at the very beginning of a piece.
>
> I often use an ambitus in front- or end-matter, to give vocal ranges separate
> from the score itself. Of course, "front-matter" can be
Am Do., 1. Nov. 2018 um 14:44 Uhr schrieb Jérôme Plût :
>
>
> I wrote some macros to help write analysis of musical pieces.
> Here is an example file (on Bach's Invention I).
>
> Structural analysis is (of course) performed by hand, and displayed on
> a Lyrics structure on top of the music. (This
Am Mi., 31. Okt. 2018 um 19:09 Uhr schrieb Pierre-Luc Gauthier
:
>
> Hi there,
>
> Not sure if this is a bug or if I am using it wrong.
>
> I've started using :
> \consists "Mark_engraver"
> \consists "Bar_number_engraver"
> , etc
> inside StaffGroups since it is now working.
> (Fixed with I think
Am Mi., 31. Okt. 2018 um 18:11 Uhr schrieb joelhamme :
>
> My fellow singers in choir have been asking me to improve the visual chunking
> of choir staves. They wanted to have closed bar lines on the right edge of
> each choir staff.
>
> Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of
Am Mo., 29. Okt. 2018 um 12:10 Uhr schrieb David Sumbler :
>
>
> -Original Message-
> From: Thomas Morley
> To: David Sumbler
> CC: lilypond-user
> Subject: Re: Line-breaking with non-aligned barlines
> Date: Sun, 28 Oct 2018 02:01:04 +0200
>
> Am Fr., 26.
Am Mo., 29. Okt. 2018 um 07:58 Uhr schrieb Werner LEMBERG :
>
>
> >> If possible, this should be made the default. I even suggest to
> >> completely drop the current behaviour since I can't envision a
> >> situation where you really want this.
> >
> > I'll open an issue on the tracker.
>
>
Am So., 28. Okt. 2018 um 08:07 Uhr schrieb Werner LEMBERG :
>
> > A minimal would be:
> >
> > \paper { indent = 0 ragged-right = ##t }
> >
> > {
> > \override Beam.breakable = ##t
> > s2. s8
> > c'8[
> > \break
> > c'16]
> > }
> >
> > Not sure I'd call it a bug.
>
> IMHO, it is
Am Fr., 26. Okt. 2018 um 13:58 Uhr schrieb Thomas Morley
:
> currently I've not the time to dive deeper in your code, maybe later
> today or during the upcoming weekend.
Hi Urs,
I haven't looked deeply into your code, but I think it will not work as desired.
First some general words
Am So., 28. Okt. 2018 um 17:56 Uhr schrieb Kieren MacMillan
:
>
> Hi Harm,
>
> >\override BarNumber.after-line-breaking = #'()
>
> Whoa… What exactly does that do? It seems like a nuclear option!
>
> I’ll be sure to give it a try the next time I run into the issue (which
> should be very
Am So., 28. Okt. 2018 um 12:39 Uhr schrieb Simon Albrecht
:
>
> Hello list,
>
> I’m currently debugging a couple issues with a use case of the MarkLine
> context. One of them is demonstrated in the attached minimal scenario:
> with a MarkLine atop the topmost staff, the barnumbers fail to align
>
Am Fr., 26. Okt. 2018 um 23:52 Uhr schrieb David Sumbler :
> But as things are the break here is still unsatisfactory
> because the semiquaver just after the break has 2 long beams stretching
> back to the start of the line, whereas one would ideally want 1 long
> beam and a short one. I
Am So., 28. Okt. 2018 um 00:28 Uhr schrieb Kieren MacMillan
:
>
> Hi Harm,
>
> > your example works here out of the box and without any problem.
> > So I don't understand the problem.
>
> They’re nested, not interlocking/overlapping (as I want them to be).
> Even though I set the ids to be
Am So., 28. Okt. 2018 um 00:04 Uhr schrieb Kieren MacMillan
:
>
> Hi all,
>
> I’d like to use spanner-id (or similar) to interlock/overlap
> HorizontalBracket spanners.
> Is this possible?
>
> Thanks,
> Kieren.
>
> %%% MWE BEGINS
> \version "2.19.80"
> \layout { \context { \Voice \consists
Am Fr., 26. Okt. 2018 um 18:56 Uhr schrieb Thomas Morley
:
> << e { s1*15/320 \bar "" \ctxMom s } >>
Well, could be shortened to s1*3/64 and the \ctxMom-command should be
deleted after the duration is found,
Am Fr., 26. Okt. 2018 um 18:26 Uhr schrieb David Sumbler :
>
> Below I have shown a compile-able 93 lines (sorry it can't be made much
> shorter) from the files for a much longer piece.
>
> In this particular passage the harpsichord plays 4 bars in strict tempo
> whilst the flute plays 4 bars
Am Fr., 26. Okt. 2018 um 18:18 Uhr schrieb Hans Åberg :
>
>
> > On 26 Oct 2018, at 17:41, Thomas Morley wrote:
> >
> > But you could do (at least on Linux):
> >
> > lilydevel -e "(begin (define myhash (make-hash-table))(hashq-set!
> > myhash
Am Fr., 26. Okt. 2018 um 16:44 Uhr schrieb Peter Anglea :
>
> I’m trying to use the -e (--evaluate) option to define a hash, not just a
> single variable. For instance
>
> lilypond -e ‘((define myhash (make-hash-table))(hashq-set! myhash
> ‘foo “bar”))’ file.ly
>
> The above doesn’t
Am Fr., 26. Okt. 2018 um 15:41 Uhr schrieb Pierre Perol-Schneider
:
>
> Hi,
> Please consider the following example:
>
> %%
> \version "2.19.82"
> music =
> \fixed c' {
> \time 3/8
> \voiceOne
> 4. q
> }
> { \music } { \music } { \music }
> %%
>
> After trying several compilation, sometimes
Hi Urs,
currently I've not the time to dive deeper in your code, maybe later
today or during the upcoming weekend.
For now only about:
Am Fr., 26. Okt. 2018 um 11:54 Uhr schrieb Urs Liska :
> Additionally (but this is already present
> in your code) when using make-with-dimensions-markup (where
Hi Urs,
Am Do., 25. Okt. 2018 um 17:49 Uhr schrieb Urs Liska :
>
> Hi Harm,
>
> thank you for this. From the *behaviour* this seems like what I need, but I
> have a few questions that may make it not really usable for my case.
>
>
> Am 24.10.2018 um 18:25 schrieb Thoma
Am Do., 25. Okt. 2018 um 14:30 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Di., 9. Okt. 2018 um 01:24 Uhr schrieb David Kastrup :
> >>
> >> David Kastrup writes:
> >>
> >> > namely a bunch of Translator_creator s creating C
Am Do., 25. Okt. 2018 um 19:03 Uhr schrieb Pierre-Luc Gauthier
:
>
> Hi Thomas,
>
> > Yep, set-global-staff-size _must_ be set at top-level, outside of \book.
>
> That's good to know.
> The documentation got me going on using-it inside \book{}s.
>
Hi Pierre-Luc,
Am Mi., 24. Okt. 2018 um 16:01 Uhr schrieb Pierre-Luc Gauthier
:
>
> Hi there,
>
> Is this a bug?
>
> \version "2.21.0"
> %#(set-global-staff-size 4)
> \book {
> #(set-global-staff-size 4)
> \score {
> {\tempo 4=120 c4}
> \layout {}
> }
> }
>
> I'm trying to set the
Am Mi., 24. Okt. 2018 um 16:00 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Mi., 24. Okt. 2018 um 01:07 Uhr schrieb David Kastrup :
> >>
> >> Thomas Morley writes:
> >>
> >> > Am Di., 23. Okt. 2018 um 23:54 Uhr schrieb D
Am Di., 9. Okt. 2018 um 01:24 Uhr schrieb David Kastrup :
>
> David Kastrup writes:
>
> > namely a bunch of Translator_creator s creating C++ engravers (maybe the
> > print expression should at least mention _which_ C++ engraver in order
> > to make them look less similar)
>
> which is actually
Am Di., 23. Okt. 2018 um 08:28 Uhr schrieb Urs Liska :
>
> Hi,
>
> I want to use TextScript.staff-padding to produce markup elements that
> are aligned to their baseline. In order to prevent the texts from moving
> vertically to avoid collisions I used \textLengthOn (or its spelled-out
> variant):
Am Mi., 24. Okt. 2018 um 17:02 Uhr schrieb Ben :
> This should be what you need (see attached)
We do have 'number-format', so one could do:
#(define-public (format-roman-mark-numbers mark context)
(make-bold-markup (number-format 'roman-upper mark)))
#(define-public
Am Mi., 24. Okt. 2018 um 16:59 Uhr schrieb Ben :
>
> On 10/24/2018 10:39 AM, David Nalesnik wrote:
> Based on my reading of scm/translation.functions.scm, I have no idea
> why the following should not work:
>
> \version "2.19.82"
>
> \relative c'' {
> \set Score.markFormatter =
Am Mi., 24. Okt. 2018 um 01:07 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Di., 23. Okt. 2018 um 23:54 Uhr schrieb David Kastrup :
> >
> >> So you should figure out what your comparison as equal is supposed to be
> >> doing in the first
Am Di., 23. Okt. 2018 um 23:54 Uhr schrieb David Kastrup :
> So you should figure out what your comparison as equal is supposed to be
> doing in the first place.
Yep, that's the culprit.
So the question is how to find the last rhythmic event of a
music-expression and place <>\stopTextSpan right
Am Mo., 22. Okt. 2018 um 21:59 Uhr schrieb Torsten Hämmerle
:
>
> Hi Harm,
>
> All these numbers are quite confusing at first glance. And at second and
> third glance, too.
> But they are nothing but conversion factors to switch units.
> And, unfortunately, LilyPond basically uses three concurrent
Hi,
for some reason I wanted a music-function which should end a
TextSpanner automagically at the next event which starts a new
TextSpanner or the last possible event at all.
Although it needs further testing I already found a glitch I really
can't explain or cope with: Sometimes, when the
Hi Torsten,
I've created
https://sourceforge.net/p/testlilyissues/issues/5430/
Am So., 21. Okt. 2018 um 21:33 Uhr schrieb Torsten Hämmerle
:
>
> Thomas Morley-2 wrote
> > I like to understand the numerical values.
> > The pair (-0.443862992125984 . 1.09258582677165) seems to
Hi Torsten,
Am So., 21. Okt. 2018 um 17:17 Uhr schrieb Torsten Hämmerle
:
>
> Hi Harm,
>
> As it looks like, this function has not been working for some time, I've
> tested it back to 2.14.2
I even checked with 2.12.3 (without useful result)
> What does it do?
>
> In lily/stencil-interpret.cc,
Hi,
in the IR one can find:
"
Function: ly:stencil-fonts s
Analyze s, and return a list of fonts used in s.
"
Though, how to get some output from it?
At least the code below returns nothing relevant.
(I used old syntax to check with all lily-version available, i.e.
since 2.12.3 up to 2.21.0)
Am So., 21. Okt. 2018 um 09:27 Uhr schrieb Jean-Julien Fleck
:
>
> Thanks a lot Harm, it works perfectly !
A further thought:
Currently the code will return TextScript not Fingering. Thus we need
to mimic aligning/fontsize like Fingering and loose the possibility to
apply
Am Sa., 20. Okt. 2018 um 23:11 Uhr schrieb Jean-Julien Fleck
:
>
> Hi everyone,
>
> I have been searching how to indicate some optionnal finger indication in
> parenthesis but found no direct way. I ended up using some quite complicated
> hack:
>
> doigte = \markup { \halign #-0.5 \override
Am Do., 18. Okt. 2018 um 11:32 Uhr schrieb Thomas Morley
:
> I made some mistakes while typing
> the "1{2{3 4 5)|#6 7)8) 9 1)"
>
> Ok, make that "several mistakes"
Ok, one could enter it using new indented lines (the code is able to
cope wi
Am Mi., 17. Okt. 2018 um 21:40 Uhr schrieb David Wright
:
>
> On Wed 17 Oct 2018 at 15:43:40 (+0200), Thomas Morley wrote:
>
> > I'd like to propose the code below. Attached as well.
> >
> > It stores the info in a string, which is converted to
Am Mi., 17. Okt. 2018 um 15:43 Uhr schrieb Thomas Morley
:
> I'd like to propose the code below.
>
> It stores the info in a string, which is converted to a nested list
> suitable for 'systemStartDelimiterHierarchy'. It can be nested in
> arbitrary depth.
>
> I use
Hi Lukas-Fabian,
I finally found the time to look deeper into it.
Am So., 14. Okt. 2018 um 15:07 Uhr schrieb Lukas-Fabian Moser :
> For me, there are the following issues with the systemStartDelimiterHierarchy
> design:
>
> 1) There's an overlap between systemStartDelimiter and
>
Hi Lukas-Fabian,
Am So., 14. Okt. 2018 um 15:07 Uhr schrieb Lukas-Fabian Moser :
> Though, the whole thread mixes up different topics.
>
> I'm not sure, tbh. Of course, setting delimiters and setting spacing should
> be thought of as mostly orthogonal aspects of setting up a score. The
>
oid-function ()() (write (*location*)))
{ R1 \foo R1 }
In my case it display in terminal:
#
i.e. a certain line and column
Cheers,
Harm
>> Thomas Morley schrieb am Fr., 12. Okt. 2018,
>> 10:29:
>>>
>>> Am Fr., 12. Okt. 2018 um 08:10 Uhr schrieb Jan-Peter Voigt
&
Am Sa., 13. Okt. 2018 um 11:56 Uhr schrieb foxfanfare :
>
> Lukas-Fabian Moser wrote
> > I disagree that LP does not follow the standard engraving rules. It just
> > seems to me that \new GrandStaff etc. imply a certain semantics which is
> > perfectly alright for, e.g., an orchestral Piano part,
Hi Urs,
Am Sa., 13. Okt. 2018 um 00:00 Uhr schrieb Urs Liska :
> > %% Not sure if needed, though, better be paranoid and work on a copy of
> > %% default-script-alist to avoid possible bleed-over.
> > #(define my-script-alist default-script-alist)
>
> Except that this doesn't *create* a copy but
Am Fr., 12. Okt. 2018 um 20:57 Uhr schrieb Urs Liska :
>
> Hi Harm,
>
>
> Am 12.10.2018 um 18:58 schrieb Thomas Morley:
> > Hi Urs,
> >
> > not sure I understand correctly, probably something like below?
> >
> > one = \markup \score { d'1 }
> &g
Am Fr., 12. Okt. 2018 um 17:52 Uhr schrieb Urs Liska :
>
> Hi,
>
> basically this is a follow-up question to the one where I needed to
> align a text over a slur. I wanted to apply the techniques I learned
> from your valuable help but ran against the next wall (or: I didn't see
> that there is no
Hi Urs,
sorry for the late reply.
Right now I've a cold (not working in my regular job), so I've more
time to look into lilypond-tasks.
While waiting for a guile-complie to finish...
Am So., 30. Sep. 2018 um 12:01 Uhr schrieb Urs Liska :
> Creating a new articulation (or overwriting the
Am Fr., 12. Okt. 2018 um 09:59 Uhr schrieb Urs Liska :
> What is 'interval-center'? Grepping the source doesn't show a
> definition, so I'd assume it's in the C++ domain? I haven't found
> anything about that in the documentation (or through Google).
Hi Urs,
~/lilypond-git (master)$ git grep
Am Fr., 12. Okt. 2018 um 08:10 Uhr schrieb Jan-Peter Voigt :
>
> Hello Sebastian,
>
> what do you mean with "return"? Do want to add the score immediatly or
> do you want to return an object containing both?
> You used the parser-location arguments in your scheme-function, so I
> guess you are
Am Di., 9. Okt. 2018 um 16:54 Uhr schrieb Urs Liska :
>
> Hi,
>
> I have a custom \path markup, implemented as an event function.
>
> This works well, but when I add a slur I don't manage to get it to
> behave it properly. What I want is to print the vertical lines and then
> outside the slur,
Am Di., 9. Okt. 2018 um 00:47 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Well, I'm a little confused about translators and translator-creators
> > (I use the hyphen to make the wording more obvious).
> > Not the least reason is:
> > #(prett
Am Mo., 8. Okt. 2018 um 23:50 Uhr schrieb David Kastrup :
> ly:get-all-translators gets the _globally_ registered translators, those
> you can access with a _string_ as reference (should be a symbol,
> really).
>
> > So _registering_ them makes testI/II translators,
>
> No, translator creators
Am Mo., 8. Okt. 2018 um 12:28 Uhr schrieb Jogchum Reitsma :
>
> Op 06-09-18 om 09:43 schreef Thomas Morley:
> > 2018-09-05 11:15 GMT+02:00 Jogchum Reitsma :
> >> Hi,
> >>
> >> The first bar of part 5: Ecce gratum, from Orff's Camina Burana states a
>
Am So., 7. Okt. 2018 um 22:28 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am So., 7. Okt. 2018 um 18:00 Uhr schrieb David Kastrup :
> >>
> >> Thomas Morley writes:
> >>
> >> > If you have too much time, you may have
Am So., 7. Okt. 2018 um 18:00 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > If you have too much time, you may have a look at ‘scheme-engraver.ly’
> > from
> > http://lilypond.org/doc/v2.13/input/regression/collated-files.html The
> > newer file use
Am So., 7. Okt. 2018 um 19:53 Uhr schrieb Peter Crighton
:
> How would I go about either shifting the parentheses vertically or making
> them smaller? They probably make sense how they are now with regard to
> sharps/flats and possible lowercase letters, but they still look off,
> especially
Am So., 7. Okt. 2018 um 15:59 Uhr schrieb Aaron Hill :
>
> On 2018-10-07 4:29 am, Thomas Morley wrote:
> > Below my own attempt using an engraver (to have access to the
> > 'timeSignatureFraction, a context-property, and to Stem/NoteHead-grobs
> > in one go).
> > [
Am So., 7. Okt. 2018 um 00:55 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Sa., 6. Okt. 2018 um 23:48 Uhr schrieb Peter Crighton
> > :
> >>
> >> Hello all,
> >>
> >> I need the bass note of a chord symbol to be in paren
Am So., 7. Okt. 2018 um 07:31 Uhr schrieb Aaron Hill :
>
> On 2018-10-06 10:01 am, Daniel Sales wrote:
> > Hi, is it possible to identify the beats on each different timing
> > automatically, in order to set a different color for strong, medium
> > and weak beats ?
> The biggest hurdle as I see
Am Sa., 6. Okt. 2018 um 23:48 Uhr schrieb Peter Crighton
:
>
> Hello all,
>
> I need the bass note of a chord symbol to be in parentheses, like so:
> C(/G)
>
> How could I achieve this? I am, sadly, clueless.
>
> \version "2.19.82"
> \new ChordNames {
> \chordmode {
> % like this, but with
Hi,
Am Fr., 5. Okt. 2018 um 12:53 Uhr schrieb Tom Campbell :
>
> I'm writing multiple pages of text and noticed that the bottom margin wasn't
> being observed. I think it's because I'm placing the whole chapter inside a
> \markup. I can't seem to find a cohesive explanation of \markup all in
Am Mi., 3. Okt. 2018 um 00:38 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Di., 2. Okt. 2018 um 23:17 Uhr schrieb David Kastrup :
> >
> >> So what is wrong with using \"var2" or \var.2 ?
> >
> > As a side note.
> >
&g
Am Di., 2. Okt. 2018 um 23:17 Uhr schrieb David Kastrup :
> So what is wrong with using \"var2" or \var.2 ?
As a side note.
I wasn't aware a comma works as well
qwerty,2 = "bar"
Although, while calling it, you _must_ use the dot
\new Lyrics \lyricmode { \qwerty.2 }
Cheers,
Harm
Am Di., 2. Okt. 2018 um 23:17 Uhr schrieb David Kastrup :
> So what is wrong with using \"var2" or \var.2 ?
Ah, I forgot about var.1 etc
Ofcourse below is a bit ugly I'd say:
val.1 = "foo"
<<
\new Staff \repeat unfold 4 c'4
\new Lyrics \lyricmode { \val.1 4 \val.1 2 \val.1 4 }
>>
Another
Am Di., 2. Okt. 2018 um 22:37 Uhr schrieb Kieren MacMillan
:
>
> Hi Harm,
>
> > val = "foo"
> > <<
> > \new Staff \repeat unfold 4 c'4
> > \new Lyrics \lyricmode { \val4 \val2 \val4 }
> > \new Lyrics \lyricmode { \val4 \val4 \val2 }
> >>>
> >
> > Your proposal would make it impossible.
>
>
Am Di., 2. Okt. 2018 um 21:57 Uhr schrieb Kieren MacMillan
:
> If I were developing Lilypond code, I simply wouldn’t allow a note value to
> be post-fixed to a variable, so
>
>\part2
>
> would have only one interpretation (i.e., as the variable "part2"). But
> that’s only because I can’t
Hi,
Am Di., 2. Okt. 2018 um 01:59 Uhr schrieb Tom Campbell :
>
> I want vertical space to occur after a heading. But it seems that the
> following still puts the space before it, or am I going insane?
I'm not sure what you want to achieve.
Nevertheless you could visualize what you've done. I.e.
2018-09-24 9:04 GMT+02:00 Noeck :
> Dear David,
>
> I might be wrong, but I think it is some font problem.
Most likely, I'd say.
Could you try:
\version "2.19.81"
#(define ((time-parenthesized-time up down upp1 downp1 upp2 downp2) grob)
(grob-interpret-markup grob
(markup
2018-09-22 17:29 GMT+02:00 Gianmaria Lari :
> This code write some fingering on "b" pitch.
>
> \version "2.19.82"
> {b4\finger\markup {2 \circle 3 2} \prall}
>
>
> .. and here it is the result:
>
> [image: image.png]
>
> This is ok except the fact that the elements 2 (3) 2 are written not
>
2018-09-22 8:53 GMT+02:00 Aaron Hill :
> On 2018-09-21 8:11 pm, Juan Cristóbal Cerrillo wrote:
>>
>> Hello,
>>
>> This snippet (Notation Reference 1.6.1) works fine on 2.18.2-1 but is
>> incorrect on 2.19.82-1 (the SystemStartSquare on staff b vanishes).
>>
>> \new StaffGroup
>> \relative c'' <<
2018-09-20 10:37 GMT+02:00 foxfanfare :
> James Harkins-4 wrote
>> That's exactly it. Thanks!
>>
>> Would be useful as a snippet perhaps... this totally eluded me in the
>> manual. I tried to find info about bound-details but missed it somehow.
>>
>> hjh
>
> I agree, I learnt more about
2018-09-18 11:13 GMT+02:00 Urs Liska :
>
>
> Am 18.09.2018 um 11:09 schrieb Urs Liska:
>>
>> Hi Harm,
>>
>> thank you very much!
>>
>>
>> Am 17.09.2018 um 22:35 schrieb Thomas Morley:
>>>
>>> 2018-09-17 12:05 GMT
2018-09-17 12:40 GMT+02:00 Bernhard Kleine :
> I found it.
> However without the -"legato" the \f is centered , with the -"legato" it is
> not. How to draw them on the same line?
>
> dynOrgel = {
> {
>s2\f s4-"legato"
> }
> }
>
\new Dynamics = "dynOrgel"
\with { \override
2018-09-17 12:05 GMT+02:00 Thomas Morley :
> 2018-09-17 11:55 GMT+02:00 Urs Liska :
>> thanks for this, which gives me a handle to the first part of the hairpin at
>> least.
>>
>> But my problem is not solved with the 'height property.
> [...]
>
>> See m
2018-09-17 11:55 GMT+02:00 Urs Liska :
> thanks for this, which gives me a handle to the first part of the hairpin at
> least.
>
> But my problem is not solved with the 'height property.
[...]
> See my updated example
[...]
I'll have a look in the evening, now I have to run for my regular job
2018-09-17 8:43 GMT+02:00 Urs Liska :
> I have a broken hairpin whose first part is pretty short. As a consequence
> its internal angle looks too wide for my taste (see attached PNG). I would
> like to have the two lines wider apart with a narrower angle to more
> adequately reflect the overall
2018-09-09 19:47 GMT+02:00 Kieren MacMillan :
> Hi Joram,
>
> How is your Scheme-fu?
> Maybe you can adapt one of the snippets that applies different tweaks (e.g.,
> color, shape) to notes of different duration.
Hi Joram,
a walk-through:
(1) Create code example:
{ r2 r1 }
(2) Initiate a most
2018-09-08 22:15 GMT+02:00 Kieren MacMillan :
> Hi Joram,
>
>> you can set the positions by hand (in staff spaces):
>
> Well, I had tried that in my real-world (non-MWE) example… but it didn’t seem
> to work:
>
> \version "2.19.80"
>
> upper = {
> \time 3/4
> 2.\arpeggio
> \once \override
2018-09-07 16:39 GMT+02:00 Lukas-Fabian Moser :
> I took this as an intencive to take a stab at delving into the source code
> (which I always did read-only up to now). I think I managed to create a
> working branch from current master (I also never got the hang of git...) that
> allows for
2018-09-05 11:15 GMT+02:00 Jogchum Reitsma :
> Hi,
>
> The first bar of part 5: Ecce gratum, from Orff's Camina Burana states a
> time of 4 \breve notes. In the Schott-edition I have, that is noted not on
> the staff, but above it.
>
> Is there a possiblility in Lilypond to define that time? Simpy
901 - 1000 of 3885 matches
Mail list logo
