>> /tmp/frescobaldi-_MMpyy/tmpsaOidZ/document.ly:9:68: error: wrong type
>> for argument 1. Expecting duration, found "4."
>> "Allegretto vivace"\smaller \general-align #Y #DOWN \note
>> #"4." #UP
>
> It’s not a
Am 12.07.2018 um 07:33 schrieb Menu Jacques:
/tmp/frescobaldi-_MMpyy/tmpsaOidZ/document.ly:9:68: error: wrong type for argument 1.
Expecting duration, found "4."
"Allegretto vivace"\smaller \general-align #Y #DOWN \note
OK, I have to go back to 2.19.82. What’s the easiest way to do that?
Thanks!
JM
> Le 12 juil. 2018 à 07:33, Menu Jacques a écrit :
>
> Hello folks,
>
> Doing a ‘git pull’ on my LilyDev 4 virtual machine and building Lily produced
> a 2.21.0 version, that rejects:
>
>
> \version "2.21.0"
>
Hello folks,
Doing a ‘git pull’ on my LilyDev 4 virtual machine and building Lily produced a
2.21.0 version, that rejects:
\version "2.21.0"
P_POne_Staff_One_Voice_One = \relative c' {
\tempo \markup {
\concat {
(
"Allegretto vivace"\smaller \general-align #Y #DOWN \note
Hello to everyone,
For some rather obscure reason I wanted to use old style numbers in a
series of scores I'm working in. In a first moment I worked using some
functions written by Michael Lauer (to be found in
https://www.mrlauer.org/music/) but they were intended for version 2.12 and
I couldn't
On 11.07.2018 10:05, Menu Jacques wrote:
The cross staff chord can actually be obtained with the code below, in
which the upper part of the last two chords has been moved to the
first staff ‘by hand' and rests set up accordingly,
The two actual voices are still independent from each other and
On 11.07.2018 10:05, Menu Jacques wrote:
Is one among the three scores above clearly preferable for a keyboard
player?
And what if moving notes to the first staff conflicts with other music
already present there?
Cross-staff chords are very rarely used in keyboard music and are
definitely
Urs Liska writes:
> Am 11.07.2018 um 11:55 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> Am 10.07.2018 um 19:48 schrieb Urs Liska:
This seems to confirm that I should *not* break out of the for-each
loop that iterates over all-grobs in process-acknowledged.
Does that
Urs Liska writes:
> Am 11.07.2018 um 10:33 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> One more understanding question regarding contexts and engravers.
>>>
>>> If I \consist an engraver in a bottom context like Voice I can travel
>>> up the chain of parent contexts, retrieving their
Am 11.07.2018 um 11:55 schrieb David Kastrup:
Urs Liska writes:
Am 10.07.2018 um 19:48 schrieb Urs Liska:
This seems to confirm that I should *not* break out of the for-each
loop that iterates over all-grobs in process-acknowledged.
Does that mean that resetting the all-grobs list in
Am 11.07.2018 um 10:33 schrieb David Kastrup:
Urs Liska writes:
One more understanding question regarding contexts and engravers.
If I \consist an engraver in a bottom context like Voice I can travel
up the chain of parent contexts, retrieving their name and id
properties. But if I
On 7/11/2018 4:45 PM, Torsten Hämmerle wrote:
Hi Ben,
The easiest way would probably be to apply some kind of filter, extracting
the relevant music.
In the example, we have some kind of "manually created \partcombine" that
lacks certain information. It is not at all clear whether the single
Hi Ben,
The easiest way would probably be to apply some kind of filter, extracting
the relevant music.
In the example, we have some kind of "manually created \partcombine" that
lacks certain information. It is not at all clear whether the single notes
in the non-parallel music should be played
Hi everyone,
I have a question about the score I am working on at the moment, for a
group. These are not my original .ly files however I am in the process
of fine-tuning / cleaning them up and primarily focusing on engraving a
finished product with parts for players.
For this, please assume
Hello Rutger,
Fine, your solution is cleaner than the one I had come to.
I’ll make good use of that.
Thanks, and a nice day!
JM
> Le 11 juil. 2018 à 09:35, Rutger Hofman a écrit :
>
> Hi Jacques,
>
> if you follow the instructions on cross-staff stems, you will arrive at
> something like
Hi Jacques,
if you follow the instructions on cross-staff stems, you will arrive at
something like this:
\version "2.19.0"
\score {
\new PianoStaff \with {
\consists #Span_stem_engraver
} <<
\new Staff = RH <<
{
\clef treble
Urs Liska writes:
> Am 10.07.2018 um 19:48 schrieb Urs Liska:
>>
>> This seems to confirm that I should *not* break out of the for-each
>> loop that iterates over all-grobs in process-acknowledged.
>>
>> Does that mean that resetting the all-grobs list in
>> start-translation-timestep is the
Urs Liska writes:
> One more understanding question regarding contexts and engravers.
>
> If I \consist an engraver in a bottom context like Voice I can travel
> up the chain of parent contexts, retrieving their name and id
> properties. But if I \consist it in Staff level contexts I don't see
>
One more understanding question regarding contexts and engravers.
If I \consist an engraver in a bottom context like Voice I can travel up
the chain of parent contexts, retrieving their name and id properties.
But if I \consist it in Staff level contexts I don't see if/how I can
get to the
Am 10.07.2018 um 19:48 schrieb Urs Liska:
This seems to confirm that I should *not* break out of the for-each
loop that iterates over all-grobs in process-acknowledged.
Does that mean that resetting the all-grobs list in
start-translation-timestep is the right approach#
It's obviously
20 matches
Mail list logo
