Malte and Simon - I didn't have the opportunity to try your suggestions yet,
but just wanted to say thanks for helping!
Am 07.05.2018 um 01:21 schrieb Simon Albrecht:
> On 06.05.2018 23:03, Malte Meyn wrote:
>> Am 06.05.2018 um 22:35 schrieb Thomas Weber:
>>> Can anybody he
Can anybody help me with keeping the dynamics alive? Many thanks!
dynamics = {s1\p}
music = {c'1}
\layout {
\context {
\Score
\RemoveEmptyStaves
\override VerticalAxisGroup.remove-first = ##t
}
}
\score {
<<
\new Staff \music
\new Dynamics \dynamics
>>
}
Am 05.05.2018 um 11:23 schrieb Malte Meyn:
> • or \override DynamicText.extra-spacing-width = #empty-interval for the
> lowest Staff in a StaffGroup.
That is very useful to know! Also when the dynamics would actually cross a
barline in combination with whiteout:
violinIIa = \relative c'' {
Sibelius 8.1.1 creates exactly the same beaming.
Am 05.05.2018 um 09:38 schrieb Robert Blackstone:
> Hi Urs,
>
> This is what your file produces with Finale 2024.5, on a MacBook with
> OSX 10.9.5.
>
>
>
> (I should have compressed it a bit.)
>
> Best regards,
>
>
Hi all,
when I compile the below example with 2.18.2, I get the output that I want -
the "pp" below the staff is offset as expected. When I compile with 2.19.54,
more unnecessary space is created after the barline to avoid that the dynamic
crosses below the barline. (See attached images.)
Is
Am 11.02.2017 um 13:51 schrieb Thomas Morley:
Arnold has put up some work to get a more automagic workflow.
http://lsr.di.unimi.it/LSR/Item?id=990
http://lsr.di.unimi.it/LSR/Item?id=978
IIRC his work is not finished, so you probably will need to fall back
to grace-spacers sometimes...
Am 10.02.2017 um 23:48 schrieb Jacques Menu Muzhic:
Not a bug, but a feature : you have to add graces in all voices :
I already realized that:
Le 10 févr. 2017 à 23:23, Thomas Weber <t...@notabit.eu> a écrit :
* I can add a "grace space" to the bottom staff
But
).
* I have to analyze all other staffs when writing out one staff.
I'm looking for a reliable solution that works well for auto-generating
Lilypond code.
Highly appreciating any help on this,
Thomas Weber
[1] https://lists.gnu.org/archive/html/lil
11.01.2017 um 18:46 schrieb Malte Meyn:
You can get the duration from the context property timeSignatureFraction
or baseMoment:
%
\version "2.19.53"
{
\time 12/8
\applyContext
#(lambda (context)
(display (ly:context-property
context
Dear all,
I wonder how I can create a duration that is so to say exactly one time
signature denominator long (e.g. an eigth in 6/8, a quarter in 4/4 etc.). I
thought something like this would work:
#(make-music
'SkipEvent
'duration
(ly:make-duration 0 0 1
Thanks for bringing me on track, Werner. I was able to solve the problem in a
quick and dirty manner, however it would be useful to learn how to solve it
properly.
What I did was:
$ sudo ln -s /usr/include/freetype2/freetype/config
/usr/include/freetype2/config
$ sudo sed -i
Thanks for your reply, Werner. What I did is the following:
$ git pull ; LANG=C make all | tail
Already up-to-date.
make[1]: *** No rule to make target '/usr/include/freetype2/freetype.h', needed
by 'out/vaticana-ligature.o'. Stop.
make: *** [all] Error 2
make[2]: Entering directory
When I try to "make" Lilypond on Ubuntu 16.04, the freetype headers are
expected to be located in /usr/include/freetype2/. That's also where Ubuntu's
package libfreetype6-dev used to put them, at least in Ubuntu versions 14.04 to
15.10, but in 16.04 (also 12.04, interestingly), it's in
Am 12.08.2016 um 17:29 schrieb Mark Knoop:
> At 16:30 on 12 Aug 2016, Thomas Weber wrote:
>
>> Secondly, how can I make rehearsal marks appear both on the very top
>> staff and the top staff of the strings? As far as I can see,
>> rehearsal marks will always be put at t
There are two things about rehearsal marks in orchestral scores I'd like to
know about.
Firstly, how can I separate rehearsal marks (and other structural stuff like
\break or \pageBreak) from the actual musical content? Can I somehow add a
virtual staff to carry the rehearsal mark
Am 10.08.2016 um 23:44 schrieb Simon Albrecht:
>
> Am 10.08.2016 um 19:13 schrieb Thomas Weber:
>
> > in old orchestral scores one can observe that engravers did not hesitate to
> > make more room in dense situations by moving dynamics into the staff rather
> &
Am 10.08.2016 um 20:33 schrieb Robin Bannister:
> Thomas Weber wrote:
>> But Lilypond insist on keeping the dynamic outside of the staff.
>
> Try
> {
> \override Staff.DynamicLineSpanner #'outside-staff-priority = ##f
> \override Staff.DynamicText #'X-o
Hi all,
in old orchestral scores one can observe that engravers did not hesitate to
make more room in dense situations by moving dynamics into the staff rather
than putting them below (or above). To achieve the same effect, I tried the
following:
{
\once \override Staff.DynamicText
18 matches
Mail list logo
