lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.24 weirdness with slurred chords


From: Michael Werner
Subject: Re: 2.24 weirdness with slurred chords
Date: Mon, 26 Dec 2022 06:18:08 -0500

Lukas & Pierre:

Thank you both so very much - that was exactly what I was wanting. That tab staff is working perfectly now. Well, at least until I come up with some other goofy thing I want / need to figure out. In the mean time I'm going to have another extended trawl through that Internals Reference - there's just so much in there it's taking me a while to hammer it all through my thick skull. That and go back to change over to using ties. It'll certainly be easier than all the \=1( and \=2( and on and on.

Again, thank you both for the pointer. And while I'm at it, I'd say a huge thanks to all the devs is in order as well. Thanks to everyone involved for so much effort leading to such a fantastic software package.

Thanks,
Michael

On Mon, Dec 26, 2022 at 5:08 AM Pierre Perol-Schneider <pierre.schneider.paris@gmail.com> wrote:
Hi Michael,
You could do:

\version "2.24.0"

music = { <e a c'>1_~ q }

\new StaffGroup <<
  \new Staff { \clef "G_8" \music }
  \new TabStaff
  \with {
    \revert Tie.stencil
    \revert Tie.after-line-breaking
  } \music
>>

HTH, Cheers,
Pierre

Le lun. 26 déc. 2022 à 03:37, Michael Werner <reznaeous@gmail.com> a écrit :
On Sun, Dec 25, 2022 at 4:15 PM Werner LEMBERG <wl@gnu.org> wrote:

> Hey all.  Ran into a bit of weirdness when trying to do slurred
> chords.  I'm wanting a slur between each of the matching notes
> within the chord.

Why slurs and not ties?

> Here's an MWE showing this.
%< snippity 
Indeed, this looks like a bug.  However, a simple solution is to do
the following – but I guess you know this already :-)

```
\version "2.25.0"

\relative c'' {
  b4 b b
  <b\1 f\2 b,\3>4 ~ <b\1 f\2 b,\3>
  <e,\1 b\2 e,\3>2. ~ <e\1 b\2 e,\3>2
}
```

Yup, thought about doing that. Unfortunately in this case that actually won't do what I need. And here's examples of why. Keep an eye on the tab staff - with these scores the finished version will have only two of the three staves currently shown. The middle one is a temporary I added in for my own use while entering everything. It helps me make sure I'm getting the chords right. The top staff (with the simpler melody) and the bottom staff (the tablature) are the two that will remain when I'm done. And for the folks I'm producing this for the tab staff is the higher priority.

Done with slurs:

 
image.png

And now done with ties:

image.png

So, yes, the middle staff works as I would like when done with ties. But the tab staff doesn't. And since the tab staff is the more important one doing it with ties in this case won't work. Fortunately, since that middle staff is a temporary one that won't be in the finished version I can stay with using the slurs to do what I need to do. And it's the slur version of the tab staff that:  1) the locals are used to seeing and 2) is how the original score I'm reproducing is written.

So in this case there really is a bit of method to my madness in insisting on using slurs. Seems a bit ironic to me that the staff that showed the issue is one that won't even be there when it's all said and done with. Ah well. Funny ol' thing life.

Thanks,
Michael

reply via email to

[Prev in Thread] Current Thread [Next in Thread]