RE: command request

[Mark Stephen Mrotek]

David,

Thanks for your reply.
I found my error, \cadenzaOn was inserted after the first beat of a measure.


Mark

-Original Message-
From: David Rogers [mailto:davidandrewrog...@gmail.com] 
Sent: Thursday, June 11, 2020 3:44 PM
To: Mark Stephen Mrotek 
Cc: 'Karlin High' ; 'Lilypond-User Mailing List'

Subject: Re: command request

"Mark Stephen Mrotek"  writes:

> Karlin,
>
> Thank you for your reply and suggestion.
> The piano piece has a long cadenza (unmetered). 
> After the cadenza ends the next measure (metered) starts on what 
> appears to be the second beat.
>
> Mark
>

I'd instead be looking for better/cleaner ways of declaring to Lilypond that
the cadenza is unmetered, and/or clarifying the structure of what's before
and after it, in the hope of preventing the problem in the first place.

--
David Rogers

Re: command request

[David Rogers]

"Mark Stephen Mrotek"  writes:


Karlin,

Thank you for your reply and suggestion.
The piano piece has a long cadenza (unmetered). 
After the cadenza ends the next measure (metered) starts on what 
appears to

be the second beat.

Mark



I'd instead be looking for better/cleaner ways of declaring to 
Lilypond that the cadenza is unmetered, and/or clarifying the 
structure of what's before and after it, in the hope of preventing 
the problem in the first place.


--
David Rogers

Re: Text above a vertically shifted MultiMeasureRest

[Paolo Prete]

On Thu, Jun 11, 2020 at 7:03 PM Thomas Morley 
wrote:

>
>
> {
>   \override MultiMeasureRest.Y-offset = #-5
>   %% probably apply padding or Y-offset
>   %\override MultiMeasureRestText.padding = 2
>   \override MultiMeasureRestText.staff-padding = #'()
>   \override MultiMeasureRestText.outside-staff-priority = #'()
>   \time 2/4
>   R2^\markup { \italic "ad lib." }
> }
>
> Cheers,
>   Harm
>

Got it, thanks!

Re: Staff.OttavaBracket.direction

[David Kastrup]

Gianmaria Lari  writes:

> On Thu, 11 Jun 2020 at 17:33, Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com> wrote:
>
>> Hi Gianmaria,
>> Are you sure to want an *ottava bassa* on above the staff?
>> This could be pretty disturbing...
>>
>
>
> No, I'm not sure.
> I have no experience; in my particular case it just looked better. If you
> advise against it I will avoid it .

It may look better but it means playing an octave higher rather than an
octave lower.

-- 
David Kastrup

Re: horizontal spacing inside \magnifyMusic

[Valentin Petzel]

Hi Kieren,

Note that doing it this way has the same problem I explained before if two 
stems a considerably vertically apart (as we just regulate the horizontal 
space to the neighboring Note, which is not nescessarily the next note.

Regards,
Valentin

Am Donnerstag, 11. Juni 2020, 20:51:48 CEST schrieb Kieren MacMillan:
> Hi Eby,
> 
> > I'm looking for to achieve something like the output without using
> > "skips". I plan to run the midi output thru VST instrument, thus adding
> > skips is a big no. The example is achieved using "skip".
> 
> \version "2.19.83"
> { c'4 4 \tweak extra-spacing-width #'(-10 . 0) 4 4 }
> 
> Hope that helps!
> Kieren.
> 
> p.s. This kind of thing is EXACTLY why I use the edition-engraver so
> heavily!  =) 
> 
> Kieren MacMillan, composer (he/him/his)
> ‣ website: www.kierenmacmillan.info
> ‣ email: i...@kierenmacmillan.info

signature.asc
Description: This is a digitally signed message part.

Re: horizontal spacing inside \magnifyMusic

[Kieren MacMillan]

Hi Eby,

> I'm looking for to achieve something like the output without using "skips". I 
> plan to run the midi output thru VST instrument, thus adding skips is a big 
> no.
> The example is achieved using "skip".

\version "2.19.83"
{ c'4 4 \tweak extra-spacing-width #'(-10 . 0) 4 4 }

Hope that helps!
Kieren.

p.s. This kind of thing is EXACTLY why I use the edition-engraver so heavily!  
=)


Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info

Re: horizontal spacing inside \magnifyMusic

[Valentin Petzel]

Hello Eby,

As far as I know Lilypond does not offer an easy, clean way to add spacing 
between certain 
notes. If two stems are adjacent, you can specify the spacing of the stems. 
This does not 
work if there are no Stems or Stems are too far apart vertically.

One hacky way around would be using skips as grace notes. Thus you won’t get 
midi events, 
but still the spacing (though you are limited in the quantisiation of spacing 
you can add).


Have a look at the appended file.

Regards,
Valentin


Hello Valentine, 

I'm looking for to achieve something like the output without using "skips". I 
plan to run the 
midi output thru VST instrument, thus adding skips is a big no.

The example is achieved using "skip".

Thanks,eby


On Thursday, 11 June, 2020, 04:06:16 pm IST, Valentin Petzel 
 wrote: 




Hello Eby,




You could do as I’ve done in the appended file. That is basically whenever you 


need a more loose spacing, you do something like


\temporary\override Score.SpacingSpanner.common-shortest-duration =


#(ly:make-moment 1 256)


(where the 1/256 can be anything to your liking, using bigger note values like 


1/8 will result in tighter spacing, using smaller values will result in looser 


spacing.




Note that you could avoid the skips in the rests of the piano voice by scaling 


eighter the lengths of the respective violine notes, or scaling the length of 


the rests (like this: r1 r1*3/2 r1*5/4)




Regards,


Valentin 


\version "2.20.0"

global = {
  \key des \major
  \time 4/4
}

violin = \relative c' {
  \global

  \cadenzaOn 
  aes2\fermata
   
   %%spacerequired

\magnifyMusic 0.61 {
g32 \([aes b c d ees b c d ees 
ges] %%spacerequired
\once\override Stem.extra-spacing-width = #'(-0.8 . 1)
aes32\)[ %%spacerequired

d,!32 \(ees ges aes bes c des ees f ges aes bes]
}
%%spacerequired

   \once\override Stem.extra-spacing-width = #'(-1 . 0) c8-.\)
   
   \grace{ s s s s s }

%%spacerequired

\magnifyMusic 0.61 {
aes,,8-^ [c-^ ees-^ aes-^ c-^ ees-^ c-^ ees-^ aes-^ c-^ ees-^]

%%spacerequired
\ottava #1
\override Script.staff-padding = #2.5 {
   \stemDown  aes2\trill \pp a2\trill bes2\trill c2\trill \fermata } \bar "|"
\override Script.staff-padding = #0
}

\cadenzaOff

des1~
des2\fermata
\ottava #0
r \fermata \bar "|."

}

pianoVoice = \relative c'' {
  \global

  \cadenzaOn 1\fermata  r1 r s2 r1 s4 \bar"|" \cadenzaOff
f2 (f4-. f-.)
f2\fermata r\fermata \bar "|."
}


violinPart = \new Staff \with {
  instrumentName = "Violin"
  shortInstrumentName = "Vl."
  midiInstrument = "violin"
} \violin


\score {
  <<
\violinPart
\pianoVoice
  >>
  \layout { }
  \midi{ }
}

signature.asc
Description: This is a digitally signed message part.

RE: command request

[Mark Stephen Mrotek]

Karlin,

Thank you for your reply and suggestion.
The piano piece has a long cadenza (unmetered). 
After the cadenza ends the next measure (metered) starts on what appears to
be the second beat.

Mark

-Original Message-
From: Karlin High [mailto:karlinh...@gmail.com] 
Sent: Thursday, June 11, 2020 11:32 AM
To: Mark Stephen Mrotek ; 'Lilypond-User Mailing List'

Subject: Re: command request

On 6/11/2020 12:53 PM, Mark Stephen Mrotek wrote:
> What is the command that resets the next pitch to be on the first beat 
> of a measure?

How about \partial ?


--
Karlin High
Missouri, USA

Re: command request

[Karlin High]

On 6/11/2020 12:53 PM, Mark Stephen Mrotek wrote:
What is the command that resets the next pitch to be on the first beat 
of a measure?


How about \partial ?


--
Karlin High
Missouri, USA

command request

[Mark Stephen Mrotek]

Hello,

 

What is the command that resets the next pitch to be on the first beat of a
measure?

 

Thank you for your kind attention.

 

Mark

Re: Text above a vertically shifted MultiMeasureRest

[Thomas Morley]

Am Do., 11. Juni 2020 um 18:52 Uhr schrieb Paolo Prete :
>
> Hello,
>
> How can I put a text above a MultiMeasureRest, and not above the staff? This 
> would be useful for cross-staff MultiMeasureRests; for them I normally use 
> the Y-offset property in order to shift them down, as shown in the below code:
>
> { \override MultiMeasureRest.Y-offset = #-5 \time 2/4 R2^\markup { \italic 
> "ad lib." } }
>
> Thanks!

{
  \override MultiMeasureRest.Y-offset = #-5
  %% probably apply padding or Y-offset
  %\override MultiMeasureRestText.padding = 2
  \override MultiMeasureRestText.staff-padding = #'()
  \override MultiMeasureRestText.outside-staff-priority = #'()
  \time 2/4
  R2^\markup { \italic "ad lib." }
}

Cheers,
  Harm

Text above a vertically shifted MultiMeasureRest

[Paolo Prete]

Hello,

How can I put a text above a MultiMeasureRest, and not above the staff?
This would be useful for cross-staff MultiMeasureRests; for them I normally
use the Y-offset property in order to shift them down, as shown in the
below code:

{ \override MultiMeasureRest.Y-offset = #-5 \time 2/4 R2^\markup { \italic
"ad lib." } }

Thanks!

Re: Staff.OttavaBracket.direction

[Gianmaria Lari]

On Thu, 11 Jun 2020 at 17:33, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> wrote:

> Hi Gianmaria,
> Are you sure to want an *ottava bassa* on above the staff?
> This could be pretty disturbing...
>


No, I'm not sure.
I have no experience; in my particular case it just looked better. If you
advise against it I will avoid it .

Thank you Pierre!
g.

Re: Staff.OttavaBracket.direction

[Pierre Perol-Schneider]

Hi Gianmaria,
Are you sure to want an *ottava bassa* on above the staff?
This could be pretty disturbing...
Cheers,
Pierre

Le jeu. 11 juin 2020 à 17:10, Gianmaria Lari  a
écrit :

> My apologies if the question is trivial.
>
> I would like to print the ottavaBracket up the staff but even if I specify
> the direction of ottava bracket it doesn't work.  Here it is a not working
> example.
>
> \version "2.21.1"
> \fixed c'' {
>   \override Staff.OttavaBracket.direction = #UP
>   \ottava #-1 c d e f
> }
>
>
> Any suggestions?
>
> Thanks, g.
>

Staff.OttavaBracket.direction

[Gianmaria Lari]

My apologies if the question is trivial.

I would like to print the ottavaBracket up the staff but even if I specify
the direction of ottava bracket it doesn't work.  Here it is a not working
example.

\version "2.21.1"
\fixed c'' {
  \override Staff.OttavaBracket.direction = #UP
  \ottava #-1 c d e f
}


Any suggestions?

Thanks, g.

Possible Feature Request?

[Fr. Samuel Springuel]

Right now we have ly:source-files which contains a list of all input files 
which have been opened up to the point of it’s call, but there is, so far as I 
can tell, no equivalent for output files.  How difficult would it be to add 
such a scheme function/list?

As I see it, LilyPond obviously knows the name of each file it writes to at the 
time of the write operation (regardless of the kind of file it’s writing), so 
it ought to be possible to simply have it store said name in a list (perhaps 
with a check to make sure it’s unique if LilyPond writes to the same file 
multiple times) either just before or just after the write operation.  
Temporary/intermediate files would not need to be added to the list (if 
LilyPond knows they are temporary/intermediate at the time of the write) or 
could be removed from the list as part of the clean-up operations that remove 
the files themselves.

Of course I’m entirely speculating without having examined the source to look 
for the various write operations.  Could one of the developers with more 
knowledge of the source be so kind as to reality-check this idea?

✝✝
Fr. Samuel, OSB
(R. Padraic Springuel)
St. Anselm’s Abbey
4501 South Dakota Ave, NE
Washington, DC, 20017
202-269-2300
(c) 202-853-7036

PAX ☧ ΧΡΙΣΤΟΣ

Re: Odd \time bar check behaviour

[ebenezer]

Thank you Thomas,

That's a nice simple fix. It makes sense that \midi and \layout should 
be independent and thus the \contexts should be repeated. Now I know better.


Ebby.


On 2020-06-11 12:28, Thomas Morley wrote:

Am Do., 11. Juni 2020 um 09:43 Uhr schrieb ebenezer
:

Hello gentlemen,

Thank you for the replies. I have enclosed the full file as it seems
there may be some interaction between the voice in 7/4 and piano in 5/4.

Ebby.


On 2020-06-10 23:33, Martin Neubauer wrote:

On 10/06/2020 13:41, Michael Käppler wrote:

Am 10.06.2020 um 13:27 schrieb ebenezer:

Hi all,

The 1st code snippett generates warnings, but the 2nd does not.

I'd like to keep the bar symbols in place as it helps me to keep track
in the music.

This is my first piece so I've likely made some newbie error, please
advise.


Hi Ebby,
your first snippet does compile without warnings for me.
If your piece does have multiple voices (your filename suggests that),
it may well be that you have a rhythmical error in another voice.

To expand somewhat on this point: for me neither snippet compiles
without warning (or yielding any music, for that matter...), but just by
enclosing either on with braces both gets rid of the warnings and
results in correct output. That does indeed suggest that whatever
problem is causing you trouble isn't present in the excerpts you sent.

Regards,
Martin


Hi Ebby,

the warning comes from \midi

You move engravers in layout, which is fine. Alas, \midi does not know
about \layout-settings. Thus the bar-check fails for midi.
I think it's a known issue.

Workaround is to move engravers in \midi as well.

HTH,
   Harm

Re: Odd \time bar check behaviour

[Thomas Morley]

Am Do., 11. Juni 2020 um 09:43 Uhr schrieb ebenezer
:
>
> Hello gentlemen,
>
> Thank you for the replies. I have enclosed the full file as it seems
> there may be some interaction between the voice in 7/4 and piano in 5/4.
>
> Ebby.
>
>
> On 2020-06-10 23:33, Martin Neubauer wrote:
> >
> > On 10/06/2020 13:41, Michael Käppler wrote:
> >> Am 10.06.2020 um 13:27 schrieb ebenezer:
> >>> Hi all,
> >>>
> >>> The 1st code snippett generates warnings, but the 2nd does not.
> >>>
> >>> I'd like to keep the bar symbols in place as it helps me to keep track
> >>> in the music.
> >>>
> >>> This is my first piece so I've likely made some newbie error, please
> >>> advise.
> >>>
> >> Hi Ebby,
> >> your first snippet does compile without warnings for me.
> >> If your piece does have multiple voices (your filename suggests that),
> >> it may well be that you have a rhythmical error in another voice.
> > To expand somewhat on this point: for me neither snippet compiles
> > without warning (or yielding any music, for that matter...), but just by
> > enclosing either on with braces both gets rid of the warnings and
> > results in correct output. That does indeed suggest that whatever
> > problem is causing you trouble isn't present in the excerpts you sent.
> >
> > Regards,
> > Martin
> >
>

Hi Ebby,

the warning comes from \midi

You move engravers in layout, which is fine. Alas, \midi does not know
about \layout-settings. Thus the bar-check fails for midi.
I think it's a known issue.

Workaround is to move engravers in \midi as well.

HTH,
  Harm

Re: Odd \time bar check behaviour

[Rutger Hofman]

Did you have a look at the Notation Reference -- displaying rhythms - 
polymetric notation -- Different time signatures with unequal-length 
measures? See 
http://lilypond.org/doc/v2.21/Documentation/notation/displaying-rhythms#polymetric-notation 
then travel down to :Different time signatures with unequal-length".


Basically, you must move the Timing_translator and the 
Default_bar_line_engraver from the Score context to the Staff context.


HTH,

Rutger

On 6/11/20 9:43 AM, ebenezer wrote:

Hello gentlemen,

Thank you for the replies. I have enclosed the full file as it seems 
there may be some interaction between the voice in 7/4 and piano in 5/4.


Ebby.


On 2020-06-10 23:33, Martin Neubauer wrote:


On 10/06/2020 13:41, Michael Käppler wrote:

Am 10.06.2020 um 13:27 schrieb ebenezer:

Hi all,

The 1st code snippett generates warnings, but the 2nd does not.

I'd like to keep the bar symbols in place as it helps me to keep track
in the music.

This is my first piece so I've likely made some newbie error, please
advise.


Hi Ebby,
your first snippet does compile without warnings for me.
If your piece does have multiple voices (your filename suggests that),
it may well be that you have a rhythmical error in another voice.

To expand somewhat on this point: for me neither snippet compiles
without warning (or yielding any music, for that matter...), but just by
enclosing either on with braces both gets rid of the warnings and
results in correct output. That does indeed suggest that whatever
problem is causing you trouble isn't present in the excerpts you sent.

Regards,
Martin

Re: Collision on tremolo

[Thomas Morley]

Am Do., 11. Juni 2020 um 08:50 Uhr schrieb Pierre Perol-Schneider
:
>
> Hi Paolo,
>
> Le mer. 10 juin 2020 à 22:29, Paolo Prete  a écrit :
>>
>> Hello,
>>
>> as you can see in Lilybin's output, the below expression produces a 
>> collision:
>>
>> { \repeat tremolo 8 { aes'16 bes' } }
>>
>> http://lilybin.com/tmdugu/1
>>
>> What's wrong
>
>
> Definitly a bug.

Yep,
https://gitlab.com/lilypond/lilypond/-/issues/704
(there are some other related issues)
There you can find an image from Gould proposing tremolo-beams with
whole notes should be done as if there were stems. Alternatively
between the NoteHeads.

You may be interested in
http://lilypond.1069038.n5.nabble.com/Proposal-Changing-tremolo-beam-gap-implementation-td230988.html
and
http://lilypond.1069038.n5.nabble.com/Whole-note-tremolo-beams-td230689.html
where I try to propose some code for the note-head centered alternative.

Paolo, if you try my code from there (tremolo-gap.ly), you'll notice
the Beam comes out very short. You may want to lengthen it.
Furthermore, to get the appearance of between-invisible-stems tremolo,
apply a positions-override as demonstrated by Pierre already:

%% include the code from tremolo-gap.ly
{
\override Beam.springs-and-rods = #ly:spanner::set-spacing-rods
\override Beam.minimum-length = 8
%\override Beam.positions = #'(3 . 3.5)
\repeat tremolo 8 { aes'16 bes' }
}

Torsten planned to provide a patch, though I don't know the current
status. cc-ing him.

Cheers,
  Harm

Re: horizontal spacing inside \magnifyMusic

[Valentin Petzel]

Hello Eby,

You could do as I’ve done in the appended file. That is basically whenever you 
need a more loose spacing, you do something like
\temporary\override Score.SpacingSpanner.common-shortest-duration =
#(ly:make-moment 1 256)
(where the 1/256 can be anything to your liking, using bigger note values like 
1/8 will result in tighter spacing, using smaller values will result in looser 
spacing.

Note that you could avoid the skips in the rests of the piano voice by scaling 
eighter the lengths of the respective violine notes, or scaling the length of 
the rests (like this: r1 r1*3/2 r1*5/4)

Regards,
Valentin\version "2.20.0"

global = {
  \key des \major
  \time 4/4
}

violin = \relative c' {
  \global

  \cadenzaOn 
  \temporary\override Score.SpacingSpanner.common-shortest-duration = #(ly:make-moment 1 256)
  aes2\fermata
   
   %%spacerequired

\magnifyMusic 0.61 {
g32 \([aes b c d ees b c d ees ges] %%spacerequired

aes32\) %%spacerequired

d,!32 \(ees ges aes bes c des ees f ges aes bes]
}
%%spacerequired

c8-.\)

%%spacerequired

\magnifyMusic 0.61 {
aes,,8-^ [c-^ ees-^ aes-^ c-^ ees-^ c-^ ees-^ aes-^ c-^ ees-^]

%%spacerequired
\ottava #1
\revert Score.SpacingSpanner.common-shortest-duration
\override Script.staff-padding = #2.5 {
   \stemDown  aes2\trill \pp a2\trill bes2\trill c2\trill \fermata } \bar "|"
\override Script.staff-padding = #0
}

\cadenzaOff

des1~
des2\fermata
\ottava #0
r \fermata \bar "|."

}

pianoVoice = \relative c'' {
  \global

  \cadenzaOn 1\fermata  r1 r s2 r1 s4 \bar"|" \cadenzaOff
f2 (f4-. f-.)
f2\fermata r\fermata \bar "|."
}


violinPart = \new Staff \with {
  instrumentName = "Violin"
  shortInstrumentName = "Vl."
  midiInstrument = "violin"
} \violin


\score {
  <<
\violinPart
\pianoVoice
  >>
  \layout { }
}

signature.asc
Description: This is a digitally signed message part.

Re: Collision on tremolo

[Pierre Perol-Schneider]

Hi Paolo,

Le mer. 10 juin 2020 à 22:29, Paolo Prete  a écrit :

> Hello,
>
> as you can see in Lilybin's output, the below expression produces a
> collision:
>
> { \repeat tremolo 8 { aes'16 bes' } }
>
> http://lilybin.com/tmdugu/1
>
> What's wrong
>

Definitly a bug.


> how can I fix it?
>

Maybe:

\version "2.20.0"

{
  \once\override Beam.positions = #'(3 . 3)
  \repeat tremolo 8 { aes'16 bes' }
}


> Thanks!
>

Cheers,
Pierre