Re: Tweaking Hairpin shape

Hi Harm, On Sun, Feb 4, 2018 at 6:23 PM, Thomas Morley wrote: > Hi David, > > I was going to post something similiar. > You're code is much more elegant with respect to linebreaks, great stuff. > Though, it will not work as desired if the beam/hairpin is distributed >

Re: Tweaking Hairpin shape

Hi David, I was going to post something similiar. You're code is much more elegant with respect to linebreaks, great stuff. Though, it will not work as desired if the beam/hairpin is distributed over _three_ lines. I've no clue how to make it work, admittedly it's a real rare case. Some inline

Re: Tweaking Hairpin shape

Hi Stefano, On Sun, Feb 4, 2018 at 4:09 PM, Stefano Troncaro wrote: > Harm, I've been thinking about this, and perhaps you have an idea of how the > following can be achieved. > > A consequence of explicitly stating the degree in which the stencil has to > be rotated

Re: Interesting glitch when using tags ...

On 04.02.2018 21:27, Wols Lists wrote: The problem here is that your two melody passages are all in the same voice, and that means that f4 is_not_ the next note after f4. ~ but rather the d8 in the previous line of entry is. Oh ... so lily is being its usual rather non-intuitive self :-)

Re: endless tab?

On 04.02.2018 14:19, bb wrote: It is not really endless but the tab does not have any line break. If I try to insert \break this will be ignored? There must be something wrong with my code I cannot figure out? Thanks for help \version "2.19.80"     \new TabStaff {     \set

Re: Tweaking Hairpin shape

Harm, I've been thinking about this, and perhaps you have an idea of how the following can be achieved. A consequence of explicitly stating the degree in which the stencil has to be rotated is that if anything changes the spacing of that system it's very likely that the degree of rotation will

Re: Interesting glitch when using tags ...

Wols Lists writes: > On 04/02/18 19:20, David Kastrup wrote: > >> So can we agree that diagnosing this required an actual complete example >> showing the context in which this problem occured? >> > (Which, while it wasn't a compilable example, was why I included the >

Re: Interesting glitch when using tags ...

On 04/02/18 19:20, David Kastrup wrote: > Wol's lists writes: > >> Okay. You wanted a minimal example ... >> >> But surely, "f4. ~ f4" is clearly something wrong if it's complaining >> about an unterminated tie? Yes you might need a bit more information >> to debug it,

Re: Tweaking Hairpin shape

2018-02-04 21:02 GMT+01:00 Kieren MacMillan : > Hi Harm, > >> See below. > > Once again, a wonderful solution/contribution. > >> 'rotation comes too late, use a stencil-override with ly:stencil-rotate >> instead. > > Is there any reason 'rotation can't come sooner

Re: Tweaking Hairpin shape

Amazing, perfect solution! Thank you very much! 2018-02-04 17:02 GMT-03:00 Kieren MacMillan : > Hi Harm, > > > See below. > > Once again, a wonderful solution/contribution. > > > 'rotation comes too late, use a stencil-override with ly:stencil-rotate > instead. > >

Re: Tweaking Hairpin shape

Hi Harm, > See below. Once again, a wonderful solution/contribution. > 'rotation comes too late, use a stencil-override with ly:stencil-rotate > instead. Is there any reason 'rotation can't come sooner for all grobs, so that skylines and spacing Do The Right Thing™? Thanks, Kieren.

Re: Tweaking Hairpin shape

2018-02-04 20:30 GMT+01:00 Stefano Troncaro : > Thank you! This is a workable starting point. However, it raised a few > questions. > > 1) I noticed that rotating the grob doesn't work well with automatic > collision detection, since the grob skylines are still where

RE: Placement of clefs at repeat bars

Peter, As I said in my suggestion, using the same "\once" command for the treble clef achieves want you want. Try, \version "2.19.52" \language "english" \new Staff { \repeat volta 2 { c'' c'' \once \override Score.BreakAlignment #'break-align-orders = #(make-vector

Re: Tweaking Hairpin shape

Thank you! This is a workable starting point. However, it raised a few questions. 1) I noticed that rotating the grob doesn't work well with automatic collision detection, since the grob skylines are still where they would be for the unrotated grob. See this example code and the attached images:

Re: Interesting glitch when using tags ...

Wol's lists writes: > Okay. You wanted a minimal example ... > > But surely, "f4. ~ f4" is clearly something wrong if it's complaining > about an unterminated tie? Yes you might need a bit more information > to debug it, but on the face of it it's a blatant bug ... And

Re: Interesting glitch when using tags ...

Whoops - I've just spotted a genuine unterminated tie at the end of the first line of notes - but removing it does not get rid of the warning... So this minimal example demonstrates both a genuine unterminated tie that doesn't warn, and a terminated tie that warns when it shouldn't...

Re: Placement of clefs at repeat bars

Mark, Thanks. You read my email correctly - the bass clef should be after the barline, not before. But your idea didn't change this. Should it have done so? Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.com - Sunday, February 4, 2018, 3:45:33 PM, you wrote:

Re: Interesting glitch when using tags ...

Okay. You wanted a minimal example ... But surely, "f4. ~ f4" is clearly something wrong if it's complaining about an unterminated tie? Yes you might need a bit more information to debug it, but on the face of it it's a blatant bug ... Cheers, Wol On 04/02/18 00:59, David Kastrup wrote:

Re: Tweaking Hairpin shape

For your first question: http://lilypond.org/doc/v2.19/Documentation/notation/rotating-objects should help. -- Phil Holmes - Original Message - From: Stefano Troncaro To: lilypond-user Mailinglist Sent: Sunday, February 04, 2018 4:43 PM Subject: Tweaking Hairpin shape

Re: Tweaking Hairpin shape

On 2/4/2018 11:43 AM, Stefano Troncaro wrote: Hello everyone! I'm struggling with Hairpins this time. I can't find how to tweak the placement of it's starting and ending points. Suppose that in the following example I want to make the Hairpin follow the same slope as the Beam. Furthermore,

Tweaking Hairpin shape

Hello everyone! I'm struggling with Hairpins this time. I can't find how to tweak the placement of it's starting and ending points. Suppose that in the following example I want to make the Hairpin follow the same slope as the Beam. Furthermore, I'd like the Hairpin to start a little bit to the

RE: Placement of clefs at repeat bars

Peter, I regret that my suggestion did not solve all of your issues. My reading of your e-mail lead me to the awkward placement of the bass clef. That is the crux of my recommendation. The same command could be used to "accurately" place the subsequent treble clef. Mark Never let the

Re: endless tab?

Changed the note duration to something that makes sense. (Originally was just an experiment for checking regex.) Works now. Thanks. Am 04.02.2018 um 14:54 schrieb David Kastrup: bb writes: Thanks! If I try this, I get multiple warnings for different lines:

Re: endless tab?

bb writes: > Thanks! If I try this, I get multiple warnings for different lines: > Crosses bar! > > Even if I copy/paste the code you sent me back I get a lot of warnings. Well, that's the idea. LilyPond does not break across notes, so if you have notes crossing bar

Re: endless tab?

Thanks! If I try this, I get multiple warnings for different lines: Crosses bar! Even if I copy/paste the code you sent me back I get a lot of warnings. Regards Am 04.02.2018 um 14:34 schrieb David Kastrup: bb writes: It is not really endless but the tab does

Re: endless tab?

bb writes: > It is not really endless but the tab does not have any line break. If > I try to insert \break this will be ignored? There must be something > wrong with my code I cannot figure out? > > Thanks for help Does this help? \version "2.19.80" \layout {

endless tab?

It is not really endless but the tab does not have any line break. If I try to insert \break this will be ignored? There must be something wrong with my code I cannot figure out? Thanks for help \version "2.19.80"     \new TabStaff {     \set TabStaff.tablatureFormat =

Re: Placement of clefs at repeat bars

Mark, Your snippet raises two points: 1) There really should be a treble clef before the final repeat, to remind the performer to switch back. This is important when there's music before the repeated section as the performer may have forgotten which clef the repeat started in. In your

Re: Placement of clefs at repeat bars

Saturday, February 3, 2018, 8:22:38 PM, you wrote: > Hi Peter, > 2018-02-03 20:08 GMT+01:00 ptoye : >> I've found that this is was reported as an "ugly" in 2011. > Plese provide the link. https://sourceforge.net/p/testlilyissues/issues/1862/ >> I think it's a bug >> as the

Re: MIDI dynamics

On 04/02/18 05:19, Abraham Lee wrote: Hi, Hilary! On Sat, Feb 3, 2018 at 9:42 PM Hilary Snaden wrote: I have been trying to get LilyPond to generate MIDI versions of some piano music. The music script renders nicely, and there are no errors or warnings, but the MIDI

Re: MIDI dynamics

I'd suggest either moving the DynamicsPerformer to the Staff context or replacing the \upper with << \upper \dynamics >> (and the same for \lower). Normally, dynamics only affect the voice they are in, which in your example is a different voice from the ones the notes are in. On 02/04/18