Re: Frescobaldi installation on Mac OS X (was: Re: Frescobaldi install)

Oh, wow - I had no idea about that bug. Honestly, in my experience, Frescobaldi has always been near-instant loading and wicked fast in usage - but thanks for the heads up! :) Ben Wilbert Berendsen-4 wrote > There is a recent, confirmed PyQt4 bug that caused very large delays in > Frescobaldi,

Re: Fingering not aligned in 2.17, ok in 2.16

On 24/03/13 04:07, Jan Nieuwenhuizen wrote: Nick Payne writes: Do you consider this a bug? Actually, I like the new behaviour better. What does the literature say? The great majority of commercial guitar scores I possess align the fingering vertically on chords, as 2.16 does. Which means th

RE: \relative proposal: putting absolute pitches anywhere within \relative block using @-sign

> On 13/03/2013 19:24, nothingwaver...@gmail.com wrote: >> 1. Define absolute octave syntax with the @-sign (let it be a mnemonic for _A_bsolute) >> to be the syntax for temporarily specifying an ABSOLUTE PITCH within a \relative block, >> such that the next pitch, if it doesn't use the @-sign also

Re: how offsets and alignment works: an explanation

2013/3/23 Janek Warchoł : > Hi, > > here's an explanation of what's happening when we're using XY-offset, > self-alignment etc. I hope that it'll help users get a better > understanding of LilyPond internals; i also think it would be a good > material for documentation, but i'm not sure where shou

Re: \relative proposal: putting absolute pitches anywhere within \relative block using @-sign

On 13/03/2013 19:24, nothingwaver...@gmail.com wrote: Here's the idea. 1. Define absolute octave syntax with the @-sign (let it be a mnemonic for _A_bsolute) to be the syntax for temporarily specifying an ABSOLUTE PITCH within a \relative block, such that the next pitch, if it doesn't use the

Re: Removing time change from previous line

On Sat, Mar 23, 2013 at 6:11 PM, Noeck wrote: > > % why doesn't the following line work? > > \override Staff.KeySignature #'break-visibility = > #end-of-line-invisible > > % this does: > > \set Staff.explicitKeySignatureVisibility = #end-of-line-invisible > > It is explained here: > > htt

Re: Time change breaks the layout

Sorry for the noise. It the second note should be a2. - then it works as expected. Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Removing time change from previous line

> % why doesn't the following line work? > \override Staff.KeySignature #'break-visibility = #end-of-line-invisible > % this does: > \set Staff.explicitKeySignatureVisibility = #end-of-line-invisible It is explained here: http://lilypond.org/doc/v2.14/Documentation/notation/visibility-of-o

Re: Removing time change from previous line

On Sat, Mar 23, 2013 at 5:32 PM, Noeck wrote: > Hi Alberto, > > this line should help you (2.16): > \override Staff.TimeSignature #'break-visibility = ##'end-of-line-invisible > > or in version 2.17: > \override Staff.TimeSignature.break-visibility = ##'end-of-line-invisible > > This is explained

Re: Removing time change from previous line

> The rest appears to be nonsense. I'd expect #end-of-line-invisible to > work just fine. Oh, thanks! That reassures me. (I must have had some other problem before with this.) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/m

Time change breaks the layout

Hi, while testing some snippets, I encountered a strange behaviour in the following code: \version "2.16.0" % "2.17.14" as well { a1 \break \time 3/4 % fine without time change a1 \break %\time 6/8 % "6/8" is also at an ugly position %a2. } The barline is not at the end of the second

Re: how offsets and alignment works: an explanation

On 24/03/13 03:56, Trevor Daniels wrote: Hi Janek This is explained very concisely and without examples in the NR, see http://www.lilypond.org/doc/v2.17/Documentation/notation/aligning-objects BTW, the text in that section ("an accidental can be repositioned vertically by setting Y-offset but

Re: Removing time change from previous line

Noeck writes: > Hi Alberto, > > this line should help you (2.16): > \override Staff.TimeSignature #'break-visibility = ##'end-of-line-invisible > > or in version 2.17: > \override Staff.TimeSignature.break-visibility = ##'end-of-line-invisible > > This is explained here: > http://www.lilypond.org

Re: Removing time change from previous line

Hi Alberto, this line should help you (2.16): \override Staff.TimeSignature #'break-visibility = ##'end-of-line-invisible or in version 2.17: \override Staff.TimeSignature.break-visibility = ##'end-of-line-invisible This is explained here: http://www.lilypond.org/doc/v2.16/Documentation/notation

Removing time change from previous line

Hello Is there any way to remove the time signature that is shown in a previous line, when the time is changing? Not sure if I made myself clear: when issuing a \time command, if it occurs at the end of the staff line, it is repeated at the end of the current staff, and in the beginning of t

Re: ANN: Frescobaldi 2.0.9

Also just a heads up for my fellow Ubuntu friends: This v2.0.9 update fixes that annoying Insert menu bug where the whole menu duplicated itself everytime you clicked to expand it. :) It was due to Unity I believe, but either way it's fixed so this program is rockin' now! Thanks again Wilbert,

Re: How to get a book twice with different page-footers?

Thomas Morley writes: > Hi, > > I'm trying to parse a book twice with different footers. > The function below > (thanks to Jan-Peter and Urs > http://lilypond.1069038.n5.nabble.com/Compile-twice-with-different-includes-td140953.html > ) > below works quite nice so long as very simple footers are

Re: Fingering not aligned in 2.17, ok in 2.16

Original-Nachricht Nick Payne writes: Do you consider this a bug? Actually, I like the new behaviour better. What does the literature say? The great majority of commercial guitar scores I possess align the fingering vertically on chords, as 2.16 does. Which means that

Re: how offsets and alignment works: an explanation

Am 23.03.2013 19:13, schrieb Trevor Daniels: > > Noeck wrote Saturday, March 23, 2013 5:55 PM >> >>> This is explained very concisely and without examples in the NR, see >>> http://www.lilypond.org/doc/v2.17/Documentation/notation/aligning-objects >> >> I disagree. As an average user, I feel qui

Re: how offsets and alignment works: an explanation

Noeck wrote Saturday, March 23, 2013 5:55 PM > >> This is explained very concisely and without examples in the NR, see >> http://www.lilypond.org/doc/v2.17/Documentation/notation/aligning-objects > > I disagree. As an average user, I feel quite lost in this section > especially with the "two-dime

Re: how offsets and alignment works: an explanation

> This is explained very concisely and without examples in the NR, see > http://www.lilypond.org/doc/v2.17/Documentation/notation/aligning-objects I disagree. As an average user, I feel quite lost in this section especially with the "two-dimensional" extents. Some images and the explanation from

Re: ANN: Frescobaldi 2.0.9

Thank you so very much!!! Your program is a JOY to work with. LilyPond and Frescobaldi are an unbeatable combination. Ben Wilbert Berendsen-6 wrote > Hi all, > > Frescobaldi 2.0.9 has been released in the wild. > > Due to GitHub removing the file upload section, the tarball is on > Googlecode

Re: how offsets and alignment works: an explanation

Hi Janek, thanks for these explanations. If the feedback doesn't give you a sufficiently clear idea where to put the material, you know what I'd suggest? ;-) Best Urs Am 23.03.2013 15:05, schrieb Janek Warcho?: Hi, here's an explanation of what's happening when we're using XY-offset, self-a

Re: User comments on R shorthand

On Wed, Mar 20, 2013 at 3:54 PM, James Harkins wrote: > My opinion (as a somewhat-more-than-casual Lilypond user, and as a > contributor to another music software package [SuperCollider]): Any > change in syntax that will break prior usage should be considered > very, very carefully to be sure th

Re: barline at end of staff

Wilbert, On Sat, Mar 23, 2013 at 9:26 AM, Wilbert Berendsen wrote: > Op 16-03-13 17:35, Arno Rog schreef: > > L.S. >> >> I'm trying to figure out a way to place the last bar line exactly at the >> end of >> the staff in the score of the Dutch anthem at >> http://lsr.dsi.unimi.it/LSR/**Snippet

Re: Fingering not aligned in 2.17, ok in 2.16

Nick Payne writes: >> Do you consider this a bug? Actually, I like the new behaviour >> better. What does the literature say? > > The great majority of commercial guitar scores I possess align the > fingering vertically on chords, as 2.16 does. Which means that there is no strict agreement? Th

Re: how offsets and alignment works: an explanation

Hi Janek This is explained very concisely and without examples in the NR, see http://www.lilypond.org/doc/v2.17/Documentation/notation/aligning-objects For a reference manual I think is is adequate, especially given the length of the NR already. So the best place for this is probably the CG, as

Frescobaldi installation on Mac OS X (was: Re: Frescobaldi install)

There is a recent, confirmed PyQt4 bug that caused very large delays in Frescobaldi, but 2.0.9 will run fine regardless, even with PyQt-4.9.6 or 4.10, allbeit slightly slower. I'd very happy if someone with an Apple machine could create a good, easily installable Frescobaldi package (maybe wit

Re: barline at end of staff

Op 16-03-13 17:35, Arno Rog schreef: L.S. I'm trying to figure out a way to place the last bar line exactly at the end of the staff in the score of the Dutch anthem at http://lsr.dsi.unimi.it/LSR/Snippet? id=648 Now it's done manually: \override Staff.BarLine #'extra-offset = #'(23 . 0) \bar "

Re: barline at end of staff

Hi Arno, On Sat, Mar 23, 2013 at 10:29 AM, Arno Rog wrote: > Hi David, > > It sure does!! > With Lilypond 2.16.1 it is almost(!) at the outer right side of the staff, > there is still a little bit of staff visible after the final barline. > I just tried this with 2.16.1, and there is quite a no

Re: how offsets and alignment works: an explanation

> here's an explanation of what's happening when we're using XY-offset, > self-alignment etc. I hope that it'll help users get a better > understanding of LilyPond internals; i also think it would be a good > material for documentation, Hi Janek, I loved to read this long mail. I would like to

Re: how offsets and alignment works: an explanation

Am 23.03.2013 16:07, schrieb Phil Holmes: - Original Message - From: "Janek Warchoł" To: "LilyPond Users" Sent: Saturday, March 23, 2013 2:05 PM Subject: how offsets and alignment works: an explanation Hi, here's an explanation of what's happening when we're using XY-offset, self-al

Re: barline at end of staff

Hi David, It sure does!! With Lilypond 2.16.1 it is almost(!) at the outer right side of the staff, there is still a little bit of staff visible after the final barline. Please ignore my ignorance but can I add a value 0.5 or 1.0 somewhere in your code to nudge it a little to the right? _

Re: how offsets and alignment works: an explanation

- Original Message - From: "Janek Warchoł" To: "LilyPond Users" Sent: Saturday, March 23, 2013 2:05 PM Subject: how offsets and alignment works: an explanation Hi, here's an explanation of what's happening when we're using XY-offset, self-alignment etc. I hope that it'll help users

Re: barline at end of staff

Hi Arno, On Sat, Mar 23, 2013 at 8:59 AM, Arno Rog wrote: > Arno Rog gmail.com> writes: > > > > Below a MWE of what I am trying to achieve (mind the wordwrap) > I hope someone has a solution to automatically place it at the end > of the staff, irrespective of the width of the staff. > > I'd lik

Re: barline at end of staff

Arno Rog gmail.com> writes: > Below a MWE of what I am trying to achieve (mind the wordwrap) I hope someone has a solution to automatically place it at the end of the staff, irrespective of the width of the staff. I'd like to have the last barline exactly at the end of the last staff without h

Re: ANN: Frescobaldi 2.0.9

on 2013-03-23 at 07:24 Wilbert Berendsen wrote: > Hi all, > > Frescobaldi 2.0.9 has been released in the wild. yay! right in time for my project... i was virtually waiting by the computer for this new release, since i was badly hit by the problem with PyQt-4.9.6. i can confirm that 2.0.9 compil

Re: Ties across variables

James Harkins-2 wrote > I've run into this limitation a few times -- enough that it's now > worth asking about. > > ~~ > notesA = \relative c'' { c d e f ~ } > notesB = \relative c'' { f e d c } > \new Staff { \notesA \notesB } > ~~ > > This doesn't render the tie. I'm sure there's a good reason

Ties across variables

I've run into this limitation a few times -- enough that it's now worth asking about. ~~ notesA = \relative c'' { c d e f ~ } notesB = \relative c'' { f e d c } \new Staff { \notesA \notesB } ~~ This doesn't render the tie. I'm sure there's a good reason why the tie can't carry over from one vari