Re: TimeSignature and magnifyStaff

Hello, On Tue, 17 Jul 2018 06:05:13 -0700 (MST), foxfanfare wrote: > As a new LilyPond user, I never opened an issue for signaling a bug. Could > someone please do it, or explain me how to proceed? Thx We're still establishing if it is a bug or an enhancement (see thread). However, for now I

Re: TimeSignature and magnifyStaff

On 7/17/2018 8:05 AM, foxfanfare wrote: or explain me how to proceed? Have you already reviewed the LilyPond website's bug report instructions? Or, for in-depth instructions for regular contributors, try the Contributor Guide's chapter 8, "Issues."

Re: TimeSignature and magnifyStaff

As a new LilyPond user, I never opened an issue for signaling a bug. Could someone please do it, or explain me how to proceed? Thx -- Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: TimeSignature and magnifyStaff

Am 16.07.2018 um 19:10 schrieb foxfanfare: I also think this tool has been written for chamber music with piano. That's why the smaller staves should be above. But it could be different, for instance, I have to write a piano piece with a "tracker" part (it is an electronic tape). In this case,

Re: TimeSignature and magnifyStaff

Malte Meyn-3 wrote > I just realized that this use was not intended: The scaling of bar lines > is explicitely intended, as one can see by looking at the regtest > magnifyStaff-bar-lines.ly. Thanks for your comments on this issue. Concerning the barlines, I think it is really a mistake in this

Re: TimeSignature and magnifyStaff

Am 16.07.2018 um 13:06 schrieb Malte Meyn: Of course, maybe I’m wrong and \magnifyStaff wasn’t intended for these use cases (f. e. piano parts in chamber music) but that’s the main purpose I would use it for if I could. I just realized that this use was not intended: The scaling of bar

Re: TimeSignature and magnifyStaff

Am 16.07.2018 um 07:52 schrieb James Lowe: So is this a bug or is it really an enhancement request/feature (i.e. is the code expected to do this or is it just a poorly chosen name for a function)? IMO it’s really a bug for the following reasons: 1. The behaviour of \magnifyStaff is

Re: TimeSignature and magnifyStaff

On Sun, 15 Jul 2018 08:05:05 +0200, Malte Meyn wrote: > > Am 14.07.2018 um 23:40 schrieb foxfanfare: > > I found a strange bug when using the magnifyStaff tool. In this example, you > > can see a collusion between the clef and the time signature occurs when the > > lowest staff is smaller

Re: TimeSignature and magnifyStaff

Am 14.07.2018 um 23:40 schrieb foxfanfare: I found a strange bug when using the magnifyStaff tool. In this example, you can see a collusion between the clef and the time signature occurs when the lowest staff is smaller (and not otherwise). Sounds like a bug to me, what do you think? Is there

Re: TimeSignature and magnifyStaff

Okay, I found how to trick this bug and move the TimeSignature with \override Score.TimeSignature.extra-offset = #'(1 . 0) but it still isn't very convenient! -- Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html ___ bug-lilypond

TimeSignature and magnifyStaff

Hi everyone, I found a strange bug when using the magnifyStaff tool. In this example, you can see a collusion between the clef and the time signature occurs when the lowest staff is smaller (and not otherwise). Sounds like a bug to me, what do you think? Is there a way to avoid this? \version