Hi Valentin;
Thank you for your insights. I think I'll just drop this attempt to
reproduce exactly what the last transcriber/arranger tried to
accomplish (even though the person in question is an established
modern day composer, David Bruce).
I appreciate both you and Aaron sharing your
Thank you, Aaron.
Interesting thoughts...
Ken
On Fri, May 13, 2022 at 9:21 PM Aaron Hill wrote:
>
> On 2022-05-13 8:28 pm, Kenneth Wolcott wrote:
> > The ottava spanner terminates at the end of the note, not at the end
> > of the bar.
> >
> > How to change this?
> >
> > Screenshots
I actually tested that shortly after I sent the original post and will
definietly be utilizing something like that. Thanks!
On 5/14/2022 12:42, Kieren MacMillan wrote:
Hi Josh,
I use a slightly modified header and I am trying to position the composer,
arranger, and opus (which I am using
Hi Josh,
> I use a slightly modified header and I am trying to position the composer,
> arranger, and opus (which I am using for additional arranger information)
> fields evenly.
One note (especially if this is a "housestyle" that will be used again): No
need to overload the opus field. Just
Try using vspace instead of raise/lower. I put \vspace #.15 in front of the
\concat in the opus markup, which had about the right effect.
Paul
From: josh
To:
Sent: 14/05/2022 16:35
Subject: "Opus" positioning
I use a slightly modified header and I am trying to
Thanks Jean for marks formatting.
That leaves the font problem in 2.23.6 open.
JM
> Le 14 mai 2022 à 17:14, Jean Abou Samra a écrit :
>
>
>
> Le 14/05/2022 à 17:10, Jacques Menu a écrit :
>> Hello Jean,
>>
>> Sorry, my example wasn’t overly minimal…
>>
>> Here is one, attached.
>>
>> JM
I use a slightly modified header and I am trying to position the
composer, arranger, and opus (which I am using for additional arranger
information) fields evenly.
I can move the arranger field up and down using \raise and \lower,
however the opus field doesn't respond to such commands as it
Le 14/05/2022 à 17:10, Jacques Menu a écrit :
Hello Jean,
Sorry, my example wasn’t overly minimal…
Here is one, attached.
JM
OK, so it's an issue in 2.22, not in 2.23.6. That's expected:
markFormatter was renamed to rehearsalMarkFormatter. If you "backport" a
2.23.6 file to 2.22, you
Hello Jean,
Sorry, my example wasn’t overly minimal…
Here is one, attached.
JM
\version “2.23.6":
\version “2.22.0”:
JazzFontProblem.ly
Description: Binary data
Xavier
Thanks a lot for refining my hypothesis to correct code! This helps me
understand how to handle specific attributes in a nested list!
Am 13.05.2022 um 10:14 schrieb Xavier Scheuer:
On Fri, 13 May 2022 at 09:25, Mario Bolognani
wrote:
>
> Any idea on how to obtain this kind of
Le 14/05/2022 à 12:53, Jean Abou Samra a écrit :
Le 14/05/2022 à 09:08, Jacques Menu a écrit :
Another issue with 2.23.6 is that:
\set Score.rehearsalMarkFormatter = #format-mark-box-letters
is ignored.
Could you give an example? This works for me:
\version "2.23.6"
{
\set
Le 14/05/2022 à 09:08, Jacques Menu a écrit :
Another issue with 2.23.6 is that:
\set Score.rehearsalMarkFormatter = #format-mark-box-letters
is ignored.
Could you give an example? This works for me:
\version "2.23.6"
{
\set Score.rehearsalMarkFormatter = #format-mark-box-letters
Hello Ken,
As far as I know Lilypond's behaviour here is pretty much the standard
behaviour, as done by most Software, Editions and recommended by Gould. Thus
doing ottava markings like this should be considered uncommon notation.
Considering Tchaikovsky is not exactly modern music I think it
Another issue with 2.23.6 is that:
\set Score.rehearsalMarkFormatter = #format-mark-box-letters
is ignored.
JM
> Le 14 mai 2022 à 09:00, Jacques Menu a écrit :
>
> Hello folks,
>
> I have posted recently about a Jazz font problem, in which the chords names
> didn’t use it. I’ve noticed
14 matches
Mail list logo
