Re: LilyPond 2.24.4 released!

2024-07-21 Thread Hajo Baess
Thank you for the good news! And of course another big Thank You to
everyone who made this new version possible.

Can't wait to test-drive it...

Am Sonntag, dem 21.07.2024 um 22:31 +0200 schrieb Jonas Hahnfeld via
LilyPond user discussion:
> We are proud to announce the release of GNU LilyPond 2.24.4. LilyPond
> is a music engraving program devoted to producing the highest-quality
> sheet music possible. It brings the aesthetics of traditionally
> engraved music to computer printouts.
> 
> This version contains a number of fixes since the release of the
> previous stable version in November 2023. We recommend all users to
> update. Scores converted to or written for 2.24.0 will continue to
> work
> with this release.
> A list of added features and other user-visible changes for 2.24 can
> be
> found at https://lilypond.org/doc/v2.24/Documentation/changes/. Among
> others, version 2.24.0 switched to Guile 2.2 and features a
> completely
> rewritten infrastructure for creating the official packages, finally
> allowing us to offer 64-bit binaries for macOS and Windows. These
> pre-
> built binaries are linked from https://lilypond.org/download.html and
> available from GitLab:
> https://gitlab.com/lilypond/lilypond/-/releases/v2.24.4
> 
> For distributions, Guile 3.0 is officially supported since the
> previous
> LilyPond 2.24.3, even though the recommended version will remain
> Guile
> 2.2 for the LilyPond 2.24 series.




Re: Frescobaldi... panic alternatives?

2024-05-02 Thread Hajo Baess
And while you are about to extend the 'Easier Editing' section: maybe
for the Mac users in particular one might want to add the combination
of TeXShop/LaTeX and Skim/Preview. I had a Mac until about 12 years ago
when I started to use LilyPond. That was on Mac OS 10.4, before I left
the Apple universe for good in favor of Linux. But this combo worked
very well for me, and both programs are still around, so that one can
safely assume that it still is an option today.

It is just good to know there are alternatives to Frescobaldi, and it
would be convenient to have them mentioned in one place, so everyone
can check them out.

Am Donnerstag, dem 02.05.2024 um 04:33 + schrieb Kenneth Flak:
> OK, giving it a shot... Feel free to edit as needed!
> 
> Kenneth
> 
> 
> Neovim
> 
> https://neovim.io
> 
> Neovim is a minimal text editor and fork of vim. It is highly
> extensible and configurable through the vimscript and lua programming
> languages. Lilypond support is provided by the nvim-lilypond-suite
> plugin (https://github.com/martineausimon/nvim-lilypond-suite). The
> plugin supports playback of midi files through external programs;
> point-and-click when using a supported PDF viewer; snippets and code
> completion when combined with other plugins; in addition to the full
> range of tools available in the neovim ecosystem. For more details on
> how to set it up consult the plugin's github page. You will also want
> to spend some time with some of the numerous online tutorials for
> learning vim/neovim to get the most out of your editing experience.
> 
> 
> Werner LEMBERG, May 02, 2024 at 05:49:
> > 
> > > > Maybe one of you two can provide some text for
> > > > 
> > > >   
> > > > https://lilypond.org/doc/v2.24/Documentation/web/easier-editing
> > > 
> > > It happens that my first contribution to the Lilypond
> > > documentation
> > > was a rewrite of the Easier Editing section, some 14 years ago or
> > > so.
> > 
> > Aaah :-)
> > 
> > > If either or both care to send me their thoughts and comments,
> > > I'll
> > > be glad to turn it into a patch.
> > 
> > This would be great!  Thanks for the offer.
> > 
> > 
> >     Werner
> 
> 
> 
> 




Re: Fw: Frescobaldi ... panic alternatives?

2024-04-30 Thread Hajo Baess
Hi all,

There are various alternatives around at least for Linux users, but
there will certainly be different ones available for the Mac users as
well. And who knows: maybe Frescobaldi will survive after all. And if
it may stop working one day, it is good to know that at least you are
not completely left in the wild. 

I have checked out the following ones for Linux:
1. Spontini (not so known maybe, but definitely worth a try)
2. Kate/Okular as a "team" with one-way point-and-click from Okular to
Kate
3. Visual Studio Code with its LilyPond plugins/extensions

All three are not exactly like Frescobaldi, but can certainly amply be
adapted to individual needs into a good workspace.

And then, of course, there is also lilypond-book, which I personally
find a bit complicated - at least when you come from Frescobaldi.
Steeper learning curve, but not impossible if you are determined and
open to something new.

So: don't panic (do not forget the towel either) and let us keep using
Frescobaldi and enjoy as long as it will exist...

Am Dienstag, dem 30.04.2024 um 12:56 +0200 schrieb Paolo Prete:
> On Tue, Apr 30, 2024 at 6:45 AM Dirck Nagy  wrote:
> 
> > Hi all
> > 
> > Reading that last thread about Frescobaldi and its possible
> > disappearance
> > from Mac is causing me to panic. Jean, I did not realize that you
> > were the
> > last person to seriously work on Frescobaldi / Mac.
> > 
> > 
> > I use Mac exclusively, and Frescobaldi / Lilypond is very important
> > to me.
> > 
> > 
> > FYI, what I like the most about Frescobaldi are:
> > 
> > 
> > 
> >    -
> > 
> >    Templates and wizards
> >    -
> > 
> >    Snippets
> >    -
> > 
> >    Point and Click selection
> >    -
> > 
> >    Syntax highlighting
> > 
> > 
> > If Frescobaldi for Mac does indeed vanish, what are my alternatives
> > for a
> > Lilypond editor?
> > 
> > 
> > 
> Hi,
> 
> Although https://github.com/paopre/Spontini is focused on _very
> different_
> tasks than Frescobaldi, it has the features you just mentioned (they
> are
> exposed in a somewhat different way, but they should work), including
> code
> completion
> I could not extensively test it in the past months, nor I own a Mac,
> but
> thanks to CI/CD it should work on newer versions.
> I'm planning to make a new release in the next few weeks.
> Also, at the moment there are no active contributors for it.
> Therefore, any
> help is really appreciated...




Re: Frescobaldi?

2024-04-29 Thread Hajo Baess
Would it maybe make things a bit easier to leave the whole MacOS
business aside and take care of the Linux-specific stuff first? And
what actually about Windows - out of curiosity. I myself am a Linux
user (Mint), and so far Frescobaldi is still running flawlessly.

And - another question out of curiosity: Could it be a workaround (if
Qt5 would be officially retired and no longer be available in the repos
of the "big" distros like Mint, Ubuntu and the like) if one used a
distro for older computers which might stick to Qt5 much longer?

At any rate the present state of affairs is really sad, since
Frescobaldi just is a masterpiece of software for its purpose. I have
looked at a couple of alternatives, but I was less convinced of them.

Maybe in case Frescobaldi one day will not run any more, I need to
return to a combination of a good text editor and a PDF viewer like I
had many years ago when I was still a Mac user. I had TeXShop and Skim,
and that worked well enough. And then I also sometimes used
LilyPondTool which in the meantime is defunct as well, but was a
similar approach to editing LilyPond files as Frescobaldi.

This is the moment when I wish I'd be a programmer, but I am afraid the
learning curve for helping out with Frescobaldi would be way to steep
for me...

Am Sonntag, dem 28.04.2024 um 22:14 +0200 schrieb Jean Abou Samra:
> > […]
> > Well, the explanation wasn't that brief. Sorry that I didn't have
> > time to write a shorter one, as they say.
> 
> 
> PS: Maybe I should mention that at the time I went down the rabbit
> hole of Python packaging in general because of Frescobaldi, I wrote
> two articles on the LinuxFR site, which may be of interest here if
> one reads French:
> 
> https://linuxfr.org/news/l-installation-et-la-distribution-de-paquets-python-1-4
> https://linuxfr.org/news/l-installation-et-la-distribution-de-paquets-python-2-4
> 
> (Yes, these are ~8 and ~14 pages long. Yes, they're only the two
> first articles in a series of four. I haven't given up on publishing
> the two others, but it's not my priority at the moment.)
> 




Re: Force LilyPond to show same time signature again

2024-04-22 Thread Hajo Baess
Not quite yet: I do not want the 3/4 to appear in the left hand where
for this part there is no actual meter change. But I think you put me
on the right track: the solution is that you need to add \omit
Staff.TimeSignature before the second 3/4. Then the only the first 3/4
is shown.

Thank you so much for your helpfulness. It's always satifying for both
sides if you can say afterwards: 'case solved'.


Am Montag, dem 22.04.2024 um 07:42 -0700 schrieb Knute Snortum:
> On Mon, Apr 22, 2024 at 3:32 AM Hajo Baess  wrote:
> 
> > > Is there a reason you are writing...
> > 
> > Yes there is.
> 
> [...]
> 
> > The question is only: will it work as well in my score. I still
> > have to try and see, and I will report what will happen...
> > 
> 
> I think this does what you want:
> 
> \version "2.24.3"
> 
> rightHand = \relative c' {
>   \time 3/4
>   \repeat unfold 6 { c8 }
>   \set Staff.timeSignatureFraction = 9/8
>   \scaleDurations 2/3 {
>     \repeat unfold 9 { c8 }
>   }
>   \set Staff.timeSignatureFraction = 3/4
>   \repeat unfold 6 { c8 }
> }
> 
> leftHand = \relative c {
>   \clef bass
>   \time 3/4
>   \repeat unfold 6 { c8 }
>   \time 3/4
>   \repeat unfold 6 { c8 }
>   \time 3/4
>   \repeat unfold 6 { c8 }
> }
> 
> \score {
>   \new GrandStaff <<
>     \new Staff = "upper" \rightHand
>     \new Staff = "lower" \leftHand
>   >>
> }
> 
> 
> --
> Knute Snortum




Re: Force LilyPond to show same time signature again

2024-04-22 Thread Hajo Baess
> Is there a reason you are writing...

Yes there is. Let me explain, because from what you have seen so far,
this is not obvious.
What I am typesetting is an Italian violin piece from a manuscript from
around 1800. Back then it seems that our modern triplet notation were
unknown in Italy or did not exist yet. Composers instead just wrote a
meter change - in my case from 3/4 to 9/8 and back where it was no
longer necessary. But they only notated this meter change in the
part(s) where it was necessary. I other parts they just went on with
the initial meter. Like that it was clear nevertheless for a musician
that the 9/8 meant triple subdivision to a beat instead of the standard
even subdivision.

Since I am writing a score (trying to keep the original notation), I
have a pseudo-polymetric setup in those places, and that's why I had
the idea of scaling the rhythm in there: if I dont, Lilypond gets it
wrong in the 9/8 bars, of course, because it expects six eighth notes
to a bar instead of nine.

Of course these things are easier to implement in an individual part
(or I just could simply turn to triplets) than in a score, but maybe I
mentally made it too complicated, and there does exist a better and
more efficient way.

I can confirm that your suggestion vs. my weirdo code in my test file
produces exactly the same result, and that it is the intended one
indeed. The question is only: will it work as well in my score. I still
have to try and see, and I will report what will happen...

In the score, if you look at the screenshot again, you can see that 
the two upper parts temporarily need that pseudo meter change, whereas
the bass part keeps going in 3/4. What I initially have typed before
asking here worked alright except for the fact that at the switch back
to 3/4 there was no 3/4 again, although I had written "\time 3/4", and
I could not figure out why.

Am Samstag, dem 20.04.2024 um 16:06 -0700 schrieb Knute Snortum:
> On Sat, Apr 20, 2024 at 3:02 PM Hajo Baess  wrote:
> 
> > I have messed around with this little lab specimen here, and I have
> > found a solution, but it is weird. You obviously (after having
> > scaled
> > some rhythm just once) have to explicitly unscale the rhythm  e v e
> > r y
> > time you want it to appear in the staff. I have extended the
> > example
> > with a short quote from the piece I am typesetting. this is what
> > obviously works:
> > 
> > > \version "2.24.2"
> > > \language "deutsch"
> > > 
> > > \relative c''  {
> > >   \time 3/4 c4 c c c2 c4
> > >   \time 3/4 c4 c c c2 c4
> > >   \omit Score.TimeSignature
> > >   \time 3/4 c4 c c c2 c4
> > >   \undo \omit Score.TimeSignature
> > >   \time 3/4 c4 c c c2 c4
> > >   \time 3/4 \set Staff.timeSignatureFraction = 9/8
> > >   \scaleDurations 2/3 {
> > >   \repeat unfold 3 { f8 ( d a ) }  \repeat unfold 3 {
> > > e' ( cis a ) } \repeat unfold 3 { f'8 ( d a ) }
> > >   \repeat unfold 3 { g' ( e c ) } \repeat unfold 3 {
> > > a' ( f c ) } \repeat unfold 3 { g' ( e c ) }
> > >   \repeat unfold 3 { f8 ( d a ) }
> > >   } %\override Score.TimeSignature.stencil = ##f
> > >   \time 3/4  \set Staff.timeSignatureFraction = 3/4
> > >   \scaleDurations 1/1
> > >   {
> > >   cis4\trill cis2 d4 d4. c16 d e2 e4 f4 f4. g8 e2 e4
> > > f
> > > d d ~ d8 cis d4 d4
> > >   }
> > >   \time 3/4 \set Staff.timeSignatureFraction = 3/4
> > >   \scaleDurations 1/1
> > >   { d2 d4\fermata}
> > >   \bar "|."
> > > }
> > 
> > If you just type "\time 3/4" at the end for instance, you won't get
> > your time signature shown. At least this prodecure is completely
> > unintuitive, I think.
> > 
> 
>  A couple of points:
> 
> * 


>  " \time 3/4 \set
> Staff.timeSignatureFraction = 9/8" and then scaling by 2/3 rather
> than just
> writing "\time 9/8"?
> * Why are you writing "\time 3/4  \set Staff.timeSignatureFraction =
> 3/4"
> instead of just "\time 3/4"?
> * "\scaleDuractions 1/1 {}" is doing nothing and can be removed.
> 
> Applying my suggestions to your music, you get this, which seems to
> work as
> you want it to:
> 
> \version "2.24.2"
> \language "deutsch"
> 
> \relative c''  {
>   \time 3/4 c4 c c c2 c4
>   \time 3/4 c4 c c c2 c4
>   \omit Score.TimeSignature
>   \time 3/4 c4 c c c2 c4
>   \undo \omit Score.TimeSignature
>   \time 3/4 c4 c c c2 c4
>   \time 9/8
>   \repeat unfold 3 { f8 ( d a ) }
>   \repeat unfold 3 {e' ( cis a ) }
>   \repeat unfold 3 { f'8 ( d a ) }
>   \repeat unfold 3 { g' ( e c ) }
>   \repeat unfold 3 {a' ( f c ) }
>   \repeat unfold 3 { g' ( e c ) }
>   \repeat unfold 3 { f8 ( d a ) }
>   \time 3/4
>   cis4\trill cis2 d4 d4. c16 d e2 e4 f4 f4. g8 e2 e4 f d d ~ d8 cis
> d4 d4
>   \time 3/4
>   d2 d4\fermata
>   \bar "|."
> }




Re: Force LilyPond to show same time signature again

2024-04-20 Thread Hajo Baess
I have messed around with this little lab specimen here, and I have
found a solution, but it is weird. You obviously (after having scaled
some rhythm just once) have to explicitly unscale the rhythm  e v e r y
time you want it to appear in the staff. I have extended the example
with a short quote from the piece I am typesetting. this is what
obviously works:

> \version "2.24.2"
> \language "deutsch"
> 
> \relative c''  {
>   \time 3/4 c4 c c c2 c4
>   \time 3/4 c4 c c c2 c4
>   \omit Score.TimeSignature
>   \time 3/4 c4 c c c2 c4
>   \undo \omit Score.TimeSignature
>   \time 3/4 c4 c c c2 c4
>   \time 3/4 \set Staff.timeSignatureFraction = 9/8
>   \scaleDurations 2/3 {
>   \repeat unfold 3 { f8 ( d a ) }  \repeat unfold 3 {
> e' ( cis a ) } \repeat unfold 3 { f'8 ( d a ) }
>   \repeat unfold 3 { g' ( e c ) } \repeat unfold 3 {
> a' ( f c ) } \repeat unfold 3 { g' ( e c ) }
>   \repeat unfold 3 { f8 ( d a ) }
>   } %\override Score.TimeSignature.stencil = ##f
>   \time 3/4  \set Staff.timeSignatureFraction = 3/4
>   \scaleDurations 1/1
>   {
>   cis4\trill cis2 d4 d4. c16 d e2 e4 f4 f4. g8 e2 e4 f
> d d ~ d8 cis d4 d4
>   }
>   \time 3/4 \set Staff.timeSignatureFraction = 3/4
>   \scaleDurations 1/1
>   { d2 d4\fermata}
>   \bar "|."
> }

If you just type "\time 3/4" at the end for instance, you won't get
your time signature shown. At least this prodecure is completely
unintuitive, I think.

Am Samstag, dem 20.04.2024 um 14:02 -0700 schrieb Knute Snortum:
> On Sat, Apr 20, 2024 at 1:32 PM Hajo Baess  wrote:
> 
> > What you suggest sounds all so common-sense, but LilyPond still
> > does
> > not get it...
> > If I implant "\omit Score.TimeSignature" and "\undo \omit
> > Score.TimeSignature" into my code instead of the previous commands,
> > I
> > get this - see screenshot.
> > 
> > But if I do something really basic like:
> > 
> > \version "2.24.2"
> > \language "deutsch"
> > 
> > \relative c''  {
> >     \time 3/4 c4 c c c2 c4
> >     \time 3/4 c4 c c c2 c4
> >     \omit Score.TimeSignature
> >     \time 3/4 c4 c c c2 c4
> >     \undo \omit Score.TimeSignature
> >     \time 3/4 c4 c c c2 c4
> >     \bar "|."
> > }
> > 
> > it works as expected. It really seems to have something to do with
> > the
> > scaled rhythms - that is my guess.
> > 
> 
> This is where tiny examples (https://lilypond.org/tiny-examples.html)
> are
> important.  Build an example of the problem with as little other
> stuff as
> possible.  It's difficult sometimes, but it will sometimes lead you
> to an
> answer, and it certainly helps anyone trying to assist you.
> 
> 
> --
> Knute Snortum
> 
> 
> 
> 
> --
> Knute Snortum
> 
> 
> 
> 
> --
> Knute Snortum
> 
> 
> 
> 
> --
> Knute Snortum



Re: Force LilyPond to show same time signature again

2024-04-20 Thread Hajo Baess
What you suggest sounds all so common-sense, but LilyPond still does
not get it...
If I implant "\omit Score.TimeSignature" and "\undo \omit
Score.TimeSignature" into my code instead of the previous commands, I
get this - see screenshot.

But if I do something really basic like:

\version "2.24.2"
\language "deutsch"

\relative c''  {
\time 3/4 c4 c c c2 c4
\time 3/4 c4 c c c2 c4
\omit Score.TimeSignature
\time 3/4 c4 c c c2 c4
\undo \omit Score.TimeSignature
\time 3/4 c4 c c c2 c4
\bar "|."
}

it works as expected. It really seems to have something to do with the
scaled rhythms - that is my guess. 

Unfortunately my exact situation is not covered in the NR - at least I
could not find anything.


Am Samstag, dem 20.04.2024 um 06:01 -0700 schrieb Knute Snortum:
> On Sat, Apr 20, 2024 at 4:17 AM Hajo Baess  wrote:
> 
> > If I do this, I get other unwanted results - see screenshot. The
> > problem is that I am switching back and forth between scaled and
> > non-
> > scaled rhythm. And as you will notice, the 6/4 only appears in the
> > piano staff and  n o t   in the top parts. And the 3/4 also does
> > not
> > appear (although I think it should) in the top part like in bars
> > 195
> > and 197...
> > 
> > Is there no simple way to just toggle "\override
> > Score.TimeSignature.stencil = ##f " ?
> > 
> > 
> Simpler than
> 
>   \override Score.TimeSignature.stencil = ##f
>   \override Score.TimeSignature.stencil = ##t
> 
> ?
> 
> You could use
> 
>   \omit Score.TimeSignature
> 
> instead of
> 
>   \override Score.TimeSignature.stencil = ##f
> 
> and use
> 
>   \undo  \omit Score.TimeSignature
> 
> for
> 
>   \override Score.TimeSignature.stencil = ##t
> 
> If you wanted to shorten it more, you could put this at the top of
> your
> file:
> 
>   stopTimeSignature = \omit Score.TimeSignature
>   startTimeSignature = \undo \omit Score.TimeSignature
> 
> 
> Then you could use
> 
>   \stopTimeSignature  \startTimeSignature
> 
> in your file.
> 
> 
> --
> Knute Snortum



Re: Force LilyPond to show same time signature again

2024-04-20 Thread Hajo Baess
If I do this, I get other unwanted results - see screenshot. The
problem is that I am switching back and forth between scaled and non-
scaled rhythm. And as you will notice, the 6/4 only appears in the
piano staff and  n o t   in the top parts. And the 3/4 also does not
appear (although I think it should) in the top part like in bars 195
and 197...

Is there no simple way to just toggle "\override
Score.TimeSignature.stencil = ##f " ?

Am Samstag, dem 20.04.2024 um 11:41 +0100 schrieb Mark Knoop:
> This line:
> 
> \override Score.TimeSignature.stencil = ##f
> 
> means that the time signature will not be displayed (its stencil is
> set
> to false). Either remove it, or if you need it for some other reason,
> prefix with \once.
> 
> Regards,
> 
> Mark
> 
> At 10:13 on 20 Apr 2024, Hajo Baess wrote:
> > This time  w i t h   screenshot attached - sorry about that...
> > Delete
> > the previous one ;-)
> 
> > Unfortunately this does not work - because I have tried exactly
> > this
> > one, and there is no time signature. I attach a screenshot of the
> > passage. My piece is in 3/4, and in the top part in bar 185, I have
> > to
> > do some rhythmical scaling, whereas the other parts continue in
> > 3/4. I
> > could as well have written triplets, of course, to achieve the same
> > musical result, but I wanted to keep the original 'flavor'.
> > I bar 199, for the top part, I want to revert to the original 3/4,
> > but
> > \time 3/4 does not do the trick. It even does not show a time
> > signature
> > which is different from the previous one, although LilyPond
> > typesets it
> > ok. As you will notice, I have set a (nonsensical) 6/4 signature
> > there
> > in all the parts for testing purposes.
> > There must be some other mechanism involved which prevents the time
> > signature from being indicated, but which one?
> 
> > Here's the top part code for the passage in the screenshot:
> 
> > > d2.
> > > \time 3/4 \set Staff.timeSignatureFraction = 9/8
> > > \scaleDurations 2/3 {
> > > \repeat unfold 3 { f8 ( d a ) }  \repeat unfold 3 { e' ( cis a )
> > > }
> > > \repeat unfold 3 { f'8 ( d a ) }
> > > \repeat unfold 3 { g' ( e c ) } \repeat unfold 3 { a' ( f c ) }
> > > \repeat unfold 3 { g' ( e c ) }
> > > \repeat unfold 3 { f8 ( d a ) }
> > > } 
> > > \override Score.TimeSignature.stencil = ##f \time 3/4 cis4\trill
> > > cis2
> > > \set Staff.timeSignatureFraction = 9/8
> > > \scaleDurations 2/3
> > > \repeat unfold 3 { d8 ( a f ) } \time 3/4 cis'4\trill
> > > cis2
> > > \set Staff.timeSignatureFraction = 9/8
> > > \scaleDurations 2/3 \repeat unfold 3 { d8 ( a f ) }
> > > \time 3/4 e'4 e2 \time 3/4 \set
> > > Staff.timeSignatureFraction
> > > = 9/8
> > > \scaleDurations 2/3
> > > {\repeat unfold 3 { f8 ( c a ) } \repeat unfold 3 { e' (
> > > c g
> > > ) }}
> > > \time 6/4 f8 d' cis4. d8 d2. 
> 
> > Could it have something to do with the scaling applied before?
> 
> 
> > Am Freitag, dem 19.04.2024 um 17:44 -0700 schrieb Knute Snortum:
> > > On Fri, Apr 19, 2024 at 4:31 PM Hajo Baess 
> > > wrote:
> > > 
> > > > Hello all,
> > > > 
> > > > I look for a way to force LilyPond to show the same time
> > > > signature
> > > > again, although there is no change - just as a reminder. I
> > > > could
> > > > not
> > > > find anything in the NR and in the Snippet Repository.
> > > > 
> > > > 
> > > Unless I'm misunderstanding, just repeating the \time should do
> > > it:
> > > 
> > > \version "2.24.3"
> > > \score {
> > >   \new Staff {
> > >     \relative {
> > >   \time 4/4
> > >   \repeat unfold 8 { c'8 } |
> > >   \time 4/4
> > >   \repeat unfold 8 { c8 } |
> > >     }
> > >   }
> > > }
> > > 
> > > 
> > > --
> > > Knute Snortum
> 
> 
> > [2. image/png; Auswahl_081.png]...
> 



Re: Force LilyPond to show same time signature again

2024-04-20 Thread Hajo Baess
This time  w i t h   screenshot attached - sorry about that... Delete
the previous one ;-)

Unfortunately this does not work - because I have tried exactly this
one, and there is no time signature. I attach a screenshot of the
passage. My piece is in 3/4, and in the top part in bar 185, I have to
do some rhythmical scaling, whereas the other parts continue in 3/4. I
could as well have written triplets, of course, to achieve the same
musical result, but I wanted to keep the original 'flavor'.
I bar 199, for the top part, I want to revert to the original 3/4, but
\time 3/4 does not do the trick. It even does not show a time signature
which is different from the previous one, although LilyPond typesets it
ok. As you will notice, I have set a (nonsensical) 6/4 signature there
in all the parts for testing purposes.
There must be some other mechanism involved which prevents the time
signature from being indicated, but which one?

Here's the top part code for the passage in the screenshot:

> d2.
> \time 3/4 \set Staff.timeSignatureFraction = 9/8
> \scaleDurations 2/3 {
> \repeat unfold 3 { f8 ( d a ) }  \repeat unfold 3 { e' ( cis a ) }
> \repeat unfold 3 { f'8 ( d a ) }
> \repeat unfold 3 { g' ( e c ) } \repeat unfold 3 { a' ( f c ) }
> \repeat unfold 3 { g' ( e c ) }
> \repeat unfold 3 { f8 ( d a ) }
> } 
> \override Score.TimeSignature.stencil = ##f \time 3/4 cis4\trill cis2
> \set Staff.timeSignatureFraction = 9/8
> \scaleDurations 2/3
> \repeat unfold 3 { d8 ( a f ) } \time 3/4 cis'4\trill cis2
> \set Staff.timeSignatureFraction = 9/8
> \scaleDurations 2/3 \repeat unfold 3 { d8 ( a f ) }
> \time 3/4 e'4 e2 \time 3/4 \set Staff.timeSignatureFraction
> = 9/8
> \scaleDurations 2/3
> {\repeat unfold 3 { f8 ( c a ) } \repeat unfold 3 { e' ( c g
> ) }}
> \time 6/4 f8 d' cis4. d8 d2. 

Could it have something to do with the scaling applied before?


Am Freitag, dem 19.04.2024 um 17:44 -0700 schrieb Knute Snortum:
> On Fri, Apr 19, 2024 at 4:31 PM Hajo Baess  wrote:
> 
> > Hello all,
> > 
> > I look for a way to force LilyPond to show the same time signature
> > again, although there is no change - just as a reminder. I could
> > not
> > find anything in the NR and in the Snippet Repository.
> > 
> > 
> Unless I'm misunderstanding, just repeating the \time should do it:
> 
> \version "2.24.3"
> \score {
>   \new Staff {
>     \relative {
>   \time 4/4
>   \repeat unfold 8 { c'8 } |
>   \time 4/4
>   \repeat unfold 8 { c8 } |
>     }
>   }
> }
> 
> 
> --
> Knute Snortum




Re: Force LilyPond to show same time signature again

2024-04-20 Thread Hajo Baess
Unfortunately this does not work - because I have tried exactly this
one, and there is no time signature. I attach a screenshot of the
passage. My piece is in 3/4, and in the top part in bar 185, I have to
do some rhythmical scaling, whereas the other parts continue in 3/4. I
could as well have written triplets, of course, to achieve the same
musical result, but I wanted to keep the original 'flavor'.
I bar 199, for the top part, I want to revert to the original 3/4, but
\time 3/4 does not do the trick. It even does not show a time signature
which is different from the previous one, although LilyPond typesets it
ok. As you will notice, I have set a (nonsensical) 6/4 signature there
in all the parts for testing purposes.
There must be some other mechanism involved which prevents the time
signature from being indicated, but which one?

Here's the top part code for the passage in the screenshot:

> d2.
> \time 3/4 \set Staff.timeSignatureFraction = 9/8
> \scaleDurations 2/3 {
> \repeat unfold 3 { f8 ( d a ) }  \repeat unfold 3 { e' ( cis a ) }
> \repeat unfold 3 { f'8 ( d a ) }
> \repeat unfold 3 { g' ( e c ) } \repeat unfold 3 { a' ( f c ) }
> \repeat unfold 3 { g' ( e c ) }
> \repeat unfold 3 { f8 ( d a ) }
>   } 
> \override Score.TimeSignature.stencil = ##f \time 3/4 cis4\trill cis2
> \set Staff.timeSignatureFraction = 9/8
>   \scaleDurations 2/3
>   \repeat unfold 3 { d8 ( a f ) } \time 3/4 cis'4\trill cis2
> \set Staff.timeSignatureFraction = 9/8
>   \scaleDurations 2/3 \repeat unfold 3 { d8 ( a f ) }
>   \time 3/4 e'4 e2 \time 3/4 \set Staff.timeSignatureFraction
> = 9/8
>   \scaleDurations 2/3
>   {\repeat unfold 3 { f8 ( c a ) } \repeat unfold 3 { e' ( c g
> ) }}
>   \time 6/4 f8 d' cis4. d8 d2. 

Could it have something to do with the scaling applied before?


Am Freitag, dem 19.04.2024 um 17:44 -0700 schrieb Knute Snortum:
> On Fri, Apr 19, 2024 at 4:31 PM Hajo Baess  wrote:
> 
> > Hello all,
> > 
> > I look for a way to force LilyPond to show the same time signature
> > again, although there is no change - just as a reminder. I could
> > not
> > find anything in the NR and in the Snippet Repository.
> > 
> > 
> Unless I'm misunderstanding, just repeating the \time should do it:
> 
> \version "2.24.3"
> \score {
>   \new Staff {
>     \relative {
>   \time 4/4
>   \repeat unfold 8 { c'8 } |
>   \time 4/4
>   \repeat unfold 8 { c8 } |
>     }
>   }
> }
> 
> 
> --
> Knute Snortum




Force LilyPond to show same time signature again

2024-04-19 Thread Hajo Baess
Hello all,

I look for a way to force LilyPond to show the same time signature
again, although there is no change - just as a reminder. I could not
find anything in the NR and in the Snippet Repository.

Grateful for any suggestion how to achieve this.



Re: Frescobaldi: Keyboard shortcut for toggling between editor and music view?

2024-02-14 Thread Hajo Baess
I have (just completely accidentally, with a little help from the
Breeze theme color scheme) discovered a keyboard shortcut for switching
back and forth between the editor and the Music View. I think that it
is undocumented, and strange it is, too. Here it is:

 * from editor to Music View: press CTRL+TAB 5 times or until the Music
   View scroll bar is not greyed out any more. In Breeze for example,
   it turns light blue. The editor scroll bar turns grey at the same
   time.
 * from Music View to editor: press CTRL+Shift+TAB 5 times or until the
   editor's scroll bar is no longer greyed out, but Music View's is.

This is a crazy thing, but it seems to work...

No mouse needed.



Am Dienstag, dem 13.02.2024 um 13:24 -0600 schrieb Guy Stalnaker:
> I do not see such a toggle or any system call in the Key Shortcuts 
> preferences that seems relevant. And perhaps that is not surprising -
> Frescobaldi is after all a code editor; that it assumes (!) one would
> always want the code visible makes sense to me.
> 
> Regards
> 
> On 2/12/24 15:36, Hajo Baess wrote:
> > Hello all,
> > 
> > Maybe I am missing it alltogether or it does not exist or it is to
> > hard
> > to find for me:
> > I am looking for a keyboard shortcut in Frescobaldi enabling me to
> > toggle between editor and music view, so I do not have to click
> > with
> > the mouse.
> > 
> > I just can't find it. I have tried all kinds of possible candidates
> > to
> > no avail. Is someone here who happens to know?
> > 
> > Thank you for pointing this out to me...
> > 




Re: Frescobaldi: Keyboard shortcut for toggling between editor and music view?

2024-02-13 Thread Hajo Baess
Maybe I was not clear enough in what I said: Of course the code should
be visible all the time. What I mean is the following:
When you have Frescobaldi open with its split window, there is always
one of the two halves active and reacts to input. Say, you are in the
editor, but want to go to a different page of your doc in the music
view, you always have to click into the Music View half of
Frescobaldi's window in order to activate it, so you can use a keyboard
shortcut there. And when you have done this and want to go back to the
editor, you have to click again into the editor pane to activate that
one for more input.

I am looking for a keyboard shortcut for activating whatever pane I
want to be in for input instead of having to click all the time,
because LilyPond is mostly keyboard work. The mouse (at least with me)
is hardly in use...

Am Dienstag, dem 13.02.2024 um 13:24 -0600 schrieb Guy Stalnaker:
> I do not see such a toggle or any system call in the Key Shortcuts 
> preferences that seems relevant. And perhaps that is not surprising -
> Frescobaldi is after all a code editor; that it assumes (!) one would
> always want the code visible makes sense to me.
> 
> Regards
> 
> On 2/12/24 15:36, Hajo Baess wrote:
> > Hello all,
> > 
> > Maybe I am missing it alltogether or it does not exist or it is to
> > hard
> > to find for me:
> > I am looking for a keyboard shortcut in Frescobaldi enabling me to
> > toggle between editor and music view, so I do not have to click
> > with
> > the mouse.
> > 
> > I just can't find it. I have tried all kinds of possible candidates
> > to
> > no avail. Is someone here who happens to know?
> > 
> > Thank you for pointing this out to me...
> > 




Frescobaldi: Keyboard shortcut for toggling between editor and music view?

2024-02-12 Thread Hajo Baess
Hello all,

Maybe I am missing it alltogether or it does not exist or it is to hard
to find for me:
I am looking for a keyboard shortcut in Frescobaldi enabling me to
toggle between editor and music view, so I do not have to click with
the mouse.

I just can't find it. I have tried all kinds of possible candidates to
no avail. Is someone here who happens to know?

Thank you for pointing this out to me...



Re: Incipit with default noteheads possible?

2024-01-24 Thread Hajo Baess
That 'manual' solution is absolutely good enough for my purpose.
Furthermore it is easy to understand and to modify if necessary. I'll
adopt it for my project.

At any rate: thank you all for your very valuable advice and hints. I
already suspected as well that \incipit is hardcoded to mensural style
without knowing anything about its inner workings. You can assume it,
though, from its reluctance to accept or process any attempts at
changing the result.

Am Mittwoch, dem 24.01.2024 um 22:42 +0100 schrieb Mats Bengtsson:
>  I have to try it. So far, I've used the more manual solution
> available in https://lsr.di.unimi.it/LSR/Item?id=451
>     /Mats
> On 2024-01-24 18:39, YTG 1234 wrote:
>  > betterIncipit = 
> >   #(define-music-function (incipit-music) (ly:music?) 
> >     (_i "Output @var{incipit-music} as an incipit. 
> >   
> >   @var{incipit-music} is typeset within a @code{MensuralStaff} if
> > no other staff-like context is created; the result 
> >   is positioned before the main staff (as part of an
> > @code{InstrumentName} grob) 
> >   to indicate the music's original notation.") 
> >     #{ 
> >       \once \override Staff.InstrumentName.stencil = 
> >     #(lambda (grob) 
> >       (let* ((instrument-name (ly:grob-property grob 'long-
> > text)) 
> >      (align-x (ly:grob-property grob 'self-alignment-X
> > 0)) 
> >      (align-y (ly:grob-property grob 'self-alignment-Y
> > 0))) 
> >       (set! (ly:grob-property grob 'long-text) 
> >     #{ \markup { 
> >       \score 
> >       { 
> >         $(if (member (ly:music-property incipit-music
> > 'context-type) '(ChoirStaff DrumStaff GrandStaff
> > GregorianTranscriptionStaff KievanStaff MensuralStaff OneStaff
> > PetrucciStaff PianoStaff RhythmicStaff Staff StaffGroup
> > StandaloneRhythmStaff TabStaff VaticanaStaff)) 
> >           #{ { $incipit-music } #} 
> >               #{ \new MensuralStaff { $incipit-music } #}) 
> >     \layout { 
> >           $(ly:grob-layout grob) 
> >           \context { 
> >                 \Staff 
> >                 \override InstrumentName.self-alignment-X =
> > #align-x 
> >                 \override InstrumentName.self-alignment-Y =
> > #align-y 
> >                 instrumentName = #instrument-name 
> >               } 
> >       indent-incipit-default = 15\mm 
> >       line-width = #(primitive-eval 
> >     '(or (false-if-exception indent) 
> >       indent-incipit-default)) 
> >       indent = #(primitive-eval 
> >      '(or (false-if-exception (- line-width
> > incipit-width)) 
> >       (* 0.5 line-width))) 
> >       ragged-right = ##f 
> >       ragged-last = ##f 
> >       system-count = 1 
> >     } 
> >       } 
> >       } 
> >     #}) 
> >     (set! (ly:grob-property grob 'self-alignment-Y) #f) 
> >     ;; Do 'self-alignment-X RIGHT only for the first
> > InstrumentName, which 
> >     ;; actually is the incipit. Otherwise self-alignment-X
> > for the 
> >     ;; shortInstrumentName is not longer settable. 
> >     (let ((parts (ly:spanner-broken-into (ly:grob-original
> > grob 
> >       (if (and (pair? parts) (equal? grob (car parts))) 
> >       (ly:grob-set-property! grob 'self-alignment-X
> > RIGHT))) 
> >     (system-start-text::print grob))) 
> >     #} 
> >   ) 
>  
> I have to try it. So far, I've used the more manual solution
> available in https://lsr.di.unimi.it/LSR/Item?id=451
>     /Mats
> On 2024-01-24 18:39, YTG 1234 wrote:
>  
> > betterIncipit = 
> >  #(define-music-function (incipit-music) (ly:music?) 
> >    (_i "Output @var{incipit-music} as an incipit. 
> >  
> >  @var{incipit-music} is typeset within a @code{MensuralStaff} if no
> > other staff-like context is created; the result 
> >  is positioned before the main staff (as part of an
> > @code{InstrumentName} grob) 
> >  to indicate the music's original notation.") 
> >    #{ 
> >  \once \override Staff.InstrumentName.stencil = 
> >    #(lambda (grob) 
> >  (let* ((instrument-name (ly:grob-property grob 'long-
> > text)) 
> >     (align-x (ly:grob-property grob 'self-alignment-X
> > 0)) 
> >     (align-y (ly:grob-property grob 'self-alignment-Y
> > 0))) 
> >  (set! (ly:grob-property grob 'long-text) 
> >    #{ \markup { 
> >  \score 
> >  { 
> >        $(if (member (ly:music-property incipit-music
> > 'context-type) '(ChoirStaff DrumStaff GrandStaff
> > GregorianTranscriptionStaff KievanStaff MensuralStaff OneStaff
> > PetrucciStaff PianoStaff RhythmicStaff Staff StaffGroup
> > StandaloneRhythmStaff TabStaff VaticanaStaff)) 
> >          #{ { 

Re: Incipit with default noteheads possible?

2024-01-24 Thread Hajo Baess
This works for the note heads, but if there happen to be accidentals
around (in my project this is the case), they remain mensural style. Is
there another override for this, too?

Am Mittwoch, dem 24.01.2024 um 16:14 +0200 schrieb YTG 1234:
> > I have tried an override ( \override
> > Staff.NoteHead.style = #'default )
> 
> Note heads are drawn in Voice, so you can just omit the context name.
> \override NoteHead.style = #'default
> 
> The more fundamental issue here, though, is that \incipit is
> hardcoded 
> to create a MensuralStaff context. Does anyone know how to replicate
> its 
> effect with a normal Staff, short of just substituting in its source
> code?
> 




Incipit with default noteheads possible?

2024-01-22 Thread Hajo Baess
Hello all,

I am typesetting a piece where the violin plays in a different tuning.
Of course you have to indicate the tuning before the music starts. I
would like to implement this with the \incipit command, if possible,
but there is one downside: you get your notes in the incipit with
mensural noteheads. I have tried an override ( \override
Staff.NoteHead.style = #'default ), but this does not seem to work.

Here is my code example:

\version "2.24.2"
\language "deutsch"

Incipit = \relative c'' {
\clef treble \time 4/4
\omit Staff.TimeSignature
\hide Stem
%\mark "A D FIS CIS"
\override Staff.NoteHead.style = #'default
< a, d fis cis' >

}

noten =  \relative c'' {
\clef treble \key f \major \time 4/4
c4 d e f \bar "|."
}

\score {

\new Staff
<<
\incipit \Incipit
\set Staff.instrumentName = "Violino discordato"
\noten
>>


\layout {
indent = 4\cm
incipit-width = 1\cm
}
}

Do note-head styles just not work with \incipit, did I miss something,
or is there a way to obtain the desired result?

Any suggestions are greatly appreciated...



Re: Can I define custom bar lengths in LilyPond?

2024-01-16 Thread Hajo Baess
Thank you so much for your answer. I was talking about the dimensional
width of a bar. The situation in my "fat" bar is complicated, because
one singer in a recit enters while the other one is on her last note.
So I had the problem of accommodating the lyrics and moving them
around, so they are well aligned on the sheet. And because with
LilyPond's standard behaviour there still was not enough space, I
inserted a line break after the "fat" bar. That way I have forced
LilyPond to only put two bars in the line instead of three. The result
looks OK, but I hope there is a much more elegant way to achieve this.

Here is the code snippet (hope this is enough for evaluation):

... c4 ( h8.\trill ) c16 
<<
  { r8 \clef bass \tempo "Recitativo" \stemDown \autoBeamOff  
  \once \override TextScript.padding = #1.7 
  g,8^\markup {  "Basso" }_\markup  \fontsize #1.5 
  { \halign #-0.9 "Auch  indem" } g e  \break}
\\
 { \once \override TextScript.padding = #1.7 
   c''2_\markup \fontsize #1.5 { \halign #-0.7 "Stamm!" } }
>> 
  \appoggiatura d,,8 cis4 ...

I also attach a screenshot.
Thank you also for mentioning the \newSpacingSection command, which I
did not know. I have looked in the documentation, but the example there
is about a different time signature again. In my example it does not
change, and I wonder how I can take advantage of the command.
SpacingSpanner? uniform-stretching? But how exactly? For my LilyPond
knowledge at the moment this goes too deep under the hood...

Am Dienstag, dem 16.01.2024 um 09:50 -0800 schrieb Aaron Hill via
LilyPond user discussion:
> On 2024-01-16 8:06 am, Hajo Baess wrote:
> > Hello LilyPond users,
> > 
> > I wonder if there is a possibility to define a custom bar length,
> > thus
> > for once cancelling LilyPond's automatic insertion of bar lines.
> > 
> > I have a complicated measure here with quite a bit of markup to
> > accommodate in one bar. I have worked out a solution which is maybe
> > good enough, but it contains lots of tweaks in order to squeeze
> > everything into the automatically assigned bar length.
> > 
> > If I could define my own bar lengths, I would get more space in the
> > bar, so I hope at least. My search in the documentation did not
> > yield a
> > result for me, but maybe I did not look in the right places.
> > 
> > Hopefully someone here can troubleshoot me.
> > Any help is much appreciated.
> 
> I suspect we are going to need more information as there are at least
> two interpretations of "length" here.
> 
> This is why we highly recommend including MWEs (minimum working 
> examples) with questions, as this gives us a common starting point 
> without having to make potentially derailing guesses.
> 
> 
> 
> Length interpretation one: Metrical length (i.e. number of beats in a
> bar)
> 
> If you need to momentarily step away from the defined time signature,
> the easiest option I find is to use a cadenza--a section of music
> that 
> is not bound by the time signature.  Begin the section with
> \cadenzaOn, 
> cram whatever notes you want, and then end the section with
> \cadenzaOff 
> to resume the original time signature.
> 
> NOTE: LilyPond will not attempt to subdivide a cadenza on its own for
> the purposes of line breaking.  You can of course provide hints using
> \bar "" as needed.
> 
> For more information, see: NR 1.2.3 - Displaying Rhythms; Unmetered 
> Music
> https://lilypond.org/doc/v2.24/Documentation/notation/displaying-rhythms#unmetered-music
> 
> 
> 
> Length interpretation two: Dimensional width (i.e. physical space on
> the 
> paper)
> 
> LilyPond's spacing engine tries to keep things unified across the
> music, 
> so notes should look consistently spaced throughout the piece.  You
> can 
> define a new "spacing section" within your score with the aptly named
> \newSpacingSection command.  Each use of this command will break up
> the 
> larger score into chunks that the spacing engine will handle 
> independently.  There are several context properties that affect note
> spacing, and these can be adjusted within each spacing section as 
> desired.
> 
> For your scenario of a measure that just needs to be wider than
> everyone 
> else, you would at a minimum need to start a new spacing section
> coming 
> into the measure and then start yet another section for the
> subsequent 
> measure--a total of three sections: one before, one for the "fat" 
> measure, and one after.
> 
> For more information, see: NR 4.5.2 - New Spacing Section
> https://lilypond.org/doc/v2.24/Documentation/notation/new-spacing-section
> 
> 
> 
> If you are talking about something else entirely, please see about 
> providing a brief example of what you have tried.
> 
> 
> -- Aaron Hill
> 



Can I define custom bar lengths in LilyPond?

2024-01-16 Thread Hajo Baess
Hello LilyPond users,

I wonder if there is a possibility to define a custom bar length, thus
for once cancelling LilyPond's automatic insertion of bar lines.

I have a complicated measure here with quite a bit of markup to
accommodate in one bar. I have worked out a solution which is maybe
good enough, but it contains lots of tweaks in order to squeeze
everything into the automatically assigned bar length.

If I could define my own bar lengths, I would get more space in the
bar, so I hope at least. My search in the documentation did not yield a
result for me, but maybe I did not look in the right places.

Hopefully someone here can troubleshoot me.
Any help is much appreciated.



Define custom bar length

2024-01-16 Thread Hajo Baess




How to move an ornament vertically

2024-01-02 Thread Hajo Baess
Dear all,

I wonder how you can "talk" LilyPond into moving a dashPlus symbol
above a slur. Without any tweaking it always puts the dashPlus under a
slur, whereas if you replace the dashPlus by a \trill command, the
trill symbol is always placed above the slur.
If I move around the slur like this:

\override Slur.positions = #'(2 . 2)

there is a collision between the beginning of the slur and the
dashPlus. I am sure there is a way to fix this, but I have not been
able to find it.

Hopefully there will be someone here who can show me the solution.
Thank you in advance for taking the time...

Hajo



Re: Obscure message in Frescobaldi

2023-09-27 Thread Hajo Baess
Thank you for your answer, but I already put that question on Github on
the Frescobaldi page, but the question has not been answered there
either. So I had the idea to ask here...


Am Mittwoch, dem 27.09.2023 um 13:35 +0200 schrieb Simon Albrecht:
> Hello Hajo,
> 
> I can’t answer your question, but I can say that the better place to
> ask 
> it would be either the Issue tracker in the Frescobaldi project on 
> Github, or via the contact adress included in Frescobaldi at Help-
> >About.
> 
> Hope that helps!
> Simon
> 
> On 26.09.23 21:51, Hajo Baess wrote:
> > This is not about a Lilypond problem, strictly speaking, but it is
> > related indirectly, and since here there are very many LilyPond
> > users
> > around here, I also hope to address at least a couple of
> > Frescobaldi
> > users here with an unanswered question, hoping that someone can
> > solve
> > this for me:
> > I am localising Frescobaldi, and I am stuck with an obscure message
> > which I have never seen using it. It says:
> > 
> > Clear Grab
> > 
> > Since it is hard to translate something you don't understand: what
> > is
> > this about? What is the context? What has been grabbed and can be
> > cleared?
> > 
> > The message entry can be found in the messages.py file in the i18n
> > folder of Frescobaldi:
> > 
> > > _("QShortcut", "Clear Grab")
> > Thanks a lot for any suggestions to help me understand...
> > 
> 
> 




Obscure message in Frescobaldi

2023-09-26 Thread Hajo Baess
This is not about a Lilypond problem, strictly speaking, but it is
related indirectly, and since here there are very many LilyPond users
around here, I also hope to address at least a couple of Frescobaldi
users here with an unanswered question, hoping that someone can solve
this for me:
I am localising Frescobaldi, and I am stuck with an obscure message
which I have never seen using it. It says:

Clear Grab

Since it is hard to translate something you don't understand: what is
this about? What is the context? What has been grabbed and can be
cleared? 

The message entry can be found in the messages.py file in the i18n
folder of Frescobaldi:

> _("QShortcut", "Clear Grab")

Thanks a lot for any suggestions to help me understand...



Re: Subject: Re: Lilypond in Termux (Android)

2023-02-03 Thread Hajo Baess
Thank you very much for this step-by-step guide. I followed the
instructions, and now I can also write Lily files on my mobile. Not the
most comfortable thing, but very useful for little things on the fly
anyway! With a Bluetooth keyboard it's certainly much better, but for a
first try I really used my built-in mobile keyboard, and that was a bit
awkward. I wrote something small, it compiled allright, and I even
could print it on my wifi printer.

Cool thing! Maybe I will find a better text editor, but even nano is
available in Termux. For a long-time Linux user it makes you really
feel at home ;-)


Am Freitag, dem 03.02.2023 um 21:25 +0100 schrieb gmail:
> Hi, I tried the tips given by Martin Tarenskeen and thought that a
> small 
> sample guide may be useful for other users.
> 
> Open PlayStore > search app Termux >
> Open the terminal Termux and write: pkg install guile
> 
> Then write: pkg install lilypond
> LilyPond 2.24.0 will be installed
> 
> Create a new directory: mkdir lilypond2.24
> Create a new file: touch file1.ly
> 
> The directory where Termux put folder and file created is: data 
> /data/com.termux/files/home
> but it is not visible from android file manager.
> 
> Open PlayStore and download Material Files and start it, give all 
> permissions.
> Click the 3 dots at the top of dx to do "Add Storage > External
> Storage".
> 
> At this point the Termux folder appears. Open it and manipulate the 
> files. Once you open the folder "LilyPond2.24" do "Use this folder",
> and 
> from now on the folder path will appear in the side menu of Material
> Files.
> 
> Open the previously created file from here file1.ly and fill in the 
> lilypond code to compose the sheet music and save it.
> 
>  From Termux terminal go to the director lilypond2.24 where is
> located 
> file.ly, then compile it from terminal: $ lilypond file.ly
> Output a pdf in the same folder lilypond2.24 with the compiled sheet
> music.
> 
> I tested and it works.




Different time signatures on staves bug?

2022-10-31 Thread Hajo Baess
Hello all,

I need to typeset a lied (voice/piano) where temporarily the time
signatures change from 4/4 for both parts to 2/4 for the voice and to
6/8 for the piano and back to 4/4 again.
In the NR there is a nice example how to achieve this with equal
measure lenghts for the different time signatures.

I have tried to apply this model to my use case, but something does not
work as expected. The problem shows when you do not have have all the
same values in your last bar. In that case Lilypond only accepts less
than 6 crotchets there. Whatever I have tried with 

\set Staff.timeSignatureFraction = x/x

did not work, and I have no idea what is wrong here. To make things
worse: when I fiddle with the NR example and add a line with not all
the same values in 9/8, the same thing happens, too (see the added
third line there), and it even reacts to markup.

I hope that it is not a bug, but that I may have got something wrong.
But if it is one, the example is unusable as a global model.

Could someone here, please, with more experience than I have, help me?
Otherwise I am stuck with my project for the moment... I attach a
minimal example.

Thank you very much in advance
%hier ist irgendwo der Wurm drin: es funktioniert nur mit gleichen Notenwerten im 6/8.
\version "2.22.2"
\paper {
  indent = 0\mm
}
\markup { What goes wrong in the 6/8 line, when in a bar there are not only the same values? (no error during  }
\markup {  compilation. Why does Lilypond only accept a quaver on the second beat in the second bar):}
\relative <<
  \new Staff {
\time 2/4
c'4. c8  |
c4 c16 c c c  | 
c8 c c4 \bar "|."
  }
  \new Staff {
\time 2/4
\set Staff.timeSignatureFraction = 6/8
\scaleDurations 2/3
\repeat unfold 4 { c16[ c c c c c] } c8 c c \repeat unfold 6 {c16}\bar "|."
  }

>>
\markup { What I want to do: }
\relative c'
<<
  \new Staff {
\time 4/4
c'4 c c c | \bar "||"
\time 2/4
c4 c  |
R1*2/4  |\bar "||"
\time 4/4
c4 c c c | \bar "|."
  }
  \new PianoStaff
  <<
\new Staff {
  \time 4/4
  \repeat unfold 8 {c,8}
  \time 2/4
  \set Staff.timeSignatureFraction = 6/8
  \scaleDurations 2/3
  \repeat unfold 4 { c16[ c c c c c] }  \bar "||"
  \set Staff.timeSignatureFraction = 4/4
  \scaleDurations 2/3
  \time 4/4
  \repeat unfold 4 {c8} c8 c16 c c8 c16 c
}
\new Staff {
  \clef bass \time 4/4
  \repeat unfold 4 {c,,4}
  \time 2/4
  \set Staff.timeSignatureFraction = 6/8
  \scaleDurations 2/3
  \repeat unfold 4 { c16[ c c c c c] }  \bar "||"
  \time 4/4
  \set Staff.timeSignatureFraction = 4/4
  \scaleDurations 4/4
  \repeat unfold 2 {c4} c4. c8
}
  >>
>>
\markup { Example rom the NR: }
\relative <<
\new Staff {
\time 3/4
c'4 c c |
c4 c c |
}
\new Staff {
\time 3/4
\set Staff.timeSignatureFraction = 9/8
\scaleDurations 2/3
\repeat unfold 6 { c8[ c c] }
}
\new Staff {
\time 3/4
\set Staff.timeSignatureFraction = 9/8
\scaleDurations 2/3
c8^\markup { The line below has been added to show that maybe there is a bug } c c \repeat unfold 4 { c8[ c c] } c4 d8
}
\new Staff {
\time 3/4
\set Staff.timeSignatureFraction = 10/8
\scaleDurations 3/5 {
\repeat unfold 2 { c8[ c c] }
\repeat unfold 2 { c8[ c] } |
c4. c \tuplet 3/2 { c8[ c c] } c4
}
}
>>


tempo marks

2008-12-27 Thread Hajo Baess
hello out there,

I am a LilyPond novice and just getting familiar with it. 
But one question is there which does not seem to 
be answered in a satisfactory way:

How do I insert a tempo indication such as Allegro, 
Adagio and the like above the beginning of the staff?

I'd be very grateful if anybody could show me how this #
can be done.


Hajo



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user