Re: centralising markups above notes

Hi Jean, On 09/04/2021 15:36, Jean Abou Samra wrote: What you are doing is more or less the proper way. Objects have two parameters for alignment because it should depend on both the extents of the aligned object and its parent. This was briefly discussed in this recent thread:

Re: centralising markups above notes

Hi David, On 09/04/2021 12:32, David Kastrup wrote: Where does the documentation suggest that \center-align (and similar) does anything to a single item?  It aligns the things passed to it, not their outside. See the Text alignment section in

centralising markups above notes

Hi everyone, I'm trying to add centred string numbers to some notes in my composition using markup. Using only \center-align as the documentation suggests does not seem to do the trick, as the text is still not centralised. I am only able to get them properly centred when I set

Re: Cowell clusters

Hi Thomas, Thank you so much for the files, this is super useful! Cheers, Gilberto On 24/12/2020 20:38, Thomas Morley wrote: Hi Gilberto, I reworked the code, see https://lilypondforum.de/index.php/topic,820.msg4562.html#msg4562 You'll need an account there to get the files, thus I attach

Re: Cowell clusters

Hi Klaus, thanks for your reply! Yes, that function is great, that's the kind of thing I am looking for! This is already so much better than working on it manually. I have tweaked it a bit to my liking, particularly by setting \tweak Stem.thickness #6 for the stem that represents the cluster. I

Cowell clusters

Hi everyone, I am notating a score which uses a lot of clustered chords, to be notated in the style of Henry Cowell. I found a post from 2008 from the Lilypond user list but the solution is very cumbersome, unfortunately. The code below is adapted from that post: (

Re: Scores of Beauty

AM Gilberto Agostinho <mailto:gilbertohasn...@googlemail.com>> wrote: Hi everyone, When I try accessing the Scores of Beauty blog, I get an error message from WordPress. Just thought I would flag it here. Best, Gilberto

Scores of Beauty

Hi everyone, When I try accessing the Scores of Beauty blog, I get an error message from WordPress. Just thought I would flag it here. Best, Gilberto

Re: collisions between tuplet numbers and accidentals

Hi Knute, Thank you so much for the quick reply! On 11/12/2020 17:37, Knute Snortum wrote: Try this: %%% \version "2.20.0" {       \override TupletBracket.outside-staff-priority = 1000       \tuplet 3/2 {          f'2          r8          ges''4.          aes'2      }      \tuplet 5/4 {      

collisions between tuplet numbers and accidentals

Hi everyone, I am having an issue with collisions between tuplet numbers and accidentals. Is there a good way of handling these other than manually tweaking every single tuplet in the score? Example: \version "2.20.0" { \tuplet 3/2 {     f'2     r8     ges''4.     aes'2

Re: restating clef and StaffGroup brace after \startStaff

Hello Jean, Thank you so much for your reply, this is a great solution! On 21/10/2020 17:47, Jean Abou Samra wrote: > I would rather create separate systems and stack them in markups. This works wonderfully well. I adapted the function you wrote in order to control whether time signatures and

restating clef and StaffGroup brace after \startStaff

Hello, Does anyone know if it would be possible to restate a staff's clef and a StaffGroup's brace after the \startStaff command? I am again trying to create a diagram showing non-consecutive measures side by side. I am able to set the bar numbers of these measures to arbitrary values as I

Re: Removing bar connecting grouped staves

Hi everyone, Thank you so much for all your replies. Omitting Score.SystemStartBar did the trick for me, the diagram looks great now! (for some reason, StaffGroup.SpanBar did not work over here). This will be super handy for the rhythmic diagrams I'm doing for my dissertation, thank you so

Removing bar connecting grouped staves

Hi everyone, I am trying to create a diagram using Lilypond and I would like to remove the vertical bar connecting a series of grouped staves. This is the bar that is in the left hand side of a score and runs through all staves, and where instrument names are normally written. Would it be

Re: Using showStaffSwitch only for non-beamed notes

Aaron Hill wrote > Something like this might work This works really great, Aaron! Thank you so much! Best, Gilberto -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

Re: Using showStaffSwitch only for non-beamed notes

Aaron Hill wrote > Something like this might work This works really great, Aaron! Thank you so much! Best, Gilberto -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

Using showStaffSwitch only for non-beamed notes

Hi all, Would anyone have an idea of how could I use \showStaffSwitch only for non-beamed notes? I think these switch lines tend to be omitted when notes are beamed, since the voicing is obvious in those cases. Right now I can manually create them using \glissando lines, but would there be a more

Re: Beams over rests and concaveness

Hi Carl, Thank you so much for the reply, I will report this in the bugs subforum. Also, thanks for the workaround, I will use it for the moment being. Best, Gilberto -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

Beams over rests and concaveness

Hi everyone, It seems that the beam concaveness value is ignored when beaming over rests, in the case of a single note with a single rest. This happens with and without stemlet. See the code and score below, the groups marked with an asterisk should have been flat (+inf.0 concaveness): \version

Beams over rests and concaveness

Hi everyone, It seems that the beam concaveness value is ignored when beaming over rests, in the case of a single note with a single rest. This happens with and without stemlet. See the code and score below, the groups marked with an asterisk should have been flat (+inf.0 concaveness): \version

Unusual beam divisions

Hi all, I am dealing with some unusual beam divisions. See: and I did manage to emulate this style but I am using a hack to get it done: multiplying an eighth note by 1/4 to

Re: MIDI tick resolution

Hi Karl, thanks for your reply! Karl Hammar wrote > The technical limitation of midi file format is that the tick is a > 15bit quantity, i.e. the maximum value is 2^15-1 = 32767. > > [...] > > So you can't get 128*9*5*7 = 40320, but 64*9*5*7 = 20160 is possible, > and if you really need

Re: MIDI tick resolution

Just one more example, this time from old music, from Beethoven's/ Sonata Pathétique/. Look at the last beat of the last bar in the image below: At 384 PPQ, the very last beat is a quarter note

Re: MIDI tick resolution

Hi all, thanks for all replies. I will not enter on the merit of what can be perceived by ear or not at a reasonable tempo, we already have plenty of that in the audio parameter wars (44100 vs 48000 Hz, 16 vs 24 bit, etc.) But akin to those, it's a fact that modern DAWs have much higher MIDI tick

Re: MIDI tick resolution

Hi all, thanks for all replies. I will not enter on the merit of what can be perceived by ear or not at a reasonable tempo, we already have plenty of that in the audio parameter wars (44100 vs 48000 Hz, 16 vs 24 bit, etc.) But akin to those, it's a fact that modern DAWs have much higher MIDI tick

MIDI tick resolution

Hi all, Does anyone know if it possible to change the tick resolution of LilyPond's MIDI output to a value other than the default 384? One reason for wanting this change is due to the fact that 384 cannot be divided by 5 and so quintuplets on a crotchet are not precise. For instance, the default

Re: custom articulation position

caagr98 wrote > What you're doing is just creating a text script, not an articulation. I > use the following code to create a custom real articulation; you'll > obviously have to adapt some of it to fit yours. Fantastic, thank you so much! This solves both of my problems! For anyone interested,

custom articulation position

Hi all, I am having a bit of trouble trying to create a custom articulation in LilyPond. At the moment I have the following code: % \version "2.19.53" doubleAccent = \markup { \halign #-0.72 \combine \musicglyph #"scripts.sforzato" \raise #1.1

Re: Position of rests inside beamed groups

Hello Harm, Thanks for your reply. Thomas Morley-2 wrote > Best I can think of is: > > { > \override Staff.Stem.stemlet-length = #1.25 > c'16[ d' > \once\override NoteColumn.X-offset = 1 > r deses'] > } This works quite well! I've made some quick tests and the scores are looking much

Position of rests inside beamed groups

Hello all, I am writing a composition in which all rests inside beamed groups have stemlets. The problem is that because of my use of accidentals on every single note and because spacing is sometimes a bit critical, there is very little space between the rests's stemlets and the previous regular

Re: Circled numbers for live electronics

Thomas Morley-2 wrote > Approved now as > "Circled numbers for live electronics" Great, thanks a lot, Thomas! Cheers, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/Circled-numbers-for-live-electronics-tp197953p198651.html Sent from the User mailing list

Re: Circled numbers for live electronics

Hi Thomas, Thomas Morley-2 wrote > I had a look into your code here: > http://lsr.di.unimi.it/LSR/Item?u=1=1047 > and now come up with the shortened version below. > What do you think? Thanks a lot for the feedback, the shortened versions you posted are looking very nice. It's quite clever to

Re: Better slashed graces

Hi Andrew, Thanks for your reply! Andrew Bernard wrote > You may not be aware of my detailed work on slashed beams and slashed > stems > that I recently contributed to openlilylib. Theres a function that > provides > fine control over the parameters of beam slashes, and which works on the >

Re: Better slashed graces

Hi David, David Nalesnik wrote >> I think the function needs >> something like "if there is a beam, then add a slash, else if no beam >> then >> no slash". Do you think you could give me a hand with that? > > Sure, that's no problem. And it looks a bit cleaner than what I went > in the last

Re: Better slashed graces

Hi David, First of all, thanks for your reply and for your help! David Nalesnik wrote > The problem is that there is no Beam grob, so an error is raised when > you query its properties. I see! > Following is a simple way to use substitute values when there is no Beam > object. This modified

Re: Better slashed graces

Hi all, I just discovered a bug with my function above. It turns out the function works well when there are two of more notes inside the \slashedGrace{}, but when a single note is there the file does not compile. I believe I need a conditional somewhere to take care of this but I don't really

Re: Markup and staff spacing

Hi Simon, Simon Albrecht-2 wrote > try wrapping the markup in > \markup { >\with-dimensions-from \null { >% insert your markup here > } Thanks for your reply, that's exactly what I was looking for! I really appreciate your help. Cheers, Gilberto -- View this message in context:

Markup and staff spacing

Hello all, Is there a way to make LilyPond ignore collisions or spacing issues between a markup text and other staves or grobs? For instance, consider this example below: \version "2.19.37" \new PianoStaff << \new Staff { des''4 f'' e'_\markup{ \hspace #-1.5

Re: Circled numbers for live electronics

SoundsFromSound wrote > Thank you for this very useful code! I can use this in my electro-acoustic > works for sure. I am glad to hear you found this useful! And because the function has a markup section, it should also be easily hackable depending on how you want your scores with live

Re: Circled numbers for live electronics

Hi all, I started using the raw tag for enclosing any LilyPond code because without it the Nabble interface often does not display the code properly (because it sometimes thinks the chords are tags and end up omitting part of it, making the code shown at Nabble uncompilable!). It happened to me

Re: Circled numbers for live electronics

A small revision of the functions above, the functions now take numbers as input and I then used Scheme to automatically ensure that all circles have the same size for inputs up to 999. For inputs larger than that, use some \override TextScript.extra-offset if the arrows are slightly off place in

Circled numbers for live electronics

Hi all, I just want to share two small functions I wrote to deal with live electronics. This type of notation is particularly useful when using a MIDI footpedal to activate events. The code is: Producing: I hope someone will find

Re: omiting barlines with autochange

Hi Pierre, Thanks a lot for the quick reply, \omit SpanBar indeed does the trick! I really appreciate the help. Cheers, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/omiting-barlines-with-autochange-tp194395p194399.html Sent from the User mailing list

omiting barlines with autochange

Hello all, Does anyone know if it's possible to omit the barlines when using autochange? I tried using both \omit PianoStaff.BarLine and \omit Score.BarLine and while the barlines are omitted inside the 5 line staves, they are shown in between staves. See: \version "2.19.37" \new PianoStaff {

Re: whiteout outline thickness

Hi Abraham, tisimst wrote > That's what > > \override Staff.Clef.whiteout = 3 > > means. Change that value (in units of staff-line-thickness) to change the > thickness of the white. Derp, that was quite easy (and obvious). I was used to set the whiteout property of a grob to either true or

whiteout outline thickness

Hello all, I would like to ask how can I change the thickness of the whiteout shape around a glyph when the whiteout style is set to outline. The the documentation ( http://lilypond.org/doc/v2.19/Documentation/changes/ ) gives the following examples: \markup { \combine \filled-box #'(-1 .

Re: tuplet bracket slope

Hi Simon, Simon Albrecht-2 wrote > On 09.07.2016 17:14, Gilberto Agostinho wrote: >> Andrew Bernard wrote >>> What nonsense Gould writes here. I perceive duration in notation on any >>> angle. The book is not always right in its justifications. >> I think

Re: tuplet bracket slope

Hi Andrew, Andrew Bernard wrote > What nonsense Gould writes here. I perceive duration in notation on any > angle. The book is not always right in its justifications. I think what Gould means is that duration is notated in the x-axis of a staff, and so keeping beams close to the axis alignment

Re: tuplet bracket slope

Brian Barker replied to me and to the list, but for some reason his reply isn't showing here, so I quote: Brian Barker wrote > Angle of brackets > Groups without beams > Brackets may slant in the direction of the tuplet's outer pitches > The angle of slant should not be too acute; match an

tuplet bracket slope

Hi all, I am wondering if the way LilyPond's tuplet bracket algorithm works is really ideal. It seems to me that the algorithm does not specify a maximum slope for the brackets, and can produce things like this: \version "2.19.37" { \tuplet 5/4 { 16 d'4 } \tuplet 5/4 {

Re: broken link at lilypond.org

Hi Urs, Thanks a lot, I wasn't sure if website related problems should also go to the bug list. Cheers, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/broken-link-at-lilypond-org-tp190394p190396.html Sent from the User mailing list archive at Nabble.com.

broken link at lilypond.org

Hi all, I don't know if I should report this to the bug squad or simply point it our here in the user list, but there is a broken link in the main website. In the page about the Google Summer of Code http://lilypond.org/google-summer-of-code.html , section "Improve default beam positioning", a

Re: Some help with music theory

Hi Carl, I'd be happy to take a look on your assignments off-list. I don't know exactly which book you are using (that link lists a couple of pdf files) nor what specifically are you learning, but I think I might be able to give you a hand (I am finishing my masters in composition right now).

Re: Dynamics context and vertical positions

Hi Simon, I think you are right, it's a very specific type of music that benefits from centralized dynamics for single staffed instrument, namely contemporary music with many markings, sometimes with one marking per note. Cheers, Gilberto -- View this message in context:

Re: Dynamics context and vertical positions

Hi Abraham, Thank you for your quick reply! I believe I understand the problem now, and it seems that it can be solved by using: \layout { \context { \Dynamics \override VerticalAxisGroup.nonstaff-relatedstaff-spacing.basic-distance = #0 } } I wonder why isn't this the default

Dynamics context and vertical positions

Hi all, I have been using the Dynamics context since short time ago, and I think it substantially helps to improve the overall look of the score with its horizontal alignment of all dynamics in a system. The problem I have with it is that I often find the distance between the dynamics and the

Re: MIDI "volume"

Hi Heikki, Heikki Tauriainen wrote > You may be interested to know that there was an attempt to improve this > behavior just a few months ago, see https://sourceforge.net/p/testlily > issues/issues/4730/.  The fix has been included in the unstable > releases since 2.19.36. I just tested it and

Re: MIDI "volume"

Hi all, Heikki Tauriainen wrote > I've observed that LilyPond actually emits CC#7 events to a generated > MIDI file on dynamic (MIDI velocity) changes created by the > Dynamic_performer, but these CC#7 changes seem to always just set the > MIDI volume to 100 (in the range from 0 to 127). To me

Grace notes and PianoStaff name

Hi all, Either I found a bug or I am missing something obvious here :) So: how can I add a PianoStaff name when the music start with a grace note?! See: \version "2.19.32" \markup "1) all good here" \new PianoStaff << \set PianoStaff.instrumentName = "Foo bar" \new Staff { c'1 }

Re: Grace notes and PianoStaff name

Thank you so much! Take care, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/Grace-notes-and-PianoStaff-name-tp186702p186708.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing

Re: Grace note kicks tuplet number away

Hi all, I'd like to offer a small bounty for this issue. If anyone is able to tackle this until the 15th of April (which is the deadline for my work which is being affected by this) I am able to offer 15 EUR. Cheers, Gilberto -- View this message in context:

Re: Spanner text in parenthesis on a new system

Hi Kieren, thanks for the reply! On 06/01/16 20:39, Kieren MacMillan wrote: In the meantime, it’s fairly easy to add this as a markup. Do you mean you have to manually align each one of the "(Ped.)" texts manually? Because if that's the case, it would be quite hard to add them to the

Re: breaking chords with \autochange

Hi all, I am so sorry, I pasted the wrong code in my first post... :-( Obviously the function needs a second argument, and that's the correct code below: \version "2.19.32" autochord = #(define-music-function (parser location chordDown chordUp) (ly:music? ly:music?) #{

Re: breaking chords with \autochange

??? I just pasted the correct code and it appeared messed up again (the first argument of the function is missing). This is the correct code: http://kl1p.com/Ssse Sorry but I really don't know what's happening... -- View this message in context:

Re: breaking chords with \autochange

Hi Jacques, Jacques Menu-3 wrote > Event that is very strange: there are missing backslashes…? How annoying... so it seems that the website I used to paste the code takes two backlashes and transform them into one As for the problem here with Nabble is that if you have "<" + "a" without any

Re: Spanner text in parenthesis on a new system

Hi David, David Nalesnik-2 wrote > From my inspection of the code, though, this seems to be a > rather bigger enterprise than a modification of OttavaBracket. This > should > be tackled in C++, and the code seems awfully convoluted, I can't put the > time in to figuring it out given such

breaking chords with \autochange

Hi all, I created a simple function which helps handle chords when using \autochange, but although the function works great I get some warning messages. This is the code: \version "2.19.32" autochord = #(define-music-function (parser location chordDown chordUp) (ly:music? ly:music?)

Re: recent modifications to \partcombine

Hi Urs, Urs Liska wrote > But it does so after running convert-ly on the code (apart from the > erroneous "=" before \partcombine). Oh, of course you are right, I completely forgot about convert-ly! My bad... So we can completely ignore my previous post, except perhaps about that phrase in the

Re: recent modifications to \partcombine

Thanks David, cheers! -- View this message in context: http://lilypond.1069038.n5.nabble.com/recent-modifications-to-partcombine-tp184608p184614.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list

recent modifications to \partcombine

Hi all, It seems that a recent modification to \partcombine has cause a major problem with some older scores. The code below compiles on version 2.19.28 but not on version 2.19.32: %% A = { \repeat unfold 4 {c' d' e' f'} } B = { c' d' e' f' \partcombineApart c' d' e' f'

RE: Kneed beams and changes of staff

I reported this at http://lilypond.1069038.n5.nabble.com/Kneed-beam-and-subdivisions-td184473.html and I also offered a 30 EUR bounty to whomever fix this. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Kneed-beams-and-changes-of-staff-tp184339p184553.html Sent from the

Grace note kicks tuplet number away

Hi all, When cross staffing, I found that sometimes a grace note in the middle of the beam causes the tuplet number to move absurdly higher or lower: \version "2.19.32" \markup{"ugly"} \autochange { \tuplet 7/4 { c,32[ c, c, \grace{ c,8 } c,32 c, c''' c,] } } \markup{"pretty"} \autochange {

Re: Grace note kicks tuplet number away

Hi Simon, Thanks for your quick reply. Simon Albrecht-2 wrote > it seems the feature announced in > http://lilypond.org/doc/v2.19/Documentation/changes/index; (at > about > 2/3, search for ‘knee-to-beam’) has been implemented without providing > for this situation. So we should create a

Spanner text in parenthesis on a new system

Hi all, Is it possible to automatically change the text of a spanner so that if they last for more than one system they get parenthesized? I would like to apply this both to the ottava indications as well as for the mixed style of sustain pedalling (actually we don't show any text at all when

Re: Spanner text in parenthesis on a new system

Hi David, David Nalesnik-2 wrote > It's not difficult to do this for ottava indications. Below I simply > check > to see if the left-bound of the spanner is broken. Thanks, it works wonderfully! David Nalesnik-2 wrote > From my inspection of the code, though, this seems to be a > rather

RE: Kneed beams and changes of staff

Hi all, I got Elaine Gould's /Behind Bars/ from my library today and this is what she has to say about this issue here (pp. 316--317): I think the key is

Re: grace notes MIDI playback

David Wright wrote > That's not true for all appoggiaturas of that era, is it? Well, with old music it's always tricky to find rules for these type of things, and to cater our MIDI output around it will lead to madness IMO. But I'd say it's quite safe to assume the meaning of contemporary

RE: Kneed beams and changes of staff

One more thing: this problem is related to the kneed beams behaviour only and is not affected by changes of staff or \autochange, see: \autochange { \override Score.Beam.auto-knee-gap = #3 \tuplet 5/4 {g''32[e'' g''64 d a,32 gis]} } { \override Score.Beam.auto-knee-gap = #1 \tuplet 5/4

RE: Kneed beams and changes of staff

Mark Stephen Mrotek wrote > A rather tedious, yet precise method, is: > > \once \set stemRightBeamCount = #x > \once \set stemLeftBeamCount = #x One one more thing, this method actually does not work. Think like this: the problem isn't the number of beams for each note (these are correct) but

Re: Kneed beams and changes of staff

Hi Kieren, Kieren MacMillan wrote > There are almost certainly other [more automagic] ways… > But have you looked at stemLeftBeamCount and stemRightBeamCount? I have looked at them, but unfortunately I would need one of those automagical ways (I am dealing with algorithmic music and I manually

Re: Kneed beams and changes of staff

Hi Kieren, Kieren MacMillan wrote > True! If you look at the following [even simpler] snippet, it’s clear that > things are fine when un-kneed, but go wonky when kneed. Your example shows the problem very clearly indeed. > I’m in no way certain (a) what the current algorithm actually is/does,

RE: Kneed beams and changes of staff

Hi Mark, Mark Stephen Mrotek wrote > A rather tedious, yet precise method, is: > > \once \set stemRightBeamCount = #x > \once \set stemLeftBeamCount = #x This is what Kieren already recommended me in this thread, but it's unfortunately not really possible in my case (and even if I could, I

Kneed beams and changes of staff

Hi all, Does anyone here know how can I achieve the look of the red beams in the image below? (the black beams are the LilyPond's default, and the red I drawn on a graphics application): It makes so much easier to read subdivisions

Re: Better slashed graces

Hi all, thanks for the comments, tisimst wrote > I believe it's in response to this snippet in the LSR: > http://lsr.di.unimi.it/LSR/Item?id=721 (Slashed beamed grace notes) Yes, that's the function, sorry for being unclear. My improvements above work well on most cases, but I modified that

Re: Better slashed graces

Hi David, As I wrote, I simply tried using some basic programming skills and trial and error in order to get a better looking results, and I would need some help to make this function look decently (I am not very familiar with Scheme at all, nor with programming functions in LilyPond). The main

Better slashed graces

Hi all, I am trying to improve the slashed grace function because currently it does work only for a limited amount of examples. I am trying to make the slash always at the same position relative to the highest beam (which was one of the most annoying things about the other function) and then take

Re: Better slashed graces

David Nalesnik-2 wrote > You could have the idea of proportionality, but relative to the width of > the beam, so the line would always cross dead-center or a fixed distance > below the beams, whether you have 1, 2, 3, That's doable, but a > little > annoying: get the number of beams, the

Re: Better slashed graces

David Nalesnik-2 wrote > My question would be: what is 'stem-fraction' now? What does it now > measure? I have absolutely no idea, I just messed around with the variables and expressions until I got a result that looked right in the situations I was testing :) As you say, ideally this all could

\autochange and \override of dynamics and hairpins

Hi all, Can anyone explain to me why the second system doesn't work, while the last one does? Can't I use \override commands inside a \autochange block? \version "2.19.28" \markup{"no override, no problems"} \new PianoStaff \autochange { a\p\< d' g f'\f } \markup{"autochange doesn't work

Force minor trill playback

Hi all, In case someone else will find this useful, here is a way to force all trills to be minor: \include "articulate.ly" \version "2.19.28" #(define (ac:trill music) (let* ((hemisemidur (ly:make-duration 5 0 1/1)) (orig-len (ly:music-length music)) (t (ac:twiddletime

Re: \autochange and \override of dynamics and hairpins

Interesting enough, this works: \version "2.19.28" \new PianoStaff \autochange { \override Score.DynamicText.stencil = ##f \override Score.Hairpin.stencil = ##f a\p\< d' g f'\f } -- View this message in context:

Re: grace notes MIDI playback

Hi all, I found a workaround for my problem and I am sharing it here. If I define these in the beginning of the score and use the articulate.ly script, the grace notes will behave as I expect: #(define ac:defaultGraceBackwardness 0) #(define ac:defaultGraceFactor 1) Example: \include

Re: grace notes MIDI playback

Hi David, thanks for your reply, David Kastrup wrote > But conceivably the articulate script deals correctly > with \appoggiatura. Yes, it does! I normally use only \grace and \slashedGrace on my scores, didn't cross my mind to use \appoggiatura. Thanks again! Cheers, Gilberto -- View this

Re: grace notes MIDI playback

Hmm, but here is a huge limitation of the articulate.ly script: the duration of the appoggiaturas played on the beat depend only on the number of notes, not on their duration! See: \version "2.19.28" \include "articulate.ly" music = { \appoggiatura {c'8} d'2 \appoggiatura {c'16} d'2

Re: articulate.ly and trills

Hi Teoh, thanks for your reply, H. S. Teoh wrote > On Fri, Nov 27, 2015 at 05:32:37PM -0700, Gilberto Agostinho wrote: > Currently, I use a workaround by > separating the layout and midi scores, and use \tag to explicitly spell > out trills > [...] > This is rather ugly [...] B

grace notes MIDI playback

Hi all, In the MIDI output, is it possible to make the grace notes to be played on the beat as opposed to stealing time from the previous bar? Cheers, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/grace-notes-MIDI-playback-tp184215.html Sent from the User

Re: grace notes MIDI playback

David Kastrup wrote > So how should this be rigged instead? Nominal length, unless that would > swallow all of the following notelength or more? And otherwise scale > down repeatedly by a factor of 2 until it doesn't? That sounds like an excellent approach as appogiaturas should be played with

articulate.ly and trills

Hello all, I would like to ask if anyone knows how to control the speed of the trills in the MIDI output when using articulate.ly. Currently, the articulate.ly simply converts a note with a trill into a bunch of 32nd notes, regardless of the tempo of the piece. This works very well for slow tempi

Re: ottavation function

Simon Albrecht-2 wrote > Try: > \layout { >\context { > \Staff > \override OttavaBracket.springs-and-rods = > #ly:spanner::set-spacing-rods > %\override OttavaBracket.minimum-length = 0.3 >} > } > and adjust minimum-length to taste. For some reason this has no effect for

smaller grace notes

Hi all, Can someone please explain to me why these changes to the grace note sizes are not applied when a second voice is used? \version "2.19.28" \layout { \context { \Score \with{ $(add-grace-property 'Voice 'NoteHead 'font-size '-5) $(add-grace-property 'Voice 'Slur

  1   2   3   4   >