Enhancement: expanded Woodwind diagrams
The fingering diagrams for woodwinds are excellent. I'd like to request that they be expanded/improved, with several likely candidates: 1) add the Kontraforte -- a modernized, considerably extended improvement over the original Heckel Contrabassoon design -- to the list, as the Kontraforte is replacing the Contrabassoon in modern/new-music ensembles (as well as traditional orchestras) as fast as the maker can build them. It's a fascinating instrument. 2) by the same token: I have an older Contrabassoon (Model #644, the last one the old master made in the 50s before retiring), which has a key layout that differs from the one in Lily (among other things, a fourth key in the right- side column under my left thumb). Maybe some alternate layouts for contras, as well as maybe for French bassoons? 3) the Kingma quartertone flute, which is rare, but also a much superior instrument compared to the base layout. 4) the Bohlen-Pierce Clarinet family, which has instruments based on a just- intuned scale with a vastly simplified key layout. There's a few others, but I'd *love* to see Lily able to address some alternate/expanded fingering diagrams, especially those that are getting some more play in new music. Cheers, A ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: compile failure - parsed object should be dead in 2.19.20
Addendum: this is not a bug with ghostscript, at least for me, but rather
with a part of ghostscript failing against recent versions of fontconfig
(on my gentoo system, fontconfig-2.11.93 fails to compile .ly files with
the errors above, but downgrading to 2.11.1 allows files to compile). Can
anybody else confirm?
Cheers,
A
On Tue, Apr 28, 2015 at 10:11 PM, N. Andrew Walsh n.andrew.wa...@gmail.com
wrote:
according to Urs Liska, this resembles an error he encountered with
ghostscript, as the output on my machine when using --verbose confirms. If
you're also on the user list, the longer output is there. If not, I can
post here (but I imagine you'd prefer avoiding double-posting if it isn't
necessary).
I'm using gs 9.15.
Cheers,
A
On Tue, Apr 28, 2015 at 9:52 PM, Thomas Morley thomasmorle...@gmail.com
wrote:
2015-04-28 21:15 GMT+02:00 N. Andrew Walsh n.andrew.wa...@gmail.com:
I'm not top posting.
With a MWE:
\version 2.19.20
\relative c' {
a4 b c d
}
I get the following error in the console output under frescobaldi:
Starting lilypond 2.19.20 [Untitled]...
Processing `/tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `document.ps'...
Converting to `./document.pdf'...
warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -
dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -
r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf -c.setpdfwrite -
fdocument.ps)' failed (256)
programming error: Parsed object should be dead: #Grob NoteSpacing
continuing, cross fingers
programming error: Parsed object should be dead: #Prob: paper-system
C++:
Prob((Y-offset . 1.0) (system-grob . #Grob System ) (staff-refpoint-
extent -3.776 . -3.776) (last-in-score . #t) (page-turn-penalty) (page-
break-penalty) (page-turn-permission . allow) (page-break-permission .
allow) (vertical-skylines . #Skyline_pair) (stencil . #Stencil))()
continuing, cross fingers
fatal error: failed files: /tmp/frescobaldi-NJlynW/tmpIzKobr/
document.ly
Exited with return code 1.
-
Error output is the same on larger files.
Cheers
Can't confirm with a build from latest master in LilyDev (Ubuntu 10.04)
All works as expected.
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: compile failure - parsed object should be dead in 2.19.20
according to Urs Liska, this resembles an error he encountered with
ghostscript, as the output on my machine when using --verbose confirms. If
you're also on the user list, the longer output is there. If not, I can
post here (but I imagine you'd prefer avoiding double-posting if it isn't
necessary).
I'm using gs 9.15.
Cheers,
A
On Tue, Apr 28, 2015 at 9:52 PM, Thomas Morley thomasmorle...@gmail.com
wrote:
2015-04-28 21:15 GMT+02:00 N. Andrew Walsh n.andrew.wa...@gmail.com:
I'm not top posting.
With a MWE:
\version 2.19.20
\relative c' {
a4 b c d
}
I get the following error in the console output under frescobaldi:
Starting lilypond 2.19.20 [Untitled]...
Processing `/tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `document.ps'...
Converting to `./document.pdf'...
warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -
dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -
r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf -c.setpdfwrite -
fdocument.ps)' failed (256)
programming error: Parsed object should be dead: #Grob NoteSpacing
continuing, cross fingers
programming error: Parsed object should be dead: #Prob: paper-system
C++:
Prob((Y-offset . 1.0) (system-grob . #Grob System ) (staff-refpoint-
extent -3.776 . -3.776) (last-in-score . #t) (page-turn-penalty) (page-
break-penalty) (page-turn-permission . allow) (page-break-permission .
allow) (vertical-skylines . #Skyline_pair) (stencil . #Stencil))()
continuing, cross fingers
fatal error: failed files: /tmp/frescobaldi-NJlynW/tmpIzKobr/
document.ly
Exited with return code 1.
-
Error output is the same on larger files.
Cheers
Can't confirm with a build from latest master in LilyDev (Ubuntu 10.04)
All works as expected.
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
compile failure - parsed object should be dead in 2.19.20
I'm not top posting.
With a MWE:
\version 2.19.20
\relative c' {
a4 b c d
}
I get the following error in the console output under frescobaldi:
Starting lilypond 2.19.20 [Untitled]...
Processing `/tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `document.ps'...
Converting to `./document.pdf'...
warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -
dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -
r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf -c.setpdfwrite -
fdocument.ps)' failed (256)
programming error: Parsed object should be dead: #Grob NoteSpacing
continuing, cross fingers
programming error: Parsed object should be dead: #Prob: paper-system C++:
Prob((Y-offset . 1.0) (system-grob . #Grob System ) (staff-refpoint-
extent -3.776 . -3.776) (last-in-score . #t) (page-turn-penalty) (page-
break-penalty) (page-turn-permission . allow) (page-break-permission .
allow) (vertical-skylines . #Skyline_pair) (stencil . #Stencil))()
continuing, cross fingers
fatal error: failed files: /tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly
Exited with return code 1.
-
Error output is the same on larger files.
Cheers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
