lilypond-user
[Top][All Lists]
Advanced

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

Re: Faking a time signature


From: Menu Jacques
Subject: Re: Faking a time signature
Date: Sun, 15 Jan 2017 22:00:26 +0100

Hello,

Going on with my Gabrieli example, there is a time change to 3/2, and I can’t get rid of the warning message on the first R1*3/2.

Thanks again for your help!

JM

%%%%%%%%%%%%%%

\version "2.19.44"

PartPFourVoiceOne =  \relative g {
  \set Score.barNumberVisibility = #all-bar-numbers-visible
  \override Score.BarNumber.break-visibility = ##(#f #t #t)

  \clef "bass"
  \key f \major

  \time 4/2 | % 1
  \set Staff.timeSignatureFraction = 2/2

  g4  d4  g4  a4  bes2.
  bes4 \break | % 4
  g,1 \fermata
  \bar "||"

  \time 3/2
  \set Staff.timeSignatureFraction = 3/2

  \partial 1*3/2
  \set Score.currentBarNumber = #15

  R1*3/2 | % 16
  R1*3/2 | % 17
  g'1  g2 \break | % 18
}

{ \PartPFourVoiceOne }

%%%%%%%%%%%%%%


Starting lilypond 2.19.44 [Untitled]...
Processing `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6m0000gn/T/frescobaldi-tSGM2_/tmpVLIoVM/document.ly'
Parsing...
Interpreting music...

R1*3/2 | % 16
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6m0000gn/T//lilypond-96yPDq'...
Converting to `document.pdf'...
Deleting `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6m0000gn/T//lilypond-96yPDq'...
Success: compilation successfully completed
Completed successfully in 0.7 ».



Le 14 janv. 2017 à 07:29, Menu Jacques <address@hidden> a écrit :

Hello Andrew, Marte and Simon,

Thanks for the solutions, sorry I missed that topic in december.

Maybe such use of Staff.timeSignatureFraction is worth being mentioned in this context in the LPNR? (Score.measureLength is not as of 2.19.31).

JM

Le 13 janv. 2017 à 17:13, Simon Albrecht <address@hidden> a écrit :

On 13.01.2017 15:12, N. Andrew Walsh wrote:
I'd probably reduce all note-values by half

I strongly advise against that.  It obscures the historical evolution of notation and thus takes away an important bit of information from the performer.  And honestly: it doesn’t make it significantly easier to read.

Best, Simon

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user



reply via email to

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