Am 02.09.2017 um 13:08 schrieb Erik Ronström:
If I apply the attached patch to a cloned git archive I get the following
results with ghostscript 9.06:
bok2: Original size 9.996.691 bytes, optimized size 2.043.380 bytes
bok3: Original size 13.706.324 bytes, optimized size 2.447.232 bytes
Unfort
> The idea is to make `supressRedundantKeySigs' set an `is-redundant'
> flag in the redundant grob instead of calling `ly:grob-suicide!'. A
> modified stencil function for KeySignature can now check this flag
> together with `ly:item-break-dir' to suppress the grob if necessary.
I wonder whether
Hi Werner,
> I wonder whether it makes sense to provide this behaviour as the
> default for lilypond. Or to ask differently: Is there any practical
> use of having redundant calls to \time or \key actually print a time
> or key signature again?
1. The way the current "multi-instrumentalist" mech
>> I wonder whether it makes sense to provide this behaviour as the
>> default for lilypond. Or to ask differently: Is there any practical
>> use of having redundant calls to \time or \key actually print a time
>> or key signature again?
>
> 1. The way the current "multi-instrumentalist" mechani
Hi Werner,
sorry for late reply
2017-09-03 15:05 GMT+02:00 Werner LEMBERG :
>
>> The idea is to make `supressRedundantKeySigs' set an `is-redundant'
>> flag in the redundant grob instead of calling `ly:grob-suicide!'. A
>> modified stencil function for KeySignature can now check this flag
>> tog
Hi Werner,
> This is a completely different issue. You want exactly the opposite,
> namely to control whether time signatures are displayed at the
> beginning of a line (or whereever) inspite of not having an explicit
> \time command.
Actually, I want both. ;)
1. I'd like to be able to call \t
p.s.
I guess I want all three!
I'd like to be able to suppress redundant time and key signatures as well.
Thanks,
Kieren.
> On Sep 3, 2017, at 10:20 AM, Kieren MacMillan
> wrote:
>
> Hi Werner,
>
>> This is a completely different issue. You want exactly the opposite,
>> namely to control wh
Hi Harm,
> I've now taken this route. Full working code/pdf attached,
> though, there's surely wide room to improve it.
> Usage should be clear from comments and example,
> I'm too tired to do verbose explanations.
This is amazing!
Thank you so much for the hard work — and thanks to everyone who
Hi Knut,
On 21 July 2017 at 09:00, Knut Petersen wrote:
> Hi everybody!
>
> To generate score videos like Bach: Invention 1, Wolf: Resignation and
> Peterson-Berger: I Fyrreskoven
> that give a different color to notes and rest while they are active you
> might use the attached files if
> you run
Hi Harm,
First question: What's the best way to change the font size of the normal text
*independently* of the font size of the dynamics?
I need (a.k.a. would like) to use this function in different stylesheets (with
different base fonts), and would prefer to be able to tweak that with a
param
Adam Spiers writes:
> Hi Knut,
>
> On 21 July 2017 at 09:00, Knut Petersen wrote:
>> Hi everybody!
>>
>> To generate score videos like Bach: Invention 1, Wolf: Resignation and
>> Peterson-Berger: I Fyrreskoven
>> that give a different color to notes and rest while they are active you
>> might us
Hi Adam!
Two questions:
1. Please can you put the source files in a git repository and publish
it somewhere (e.g. GitLab.com), to reduce barrier to collaboration?
Well, not now.
2. Would it be possible to generate video which is perfectly
synchronised with a live performance with variable te
2017-09-03 17:16 GMT+02:00 Kieren MacMillan :
> Hi Harm,
>
> First question: What's the best way to change the font size of the normal
> text *independently* of the font size of the dynamics?
>
> I need (a.k.a. would like) to use this function in different stylesheets
> (with different base fonts
Hi Harm,
> The current structure makes it impossible in a convenient way.
=(
> Tbh, I didn't think of this.
Neither has the Lilypond development team, as far as I can tell: I don't know
of any way to do it currently (i.e., independent of your new functionality).
> You want to change fontsize
Hi David,
On Sun, Sep 3, 2017 at 12:51 AM, David F. wrote:
> That is great! Just what I was looking for.
>
> Your patch isn’t extracting the tonic—it always returns ‘C’. But I always
> explicitly define the key, so your original code works like a charm.
Oops.
In any case, all you'd have to do
2017-09-03 18:14 GMT+02:00 Kieren MacMillan :
> Hi Harm,
>
>> The current structure makes it impossible in a convenient way.
>
> =(
>
>> Tbh, I didn't think of this.
>
> Neither has the Lilypond development team, as far as I can tell: I don't know
> of any way to do it currently (i.e., independent
Hi all,
On 2 September 2017 at 22:07, Paul wrote:
> On 09/01/2017 05:26 PM, Flaming Hakama by Elaine wrote:
>>https://github.com/aspiers/ly2video
>
>>I wanted to see if anyone else (besides the author of that approach) has
>>been able to get this to work.
I just fixed some fundamental flaws in t
On 3 September 2017 at 16:47, David Kastrup wrote:
> Adam Spiers writes:
>> On 21 July 2017 at 09:00, Knut Petersen wrote:
>>> To generate score videos like Bach: Invention 1, Wolf: Resignation and
>>> Peterson-Berger: I Fyrreskoven
>>> that give a different color to notes and rest while they ar
2017-09-03 20:48 GMT+02:00 :
> Most obvious approaches would result in the key change being inside the
> repeat barline, which doesn't feel right. See attached pic if you don't know
> what I'm talking about.
Cheating:
{
r2. g4->
\once \override Staff.KeySignature.space-alist.firs
That is indeed a very hacky solution, but it works great. I'll probably
want to \tag out the skip during midi generation, though. (It seems
using graces also allows you to put multiple \marks at the same moment,
which is neat.)
For the record, how exactly does that space-alist override work?
2017-09-03 21:20 GMT+02:00 Caagr98 :
> For the record, how exactly does that space-alist override work?
>
> On 09/03/17 21:08, Thomas Morley wrote:
>>\once \override Staff.KeySignature.space-alist.first-note =
>> #'(fixed-space . 0)
Well, the property 'space-alist for the KeySig
David Kastrup writes:
> Gianmaria Lari writes:
>
>> On 27 August 2017 at 08:57, David Kastrup wrote:
>>
>>> However, LilyPond does not permit adding "post events" after the fact
>>> (never mind their name). You can use
>>>
>>> {
>>> <>[ \note b b b]
>>> }
>>>
>>> to have the beam start event
Am 03.09.2017 um 19:36 schrieb Adam Spiers:
However please don't write off ly2video just because I
haven't done much with it recently (except for today).
The most annoying bugs should really be fixed. One example: The problem that
ly2video needs pure 7-bit ascii as input has been discussed on
23 matches
Mail list logo
