Am 03.03.2014 12:38, schrieb Kieren MacMillan:
Hey team,
This message bounced because of the size of the attachment, but I wanted you to
see it anyway (without attachment).
H, I received it.
Maybe it bounced from -user but not from -devel?
Anyway, that looks great.
I only followed this
Hey team,
This message bounced because of the size of the attachment, but I wanted you to
see it anyway (without attachment).
Thanks,
KIeren.
On Mar 2, 2014, at 3:38 PM, Kieren MacMillan
wrote:
> Hi Jan-Peter (et al.),
>
> Your edition engraver is amazing, IMO.
>
> Here is page 1 of the Vo
Hi Jan-Peter,
> I added a function editionMMod, which takes a list of positions.
Spectacular! Thanks.
I’ll continue applying your edition engraver to my real-world files, and see
what else comes up.
Hopefully, we’ll soon be able to give this to the rest of the community at
large, in a truly ea
Hi Kieren,
I added a function editionMMod, which takes a list of positions.
Function name and argument order should be chenged ...
For now, the position-list replaces measure and moment.
So
\editionMod FTE-vocalbook 5 0/4 FTE-vocalbook-A.Score.A \break
should be equal to
\editionMMod FTE-vocalb
Hi Jan-Peter,
> sorry, I missed to mention the zero-based counting
Yeah, that was probably an important point to bring to my attention… ;)
> To add the empty barline, if there isn't one already, would be very nice. We
> should try to make it possible.
That would be great!
The other thing th
Hi Kieren,
sorry, I missed to mention the zero-based counting. We will propably
find more of those black spots ... you are the first one, with whom I
talk about using it ;)
Well, fever is decending and I will have a cup of hot tea and some aspirin.
In my first versions, I used one-based counti
Hi Jan-Peter,
Answered my own question:
> this doesn’t work for me:
> \editionMod edition-engraver-name 2 1/4 edition-name.Score.A \break
It needs rather to be
\editionMod edition-engraver-name 2 0/4 edition-name.Score.A \break
[!!]
Onwards and upwards.
Kieren.
___
Hi Jan-Peter,
> I thought, it should work also in the Staff context.
Since many of my compositions recently are polymetric, that would be a great
feature.
(It would be particularly good if it automatically broke the other Staff
contexts mid-measure, without me having to add \bar “” every time…)
Hi Kieren,
Am 28.02.14 17:01, schrieb Kieren MacMillan:
Hi again,
Any explanation for why
\editionMod edition-engraver-name 2 1/4 edition-name.Staff.A \break
I thought, it should work also in the Staff context.
But it should at least work, if you address the Score context.
\editionMod e
Hi again,
Any explanation for why
\editionMod edition-engraver-name 2 1/4 edition-name.Staff.A \break
doesn’t work? What’s the proper code?
Allowing arbitrary break points like this is a "killer feature" for your
edition engraver! =)
Thanks,
Kieren.
__
Hi Jan-Peter,
> now my family had to leave me here alone …
Sorry to hear that…
On the bright side, that means more uninterrupted Lilypond time! ;)
>> So the ‘test’ in '\addEdition test’ is not related to the ‘test’ in
>> ‘my.test’?
> I am going to produce examples with more meaningful names.
Hi Kieren,
On 28.02.2014 02:53, Kieren MacMillan wrote:
> Although my 3½ year old daughter has had several bouts of
> “day-care-itis” — and my wife picked it up several times — I’ve
> fortunately avoided all sickness this season.
Best wishes, that it stays that way and that your wife is not suffe
On 28.02.2014 09:43, David Kastrup wrote:
>> Although my 3½ year old daughter has had several bouts of
>> > “day-care-itis” — and my wife picked it up several times — I’ve
>> > fortunately avoided all sickness this season.
> Well, as long as it isn't the six-legged variant of day-care-itis...
;)
Kieren MacMillan writes:
> Hi Jan-Peter,
>
> Thanks for the detailed response!
>
>> I will answer more , when I left all infections behind, which my
>> children brought from school and kindergarten …
>
> =\
>
> Although my 3½ year old daughter has had several bouts of
> “day-care-itis” — and my w
Hi Jan-Peter,
Thanks for the detailed response!
> I will answer more , when I left all infections behind, which my
> children brought from school and kindergarten …
=\
Although my 3½ year old daughter has had several bouts of “day-care-itis” — and
my wife picked it up several times — I’ve fort
Hi Kieren,
Am 27.02.2014 04:44, schrieb Kieren MacMillan:
> Hi Jan-Peter,
> ...
> Are you interested in taking up that challenge? =)
yes, I am :)
And I will answer more , when I left all infections behind, which my
children brought from school and kindergarten ...
> I would love a dead-simple, d
Hi Jan-Peter,
> - if you use it without any template mechanism, you have to assign
> proper edition-engraver id-paths - I can't say, what that means in
> production.
> - right now it is just ripped out of my working framework and might or
> might not work as expected ... but this doesn't need to b
> Found another worthwhile optimization making a difference
> (basically, not discarding and regenerating a blob that is going to
> get analyzed next anyway). In your use case where almost all
> changes happen in the same large file, this does make a bit of a
> difference, in particular regarding
David Kastrup writes:
> David Kastrup writes:
>
>> Bah. Got only 50% off, and a third of the rest is system time. At
>> least an artificial test case went from 40 seconds to 2, but that is
>> only a 95% reduction, so still a far cry from what I fantasized.
>>
>> And the wortliste still takes m
Werner LEMBERG writes:
>>> And the wortliste still takes more than 6 minutes on my computer:
>>
>> Which is not even a factor of 3 as compared to previously:
>
> But even that is an large improvement. It's now unbearable and no
> longer unusable :-)
So since much of the load appears to be I/O b
>> And the wortliste still takes more than 6 minutes on my computer:
>
> Which is not even a factor of 3 as compared to previously:
But even that is an large improvement. It's now unbearable and no
longer unusable :-)
Werner
___
lilypond-devel ma
David Kastrup writes:
> Bah. Got only 50% off, and a third of the rest is system time. At
> least an artificial test case went from 40 seconds to 2, but that is
> only a 95% reduction, so still a far cry from what I fantasized.
>
> And the wortliste still takes more than 6 minutes on my compute
David Kastrup writes:
> Werner LEMBERG writes:
>
>>> For better or worse, I am currently focusing on speeding up "git
>>> blame" which is braking down lots of people.
>>
>> Excellent! If you want a test case from the dark side, try
>>
>> http://repo.or.cz/w/wortliste.git
Wrong URL, needs a /
Hi Jan-Peter,
> - if you use it without any template mechanism, you have to assign
> proper edition-engraver id-paths - I can't say, what that means in
> production.
I know you have a well-developed templating system… I wish I had time to look
at it.
> 2. I want to change the output in context
Hi David,
>> How much sense would it make for there to be a separate \mark-style command
>> that functioned identically but didn't mess with the counter?
>
> What do you mean? Neither \mark #4 nor \mark "G" mess with the counter.
The point is that, if \addAt (or whatever) is “relative to marks”
Hi Werner,
> what will you do with, say, 100 \addAt entries after inserting an additional
> bar?
A replace script?
In any case, since it would be an optional parameter, it wouldn’t hurt anyone
to have it in there…
As long as the syntax is clear and easy as to what is and is not a “mark” for
t
Hi Kieren,
Am 16.01.2014 03:16, schrieb Kieren MacMillan:
> 1. What — if any — drawbacks are there?
- if you use it without any template mechanism, you have to assign
proper edition-engraver id-paths - I can't say, what that means in
production.
- right now it is just ripped out of my working fram
Am 16.01.2014 06:35, schrieb David Kastrup:
Alex Loomis writes:
How much sense would it make for there to be a separate \mark-style command
that functioned identically but didn't mess with the counter?
What do you mean? Neither \mark #4 nor \mark "G" mess with the counter.
Perhaps some ki
Alex Loomis writes:
> How much sense would it make for there to be a separate \mark-style command
> that functioned identically but didn't mess with the counter?
What do you mean? Neither \mark #4 nor \mark "G" mess with the counter.
--
David Kastrup
_
>> How much sense would it make for there to be a separate \mark-style
>> command that functioned identically but didn't mess with the
>> counter?
I'm all for it!
> Meh… I don’t really like the original suggestion (of a
> RehearsalMark-relative \addAt parameter), so it makes little sense
> to me
Hi Jan-Peter,
> I extracted my edition-engraver from lalily.
This seems so magical as to be almost unbelievable. =)
1. What — if any — drawbacks are there?
2. Why is this not exactly (or even a superset of) the \addAt feature I
requested?
Thanks!
Kieren.
__
Hi Alex,
> How much sense would it make for there to be a separate \mark-style command
> that functioned identically but didn't mess with the counter?
Meh… I don’t really like the original suggestion (of a RehearsalMark-relative
\addAt parameter), so it makes little sense to me.
Cheers,
Kieren
How much sense would it make for there to be a separate \mark-style command
that functioned identically but didn't mess with the counter?
On Tue, Jan 14, 2014 at 8:30 AM, Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
> Hi Werner,
>
> > I suggest that such a command allows for a third,
Hi Kieren, James and all,
I extracted my edition-engraver from lalily. The example compiles here
with 2.18.
You can try this and comment ... I will add more comments to the code,
if this is of interest ;)
The compilation creates a file example.edition.log containing all
edition-engraver paths.
I
Werner LEMBERG writes:
>> For better or worse, I am currently focusing on speeding up "git
>> blame" which is braking down lots of people.
>
> Excellent! If you want a test case from the dark side, try
>
> http://repo.or.cz/w/wortliste.git
>
> For historical reasons, the `wortliste' is a singl
> For better or worse, I am currently focusing on speeding up "git
> blame" which is braking down lots of people.
Excellent! If you want a test case from the dark side, try
http://repo.or.cz/w/wortliste.git
For historical reasons, the `wortliste' is a single, large file
instead of smaller on
Hi all,
> So "a half-day's work" is more like the estimate for
> every single further fix making the timing simulation work closer to
> what iteration would do anyway.
Well, then… tell me the real cost, and I’ll see what I can do to [help] sponsor
it.
There is *NOTHING* I can think of which woul
Am 15.01.2014 16:21, schrieb David Kastrup:
Urs Liska writes:
Am 15.01.2014 16:13, schrieb David Kastrup:
then I need to prepare two
papers/talk proposals about LilyPond till the end of this week.
Are you talking about LAC2014?
No. http://chemnitzer.linux-tage.de>.
OK. Otherwise I'd h
Urs Liska writes:
> Am 15.01.2014 16:13, schrieb David Kastrup:
>> then I need to prepare two
>> papers/talk proposals about LilyPond till the end of this week.
>
> Are you talking about LAC2014?
No. http://chemnitzer.linux-tage.de>.
--
David Kastrup
_
Am 15.01.2014 16:13, schrieb David Kastrup:
then I need to prepare two
papers/talk proposals about LilyPond till the end of this week.
Are you talking about LAC2014?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman
Kieren MacMillan writes:
> Hi all,
>
>> So "a half-day's work" is more like the estimate for
>> every single further fix making the timing simulation work closer to
>> what iteration would do anyway.
>
> Well, then… tell me the real cost, and I’ll see what I can do to
> [help] sponsor it.
Well,
Kieren MacMillan writes:
> Hi Mike (et al.),
>
>>> What would be involved in developing a feature to add notes or
>>> tweaks at an arbitrary moment within a music expression?
>>> music = \addAt (4 3/8) \global \once \override
>>> RehearsalMark.extra-offset #’(-1 . 0)
>
>> we’re about a half-day’s
Hi Mike (et al.),
>> What would be involved in developing a feature to add notes or tweaks at an
>> arbitrary moment within a music expression?
>> music = \addAt (4 3/8) \global \once \override RehearsalMark.extra-offset
>> #’(-1 . 0)
> we’re about a half-day’s work away from a hack that doesn’
On 14/01/14 07:17, Jan-Peter Voigt wrote:
Hi Kieren and all,
I use an engraver for this task, that looks for overrides, sets and
clefs at the current measure (of the context consisting this engraver)
and at the current moment inside this measure. So this is a little bit
different from your examp
Hi Werner,
> I suggest that such a command allows for a third, optional parameter,
> which makes \addAt relative to the `rehearsalMark' property.
If you’re talking about \mark \default, then I could see the benefit of that.
The problem is, most of us overload \mark for a bunch of non \default st
Hi Kieren and all,
I use an engraver for this task, that looks for overrides, sets and
clefs at the current measure (of the context consisting this engraver)
and at the current moment inside this measure. So this is a little bit
different from your example in that it listens during compilation, wh
>global = \repeat unfold 100 s1
>music = \addAt (4 3/8) \global \once \override
>RehearsalMark.extra-offset #’(-1 . 0)
>
> where (4 3/8) means “in the fourth measure, at the moment of the 3rd
> eighth note”
I suggest that such a command allows for a third, optional parameter,
which ma
On Jan 14, 2014, at 1:03 AM, Kieren MacMillan
wrote:
> Hello all,
>
> What would be involved in developing a feature to add notes or tweaks at an
> arbitrary moment within a music expression?
>
> e.g.
>
>global = \repeat unfold 100 s1
>music = \addAt (4 3/8) \global \once \override R
Hello all,
What would be involved in developing a feature to add notes or tweaks at an
arbitrary moment within a music expression?
e.g.
global = \repeat unfold 100 s1
music = \addAt (4 3/8) \global \once \override RehearsalMark.extra-offset
#’(-1 . 0)
where (4 3/8) means “in the fourt
49 matches
Mail list logo
