Re: ANN: Frescobaldi 2.17.1
Il 28/12/14 05.27, Henning Hraban Ramm ha scritto: Am 2014-12-28 um 06:33 schrieb Stan Sanderson stans...@gmail.com: Would there be any advantage to installing the (soon to be released) MacPorts update instead of the dmg file provided by the Frescobaldi website? For me the advantage is that I can update a bunch of my tools with one call of my update script (that includes a „call to port“) without the need to open a website, search for the download, wait for it to complete, open the file, click here, click there… As Hraban said, MacPorts helps you keep your software up to date, and given that you already have MacPorts installed (if I remember correctly) I would keep using it. Anyway, from a new user's point of view, I would say that you want to install with MacPorts if you already use MacPorts for other software, or if you want to help with Frescobaldi's development. If this is not the case, it's probably simpler to use the DMG. Best wishes. Davide ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: Frescobaldi 2.17.1
Il 27/12/14 18.12, Conor Cook ha scritto: Is this available from MacPorts yet, or will it once it gets into their system? Frescobaldi 2.17.1 is now available on MacPorts. As usual you just need to sudo port selfupdate and then (to upgrade all outdated ports) sudo port upgrade outdated Best wishes. Davide ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Gregorian chant input in LilyPond
Conversion between gregorio and lilypond is a relevant topic for me too. Some time ago I started working on it - https://github.com/igneus/lygre - and for now there is grely, a Ruby script translating gabc to simple lilypond (simplified modern notation, not the quadratic notation also supported by lilypond). Now I see the installation instructions on github are outdated. I will try to update them ASAP. The lygre package is now available as a Ruby gem, which is more convenient to install and use. I'm not sure if grely as it is now would be of any use for you, Joram. If you have any wishes what more it could do, feel free to express them. In the future I might get back to grely and implement some of them. Crash- and bug-reports are also welcome. Some kind of lilypond to gabc translator is also planned, because I have a huge corpus of chants written in Lilypond that I would eventually like to be able to convert to gabc. Regards, Jakub 2014-12-28 0:12 GMT+01:00 Noeck noeck.marb...@gmx.de: Dear Br. Samuel, thanks for your thoughts in reply to my mail! Am 27.12.2014 um 23:48 schrieb Br. Samuel Springuel: The biggest issue for this would be the fact that gabc and lilypond notation approach representing music from two different view points. I know that, but it does not seem such a big issue to me: The gabc input should contain a clef (c2 or f3 etc.) and this would fix the relation between the two representations, wouldn’t it. (This implies that there is no general conversion of a-m (gabc) to a-g (LP) but a clef-dependent one). This way I would end up with a definition which note (a-m) is a do and so on. However, it would not mean that the la is 400 Hz. But this latter issue can not be solved in a general way. Or do I still have a misconception here? I would even see that difference as a gain, because the key independent input of gabc seems convenient to me (for chant notation) and the LP representation could be still used in a normal staff and could be transposed. So it would combine the best of two approaches. In fact, I am a bit more concerned about the spacing. In gabc, one can set the spacing within a neume and I don’t know how to do that in LP and gregorio cares less about the timing than LP. I suspect that not everyone would be satisfied with any particular solution. That might be true and perhaps my reasoning above is too naive. Please correct me then. Cheers, Joram ___ 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: Mac DMG
Dear Arthur, Il 28/12/14 05.30, Henning Hraban Ramm ha scritto: Am 2014-12-28 um 07:56 schrieb Arthur Hixson ac.hix...@comcast.net: My Lilypond is installed in an app and Frescobaldi is not able to find it. And I’m not able to put the app in the path in the preference dialog. I’ve tried copying the executable to my bin folder and set the path to that, but it still is not found. What’s the trick here? Include the real LilyPond executable (within the app) in your PATH: export PATH=$PATH:/Applications/LilyPond.app/Contents/Resources/bin Use this line in a ~/.bashrc or ~/.profile file. this is very handy (and I would recommend it, too) may you need to use LilyPond from the command line, but it is not necessary to make Frescobaldi use LilyPond. Go to Frescobaldi's Preferences - LilyPond Preferences: you probably have only one entry in the list. Edit it and in the LilyPond Command field choose the LilyPond application (the typical value of the text box will be `/Applications/LilyPond.app`, no need to go inside the application bundle). Then click OK and Frescobaldi should be able to find and use LilyPond. If this does not work, then there is either a bug in Frescobaldi or a fault in your setup. Please let me know in any case. Best wishes. Davide P.S. This should not have happened in the first place: with the default settings (before you edit the LilyPond list) Frescobaldi should automatically find either /Applications/LilyPond.app or /opt/local/bin/lilypond (from MacPorts), if they are present. I'd like to find out why this did not happen: let me know if you are willing to help me with a couple of tests. :) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: Frescobaldi 2.17.1
Downloaded 2.17.1 but it will NOT install on my win8.1 64bit. The install window 'vanishes', disappears halfway through and nothing has happened. Erik Op zaterdag 27 december 2014 17:43:27 UTC+1 schreef Wilbert Berendsen: Hi all, Yesterday, shortly after releasing Frescobaldi 2.17, a bug was discovered that was also present in 2.0.16: when clicking File→Quit, selecting Cancel would also quit Frescobaldi, loosing the changes in unsaved documents. That was the reason 2.17.1 was released very quickly. I am proud that now this release contains, besides the Python sourcecode, also a fully self-contained Windows executable and Mac OS X .dmg files ready to deploy on Mac OS X. Thanks go to everyone who made this possible! Download: http://frescobaldi.org/download https://github.com/wbsoft/frescobaldi/releases Homepage: http://frescobaldi.org/ Happy 'Ponding and 2015! Wilbert Berendsen -- Wilbert Berendsen (http://www.wilbertberendsen.nl) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond markdown extension
Il giorno sab 27 dic 2014 alle 22:47, Noeck noeck.marb...@gmx.de ha scritto: Hi, I just wrote a markdown extension doing something similar as lilypond-book: It takes some LilyPond code and creates an image (formats provided by LilyPond) from it, which is then inserted at this point in the output html document. Probably, I am not the first one doing this. Is there any experience with any available md-LilyPond extension? Or would anyone be interested in my md-extension (python-markdown)? Mine is quite rough just now and I try to figure out whether it is worth polishing it or if that would be reinventing the wheel. I never heard about a markdown lilypond extension before. I'd be interested in trying it out. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
\\[ as music function – stack overflow
Hello,
when I start to compile the attached file, lily takes a long time for
parsing and then exits with Microsoft’s stack overflow/stack
exhaustion error code. I tested this with lily 2.19.8 and .15 and on
both Windows and Ubuntu platforms with similar results. How does this
come? and how to circumvent it?
Best regards,
Simon
\version 2.19.8
\\[ = #(define-music-function (parser location note) (ly:music?) #{ \[ $note \melisma #} )
\\] = { \] \melismaEnd }
\score {
\new Staff { \[ c1 d \] e }
\addlyrics { vi -- de }
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \\[ as music function – stack overflow
Hello Simon, The same occurs on Mac OS Yosemite with 2.19.15, but after a couple of seconds only: Starting lilypond 2.19.15 [stack-overflow.ly]... Traitement de « /Users/menu/Library/Containers/com.apple.mail/Data/Library/Mail Downloads/E613B990-D67A-4F8D-A5B3-60014C3478BF/stack-overflow.ly » Analyse... Exited with exit status 1. JM Le 28 déc. 2014 à 16:01, Simon Albrecht simon.albre...@mail.de a écrit : Hello, when I start to compile the attached file, lily takes a long time for parsing and then exits with Microsoft’s stack overflow/stack exhaustion error code. I tested this with lily 2.19.8 and .15 and on both Windows and Ubuntu platforms with similar results. How does this come? and how to circumvent it? Best regards, Simon stack-overflow.ly___ 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: Smarter double measure numbers
2014-12-28 4:09 GMT+01:00 Jon Arnold jonarnoldsem...@gmail.com:
Hi-
I have finally achieved a solution to the question I asked here:
http://lists.gnu.org/archive/html/lilypond-user/2014-10/msg00851.html
I'm doing this:
measureFixer_One = {
\set Score.barNumberVisibility = #all-bar-numbers-visible
\bar
\override Score.BarNumber.stencil
= #(lambda (grob)(grob-interpret-markup grob
#{ \markup {1 (7)}
#}))
s1
%etc etc...
\override Score.BarNumber.stencil
= #(lambda (grob)(grob-interpret-markup grob
#{ \markup {6 (12)}
#}))
\revert Score.BarNumber.stencil
\set Score.currentBarNumber = #13
}
The above works OK, especially because I am only doing this for 15 or so
bars each time, but I would really like a smarter function that takes the
currentBarNumber, adds a the difference as a parameter (in this case 6) and
prints n (n+x)
Part of the need is due to multiple editions (multimovement with contiguous
bar numbers vs. single movements)
Help?
Hi Jon,
a compilable example would have increased your chance to get an answer
earlier. ;)
Nevertheless, maybe the code below will work for you.
It works with different 'alternativeNumberingStyle' and line-breaks
mid-measure as well.
\version 2.19.15
% works with 2.18. as well
#(define (add-parenthesized-alternative-bar-numbers number)
(lambda (grob)
(let* ((text (ly:grob-property grob 'text))
;; If the internals change this may fail.
;; Same, if custom overrides are applied before.
(txt-arg (car (last text)))
(current-bar-number
(if (string-number txt-arg)
(string-number txt-arg)
;; If BarNumber is not a single number, get a list where
;; first sublist accumulates the numbers, second other stuff.
;; Clear second list from brackets and transform the lists
;; into strings.
;; Maybe overkill ;)
(call-with-values
(lambda ()
(partition
string-number
(map string (string-list txt-arg
(lambda (a b)
(if (member ( b)
(set! b
(filter
(lambda (s)
(and (not (string=? ) s))
(not (string=? ( s
b)))
(map string-concatenate (list a b))
(added-bar-number
(if (number? current-bar-number)
(number-string (+ number current-bar-number))
(if (and (list? current-bar-number)
(string-number (car current-bar-number)))
(string-append
(number-string
(+ number (string-number (car current-bar-number
(cadr current-bar-number))
(begin
(ly:warning
(_ \n\tnot smart enough to handle this BarNumber: ~a
current-bar-number))
?)
(ly:grob-set-property! grob 'text
#{
\markup {
$text
\override #'(padding . 0.1)
\parenthesize $added-bar-number
}
#}
newBarNumber =
#(define-music-function (parser location nmbr)(number?)
#{
\override Score.BarNumber.before-line-breaking =
#(add-parenthesized-alternative-bar-numbers nmbr)
#})
%% EXAMPLES
\layout {
\context {
\Score
\override BarNumber.self-alignment-X = #CENTER
barNumberVisibility = #all-bar-numbers-visible
}
}
music =
\relative c'' {
\bar
\repeat volta 3 {
c1 \break
^Testing line-break mid-measure
c2 \bar \break c2 \break
}
\alternative {
{
^Testing line-break mid-measure in an alternative ending
d2 \bar \break d2 \break
}
{ e1 \break }
{ f1 \break }
}
g1
\bar |.
}
\header {
title =
\markup
\column {
\rounded-box
\fill-line { Add a parenthesized number to default BarNumber }
\vspace #1
}
}
\score {
\new Staff \music
\layout {
\newBarNumber #4
}
\header {
piece =
\markup
\rounded-box
\bold
Adding alternative BarNumbers, 'alternativeNumberingStyle' is not set
}
}
\score {
\new Staff \music
\layout {
\newBarNumber #5
\context {
\Score
alternativeNumberingStyle = #'numbers
}
}
\header {
piece =
\markup
\rounded-box
\bold
Adding alternative BarNumbers, 'alternativeNumberingStyle' is set 'numbers
}
}
\score {
\new Staff \music
\layout {
Re: \\[ as music function – stack overflow
2014-12-28 16:01 GMT+01:00 Simon Albrecht simon.albre...@mail.de:
Hello,
when I start to compile the attached file, lily takes a long time for
parsing and then exits with Microsoft’s stack overflow/stack exhaustion
error code. I tested this with lily 2.19.8 and .15 and on both Windows and
Ubuntu platforms with similar results. How does this come? and how to
circumvent it?
Best regards,
Simon
Not exactly sure about the reason why your code fails, though you can
workaround with:
\\[ =
#(define-music-function (parser location note) (ly:music?)
#{
#(make-span-event 'LigatureEvent START)
$note
\melisma
#} )
\\] = { \] \melismaEnd }
\score {
\new Staff { \[ c1 d \] e }
\addlyrics { vi -- de }
}
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
slur shifted up by a fingering
I'm having this problem on a piece I'm writing but I cannot reproduce it by extracting the single measure. So no minimal example, I'll just attach the image showing the problem: the slur between two notes is moved up because of a right-hand fingering on the first one. This is the relevant line: ees\5-\rightHandFinger #2 8( \glissando e4\5) I've read NR 4.4.3, Vertical collision avoidance, and tried few overrides using outside-staff-priority and avoid-slur, but honestly I don't know really what I'm doing. Thanks for any hint Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: slur shifted up by a fingering
Hi Federico, I cannot reproduce your problem with the code you're giving. I suppose that you probably have somewhere an \override StrokeFinger.avoid-slur = #'inside - or kind of - haven't you ? Cheers, Pierre 2014-12-28 17:30 GMT+01:00 Federico Bruni fedel...@gmail.com: I'm having this problem on a piece I'm writing but I cannot reproduce it by extracting the single measure. So no minimal example, I'll just attach the image showing the problem: the slur between two notes is moved up because of a right-hand fingering on the first one. This is the relevant line: ees\5-\rightHandFinger #2 8( \glissando e4\5) I've read NR 4.4.3, Vertical collision avoidance, and tried few overrides using outside-staff-priority and avoid-slur, but honestly I don't know really what I'm doing. Thanks for any hint Federico ___ 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: slur shifted up by a fingering
Here's what I meant:
\version 2.19.15
\transpose c c' {
\time 2/4
{
%% please comment the following line:
\override StrokeFinger.avoid-slur = #'inside
ees-1\5-\rightHandFinger #2 8( \glissando e4\5)
g\rightHandFinger #4 8
}
\\
{
r8 r4 r8
}
}
\layout {
\context {
\Staff
\key bes\major
\omit StringNumber
\omit TimeSignature
\omit KeySignature
\omit Clef
fingeringOrientations = #'(left)
strokeFingerOrientations = #'(up)
}
}
So maybe you could try in your score:
...
\once\revert StrokeFinger.avoid-slur
ees-1\5-\rightHandFinger #2 8( \glissando e4\5)
...
HTH,
Pierre
2014-12-28 17:52 GMT+01:00 Pierre Perol-Schneider
pierre.schneider.pa...@gmail.com:
Hi Federico,
I cannot reproduce your problem with the code you're giving.
I suppose that you probably have somewhere an
\override StrokeFinger.avoid-slur = #'inside
- or kind of - haven't you ?
Cheers,
Pierre
2014-12-28 17:30 GMT+01:00 Federico Bruni fedel...@gmail.com:
I'm having this problem on a piece I'm writing but I cannot reproduce it
by extracting the single measure.
So no minimal example, I'll just attach the image showing the problem:
the slur between two notes is moved up because of a right-hand fingering on
the first one.
This is the relevant line:
ees\5-\rightHandFinger #2 8( \glissando e4\5)
I've read NR 4.4.3, Vertical collision avoidance, and tried few overrides
using outside-staff-priority and avoid-slur, but honestly I don't know
really what I'm doing.
Thanks for any hint
Federico
___
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: slur shifted up by a fingering
No, I don't. In fact the revert suggested in your last email doesn't change anything. I'll send the files to you privately (copyrighted stuff). Il giorno dom 28 dic 2014 alle 17:52, Pierre Perol-Schneider pierre.schneider.pa...@gmail.com ha scritto: Hi Federico, I cannot reproduce your problem with the code you're giving. I suppose that you probably have somewhere an \override StrokeFinger.avoid-slur = #'inside - or kind of - haven't you ? Cheers, Pierre 2014-12-28 17:30 GMT+01:00 Federico Bruni fedel...@gmail.com: I'm having this problem on a piece I'm writing but I cannot reproduce it by extracting the single measure. So no minimal example, I'll just attach the image showing the problem: the slur between two notes is moved up because of a right-hand fingering on the first one. This is the relevant line: ees\5-\rightHandFinger #2 8( \glissando e4\5) I've read NR 4.4.3, Vertical collision avoidance, and tried few overrides using outside-staff-priority and avoid-slur, but honestly I don't know really what I'm doing. Thanks for any hint Federico ___ 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: \\[ as music function – stack overflow
Hi Simon,
On Sun, Dec 28, 2014 at 9:01 AM, Simon Albrecht simon.albre...@mail.de
wrote:
Hello,
when I start to compile the attached file, lily takes a long time for
parsing and then exits with Microsoft’s stack overflow/stack exhaustion
error code. I tested this with lily 2.19.8 and .15 and on both Windows and
Ubuntu platforms with similar results. How does this come? and how to
circumvent it?
I'd assume the reason this happens is because you call [\ within its
definition, leading to infinite recursion.
For example, this works:
\\' =
#(define-music-function (parser location note)
(ly:music?) #{ \[ $note \melisma #} )
\\] = { \melismaEnd }
\score {
\new Staff { \' c1 d \] e }
\addlyrics { vi -- de }
}
but this results in a stack overflow:
\\' =
#(define-music-function (parser location note)
(ly:music?) #{ \' $note \melisma #} )
\\] = { \melismaEnd }
\score {
\new Staff { \' c1 d \] e }
\addlyrics { vi -- de }
}
HTH,
David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Beaming problem
Hi,
I stumbled on a small beaming problem. Attached two small .PNG’s for what
should be there (never mind the 7/4, that is a writo), my experimental output
and below my compiling code as for what I tried. The problem is in the second
voice showing hickups in the second part of both measures where the 1/16 notes
are beamed special. When I don’t do the manual beaming I get a pattern which
the composer doesn’t like. It looks allright in the first voice, I have about
10 of these and always the beaming in the second voice breaks, the first voice
is allright. May be that is a clue to where the problem is?
Is there a possibility to get these beamings in a straigth line? Or is this a
bug I which should report?
Regards,
Wim.
My simple experimenting code, but not working as I want it to:
\version 2.18.0
VoiceI = \relative f' {
\time 7/8
e8.[ dis16] e8.[ dis16]
fis[
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
cis
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
cis
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
b
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
b
cis] |
e8.[ dis16] e8.[ dis16]
fis[
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
cis
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
cis
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
b
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
b
cis] |
}
VoiceII= \relative f' {
\time 7/8
fis16 e8. fis16 e8.
e16
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
e
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
e
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
fis
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
e
fis] |
e16 fis8. e16 fis8.
e16
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
fis
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
fis
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
e
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
fis
e] |
}
\score {
\new StaffGroup {
\new Staff {
\VoiceI
}
\new Staff {
\VoiceII
}
}
}%end score
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Create one png image per pageBreak?
Thomas Morley thomasmorley65 at gmail.com writes: 2014-12-23 3:58 GMT+01:00 Stan Mulder st45882wz at earthlink.net: Attachment (simple-chord-names.ly): text/x-lilypond, 11 KiB Attachment (chords-02.ly): text/x-lilypond, 5950 bytes Attachment (predefined-plectrum-banjo-fretboards.ly): text/x-lilypond, 8 KiB Thomas, That is awesome! It is over my head, but it works. I am filling out the fingerings for the plectrum banjo fretboard. I will let you know how it goes. Many thanks! Stan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem
Wim,
you are missing the open [ for the groupings in the bottomstaff.
regards,
Shane
On Sun, Dec 28, 2014 at 12:32 PM, Wim van Dommelen m...@wimvd.nl wrote:
Hi,
I stumbled on a small beaming problem. Attached two small .PNG’s for what
should be there (never mind the 7/4, that is a writo), my experimental
output and below my compiling code as for what I tried. The problem is in
the second voice showing hickups in the second part of both measures where
the 1/16 notes are beamed special. When I don’t do the manual beaming I get
a pattern which the composer doesn’t like. It looks allright in the first
voice, I have about 10 of these and always the beaming in the second voice
breaks, the first voice is allright. May be that is a clue to where the
problem is?
Is there a possibility to get these beamings in a straigth line? Or is
this a bug I which should report?
Regards,
Wim.
My simple experimenting code, but not working as I want it to:
\version 2.18.0
VoiceI = \relative f' {
\time 7/8
e8.[ dis16] e8.[ dis16]
fis[
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
cis
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
cis
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
b
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
b
cis] |
e8.[ dis16] e8.[ dis16]
fis[
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
cis
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
cis
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
b
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
b
cis] |
}
VoiceII= \relative f' {
\time 7/8
fis16 e8. fis16 e8.
e16
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
e
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
e
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
fis
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
e
fis] |
e16 fis8. e16 fis8.
e16
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
fis
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
fis
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
e
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
fis
e] |
}
\score {
\new StaffGroup {
\new Staff {
\VoiceI
}
\new Staff {
\VoiceII
}
}
}%end score
___
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: ANN: Frescobaldi 2.17.1
Thanks for the continued work. It is a wonderful tool. Shane On Sun, Dec 28, 2014 at 8:15 AM, ursus.k...@gmail.com wrote: Downloaded 2.17.1 but it will NOT install on my win8.1 64bit. The install window 'vanishes', disappears halfway through and nothing has happened. Erik Op zaterdag 27 december 2014 17:43:27 UTC+1 schreef Wilbert Berendsen: Hi all, Yesterday, shortly after releasing Frescobaldi 2.17, a bug was discovered that was also present in 2.0.16: when clicking File→Quit, selecting Cancel would also quit Frescobaldi, loosing the changes in unsaved documents. That was the reason 2.17.1 was released very quickly. I am proud that now this release contains, besides the Python sourcecode, also a fully self-contained Windows executable and Mac OS X .dmg files ready to deploy on Mac OS X. Thanks go to everyone who made this possible! Download: http://frescobaldi.org/download https://github.com/wbsoft/frescobaldi/releases Homepage: http://frescobaldi.org/ Happy 'Ponding and 2015! Wilbert Berendsen -- Wilbert Berendsen (http://www.wilbertberendsen.nl) ___ 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: Beaming problem
Wim,
On Sun, Dec 28, 2014 at 11:47 AM, Shane Brandes sh...@grayskies.net wrote:
Wim,
you are missing the open [ for the groupings in the bottomstaff.
regards,
Shane
On Sun, Dec 28, 2014 at 12:32 PM, Wim van Dommelen m...@wimvd.nl wrote:
Hi,
I stumbled on a small beaming problem. Attached two small .PNG’s for what
should be there (never mind the 7/4, that is a writo), my experimental
output and below my compiling code as for what I tried. The problem is in
the second voice showing hickups in the second part of both measures where
the 1/16 notes are beamed special. When I don’t do the manual beaming I get
a pattern which the composer doesn’t like. It looks allright in the first
voice, I have about 10 of these and always the beaming in the second voice
breaks, the first voice is allright. May be that is a clue to where the
problem is?
Is there a possibility to get these beamings in a straigth line? Or is
this a bug I which should report?
Regards,
Wim.
Looks like Shane has found your problem, but I'd like to suggest a much
less tedious way to get what you're after:
\version 2.18.0
VoiceI = \relative f' {
\time 7/8
e8.[ dis16] e8.[ dis16]
\set subdivideBeams = ##t
fis[ cis cis b b cis] |
e8.[ dis16] e8.[ dis16]
fis[ cis cis b b cis] |
}
VoiceII= \relative f' {
\time 7/8
\set subdivideBeams = ##t
fis16 e8. fis16 e8.
e16[ e e fis e fis] |
e16 fis8. e16 fis8.
e16 fis fis e fis e] |
}
\score {
\new StaffGroup {
\new Staff {
\VoiceI
}
\new Staff {
\VoiceII
}
}
}%end score
You can read about this in the snippet subdividing beams at
http://lilypond.org/doc/v2.18/Documentation/notation/beams
--David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem
Hello,
Thanks for your anser.
The last line ov VoiceII should read (typo):
e16 [fis fis e fis e] |
JM
Le 28 déc. 2014 à 18:51, David Nalesnik david.nales...@gmail.com a écrit :
Wim,
On Sun, Dec 28, 2014 at 11:47 AM, Shane Brandes sh...@grayskies.net
mailto:sh...@grayskies.net wrote:
Wim,
you are missing the open [ for the groupings in the bottomstaff.
regards,
Shane
On Sun, Dec 28, 2014 at 12:32 PM, Wim van Dommelen m...@wimvd.nl
mailto:m...@wimvd.nl wrote:
Hi,
I stumbled on a small beaming problem. Attached two small .PNG’s for what
should be there (never mind the 7/4, that is a writo), my experimental output
and below my compiling code as for what I tried. The problem is in the second
voice showing hickups in the second part of both measures where the 1/16
notes are beamed special. When I don’t do the manual beaming I get a pattern
which the composer doesn’t like. It looks allright in the first voice, I have
about 10 of these and always the beaming in the second voice breaks, the
first voice is allright. May be that is a clue to where the problem is?
Is there a possibility to get these beamings in a straigth line? Or is this a
bug I which should report?
Regards,
Wim.
Looks like Shane has found your problem, but I'd like to suggest a much less
tedious way to get what you're after:
\version 2.18.0
VoiceI = \relative f' {
\time 7/8
e8.[ dis16] e8.[ dis16]
\set subdivideBeams = ##t
fis[ cis cis b b cis] |
e8.[ dis16] e8.[ dis16]
fis[ cis cis b b cis] |
}
VoiceII= \relative f' {
\time 7/8
\set subdivideBeams = ##t
fis16 e8. fis16 e8.
e16[ e e fis e fis] |
e16 fis8. e16 fis8.
e16 fis fis e fis e] |
}
\score {
\new StaffGroup {
\new Staff {
\VoiceI
}
\new Staff {
\VoiceII
}
}
}%end score
You can read about this in the snippet subdividing beams at
http://lilypond.org/doc/v2.18/Documentation/notation/beams
http://lilypond.org/doc/v2.18/Documentation/notation/beams
--David
___
lilypond-user mailing list
lilypond-user@gnu.org mailto:lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
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: Beaming problem
Shane, David and Jacques,
Thanks very much, both solutions work, David show the easiest one for a regular
set-up, but Shane solutions gives me also the opportunity to do a 3-3 division
when needed.
Thanks again!
Regards,
Wim.
On 28 Dec 2014, at 20:07 , Jacques Menu imj-muz...@bluewin.ch wrote:
Hello,
Thanks for your anser.
The last line ov VoiceII should read (typo):
e16 [fis fis e fis e] |
JM
Le 28 déc. 2014 à 18:51, David Nalesnik david.nales...@gmail.com
mailto:david.nales...@gmail.com a écrit :
Wim,
On Sun, Dec 28, 2014 at 11:47 AM, Shane Brandes sh...@grayskies.net
mailto:sh...@grayskies.net wrote:
Wim,
you are missing the open [ for the groupings in the bottomstaff.
regards,
Shane
On Sun, Dec 28, 2014 at 12:32 PM, Wim van Dommelen m...@wimvd.nl
mailto:m...@wimvd.nl wrote:
Hi,
I stumbled on a small beaming problem. Attached two small .PNG’s for what
should be there (never mind the 7/4, that is a writo), my experimental
output and below my compiling code as for what I tried. The problem is in
the second voice showing hickups in the second part of both measures where
the 1/16 notes are beamed special. When I don’t do the manual beaming I get
a pattern which the composer doesn’t like. It looks allright in the first
voice, I have about 10 of these and always the beaming in the second voice
breaks, the first voice is allright. May be that is a clue to where the
problem is?
Is there a possibility to get these beamings in a straigth line? Or is this
a bug I which should report?
Regards,
Wim.
Looks like Shane has found your problem, but I'd like to suggest a much less
tedious way to get what you're after:
\version 2.18.0
VoiceI = \relative f' {
\time 7/8
e8.[ dis16] e8.[ dis16]
\set subdivideBeams = ##t
fis[ cis cis b b cis] |
e8.[ dis16] e8.[ dis16]
fis[ cis cis b b cis] |
}
VoiceII= \relative f' {
\time 7/8
\set subdivideBeams = ##t
fis16 e8. fis16 e8.
e16[ e e fis e fis] |
e16 fis8. e16 fis8.
e16 fis fis e fis e] |
}
\score {
\new StaffGroup {
\new Staff {
\VoiceI
}
\new Staff {
\VoiceII
}
}
}%end score
You can read about this in the snippet subdividing beams at
http://lilypond.org/doc/v2.18/Documentation/notation/beams
http://lilypond.org/doc/v2.18/Documentation/notation/beams
--David
___
lilypond-user mailing list
lilypond-user@gnu.org mailto:lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
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
undesired courtesy
Hi all,
The following code produces the desired semi-sharp but it is preceded by a
courtesy accidental. Any idea how I can get rid of it?
Thanks!
Martin
\version 2.18.0
\language italiano
\relative do'' {
\global
lad2 lasd
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: undesired courtesy
Martin,
On Sun, Dec 28, 2014 at 6:02 PM, catal...@hotmail.com catal...@hotmail.com
wrote:
Hi all,
The following code produces the desired semi-sharp but it is preceded by a
courtesy accidental. Any idea how I can get rid of it?
Thanks!
Martin
\version 2.18.0
\language italiano
\relative do'' {
\global
lad2 lasd
}
\version 2.18.0
\language italiano
\relative do'' {
%\global % undefined
\set Staff.extraNatural = ##f
lad2 lasd
}
--David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
\markup and gregorian.ly
Hello, \version 2.18.0 I get troubles with \include gregorian.ly and \markup inside music-blocks I have a main file which includes file1.ly include file2.ly include fileEtc.ly Some files contain \include gregorian.ly (version 2.17.30 says the file), the others are normal music-files When compiling, all normal files are fine. When a file with \include gregorian.ly is readen, all normal files after it containing a \markup in music-block are odd-looking, since there is a kind of wait-the-end-of-markup-text-before-next-note (look attachment, first and last example are the same file, twice included) BTW, I know I dont need gregorian.ly in this example but I will have to use it anyway in this project. So my question: is there any \exclude gregorian.ly to put after the file? Thanks in advance, Francois ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: Frescobaldi 2.17.1
Thank you Wilbert for such a wonderful Christmas and New Year's gift! Frescobaldi + LilyPond is a wonderful combo that can do amazing things with music scores! Just a quick note to say that Frescobaldi 2.17.1 is now available for Debian and Ubuntu's development branches: * https://packages.debian.org/sid/frescobaldi * http://packages.ubuntu.com/vivid/frescobaldi Merry Christmas Season and Happy New Year to all! Anthony ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: slur shifted up by a fingering
For the records, Pierre found out that the problem occurred because my file includes this file: https://github.com/openlilylib/openlilylib/blob/master/notation-snippets/guitar-string-bending/definitions.ily This override solves the problem: \override StrokeFinger.avoid-slur = #'ignore Il 28/dic/2014 18:13 Federico Bruni fedel...@gmail.com ha scritto: No, I don't. In fact the revert suggested in your last email doesn't change anything. I'll send the files to you privately (copyrighted stuff). Il giorno dom 28 dic 2014 alle 17:52, Pierre Perol-Schneider pierre.schneider.pa...@gmail.com ha scritto: Hi Federico, I cannot reproduce your problem with the code you're giving. I suppose that you probably have somewhere an \override StrokeFinger.avoid-slur = #'inside - or kind of - haven't you ? Cheers, Pierre 2014-12-28 17:30 GMT+01:00 Federico Bruni fedel...@gmail.com: I'm having this problem on a piece I'm writing but I cannot reproduce it by extracting the single measure. So no minimal example, I'll just attach the image showing the problem: the slur between two notes is moved up because of a right-hand fingering on the first one. This is the relevant line: ees\5-\rightHandFinger #2 8( \glissando e4\5) I've read NR 4.4.3, Vertical collision avoidance, and tried few overrides using outside-staff-priority and avoid-slur, but honestly I don't know really what I'm doing. Thanks for any hint Federico ___ 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
