Re: clef change confuses manual key signature
Mats Bengtsson mats.bengtsson at ee.kth.se writes:
needed the feature while trying to typeset some of the Mystery sonatas
by Biber, which are written in scordatura, i.e. a violin with a
non-standard tuning. In these pieces, the notation reflects how you
should press the fingers, not what it should sound like. Therefore, the
key signatures look very weird and actually do differ from octave to
octave, see for example Sonata III at
http://imslp.org/wiki/Special:ImagefromIndex/48908.
So Biber really needs key signatures that apply only to one octave.
Thankfully he include lots of extra accidentals to help us remember that.
LilyPond handles that (and after David's patch is done it won't crash on
clef changes).
We can even print an extra e-flat if we want
\set Staff.keySignature = #`((2 . ,FLAT) (6 . ,FLAT) ((0 . 2) . ,FLAT))
On Aug 15, 2012, at 12:18 PM, james wrote:
\set Staff.keySignature = #`(((-1 . -3) . ,SHARP) ((-1 . -4) . ,SHARP))
\set Staff.keySignature = #`((9 . ,FLAT))
The strange behavior you noticed was due to the scale steps being out of
range: 0 1 2 3 4 5 6 . Instead of (-1 . -3) you have to say (-2 . 4).
I would find it a perfectly acceptable solution to have key signatures be
consistent for all octaves, regardless with display method is chosen
[...] make my life a lot easier.
The simple forms \set Staff.keySignature =#`(2 . ,FLAT) \key d\minor
apply to all octave, but always print the key signatures in the
traditional positions.
The traditional positioning groups the sharps and flats, and the code
uses the concept of the highest-flat or -sharp, which is different for
each clef based on tradition.
I suggest we add a property of the KeySignature graphical object, to
let us choose for ourselves the range of staff-positions where the
sharps and flat should go http://codereview.appspot.com/6461085/
Then to put the sharps at the third position above centerline
(e-sharp on treble clef) or lower, we could do
{ \override Staff.KeySignature #'highest-sharp-positions = ##(3)
\key e\major fis'1 }
with the key signature affecting all octaves as usual, if that looks useful.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Suboptimal slur (easy case)
Is there an issue logged for this?
\version 2.15.36
\relative c'' {
b8^Very loopy slur ( a ) r4 r2
\override Slur #'height-limit = #0.5
b8_Cleaner look ( a ) r4 r2
}
hjh
--
James Harkins /// dewdrop world
jamshar...@dewdrop-world.net
http://www.dewdrop-world.net
Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal. -- Whitman
blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: clef change confuses manual key signature
Keith OHara k-ohara5...@oco.net writes: I would find it a perfectly acceptable solution to have key signatures be consistent for all octaves, regardless with display method is chosen [...] make my life a lot easier. The simple forms \set Staff.keySignature =#`(2 . ,FLAT) \key d\minor apply to all octave, but always print the key signatures in the traditional positions. How about \set Staff.keySignature = #`((2 . ,FLAT) ((-1 . 2) . ,FLAT)) or the other way round? Put both versions in the signature, and not print the octave-unspecific version if there is also a specific one? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilyglyphs LaTeX package
Hi Reinhold, Werner and Philippe, thanks for your feedback. Here are a few ideas before I finally leave. [I won't read this list (from tomorrow), so if you want to contact me in the next weeks, please write to g...@ursliska.de] My package works with XeLaTeX because I decided to use this flavor. Actually the possibility to access OpenType fonts and features that way was the final point for my decision to seriously jump into LaTeX use. As Philippe and Werner pointed out there are ways to use Emmentaler glyphs also in plain LaTeX, but I won't actively go after this. What I propose, and what I think is quite possible, is: * There is the generic access command (\lilyGlyph ATM) * This command is then called by the predefined commands (such as e.g. \doublesharp) and can be called within a LaTeX document. * If we can manage to keep the interface to this generic command consistent I would be happy to include another 'backend'. * I think that the generic access command could become rather an 'interface' command. Depending on an option that can be passed to the package, the interface command would then call the appropriate generic access command. * Maybe it's necessary to somehow create a lookup table to map the Type1 numbers to the OpenType glyphnames. I found this for example: https://groups.google.com/forum/?fromgroups#!topic/comp.text.tex/MDzy2xNUC84[1-25] - which could be of help. * If that works, everything that comes at a higher level (i.e. the actual glyph commands) could be independent of the used LaTeX flavor. This has a few consequences: * There will be the need for more discussion and design before my prospected first official '0.1' release - but I think it would be worth the time and effort. * I won't be able to add new glyphs before this design phase is finished (because I'm afraid of having to update all the commands due to changed syntax). This is principally OK with me, but could cause some headaches because I started all this for a current project - and I think this revision report will be quite long, and I need the glyphs for it ... * I probably won't / can't do anything about the 'plain LaTeX backend' - just because I don't know anything about it, and I can't afford the time developing something I won't ever use myself. * ATM the stuff of integrating two 'backends' through package options seems over my head (as I'm practically new to LaTeX). Maybe I will learn it on the way, but any assistance in this field would be appreciated. Best for now Urs Am 15.08.2012 17:34, schrieb Urs Liska: Hi list, this is somewhat OT, but only slightly, I think. In need to insert music glyphs in continuous text (for writing a revision report) I successfully found out how to insert glyphs from LilyPond's Emmentaler font in (Xe)LaTeX documents and wrote a few first commands (thanks to Google and Werner Lemberg). As this may well be useful for anybody writing about music with LaTeX, I decided to make a package out of it. The project is hosted at https://github.com/uliska/lilyglyphs. The package is already useable, but there will be some syntax changes in the near future, so I'd rather not use it extensively (you can see the issues in the tracker to get an impression). For now there are a few predefined commands for glyphs, and a generic command to access glyphs by their name, so anything should already be possible. In the download section there is a pdf that documents how it works so far and also gives a good impression on what it looks like. You may either clone into the repository or download the package archive from the download page. So far there aren't any useful installation instructions, but I think it should work. You can place a symlink to the .sty file and a symlink to the definitions/ directory in the directory of your .tex file, and it should work. I will be away for two weeks but would be happy to find a few collaborators afterwards to join the project. a) there are a few issues that I would prefer not to decide alone but rather discuss, b) a few issues with LaTeX programming where I'd appreciate some help, and c) the ultimate goal is to cover the whole glyph set, but this will only become reality with several contributors. I will happily work on glyphs that I use personally, but there are so many things I won't use ... I hope this is on interest to anybody. Please feel free to forward this message to whom it may concern ... Best 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: Suboptimal slur (easy case)
James Harkins-2 wrote Is there an issue logged for this? what's the issue? if the notes are not that tight (e.g. using ragged-right = ##f in your example) your cleaner look doesn't look so clean anymore (that's my personal opinion) you can check if there are issues in the tracker in https://code.google.com/p/lilypond/issues/list Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Suboptimal-slur-easy-case-tp130700p130704.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Roman page numbers.
Greetings All, There must surely be an easy answer to this, though I have yet to find it. How does one produce page numbers in Roman numerals? And how does one then revert to Arabic numerals? In a related question, will the output from a generated Table of Contents display a mix of Roman and Arabic page numbers? Many thanks. Hwaen Ch'uqi ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Subject: Re: lilyglyphs LaTeX package
Dear Urs, how can I install this package in my xelatex-system on ubuntu? Hi Reinhold, Werner and Philippe, thanks for your feedback. Here are a few ideas before I finally leave. [I won't read this list (from tomorrow), so if you want to contact me in the next weeks, please write to g...@ursliska.de] My package works with XeLaTeX because I decided to use this flavor. Actually the possibility to access OpenType fonts and features that way was the final point for my decision to seriously jump into LaTeX use. As Philippe and Werner pointed out there are ways to use Emmentaler glyphs also in plain LaTeX, but I won't actively go after this. What I propose, and what I think is quite possible, is: * There is the generic access command (\lilyGlyph ATM) * This command is then called by the predefined commands (such as e.g. \doublesharp) and can be called within a LaTeX document. * If we can manage to keep the interface to this generic command consistent I would be happy to include another 'backend'. * I think that the generic access command could become rather an 'interface' command. Depending on an option that can be passed to the package, the interface command would then call the appropriate generic access command. * Maybe it's necessary to somehow create a lookup table to map the Type1 numbers to the OpenType glyphnames. I found this for example: https://groups.google.com/forum/?fromgroups#!topic/comp.text.tex/MDzy2xNUC84[1-25] - which could be of help. * If that works, everything that comes at a higher level (i.e. the actual glyph commands) could be independent of the used LaTeX flavor. This has a few consequences: * There will be the need for more discussion and design before my prospected first official '0.1' release - but I think it would be worth the time and effort. * I won't be able to add new glyphs before this design phase is finished (because I'm afraid of having to update all the commands due to changed syntax). This is principally OK with me, but could cause some headaches because I started all this for a current project - and I think this revision report will be quite long, and I need the glyphs for it ... * I probably won't / can't do anything about the 'plain LaTeX backend' - just because I don't know anything about it, and I can't afford the time developing something I won't ever use myself. * ATM the stuff of integrating two 'backends' through package options seems over my head (as I'm practically new to LaTeX). Maybe I will learn it on the way, but any assistance in this field would be appreciated. Best for now Urs Am 15.08.2012 17:34, schrieb Urs Liska: Hi list, this is somewhat OT, but only slightly, I think. In need to insert music glyphs in continuous text (for writing a revision report) I successfully found out how to insert glyphs from LilyPond's Emmentaler font in (Xe)LaTeX documents and wrote a few first commands (thanks to Google and Werner Lemberg). As this may well be useful for anybody writing about music with LaTeX, I decided to make a package out of it. The project is hosted at https://github.com/uliska/lilyglyphs. The package is already useable, but there will be some syntax changes in the near future, so I'd rather not use it extensively (you can see the issues in the tracker to get an impression). For now there are a few predefined commands for glyphs, and a generic command to access glyphs by their name, so anything should already be possible. In the download section there is a pdf that documents how it works so far and also gives a good impression on what it looks like. You may either clone into the repository or download the package archive from the download page. So far there aren't any useful installation instructions, but I think it should work. You can place a symlink to the .sty file and a symlink to the definitions/ directory in the directory of your .tex file, and it should work. I will be away for two weeks but would be happy to find a few collaborators afterwards to join the project. a) there are a few issues that I would prefer not to decide alone but rather discuss, b) a few issues with LaTeX programming where I'd appreciate some help, and c) the ultimate goal is to cover the whole glyph set, but this will only become reality with several contributors. I will happily work on glyphs that I use personally, but there are so many things I won't use ... I hope this is on interest to anybody. Please feel free to forward this message to whom it may concern ... Best 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: Subject: Re: lilyglyphs LaTeX package
The package doesn't have real installation instructions (or even an installation procedure) yet (something for 0.1, a first official release). Fortunately xelatex-ubuntu is what I have, so I can tell you how you will make it work. One issue is that there are included files in a subfolder. (I assume I'll have to do something about that for a 'real' packaged version.) As a dirty quick 'installation' I recommend: * place lilyglyphs.sty and the complete definitions/ folder somewhere on your disk, e.g. in a directory ~/lilyglyphs. * place the Emmentaler OTF file from the OTF folder in ~/.fonts (Maybe you have to run fc-cache afterwards to update your fontconfig cache - but I don't know for sure, I can't do any harm anyway) * create symlinks to lilyglyphs.sty and the definitions/ folder _in the directory_ where your .tex file is located: ln -s ~/lilyglyphs/lilyglyphs.sty ln -s ~/lilyglyphs/definitions - This is going to pretend that the package is in the same dir as your .tex file. Alternatively you can (for testing the package) put your .tex file in the directory where lilyglyphs.sty is. You may get long lists of 'kpathsea' errors. This is what I had on some of my computers (not only with this package but also earlier with other OpenType fonts and fontspec). I finally found out that this happened when I had 'activated' the respective fonts with a font manager (FontMatrix). When all these references were away, fontspec worked fine. Hope this helps (works) Best Urs Am 16.08.2012 13:37, schrieb Stefan Thomas: Dear Urs, how can I install this package in my xelatex-system on ubuntu? ___ 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: Subject: Re: lilyglyphs LaTeX package
* place lilyglyphs.sty and the complete definitions/ folder somewhere on your disk, e.g. in a directory ~/lilyglyphs. * create symlinks to lilyglyphs.sty and the definitions/ folder _in the directory_ where your .tex file is located: ln -s ~/lilyglyphs/lilyglyphs.sty ln -s ~/lilyglyphs/definitions - This is going to pretend that the package is in the same dir as your .tex file. Alternatively you can (for testing the package) put your .tex file in the directory where lilyglyphs.sty is. Ouch. Why not simply put it into your local TEXMF folder, usually ~/texmf? Then you don't have to do any further links! If it doesn't exist yet, you should create it. An appropiate subdirectory is ~/texmf/tex/xelatex/lilyglyphs/ Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Suboptimal slur (easy case)
From: eluze James Harkins-2 wrote Is there an issue logged for this? what's the issue? The default slur extends too low. if the notes are not that tight (e.g. using ragged-right = ##f in your example) your cleaner look doesn't look so clean anymore (that's my personal opinion) My intent with the override was merely to illustrate what the slur should (IMO) look like, not to propose that this specific height limit should replace the current default. That would just be silly :-P So, why does the default slur cross the bottom staff line? Seems rather loopy-bloopy to me, and the case is not complicated: two consecutive notes, only one step apart. About as trivial as a slur gets. hjh ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Subject: Re: lilyglyphs LaTeX package
Am 16.08.2012 13:57, schrieb Werner LEMBERG: * place lilyglyphs.sty and the complete definitions/ folder somewhere on your disk, e.g. in a directory ~/lilyglyphs. * create symlinks to lilyglyphs.sty and the definitions/ folder _in the directory_ where your .tex file is located: ln -s ~/lilyglyphs/lilyglyphs.sty ln -s ~/lilyglyphs/definitions - This is going to pretend that the package is in the same dir as your .tex file. Alternatively you can (for testing the package) put your .tex file in the directory where lilyglyphs.sty is. Ouch. Why not simply put it into your local TEXMF folder, usually ~/texmf? Then you don't have to do any further links! If it doesn't exist yet, you should create it. An appropiate subdirectory is ~/texmf/tex/xelatex/lilyglyphs/ Oops, didn't think this would work with the subfolder ... Werner ___ 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: Subject: Re: lilyglyphs LaTeX package
~/texmf/tex/xelatex/lilyglyphs/ Oops, didn't think this would work with the subfolder ... This gets searched recursively by default. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Subject: Re: lilyglyphs LaTeX package
Now I know that, thanks :-) Just had to exclude this from the git repo that controls my texmf dir ;-) Best Urs Am 16.08.2012 14:29, schrieb Werner LEMBERG: ~/texmf/tex/xelatex/lilyglyphs/ Oops, didn't think this would work with the subfolder ... This gets searched recursively by default. Werner ___ 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
dynamics (and hairpins) attached to rests vs dynamics attached to notes
Hi all,
I noticed that in LP 2.14.2, dynamics and hairpins attached to rests
(r or s) are slightly out of alignment when compared to dynamics and
hairpins attached to notes.
See attached ex. A
%% EXAMPLE A %%
musicOne = { a'4\ ~ a'\ ~ a'\ r4\! }
dynamics = { r4\ r\ r\ r\! }
\score {
\new Staff { \musicOne }
\new Staff { \dynamics }
\layout {
ragged-right = ##f
}
}
%% %% %%
This leads to misaligned hairpins between different staves, if one
attaches hairpins to (hidden) spacer rests in order to specify the
duration of each hairpin, as explained here:
http://lilypond.org/doc/v2.14/Documentation/notation/expressive-marks-attached-to-notes#dynamics
%% EXAMPLE B %%
musicOne = { a'4\ ~ a'\ ~ a'\ r4\! }
musicTwo = { a'2. r4 }
dynamics = { s4\ s\ s\ s\! }
\score {
\new Staff { \musicOne }
\new Staff { \musicTwo \dynamics }
\layout {
ragged-right = ##f
}
}
%% %% %%
The attached examples are quite simple, in my score with more complex
music, such behavior leads to quite strange situations.
Am I right and if so, which would be the easiest solution?
Thank you,
Tattachment: example_A.pngattachment: example_B.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: dynamics (and hairpins) attached to rests vs dynamics attached to notes
Tiresia Giuno wrote
The attached examples are quite simple, in my score with more complex
music, such behavior leads to quite strange situations.
Am I right and if so, which would be the easiest solution?
probably the simplest is to use dynamic contexts and withdraw the dynamic
engraver in the normal staff:
musicOne = { a'4 \ ~ a'\ ~ a'\ r4 \! }
\new Staff \musicOne
\new Dynamics \musicOne
\layout {
ragged-right = ##f
\context {
\Voice
\remove New_dynamic_engraver
}
}
this way you can reuse the same voice/staff with the dynamics in it (of
course you can also use a separate voice with spacers for the dynamics…)
hth
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/dynamics-and-hairpins-attached-to-rests-vs-dynamics-attached-to-notes-tp130716p130718.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: dynamics (and hairpins) attached to rests vs dynamics attached to notes
On 16 August 2012 14:59, Tiresia GIUNO tires...@googlemail.com wrote: Hi all, I noticed that in LP 2.14.2, dynamics and hairpins attached to rests (r or s) are slightly out of alignment when compared to dynamics and hairpins attached to notes. Could you check with latest development version? Several issues concerning DynamicText(Spanner)/Hairpin alignment, especially when attached to (spacer) rests, have been corrected after 2.14. Namely issues 620, 1194, 1724, 1861, 2532. I suspect the output should be good now but I cannot check myself now because I'm not currently using my own computer (with latest LilyPond). Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: setting Delia Derbyshire's abstract electronic scores
On 14 August 2012 21:06, Francisco Vila paconet@gmail.com wrote: El 13/08/2012 21:55, martinwguy martinw...@gmail.com escribió: Is Lilypond capable of helping with exotic stuff like this, from Delia Dervyshire's notes for her, maybe lost, Radio Newsreel signature tune e.g. the bottom of http://delia-derbyshire.net/papers/html/dd164139.html the top left and bottom left corners of http://delia-derbyshire.net/papers/html/dd164239.html or most of http://delia-derbyshire.net/papers/html/dd164209.html ? I am curious to see what others respond. At first I ask you: where is the music? LP is for music engraving. Looking at the 100 percent graphic score, my question is the reverse: are the GIMP or Inkscape capable of music engraving? There are more conventional scores too, at least, they have 5 lines and notes :), but she sometimes also paints sounds with shapes. M ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: setting Delia Derbyshire's abstract electronic scores
Am 16.08.2012 19:31, schrieb martinwguy: On 14 August 2012 21:06, Francisco Vila paconet@gmail.com wrote: El 13/08/2012 21:55, martinwguy martinw...@gmail.com escribió: Is Lilypond capable of helping with exotic stuff like this, from Delia Dervyshire's notes for her, maybe lost, Radio Newsreel signature tune e.g. the bottom of http://delia-derbyshire.net/papers/html/dd164139.html the top left and bottom left corners of http://delia-derbyshire.net/papers/html/dd164239.html or most of http://delia-derbyshire.net/papers/html/dd164209.html ? I am curious to see what others respond. At first I ask you: where is the music? LP is for music engraving. Looking at the 100 percent graphic score, my question is the reverse: are the GIMP or Inkscape capable of music engraving? There are more conventional scores too, at least, they have 5 lines and notes :), but she sometimes also paints sounds with shapes. M ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user I wouldn't really judge without having seen more. But in the end I think this kind of score would be better (easier) done with some kind of graphics software. I think I would only create some snippets with LilyPond that are musical notation in a more traditional sense - and then make images from it and use these as images ... Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: dynamics (and hairpins) attached to rests vs dynamics attached to notes
On Thu, 16 Aug 2012 07:03:06 -0700 (PDT)
eluze elu...@gmail.com wrote:
Tiresia Giuno wrote
The attached examples are quite simple, in my score with more
complex music, such behavior leads to quite strange situations.
Am I right and if so, which would be the easiest solution?
probably the simplest is to use dynamic contexts and withdraw the
dynamic engraver in the normal staff:
musicOne = { a'4 \ ~ a'\ ~ a'\ r4 \! }
\new Staff \musicOne
\new Dynamics \musicOne
\layout {
ragged-right = ##f
\context {
\Voice
\remove New_dynamic_engraver
}
}
this way you can reuse the same voice/staff with the dynamics in it
(of course you can also use a separate voice with spacers for the
dynamics…)
hth
Eluze
Thanks for your answer!
I avoid using the Dynamics Context, because it places dynamics far away
from the staff (even if with LP 2.15 it looks much better)- and hairpins
are still slightly misaligned, see attached file.
I can't really remove the New_dynamic_engraver, because it is an
orchestral score, and I would loose the dynamics for the other
instruments.
Thanks, TG
attachment: test-dynamics-2.14.pngattachment: test-dynamics-2.15.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
ANN: Frescobaldi 2.0.7
Hi all, it has been a long time, but Frescobaldi 2.0.7 is there. Main new stuff is the beautiful kinetic scrolling in the music view, contributed by Richard Cognot. With many thanks for that! All changes: * Translations: - updated: nl, cs, it, fr, es * New features: - command to show music view maximized, useful on small screens - kinetic scrolling in the music view, making the movements easier on the eyes, contributed by Richard Cognot - music view scrollbars can be hidden via preferences-tools-music view * Improvements: - status of Always Engrave is saved in session (wish #76) - the 'View' - 'Music View' submenu is now a top-level menu 'Music' * Bugfixes: - fix NameError: global name 'X_OK' is not defined when a helper application has an absolute path - fix python exception when helper app does not exist, now a regular message is shown Enjoy! -- Wilbert Berendsen (http://www.wilbertberendsen.nl) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: dynamics (and hairpins) attached to rests vs dynamics attached to notes
Tiresia Giuno wrote
I avoid using the Dynamics Context, because it places dynamics far away
from the staff (even if with LP 2.15 it looks much better)- and hairpins
are still slightly misaligned, see attached file.
of course there are ways to control the distance of a dynamic context to its
(related) staff (I just don't bear them in my brain, please have a look at
sth like /vertical spacing/ or similar)
I can't really remove the New_dynamic_engraver, because it is an
orchestral score, and I would loose the dynamics for the other
instruments.
it's possible to remove the New_dynamic_engraver from only one Voice - I
just showed a global way:
with
/\new Staff \new Voice \with {\remove New_dynamic_engraver } \musicOne/ all
other staves and voices are not affected by this local change.
now if you want all orchestral staves to look the same you have to use the
same approach for all of them!
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/dynamics-and-hairpins-attached-to-rests-vs-dynamics-attached-to-notes-tp130716p130729.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: version 2.16
Hi Martin, It's better that you don't cross-post your message to several mailing lists. Cross-posts are used for important announcements. By cross-posting, you discourage others from replying, as they have to cross-post too or to make a choice which mailing list is more suitable for the discussion. On Tue, 14 Aug 2012 21:38:08 +0200 (CEST) Martin Tarenskeen m.tarensk...@zonnet.nl wrote: If I have a newer \version in my lilypond score than the LilyPond I am using I am getting a Fatal Error message, but my score compiles just fine, giving a perfect PDF or MIDI. I would expect a Warning, not a Fatal error message ? Using lilypond-2.15.95 In my testfile using: \version 2.16.0 If Lilypond notices a file that requires a newer version of the program, it's impossible for Lilypond to know what it would do wrong. Maybe the score would compile but produce subtly wrong output. If you have time and desire to check the PDF and the MIDI output, it should not be a big deal for you to change the version number in the plain text file. -- Regards, Pavel Roskin ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: TextSpanner duplicates text after \break
Hello Ian, Please could you let us know the LilyPond version on which you observed the problem? I'm using version 2.15.39, but I've been noticing this behavior since 2.14.2 and perhaps even older versions, those 2 are the ones I can confirm. Also, could you tell us how you envisage using this feature. As a player, I find the reminder on 8va passages useful at line breaks. I'm asking the question so I can determine whether this would be a real-life, useful facility or simply whether you have found a rarely-used corner case. - First of all, in order to make some transcriptions/arrangements of a work that does have an 8va/15ma/etc. passage it would be good to produce it similar on LilyPond, sometimes those 8va passages do not repeat the 8va text at line breaks on paper published scores you buy. - Another one is to make it comfortable to Sibelius users or so to have an 8va line in a similar way they are used to (afaik Sibelius don't repeat the 8va text). I know LilyPond doesn't need to imitate behavior from other software (LilyPond is already cool anyways), but users like to have options (see below). - Last but not least, it would be good to have options available, whether or not you need the duplication of 8va text the user would really appreciate being able to decide how he/she wants the output to suit his/her needs. Hope that helps! -- Daniel E. Moctezuma ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
\override Hairpin #'minimum-length
Hi,
Can any of you Lilypond people tell me why the \override Hairpin
#'minimum-length … does not actually seem to control the length of the
hairpin? Am I missing something here?
\version 2.14.2
\relative c'' {
\once \override Hairpin #'minimum-length = #5 \afterGrace c4\ s1\! c4
c4 c4
% here the hairpin is too short
\once \override Hairpin #'minimum-length = #5 \afterGrace c4\\ppp
s1\!\fz c4 c4 c4
}
regards,
Mika Kuuskankare
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
