Understanding ly:parser-include-string

Hi, I'm running into an issue with including files using ly:parser-include-string. The underlying task is that I want to conditionally include files, so I have the pseudo-code: #(if (some-condition) (ly:parser-include-string "\\include \"some-file.ily\"")) This works pretty well for single

Re: Understanding ly:parser-include-string

Urs Liska writes: > Hi, > > I'm running into an issue with including files using > ly:parser-include-string. > > The underlying task is that I want to conditionally include files, so I > have the pseudo-code: > > #(if (some-condition) > (ly:parser-include-string "\\include \"some-file.ily\""

attach glissandi to stems instead of noteheads

I'm trying to draw a suggestion for glissando in changing directions. The ideal notation would be beamed stems without note heads connected by glissandi. Here's what I got so far: \version "2.19.35" \relative c' { \override NoteHead.stem-attachment = #'(0 . 0) \hide NoteHead \override Glis

Re: Understanding ly:parser-include-string

Am 27.01.2016 um 18:22 schrieb David Kastrup: > Urs Liska writes: > >> Hi, >> >> I'm running into an issue with including files using >> ly:parser-include-string. >> >> The underlying task is that I want to conditionally include files, so I >> have the pseudo-code: >> >> #(if (some-condition) >>

Re: attach glissandi to stems instead of noteheads

I think I got it. It's a bit of an ugly code, but works. \version "2.19.35" \relative c' { \override NoteHead.stencil = #ly:text-interface::print \override NoteHead.text = \markup { \null } \override NoteHead.stem-attachment = #'(0 . 0) \override Glissando.thickness = #5 \override Glissand

Re: attach glissandi to stems instead of noteheads

Hi Caio, How about: \version "2.19.35" #(define path-gliss (lambda (handle) (lambda (grob) (if (ly:stencil? (ly:line-spanner::print grob)) (let* ((stencil (ly:line-spanner::print grob)) (X-ext (ly:stencil-extent stencil X)) (Y-ext (ly:stencil-extent stencil Y))

Re: attach glissandi to stems instead of noteheads

Well, you can see that this code is much bigger than mine. I'm a bit uncomfortable because I don't have yet the lilypond-scheme vocabulary to understand it. OTOH, it has a more convenient syntax, not needing to add a \glissando in every note. It should be a good solution for longer passages. I

Beam/fermata collision avoidance?

Hello List, is there any way to avoid the collision between fermata and beam in the following snippet? \version "2.19.36" \relative c'' { b8 b,\fermata r4 r2 } I'm surely missing something, but I don't find the override to control fermata spacing. Cheers, A _

Re: How to hide or remove the bars connecting an ossia staff

You're very welcome! Just one thing - although in this case it seems not really neccessary, it's good practice to reply to the list, mainly so that others can see that the problem has been solved. Otherwise, someone else, not realising that you already have a solution, might invest time in loo

Re: Beam/fermata collision avoidance?

Hi Andrew, > is there any way to avoid the collision between fermata and beam in the > following snippet? Multiple ways, actually. Here’s one option: \version "2.19.36" \relative c'' { b8 b,-\tweak padding 1.5 -\fermata r4 r2 } > I don't find the override to control fermata spacing. [\onc

Re: attach glissandi to stems instead of noteheads

2016-01-27 19:38 GMT+01:00 Caio Giovaneti de Barros : Well, you can see that this code is much bigger than mine. > Yep, plus some copy/paste errors. So here again: \version "2.19.32" #(define path-gliss (lambda (grob) (if (ly:stencil? (ly:line-spanner::print grob)) (let* ((stenc

Re: attach glissandi to stems instead of noteheads

Sorry, too fast: #(define (add-gliss m) (case (ly:music-property m 'name) ((NoteEvent) (set! (ly:music-property m 'articulations) (append (ly:music-property m 'articulations) (list (make-music (quote GlissandoEvent) m)

Re: Piano pedal mark collision (\sustainOn, \sustainOff)

Hi! No one played with positions of \sustainOn and \sustainOff? On Sat, Jan 23, 2016 at 1:33 PM, Przemyslaw Pawelczyk wrote: > I have a problem with \sustainOn and \sustainOff colliding each other > in some cases. > I use following pattern > > s32*31\sustainOn s32\sustainOff [...] > but it o

Re: attach glissandi to stems instead of noteheads

Sorry I was in a hurry few minutes ago and I simply copy/paste an old coding. Well, having some more time and re-reading the code I've seen some minor things: \version "2.19.35" %%% Credit to the LSR => http://lsr.di.unimi.it/LSR/Item?id=82 #(define (add-gliss m) (case (ly:music-property m 'na

Sustain pedal cautionary after line break

I would like to add a cautionary indication that the sustain pedal should remain pressed after a line break, so in the code below ideally there would be a (Ped.) in the second line. Any suggestions? \version "2.19.35" \relative c'' { \set Staff.pedalSustainStyle = #'mixed c1\sustainOn \brea

Re: Beam/fermata collision avoidance?

Thanks for the tips, guys. I think the -\tweak… method works best for me, so I'll go with that. I can't put the fermata underneath, because the voice is in the middle of an ensemble where all the other fermati are on top. But that's a handy tip, just in case it comes up again. Cheers, A On Wed,

RE: Piano pedal mark collision (\sustainOn, \sustainOff)

Przemyslaw, If acceptable, the use of "bracket" style can eliminate the conflict. Mark -Original Message- From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Przemyslaw Pawelczyk Sent: Wednesday, January 27, 20

Re: Sustain pedal cautionary after line break

Hi Caio, > I would like to add a cautionary indication that the sustain pedal should > remain pressed after a line break, so in the code below ideally there would > be a (Ped.) in the second line. Any suggestions? 1. Wait for the feature to be implemented — it’s being discussed/considered at t

Re: Piano pedal mark collision (\sustainOn, \sustainOff)

Hi, > No one played with positions of \sustainOn and \sustainOff? Well, I took a couple of seconds, and failed. Then, just now, I realized there’s a possible solution: I don’t know if markup (or even “fake markup”) support

Re: Sustain pedal cautionary after line break

Hi Caio, Here's a possible workaround: \version "2.19.35" \relative c'' { \set Staff.pedalSustainStyle = #'mixed c1\sustainOn \break c1 c1\sustainOff } sustOn = #(define-event-function (parser location)() #{ \tweak bound-details.left.text \markup\concat { \musicglyph #"pedal.Ped

Re: Sustain pedal cautionary after line break

Hi Kieren, I do not understand how you reduce the ped. spanner with a markup: \version "2.19.35" \relative c'' { \set Staff.pedalSustainStyle = #'mixed c1\sustainOn \break c1 _\markup\concat { \musicglyph #"pedal.Ped" ". " } c1\sustainOff } Could you tell me a little more? Cheers, Pierre

Fwd: [MEI-L] Registration Open: Music Encoding 2016

Forwarding this and asking for further distribution. >From last year's experience I can say that the Music Encoding Conference is a very fruitful event if one is interested in any of the discussed topics. Anybody within reach of Montréal should consider it. Best Urs Weitergeleitete Nac

Re: Sustain pedal cautionary after line break

On 27-01-2016 19:30, Pierre Perol-Schneider wrote: Hi Caio, Here's a possible workaround: Awesome, Pierre! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Sustain pedal cautionary after line break

Hi Pierre, > Could you tell me a little more? Here’s a tweaked-up example: \relative c'' { \set Staff.pedalSustainStyle = #'mixed c1\sustainOn \break c1 -\tweak extra-offset #'(-4 . -0.9) -\tweak whiteout-style #'outline -\tweak whiteout 3 -\tweak layer 2 _\markup \concat { ( \musicglyph

Re: Sustain pedal cautionary after line break

Thank you Kieren. Cheers, Pierre 2016-01-27 23:00 GMT+01:00 Kieren MacMillan : > Hi Pierre, > > > Could you tell me a little more? > > Here’s a tweaked-up example: > > \relative c'' { > \set Staff.pedalSustainStyle = #'mixed > c1\sustainOn \break > c1 -\tweak extra-offset #'(-4 . -0.9) -\tw

Re: Sustain pedal cautionary after line break

Thank you Caio, I'm glad you like it. Here are some minor corrections: sustOn = #(define-event-function (parser location)() #{ \tweak bound-details.left.text \markup\concat { \musicglyph #"pedal.Ped" ". " } %\tweak bound-details.left-broken.text \markup\concat { \musicglyph #"pedal

verbose markups?

I know that the \set stanza = "" is reformatted to be bold. I would like to changes this to regular (not bolded). Is this possible? This does relate to other environments, such as the subtitle, etc. ​Sincerely, Josh ___ lilypond-user mailing list lilyp

Reversing order of colliding noteheads?

In the following two-bar snippet, I used \voiceOne and \voiceTwo to place Tenor and Lead vocal lines on a single staff. The Tenor has a tied-over note, whose notehead collides at the beginning of the second bar with the Lead note, one step away. LilyPond places the Lead note inside of the Tenor tie

Re: verbose markups?

Josh, On Wed, Jan 27, 2016 at 7:45 PM, Joshua Nichols [via Lilypond] < ml-node+s1069038n186566...@n5.nabble.com> wrote: > I know that the \set stanza = "" is reformatted to be bold. I would like > to changes this to regular (not bolded). Is this possible? > It is! Two easy ways, actually: 1. \o

Re: Reversing order of colliding noteheads?

Michael, On Wed, Jan 27, 2016 at 10:51 PM, Michael J. O'Donnell [via Lilypond] < ml-node+s1069038n186567...@n5.nabble.com> wrote: > In the following two-bar snippet, I used \voiceOne and \voiceTwo to > place Tenor and Lead vocal lines on a single staff. The Tenor has a > tied-over note, whose not