Re: frescobaldi macports broken after update
Am 2014-01-23 um 20:35 schrieb Davide Liessi : > The patch is now in MacPorts. Great, it works again! Thank you (all of you) very much! I have two little complaints with Frescobaldi on OSX, that didn’t change in all the versions I tried: - If I start the program by opening a .ly file, Frescobaldi starts, but the file doesn’t open. - There seems to be no keyboard shortcut to get to the end of the line, that’s very inconvenient. The „End“ key is going to the end of the file, as usual on Mac, but Cmd-Right (Meta-Right), the usual key for end of line, changes the tab. I didn’t look into the code yet - in the preferences I can’t change those keys. Should I open two tickets? Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \set Score.midiPanPosition
On 24 January 2014 14:06, Jim Long wrote: > On Tue, Jan 21, 2014 at 04:09:38PM +1100, Vaughan McAlley wrote: >> On 20 January 2014 07:09, Colin Campbell wrote: >> > \set Score.midiPanPosition = #RIGHT >> > \set Staff.midiPanPosition = #LEFT >> >> This is missing in the 2.18 changes, so I didn???t know about it until >> now. Very nice! > > Strictly out of idle curiousity, are these possible, with some > degree of syntactic correction? > > \set Score.midiPanPosition = #RIGHT*0.95 > > to pan almost but not quite hard right, or: > > \set Staff.midiPanPosition = #LEFT*.1 > > To pan just slightly left of center? > > > Jim > I’m pretty sure LEFT, CENTER and RIGHT are just aliases for -1, 0 and 1, so \set Score.midiPanPosition = #0.95 or \set Staff.midiPanPosition = #-0.1 should should do what you want. Vaughan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
\set Score.midiPanPosition
On Tue, Jan 21, 2014 at 04:09:38PM +1100, Vaughan McAlley wrote: > On 20 January 2014 07:09, Colin Campbell wrote: > > \set Score.midiPanPosition = #RIGHT > > \set Staff.midiPanPosition = #LEFT > > This is missing in the 2.18 changes, so I didn???t know about it until > now. Very nice! Strictly out of idle curiousity, are these possible, with some degree of syntactic correction? \set Score.midiPanPosition = #RIGHT*0.95 to pan almost but not quite hard right, or: \set Staff.midiPanPosition = #LEFT*.1 To pan just slightly left of center? Jim ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Fw: lilypond-user Digest, Vol 134, Issue 154
4. Re:bar-check warning when generating rehearsal midi soprano, alto, tenor etc (Jan-Peter Voigt) Message: 4 Date: Thu, 23 Jan 2014 16:58:33 +0100 From: Jan-Peter Voigt To: lilypond-user@gnu.org Subject: Re: bar-check warning when generating rehearsal midi soprano, alto, tenor etc Message-ID: <52e13c29.6090...@gmx.de> Content-Type: text/plain; charset=ISO-8859-1 Hi MING TSANG, I think, there is just a typo. You give \sopranoVoiceI as last argument lyrics to the rehaersalMidi function. But that is the melody. \verseSopranoVoiceI are the lyrics. I changed that and the barcheck erros disappeared. HTH Jan-Peter On 23.01.2014 16:08, MING TSANG wrote: > 1- I now put spaces to the .ly code > 2- my original score has 129 measures; I thought cut it down to 24 > will show the warning barcheck error -- now I cut it down to 13 > 3- I updated S1*0\f with <>\f and I still have the same barcheck > warning. > > Here is the updated test-midi.ly Hi, Jan-Peter, Alex and David: Thank you for your help. I mixed up voice & verse. The pointer provided ease my frustration for sometime. I was going to give up because it is warning and everything seem ok. Thanks. Emmanuel, Ming.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shape of individual ties in chords
On Thu, Jan 23, 2014 at 8:01 AM, David Nalesnik wrote: > >> >>> >> There's also the attached file (which comes from >> http://www.mail-archive.com/lilypond-devel@gnu.org/msg47432/shape-tie-columns.ly) >> which will work with broken ties. >> >> > Here are some more useful values: \shapeTieColumn #'( ( () ((0 . 0.5) (0 . 0.5) (0 . 0.5) (0 . 0.5)) ) ; bottom ( () ((0 . 0) (0.33 . -0.25) (0.67 . -0.25) (1.0 . 0))) ; middle ( () ((0 . -0.5) (0 . -0.5) (0 . -0.5) (0 . -0.5)) ) ) % top ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Non-standard notation challenges (no game this time...)
Am 23.01.2014 16:56, schrieb Keith OHara: Urs Liska openlilylib.org> writes: The point in the edition of such snippets is to _document_ the actual state of a manuscript. This isn't _music_ but rather a remainder from the compositional process. Comparing this with later states allows an editor to draw conclusions on the genesis of the composition. You will probably need to use PostScript. http://www.lilypond.org/doc/v2.18/Documentation/notation/ formatting-text#graphic-notation-inside-markup Then those markings that have no certain interpretation are not input as musical glyphs that have an intended interpretaion, but as lines and curves. Probably the PostScript can be in text scripts, but with X-offset and Y-offset hand-tuned to particular numbers so that LilyPond does not try to place these marks herself. Thanks. I think this means: yes, I'm basically on the right track. Would text scripts be better to handle than markups? Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: bar-check warning when generating rehearsal midi soprano, alto, tenor etc
Hi MING TSANG, I think, there is just a typo. You give \sopranoVoiceI as last argument lyrics to the rehaersalMidi function. But that is the melody. \verseSopranoVoiceI are the lyrics. I changed that and the barcheck erros disappeared. HTH Jan-Peter On 23.01.2014 16:08, MING TSANG wrote: > 1- I now put spaces to the .ly code > 2- my original score has 129 measures; I thought cut it down to 24 > will show the warning barcheck error -- now I cut it down to 13 > 3- I updated S1*0\f with <>\f and I still have the same barcheck > warning. > > Here is the updated test-midi.ly ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
ekmelily- support fo microtonal notation in lilypond
Daer community, for those who are interested in microtonal music and its notation: You should have look at http://www.ekmelic-music.org/en/ekmelily.htm it supports microtonal music notation in Lilypond. It also works with Linux (I've tested it) and it runs with Lilypond 2.18.! Stefan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: Non-standard notation challenges (no game this time...)
Urs Liska openlilylib.org> writes: > The point in the edition of such snippets is to _document_ the actual > state of a manuscript. This isn't _music_ but rather a remainder from > the compositional process. Comparing this with later states allows an > editor to draw conclusions on the genesis of the composition. You will probably need to use PostScript. http://www.lilypond.org/doc/v2.18/Documentation/notation/ formatting-text#graphic-notation-inside-markup Then those markings that have no certain interpretation are not input as musical glyphs that have an intended interpretaion, but as lines and curves. Probably the PostScript can be in text scripts, but with X-offset and Y-offset hand-tuned to particular numbers so that LilyPond does not try to place these marks herself. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: frescobaldi macports broken after update
Davide, Once again, many thanks for your support of Frescobaldi through MacPorts. Stan > On Jan 23, 2014, at 6:35 AM, Davide Liessi wrote: > > 2014/1/18 Davide Liessi : >> I'll let you know when the patch will be commited. > > The patch is now in MacPorts. > Enter in the Terminal > > sudo port selfupdate > sudo port upgrade outdated > > and you'll get a working Poppler installation and a working Music View > in Frescobaldi. > Best wishes. > Davide ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: bar-check warning when generating rehearsal midi soprano, alto, tenor etc
1- I now put spaces to the .ly code 2- my original score has 129 measures; I thought cut it down to 24 will show the warning barcheck error -- now I cut it down to 13 3- I updated S1*0\f with <>\f and I still have the same barcheck warning. Here is the updated test-midi.ly Starting lilypond-windows.exe 2.19.0 [test-midi.ly]... Processing `C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly' Parsing... Interpreting music... C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:27:7: warning: barcheck failed at: 7/8 r4 R1*6 %m00-06 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:28:3: warning: barcheck failed at: 3/8 R1*3 r2^\markup"Soprano Solo"r4 g'8 a'8 |%m07-10 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:28:45: warning: barcheck failed at: 7/8 R1*3 r2^\markup"Soprano Solo"r4 g'8 a'8 |%m07-10 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:29:27: warning: barcheck failed at: 5/6 b'4. d'8~ d'4 b'8( a'8) | a'2 r4 a'8 b'8 |%m11-12 MIDI output to `test-midi-sopranoVoiceI.mid'... Interpreting music... C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:43:8: warning: barcheck failed at: 7/8 r4 R1*6 |%m00-06 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:44:3: warning: barcheck failed at: 3/8 R1*3 r2^\markup"Tenor Solo" r4 g8 a8 |%m07-10 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:44:42: warning: barcheck failed at: 7/8 R1*3 r2^\markup"Tenor Solo" r4 g8 a8 |%m07-10 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:45:18: warning: barcheck failed at: 2/3 b4. b8~ b4 d'4 | d'2 r4 c'8 b8 |%m11-12 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:45:34: warning: barcheck failed at: 7/8 b4. b8~ b4 d'4 | d'2 r4 c'8 b8 |%m11-12 MIDI output to `test-midi-tenorVoiceI.mid'... Interpreting music... C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:27:7: warning: barcheck failed at: 7/8 r4 R1*6 %m00-06 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:28:3: warning: barcheck failed at: 3/8 R1*3 r2^\markup"Soprano Solo"r4 g'8 a'8 |%m07-10 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:28:45: warning: barcheck failed at: 7/8 R1*3 r2^\markup"Soprano Solo"r4 g'8 a'8 |%m07-10 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:29:27: warning: barcheck failed at: 5/6 b'4. d'8~ d'4 b'8( a'8) | a'2 r4 a'8 b'8 |%m11-12 MIDI output to `test-midi-sopranoVoiceII.mid'... Interpreting music... C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:43:8: warning: barcheck failed at: 7/8 r4 R1*6 |%m00-06 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:44:3: warning: barcheck failed at: 3/8 R1*3 r2^\markup"Tenor Solo" r4 g8 a8 |%m07-10 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:44:42: warning: barcheck failed at: 7/8 R1*3 r2^\markup"Tenor Solo" r4 g8 a8 |%m07-10 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:45:18: warning: barcheck failed at: 2/3 b4. b8~ b4 d'4 | d'2 r4 c'8 b8 |%m11-12 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:45:34: warning: barcheck failed at: 7/8 b4. b8~ b4 d'4 | d'2 r4 c'8 b8 |%m11-12 MIDI output to `test-midi-tenorVoiceII.mid'... Interpreting music... C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:43:8: warning: barcheck failed at: 7/8 r4 R1*6 |%m00-06 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:44:3: warning: barcheck failed at: 3/8 R1*3 r2^\markup"Tenor Solo" r4 g8 a8 |%m07-10 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:44:42: warning: barcheck failed at: 7/8 R1*3 r2^\markup"Tenor Solo" r4 g8 a8 |%m07-10 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:45:18: warning: barcheck failed at: 2/3 b4. b8~ b4 d'4 | d'2 r4 c'8 b8 |%m11-12 C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly:45:34: warning: barcheck failed at: 7/8 b4. b8~ b4 d'4 | d'2 r4 c'8 b8 |%m11-12 MIDI output to `test-midi-bassVoice.mid'... Interpreting music...[8][16][16] Preprocessing graphical objects... Interpreting music... MIDI output to `test-midi.mid'... Finding the ideal number of pages... Fitting music on 2 or 3 pages... Drawing systems... Layout output to `test-midi.ps'... Converting to `./test-midi.pdf'... Success: compilation successfully completed Completed successfully in 4.7". On Thursday, January 23, 2014 4:47:10 AM, Phil Holmes wrote: - Original Message - From: "David Kastrup" To: "MING TSANG" Cc: "lilypond-user mailinglist" Sent: Thursday, January 23, 2014 2:15 AM Subject: Re: bar-check warning when generating rehearsal midi soprano, alto,tenor etc > MING TSANG writes: > >> When compile the .ly there is no warning or error in the log file: >> Starting lilypond-windows.exe 2.19.0 [test-midi.ly]... >> Processing `C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly' >> Parsing... >> Interpreting music...[8][16][24][32] >> Preprocessing graphical objects... >> Interpreting music... >> MIDI output to `test-midi.mid'... >> Finding the ideal number of pages... >> Fitting music on 3 or 4 pages... >> Drawing systems... >> Layout output to `test-midi.ps'... >> Converting to `./test-m
Re: frescobaldi macports broken after update
2014/1/18 Davide Liessi : > I'll let you know when the patch will be commited. The patch is now in MacPorts. Enter in the Terminal sudo port selfupdate sudo port upgrade outdated and you'll get a working Poppler installation and a working Music View in Frescobaldi. Best wishes. Davide ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shape of individual ties in chords
Hi again, On Thu, Jan 23, 2014 at 8:01 AM, David Nalesnik wrote: > Hi, > > > On Wed, Jan 22, 2014 at 4:55 PM, Thomas Morley > wrote: > > >> Below some coding just to show that it can be done. >> It's a very first sketch, several issues are present (p.e. linebreak) >> Might be a starting point, though. >> >> > There's also the attached file (which comes from > http://www.mail-archive.com/lilypond-devel@gnu.org/msg47432/shape-tie-columns.ly) > which will work with broken ties. > > I should point out that in the example, the first part of the broken ties is left alone: () there is equivalent to ((0 . 0) (0 . 0) (0 . 0) (0 . 0)). --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shape of individual ties in chords
Hi,
On Wed, Jan 22, 2014 at 4:55 PM, Thomas Morley wrote:
> Below some coding just to show that it can be done.
> It's a very first sketch, several issues are present (p.e. linebreak)
> Might be a starting point, though.
>
>
There's also the attached file (which comes from
http://www.mail-archive.com/lilypond-devel@gnu.org/msg47432/shape-tie-columns.ly)
which will work with broken ties.
HTH,
David
\version "2.18.0"
function for offsetting control-points of a TieColumn %
shapeTieColumn =
#(define-music-function (parser location all-offsets) (list?)
#{
\once \override TieColumn #'after-line-breaking =
#(lambda (grob)
(let ((ties (ly:grob-array->list (ly:grob-object grob 'ties
(for-each
(lambda (tie offsets-for-broken-pair)
(let* ((orig (ly:grob-original tie))
(siblings (ly:spanner-broken-into orig)))
(for-each
(lambda (piece offsets-for-piece)
(if (pair? offsets-for-piece)
(set! (ly:grob-property piece 'control-points)
(map
(lambda (x y) (coord-translate x y))
(ly:tie::calc-control-points piece)
offsets-for-piece
(if (null? siblings)
(list orig)
siblings)
offsets-for-broken-pair)))
ties all-offsets)))
#})
%% EXAMPLE %
{
1 ~
\break
q
\break
q ~
\shapeTieColumn #'(
( () ((0 . 1) (0 . 1) (0 . 1) (0 . 1)) )
( () ((0 . -0.1) (0.5 . -0.4) (1.5 . -0.4) (2 . -0.1)))
( () ((0 . -2) (0 . -1) (0 . -1) (0 . -1)) ) )
\break
q
}
\layout {
indent = 0
ragged-right = ##t
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: Non-standard notation challenges (no game this time...)
Am 23.01.2014 10:39, schrieb Phil Holmes: > The problem I would have when presented with this music is that I would have no idea - not a clue - about what the writer of the music intended with this notation. Is it explained anywhere? Without that, it seems rather pointless to try to reproduce it. The point in the edition of such snippets is to _document_ the actual state of a manuscript. This isn't _music_ but rather a remainder from the compositional process. Comparing this with later states allows an editor to draw conclusions on the genesis of the composition. And since it is very hard to describe something like this verbally it is typeset. In the case of the current example it may be that Schoenberg initially drew the barline at a different place and then "simply" turned it into a cross-staff stem by cancelling it out. Depending on the context (that I don't know in this case, I just randomly scanned a few snippets) his may suggest ideas/questions/answers about a possible change of mind regarding the metrical structure during the compositional process. Another aspect: I'm quite sure that the partial stem above the highest note doesn't mean _anything_ but simply hasn't been cancelled. But no editor can tell this definitely, and therefore it is important to document it as closely as possible to allow later editors to come to differing conclusions. This isn't a hypothetical mind-play. There were numerous instances when I came to differing conclusions than editors of scholarly editions (which isn't any critique towards them but just the way it works). And there were occasions where I came to differing conclusions after inspecting the autograph sources themselves and thought that some aspects hadn't been documented thoroughly enough in the editions. Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Hatches
Hi, I never worked with that kind of stuff, so I'd like to get some feedback and hints _before_ digging into the docs myself. So I explicitly don't expect ready solutions, just a few comments if my approach would be right. I'm looking for a way to typeset hatched cancellations in manuscripts such as in the attached images. I would approach this kind of stuff by drawing lines in a markup, is that the right way? And (more importantly) would it be possible to write a markup function where I can - create an arbitrary shape (with a path?) - make this shape itself transparent - fill this shape with hatches - configure angle, density, thickness of the hatches ? And, additionally, would it be possible to write a function that (more or less) automatically applies such a cancellation to beams or subbeams as shown in the images? As said, all I'd like to know is if that's reasonably possible so I can say that it'll be possible to create a working infrastructure for this kind of tasks. TIA Urs <><><>___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 64-bit font problems in GUB
On Thu, Jan 23, 2014 at 10:36 AM, Phil Holmes wrote: > - Original Message - From: "Simon Bailey" <...SNIP SNAP...> >> This leads me to conclude that there seems to be a problem with the >> 64-bit version of the font libraries in the build system for the >> release packages. Can anyone comment on this? Should I forward this >> information to the bug list? > > Yes. done. -- Do not meddle in the affairs of trombonists, for they are subtle and quick to anger. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: When was dot notation for dotted property paths added?
On 01/23/2014 10:52 AM, David Kastrup wrote: Peter Bjuhr writes: Could it be this: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=680df85187d0f3862b1ef1cf7a14f8ad7b7f0ee9;hp=ee89ee2c8ee328ec261b822aa9e260c9d623c086 No. Sorry! Probably followed an old link! Best Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: When was dot notation for dotted property paths added?
Am 23.01.2014 10:50, schrieb David Kastrup: Urs Liska writes: Somewhere in 2.17. David introduced the change from \override Stem #'length to \override Stem.length I would like to know in which LilyPond version this appeared. Somehow I don't seem to be able to think of the right search terms to locate the commit(s). convert-ly -s is probably most helpful for syntax changes. It's not a full hit here since the syntax change is an _optional_ one (and does not require a convert-ly rule), but there are enough _related_ changes that it's obvious. Thanks. Sorry I didn't know this. Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: When was dot notation for dotted property paths added?
Am 23.01.2014 10:47, schrieb David Kastrup: Urs Liska writes: Somewhere in 2.17. David introduced the change from \override Stem #'length to \override Stem.length I would like to know in which LilyPond version this appeared. 2.17.6, http://code.google.com/p/lilypond/issues/detail?id=2883> Thanks Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: When was dot notation for dotted property paths added?
Am 23.01.2014 10:52, schrieb Noeck:
Hi Urs,
why not just test it? It works for 2.17.9 so it should with .10, too:
\version "2.17.9"
{
\override Stem.length = #30
a
}
Cheers,
Joram
Maybe I'm somewhat selfish, but I only have 2.17.3 and 2.17.96 still
present, and I thought asking here would be less invasive than
downloading a complete version...
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: When was dot notation for dotted property paths added?
Hi Urs,
why not just test it? It works for 2.17.9 so it should with .10, too:
\version "2.17.9"
{
\override Stem.length = #30
a
}
Cheers,
Joram
Am 23.01.2014 10:40, schrieb Urs Liska:
> Somewhere in 2.17. David introduced the change from
>
> \override Stem #'length
> to
> \override Stem.length
>
> I would like to know in which LilyPond version this appeared.
> Somehow I don't seem to be able to think of the right search terms to
> locate the commit(s).
>
> Concretely, I have a snippet that needs \version "2.17.10" and I would
> like to know which notation I can use.
>
> TIA
> Urs
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: When was dot notation for dotted property paths added?
Peter Bjuhr writes: > On 01/23/2014 10:40 AM, Urs Liska wrote: >> Somewhere in 2.17. David introduced the change from >> >> \override Stem #'length >> to >> \override Stem.length >> >> I would like to know in which LilyPond version this appeared. >> Somehow I don't seem to be able to think of the right search terms >> to locate the commit(s). >> >> Concretely, I have a snippet that needs \version "2.17.10" and I >> would like to know which notation I can use. >> >> > > Could it be this: > http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=680df85187d0f3862b1ef1cf7a14f8ad7b7f0ee9;hp=ee89ee2c8ee328ec261b822aa9e260c9d623c086 No. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: When was dot notation for dotted property paths added?
On 01/23/2014 10:40 AM, Urs Liska wrote: Somewhere in 2.17. David introduced the change from \override Stem #'length to \override Stem.length I would like to know in which LilyPond version this appeared. Somehow I don't seem to be able to think of the right search terms to locate the commit(s). Concretely, I have a snippet that needs \version "2.17.10" and I would like to know which notation I can use. Could it be this: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=680df85187d0f3862b1ef1cf7a14f8ad7b7f0ee9;hp=ee89ee2c8ee328ec261b822aa9e260c9d623c086 Best Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: When was dot notation for dotted property paths added?
Urs Liska writes: > Somewhere in 2.17. David introduced the change from > > \override Stem #'length > to > \override Stem.length > > I would like to know in which LilyPond version this appeared. 2.17.6, http://code.google.com/p/lilypond/issues/detail?id=2883> -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: When was dot notation for dotted property paths added?
Urs Liska writes: > Somewhere in 2.17. David introduced the change from > > \override Stem #'length > to > \override Stem.length > > I would like to know in which LilyPond version this appeared. > Somehow I don't seem to be able to think of the right search terms to > locate the commit(s). convert-ly -s is probably most helpful for syntax changes. It's not a full hit here since the syntax change is an _optional_ one (and does not require a convert-ly rule), but there are enough _related_ changes that it's obvious. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: bar-check warning when generating rehearsal midi soprano, alto, tenor etc
- Original Message - From: "David Kastrup" To: "MING TSANG" Cc: "lilypond-user mailinglist" Sent: Thursday, January 23, 2014 2:15 AM Subject: Re: bar-check warning when generating rehearsal midi soprano, alto,tenor etc MING TSANG writes: When compile the .ly there is no warning or error in the log file: Starting lilypond-windows.exe 2.19.0 [test-midi.ly]... Processing `C:/Users/Tsang/Dropbox/CHOIR/the-rock/test-midi.ly' Parsing... Interpreting music...[8][16][24][32] Preprocessing graphical objects... Interpreting music... MIDI output to `test-midi.mid'... Finding the ideal number of pages... Fitting music on 3 or 4 pages... Drawing systems... Layout output to `test-midi.ps'... Converting to `./test-midi.pdf'... Success: compilation successfully completed Completed successfully in 7.4". but when I added rehearsal midi generation, I got warning bar-check error. The rehearsal midi is adopted (generated) from Frescobaldi v2.0.13: Starting lilypond-windows.exe 2.19.0 [test-midi.ly]... If you replace all occurences of s1*0 with <> the problem might go away. And one cannot help but notice that you don't seem fond of the space bar. I get a further warning: D:/Music/LilyPondDev/BugSquad/test-midi.ly:19:3: warning: trying to use \partial after the start of a piece \partial 4 So my guess is that it's not picking up the \partial command at the right time, and thus r4 R1*6 is a bar check error. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
When was dot notation for dotted property paths added?
Somewhere in 2.17. David introduced the change from \override Stem #'length to \override Stem.length I would like to know in which LilyPond version this appeared. Somehow I don't seem to be able to think of the right search terms to locate the commit(s). Concretely, I have a snippet that needs \version "2.17.10" and I would like to know which notation I can use. TIA Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Non-standard notation challenges (no game this time...)
- Original Message - From: "Urs Liska" To: "lilypond-user" Sent: Wednesday, January 22, 2014 11:59 PM Subject: Non-standard notation challenges (no game this time...) Hi all, I'm facing some notation challenges that aren't part of a self-devised "contest", but in way very real. I'm going to meet someone to answer his questions about how LilyPond and related tools could be integrated in the workflows of a concrete edition project. I don't know if this meeting can possibly have any particular "outcome", but _if_ it should, it would certainly not only be good for me but also for LilyPond. The issue I'm currently thinking about is that there are sketches and drafts that have to be engraved, showing very non-standard notations. The problem I would have when presented with this music is that I would have no idea - not a clue - about what the writer of the music intended with this notation. Is it explained anywhere? Without that, it seems rather pointless to try to reproduce it. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 64-bit font problems in GUB
- Original Message - From: "Simon Bailey" To: "lilypond-user Mailinglist" Sent: Thursday, January 23, 2014 9:20 AM Subject: 64-bit font problems in GUB Hello, I kicked this thread off last week sometime: http://lists.gnu.org/archive/html/lilypond-user/2014-01/msg00762.html TL/DR summary: ligatures were not being shown for lilypond-generated output. further investigation led me to: http://lists.gnu.org/archive/html/lilypond-user/2014-01/msg00804.html TL/DR summary: GUB lilypond packages for 32-bit show ligatures, 64-bit packages do not. I verified this on a stock fedora 20 installation using the 2.18.0 packages downloaded from lilypond.org. the Mac OSX packages distributed through lilypond.org also show the same behaviour, i.e. no ligatures. for testing purposes, i have also verified this behaviour with the latest 2.19.1 releases. I followed these instructions: http://nicolas.sceaux.free.fr/index.php/2008/01/20/26-building-lilypond-from-git-sources-on-mac-os-105-intel (adapting them somewhat for more modern builds and interpolating with INSTALL.txt -- removed the kpathsea options, had to install some extra ports). after building lilypond (showing version 2.19.2) on my mac, using the font libraries installed by MacPorts, ligatures are shown. I will build lilypond from source on my linux box later today; I expect the bevaviour to be the same as on OS X -- i.e. the ligatures will work. This leads me to conclude that there seems to be a problem with the 64-bit version of the font libraries in the build system for the release packages. Can anyone comment on this? Should I forward this information to the bug list? Yes. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
64-bit font problems in GUB
Hello, I kicked this thread off last week sometime: http://lists.gnu.org/archive/html/lilypond-user/2014-01/msg00762.html TL/DR summary: ligatures were not being shown for lilypond-generated output. further investigation led me to: http://lists.gnu.org/archive/html/lilypond-user/2014-01/msg00804.html TL/DR summary: GUB lilypond packages for 32-bit show ligatures, 64-bit packages do not. I verified this on a stock fedora 20 installation using the 2.18.0 packages downloaded from lilypond.org. the Mac OSX packages distributed through lilypond.org also show the same behaviour, i.e. no ligatures. for testing purposes, i have also verified this behaviour with the latest 2.19.1 releases. I followed these instructions: http://nicolas.sceaux.free.fr/index.php/2008/01/20/26-building-lilypond-from-git-sources-on-mac-os-105-intel (adapting them somewhat for more modern builds and interpolating with INSTALL.txt -- removed the kpathsea options, had to install some extra ports). after building lilypond (showing version 2.19.2) on my mac, using the font libraries installed by MacPorts, ligatures are shown. I will build lilypond from source on my linux box later today; I expect the bevaviour to be the same as on OS X -- i.e. the ligatures will work. This leads me to conclude that there seems to be a problem with the 64-bit version of the font libraries in the build system for the release packages. Can anyone comment on this? Should I forward this information to the bug list? regards, sb -- Do not meddle in the affairs of trombonists, for they are subtle and quick to anger. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
