Hi Jan-Peter,
> did you receive this message?
Yes, I received that. Sorry for not responding sooner.
> Did you have a chance to test the code?
Unfortunately not yet.
I will as soon as I can — early next week at the latest.
Thanks,
Kieren.
Kieren MacMillan, com
Hi Kieren,
did you receive this message? Did you have a chance to test the code?
Best
Jan-Peter
Am 23.08.2017 um 10:58 schrieb Jan-Peter Voigt:
Hi Kieren,
I merged a few things into master. Now upbeats and instant voices should
work as expected. At least in my tiny examples they do.
I'd l
Hi Kieren,
I merged a few things into master. Now upbeats and instant voices should
work as expected. At least in my tiny examples they do.
I'd like you to test two things:
1. test, if the master branch doesn't fail with your scores. I tested
the code and only merged stuff that passed my che
thanks!
That does it
Am 22.08.2017 um 11:54 schrieb David Kastrup:
Jan-Peter Voigt writes:
... OK, now I found it!
It is a matter of order: If the edition-engraver is consisted before
the Timing the timing-information is not updated and so the last
reported timestep is used in the start-tra
Jan-Peter Voigt writes:
> ... OK, now I found it!
>
> It is a matter of order: If the edition-engraver is consisted before
> the Timing the timing-information is not updated and so the last
> reported timestep is used in the start-translation-timestep slot of
> the engraver. A lot of the mods are
... OK, now I found it!
It is a matter of order: If the edition-engraver is consisted before the
Timing the timing-information is not updated and so the last reported
timestep is used in the start-translation-timestep slot of the engraver.
A lot of the mods are applied in that stage of transla
Hi Kieren,
the issue is not fixed (yet), but I found a hint. The EE uses the
context-properties currentBarNumber and measurePosition to collect
current mods from the tree. Somehow these values are laid back inside
the EE code so they report the preceding moment when the Timing is moved
away f
Hi all,
> In the case of cadenze, it would make more sense to use
> absolute time for additional _offsets_ to a bar/measurepos pair.
+1
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
__
Hi Jan-Peter,
Here are the features I think would be essential in the optimal
edition-engraver:
1. offset from a mark or moment 0;
2. relative (the default?) and absolute offset;
3. targetting of a context id (requires an offset for tweaking);
4. targetting of a [unique] grob id (does not requir
Hi David,
you are right. This is an idea I also thought about. I will see how to add
that.
A while ago Kieren and I discussed using a mark event together with an offset
for use in polymetric scores.
Jan-Peter
Am 18. August 2017 09:13:21 MESZ schrieb David Kastrup :
>Jan-Peter Voigt writes:
Jan-Peter Voigt writes:
> Hi Kieren,
>
> it is not implemented yet, allthough I carry this idea for a while. It
> is no problem to use ly:context-now, but it adds another schema/branch
> to the tree. That shouldn't be a big deal, but still it has to be
> implemented carefully.
Personally I think
Hi Kieren,
it is not implemented yet, allthough I carry this idea for a while. It is no
problem to use ly:context-now, but it adds another schema/branch to the tree.
That shouldn't be a big deal, but still it has to be implemented carefully.
Jan-Peter
Am 17. August 2017 23:47:56 MESZ schrieb
Hi Jan-Peter,
>> May I ask, after \cadenzaOn there is no moment anymore?
>
> It doesn't advance. That's pretty much the point of a cadenza.
>
>> Is there some other internal counter for this?
>
> Absolute time as via ly:context-now or grob::when . This is global and
> unfazed by all timing an
Francisco Vila writes:
> On 16/08/17 14:53, David Kastrup wrote:
>> Kieren MacMillan writes:
>>
>>> Hi David,
>>>
Something like
>>> This is great!
>>>
>>> …except in the *exact* circumstance I actually need it for:
>
> {
> c d-"@" f g
> c d-"@" f g
> \cadenzaOn
> c d-"@" f g
> c d-"@" f g
On 16/08/17 14:53, David Kastrup wrote:
> Kieren MacMillan writes:
>
>> Hi David,
>>
>>> Something like
>> This is great!
>>
>> …except in the *exact* circumstance I actually need it for:
{
c d-"@" f g
c d-"@" f g
\cadenzaOn
c d-"@" f g
c d-"@" f g
}
May I ask, after \cadenzaOn there is no mome
Kieren MacMillan writes:
> Hi David,
>
>> Perhaps it would have been worthwhile creating a minimal example
>> demonstrating the exact circumstance you actually need it for...
>
> Your revised code — brilliant, as always! —
I was rather angling for "illuminating". "brilliant" means one gets
sadd
Hi David,
> I'll try it in my "real-world" score and report back.
Here is a screenshot of a portion of my current engraving:
As you can see, the second staff is [correctly] displaying 36@0, and the third
staff is [correctly] displaying 35@1/4.
*HOWEVER*: the edition-engraver tweak required t
Hi David,
> Perhaps it would have been worthwhile creating a minimal example
> demonstrating the exact circumstance you actually need it for...
Your revised code — brilliant, as always! — appears to work perfectly on the
attached MWE of the exact circumstance I need.
I'll try it in my "real-worl
Kieren MacMillan writes:
> Hi David,
>
>> Something like
>
> This is great!
>
> …except in the *exact* circumstance I actually need it for:
Perhaps it would have been worthwhile creating a minimal example
demonstrating the exact circumstance you actually need it for...
--
David Kastrup
__
Kieren MacMillan writes:
> Hi David,
>
>> Something like
>
> This is great!
>
> …except in the *exact* circumstance I actually need it for:
>
> SNIPPET BEGINS
> \version "2.19.64"
>
> #(define (moment->string mom)
> (if (zero? (ly:moment-grace mom))
> (number->string (ly:moment-main mom)
Hi David,
> Something like
This is great!
…except in the *exact* circumstance I actually need it for:
SNIPPET BEGINS
\version "2.19.64"
#(define (moment->string mom)
(if (zero? (ly:moment-grace mom))
(number->string (ly:moment-main mom))
(format "~sG~a" (ly:moment-main mom) (ly:mome
Kieren MacMillan writes:
> Hi all,
>
> Is there a function (2.19.64) that will output the current context
> moment (e.g., measure number and beat) as markup?
> In my polymetric scores, I need to target moments (using the
> edition-engraver), and it currently involves a bit too much
> trial-and-er
22 matches
Mail list logo
