Re: Change direction of already positioned markup?

2015-05-31 23:43 GMT+02:00 Simon Albrecht : > Am 31.05.2015 um 18:25 schrieb Jacques Menu: > > Hello Peter, > > Maybe tags would be an easy solution, specifying variants according to the > uses of the music, i.e. inside an instrument part or inside a full score. > > What do you think? > > Probably

Re: VoltaBracket flipped vertically

Hi, On Sun, May 31, 2015 at 10:20 AM, Thomas Morley wrote: > 2015-05-26 18:09 GMT+02:00 Thomas Morley : > > 2012-12-19 16:15 GMT+01:00 Daniel Rosen : > >> I'm trying to get VoltaBrackets to appear both above and below the > Score. I've come up with the solution below, which works quite well, but

Re: Change direction of already positioned markup?

Am 31.05.2015 um 18:25 schrieb Jacques Menu: Hello Peter, Maybe tags would be an easy solution, specifying variants according to the uses of the music, i.e. inside an instrument part or inside a full score. What do you think? Probably tags contradict hardcore content/presentation separation

Re: Color note heads outside nominal instrument range

2015-05-31 22:07 GMT+02:00 Gilles THIBAULT : > >> I modified it. >> Is the output ok now? >> http://lsr.di.unimi.it/LSR/Item?u=1&id=773 >> > Perfect. > > The staff 6 is the same as staff 3. (It tests the scheme version of > \correctOctaveOutOfRange ). As in the old LSR, only one score could be > ou

Re: Color note heads outside nominal instrument range

Le dimanche 31 mai 2015, 22:07:09 Gilles THIBAULT a écrit : > The staff 6 is the same as staff 3 .. as staff 4 -- Gilles ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Color note heads outside nominal instrument range

> I modified it. > Is the output ok now? > http://lsr.di.unimi.it/LSR/Item?u=1&id=773 > Perfect. The staff 6 is the same as staff 3. (It tests the scheme version of \correctOctaveOutOfRange ). As in the old LSR, only one score could be outputted, this test 6 can perhaps be commented now. Some

Fedora issues

Hi, Jon Ciesla, Fedora lilypond maintainer. FYI, I'm aware of the issue and working on it. I've tried the latest git upstream for ghostscript, which didn't help. There's a new pango version out, so I'm working on trying that now. If that works I'll ship it for rawhide and f22. You can watch my

Re: Arrastres: function scheme question - Built from ideas of Simon and David -- Dynamic mark at the end of a bar

Thank you for that Stephen ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Center note column bug

Hi all, > As to the larger question of whether to upgrade or not, that's up to you. > Development versions come with a caveat about possible dangers, though I've > only purposely downgraded (to an earlier development version) on one occasion > because of (temporary) brokenness. I generally ha

Getting absolute position of objects

Hello, I'm looking for a way to obtain the absolute coordinates (x,y) of each graphical object LilyPond renders. I'd need such information to overlay some content on top a PNG score output from LilyPond. I've looked at the "event-listener.ly" method, but my Scheme/LilyPond internals were too lim

Re: Center note column bug

Hi Victor, On Sun, May 31, 2015 at 8:51 AM, Víctor wrote: > > El 31/05/15 a las 08:43, David Nalesnik escibió: > >> Hi Victor, >> >> Yes, you do. However, the second version I posted should work with >> earlier versions as I factored out ly:item-get-column. >> >> Sorry, I just missed that post

Re: Arrastres: function scheme question - Built from ideas of Simon and David -- Dynamic mark at the end of a bar

Hello Stephen, Changing : \once \override NoteHead.extra-spacing-width = #`(,len . 1) to : \once \override NoteHead.extra-spacing-width = #`(,(- len) . 1) allows a positive number instead. JM > Le 31 mai 2015 à 02:47, Stephen MacNeil a écrit : > > the second didn't work cor

Re: Change direction of already positioned markup?

Hello Peter, Maybe tags would be an easy solution, specifying variants according to the uses of the music, i.e. inside an instrument part or inside a full score. What do you think? JM > Le 30 mai 2015 à 20:28, Peter Crighton a écrit : > > Hello all, > > I have a variable divisiaIII = ^\mark

Re: Color note heads outside nominal instrument range

Message: 2 Date: Sat, 30 May 2015 13:40:13 +0200 From: Marc Hohl To: lilypond-user@gnu.org Subject: Re: Color note heads outside nominal instrument range Message-ID: <5569a19d.3070...@hohlart.de> Content-Type: text/plain; charset=windows-1252; format=flowed Am 30.05.2015 um 12:38 schrieb Peter

Re: VoltaBracket flipped vertically

2015-05-26 18:09 GMT+02:00 Thomas Morley : > 2012-12-19 16:15 GMT+01:00 Daniel Rosen : >> I'm trying to get VoltaBrackets to appear both above and below the Score. >> I've come up with the solution below, which works quite well, but I'd like >> to get the volta text to appear inside the bracket,

Re: Color note heads outside nominal instrument range

2015-05-31 15:54 GMT+02:00 Thomas Morley : > 2015-05-31 15:09 GMT+02:00 Gilles THIBAULT : >> Le samedi 30 mai 2015, 12:22:45 David Nalesnik a écrit : >> >>> Have you seen http://lsr.di.unimi.it/LSR/Item?id=773? >> >> Just note that if you want to understand this snippet, you have to change >> the

Re: Color note heads outside nominal instrument range

2015-05-31 15:09 GMT+02:00 Gilles THIBAULT : > Le samedi 30 mai 2015, 12:22:45 David Nalesnik a écrit : > >> Have you seen http://lsr.di.unimi.it/LSR/Item?id=773? > > Just note that if you want to understand this snippet, you have to change the > code : > > > music = \relative { > c4 d e f

Re: Center note column bug

El 31/05/15 a las 08:43, David Nalesnik escibió: Hi Victor, Yes, you do. However, the second version I posted should work with earlier versions as I factored out ly:item-get-column. Sorry, I just missed that post. Now I've checked it and it works in 2.19.15 I'll ask however, what do you ad

Re: Center note column bug

Hi Victor, On Sun, May 31, 2015 at 8:29 AM, Víctor wrote: > Hello again, > > I've tried your solution, but I get this error: > > Dibujando los sistemas... > /tmp/frescobaldi-Fwsk3s/tmpR0qdla/document.ly:6:22 : In > expression (ly:item-get-column grob): > > /tmp/frescobaldi-Fwsk3s/tmpR0qdla/docu

Re: Color note heads outside nominal instrument range

Am 31.05.2015 um 15:09 schrieb Gilles THIBAULT: Le samedi 30 mai 2015, 12:22:45 David Nalesnik a écrit : Have you seen http://lsr.di.unimi.it/LSR/Item?id=773? Just note that if you want to understand this snippet, you have to change the code : music = \relative { c4 d e f g^"g'" a

Re: Center note column bug

Hello again, I've tried your solution, but I get this error: Dibujando los sistemas.../tmp/frescobaldi-Fwsk3s/tmpR0qdla/document.ly:6:22 <0>: In expression (ly:item-get-column grob): /tmp/frescobaldi-Fwsk3s/tmpR0qdla/document.ly:6:22 <1>: Unbound variable: ly:item-get-column Se ha devuelt

Re: Color note heads outside nominal instrument range

Le samedi 30 mai 2015, 12:22:45 David Nalesnik a écrit : > Have you seen http://lsr.di.unimi.it/LSR/Item?id=773? Just note that if you want to understand this snippet, you have to change the code : music = \relative { c4 d e f g^"g'" a b c d e f g^"g''" a b c2 } % by mus

Re: Parenthesize accidental together

Hello, This is OK. Thanks a lot Venus' WInk > -Original Message- > From: simon.albre...@mail.de > Sent: Sun, 31 May 2015 13:36:09 +0200 > To: venuswi...@inbox.com, lilypond-user@gnu.org > Subject: Re: Parenthesize accidental together > > Am 31.05.2015 um 12:08 schrieb Venus' Wink: >> T

Re: Parenthesize accidental together

Am 31.05.2015 um 12:08 schrieb Venus' Wink: Thanks, All. see . This has been fixed in 2.19.20. The lambda function have worked with 2.18.2. The parens are put a bit high probably for virtical centering for flat. But it's acceptable for t

Re: lilypond-user Digest, Vol 150, Issue 183

Did you forget to write your actual text? Also please follow the advice in the e-mail header: When replying, please edit your Subject line so it is more specific than "Re: Contents of lilypond-user digest..." Thanks, Simon ___ lilypond-user mailing

Re: A slur across a line break with change of clef in another staff generates bad output

Am 31.05.2015 um 10:06 schrieb Richard Shann: On Sat, 2015-05-30 at 22:23 +0200, Simon Albrecht wrote: Am 30.05.2015 um 18:10 schrieb Richard Shann: Attached is a bit of LilyPond which has a slur over a line break. At the same moment the clef is changing in the lower staff. The result is a horr

Re: Incomplete final bar with \parallelMusic

Stephen MacNeil writes: > what about > > \set Score.measureLength = #(ly:make-moment 2/4) > > > as far as i know \partial is only for the beginning and from then on you > use ly:make-moment Has been changed with several issues, the last probably being issue 4056 https://code.google.com/p/lilypo

Re: Parenthesize accidental together

Thanks, All. >> see . This has >> been >> fixed in 2.19.20. The lambda function have worked with 2.18.2. The parens are put a bit high probably for virtical centering for flat. But it's acceptable for the time being. > For 2.18.2: > http:/

Re: A slur across a line break with change of clef in another staff generates bad output

On Sat, 2015-05-30 at 22:23 +0200, Simon Albrecht wrote: > Am 30.05.2015 um 18:10 schrieb Richard Shann: > > Attached is a bit of LilyPond which has a slur over a line break. At the > > same moment the clef is changing in the lower staff. The result is a > > horribly broken slur start in the top st

Re: Parenthesize accidental together

2015-05-31 9:08 GMT+02:00 Simon Albrecht : > Hello, > > see . This has been > fixed in 2.19.20. For 2.18.2: http://lsr.di.unimi.it/LSR/Item?u=1&id=972 Cheers, Harm > > Yours, Simos > > > Am 31.05.2015 um 02:58 schrieb Venus' Wink: > > Hi

Aw: lilypond-user Digest, Vol 150, Issue 183

> Gesendet: Samstag, 30. Mai 2015 um 18:01 Uhr > Von: lilypond-user-requ...@gnu.org > An: lilypond-user@gnu.org > Betreff: lilypond-user Digest, Vol 150, Issue 183 > > Send lilypond-user mailing list submissions to > lilypond-user@gnu.org > > To subscribe or unsubscribe via the World Wide

Re: Parenthesize accidental together

Hello, see . This has been fixed in 2.19.20. Yours, Simos Am 31.05.2015 um 02:58 schrieb Venus' Wink: Hi, I'd like to output like the attachment purpose.png. But the following simple code \parenthesize ces''4 puts the flat symb