Re: sheet music

[Michael Gerdau]

Hi Tyler,

i’m no musician, but am trying to provide sheet music for the violinist 
to play at our wedding.


is it possible to transcribe this song into sheet music with your software?


Do you mean the keyboard ostinato motiv?
Chords an lyrics you should easily find on the internet.

Anyway, here's the keyboard motiv. Might have to be transposed.

- snip - snip - snip - snip - snip - snip -
\version "2.25.13"

\paper {
  indent = 0
}

\header {
  title = "Kim Smoltz"
  subtitle = \markup \override-lines #'(baseline-skip . 2.5) {
\column \center-align {
  "from the „Mollusk Sessions“"
}
  }
  composer = \markup \override-lines #'(baseline-skip . 2.5) {
\column \right-align {
  %"Ween, 1995"
  "Ween"
}
  }
}

global = {
  \key des \major
  \time 4/4
  \partial 2
  \accidentalStyle modern
}

keyboard = \relative f' {
  \global
  \repeat volta 2 {
r8 ges8 as bes~ |
bes8 as  ges e~  e8 es  e8 ges~ |
ges8 e  es des~  des8 b  des8 es~ |
es8 des  b bes~  bes8 as  bes8 b~ |
b2
  }
}

\score {
  \keyboard
  \layout {}
  \midi {
\tempo 4=108
  }
}
- snip - snip - snip - snip - snip - snip -
--
 Michael Gerdau   email: m...@qata.de
 GPG-keys available on request or at public keyserver


Kim-Smoltz-Ween.pdf
Description: Adobe PDF document

Re: Problems with lilypond-invoke-editor

[Ben Bradshaw]

Well I fixed having multiple lilyponds installed, and at first I thought it
worked. Zathura and xpdf at least work when I open them separately. I guess
it's a minor annoyance, but if I open zathura from the C-c C-c part of
emacs, then it doesn't work and I get those errors. I have no clue why that
would make a difference, but it seems to be the case. Open the file in a
viewer separately and point and click works just fine. Use the lilypond
command view and it doesn't. I guess I haven't tried to see if other pdf
viewers work from the command menu, but it seems like it wouldn't be a
zathura problem.

On Sun, Apr 7, 2024 at 10:44 AM David Wright 
wrote:

> On Fri 05 Apr 2024 at 20:43:01 (-0600), Ben Bradshaw wrote:
> > I've been using frescobaldi mostly because I like the point and click
> > functionality. I just discovered today that you can configure that to
> work
> > with other PDF viewers and editors, which I would like to do, since I
> keep
> > trying to use emacs bindings inside frescobaldi
> > Anyways, I thought that I had everything figured out. But when I try and
> > click I get some stuff showing up in an emacs buffer.
> >
> > Traceback (most recent call last):
> >   File "/usr/local/bin/lilypond-invoke-editor", line 122, in 
> > editor_commands = [list(map(replace_template, cmd)) for cmd in
> > editor_commands]
> >
> > ^
> >   File "/usr/local/bin/lilypond-invoke-editor", line 122, in 
> > editor_commands = [list(map(replace_template, cmd)) for cmd in
> > editor_commands]
> >
> >   File "/usr/local/bin/lilypond-invoke-editor", line 79, in
> replace_template
> > return template % {
> >
> > ValueError: unsupported format character ':' (0x3a) at index 25
> >
> > Is this a problem with the program or my config? I'm using arch linux,
> > herbstluftwm window manager (followed the settings for GNOME 3 to get a
> > desktop entry, otherwise it would only launch firefox), zathura as PDF
> > viewer, emacs as LYEDITOR.
> >
> > Any help would be greatly appreciated so I can stop doing C-x C-s every
> > time I want to save!
>
> I'm not sure why you have /usr/local/bin/ occurring in your error
> messages as I don't see any string "local/" on the page:
>
>   https://archlinux.org/packages/extra/x86_64/lilypond/files/
>
> Is there any possibility that you have multiple versions of LP
> installed, and that one version is calling another?
>
> BTW you can bisect the problem and test lilypond-invoke-editor
> separately at the command line just by typing:
>
>   $ lilypond-invoke-editor textedit://:LL:CC:CC
>
>  is a .ly file, LL a line number, CC a column number
> (actual numbers not important), as in:
>
>   $ lilypond-invoke-editor textedit:///tmp/blue.ly:50:10:10
>
> Either of:
>
>   $ type  lilypond-invoke-editor
>   $ which lilypond-invoke-editor
>
> will tell you which executable is being run. But if your Gnome3
> settings include a path for that executable, you obviously need
> to test it with that path.
>
> Cheers,
> David.
>

sheet music

[Tyler Horn]

hi,

i’m no musician, but am trying to provide sheet music for the violinist to play 
at our wedding.

is it possible to transcribe this song into sheet music with your software?

if so, can you give a cost estimate?

thanks!

tyler

https://www.youtube.com/watch?v=K65dRRa3GoM_channel=destr100 

Re: nested beaming

[Carl Sorensen]

On Wed, Apr 10, 2024 at 2:02 PM Hans Åberg  wrote:

>
>
> There is actually one example of a naturally occurring meter, meaning it
> is used regularly, where such a sub-beaming might be useful, namely, a form
> of the Čoček in 9/8, 9 = 2+2+2+3, where 3 = 1+2. I wrote it as 2+2+2+1+2,
> but it would be nice to write it as 2+2+2+(1+2).
>
> If I write
>   \time 9/8
>   \set beatStructure = 2,2,2,3
>   \set subdivideBeams = ##t
> then it ends up with all 2 = 1+1, and 3 = 1+1+1.
>
> So such examples may occur even if there is not a composer trying to do
> something special.


So in the following, I think I get what you call 2+2+2+3, but unfortunately
I don't get 3 = 1+2.  Do you agree with this statement?

I have made it a little better, because the 2 are all 2, but the three is
just 3 (not 1+2)

\version "2.25.11"
{
   \time 9/8
   \set beatStructure =  #'(2 2 2 3)
   \set subdivideBeams = ##t
   \set minimumBeamSubdivisionInterval = \musicLength 4
   \repeat unfold 18 a'16
}

Carl

Re: nested beaming

[Hans Åberg]

> On 10 Apr 2024, at 20:15, Carl Sorensen  wrote:
> 
> Forwarding to keep on list.
> 
> On Wed, Apr 10, 2024 at 11:35 AM Hans Åberg  wrote:
> 
> > On 10 Apr 2024, at 19:00, Carl Sorensen  wrote:
> > 
> > On Wed, Apr 10, 2024 at 10:22 AM Hans Åberg  wrote:
> > 
> > > So is the issue that you would like to have the final [2 3] beamed with a 
> > > pair of beamed 16th notes joined to a trio of beamed sixteenth notes by a 
> > > single beam?
> > 
> > Yes.
> > 
> > This works out of the box now, as 4+5 with subdivisions and 4+3 with 
> > subdivisions
> > 
> > \version "2.25.11"
> > {
> >\time 9/16
> >\set beatStructure =  #'(4 5)
> >\set subdivideBeams = ##t
> >\repeat unfold 9 a'16
> >
> >\time 7/16
> >\set beatStructure = 4,3
> >\repeat unfold 7 a'16
> > }
> 
> This works for the 9=(2+2)+(2+3); I attach a file that compiles, in case you 
> want to check. I need to check the 7/16 later. One could also have the 3 in 
> other places. like 9 = (2+2)+(3+2) or (3+2)+(2+2). They exist in Turkey and 
> Macedonia in slower forms without the sub-beaming, but in theory, it is 
> possible.
> 
> I think that it will not work if you want to subdivide with the 3 in the 
> first position.  I can imagine that there could be some sort of flag that 
> would allow it to work correctly with the 3 in the first position, but that 
> will require some extra development.  If you think it's important, I could 
> ping Jason Yip (who did the new autobeam functionality) to see if he has any 
> ideas about it.

There is actually one example of a naturally occurring meter, meaning it is 
used regularly, where such a sub-beaming might be useful, namely, a form of the 
Čoček in 9/8, 9 = 2+2+2+3, where 3 = 1+2. I wrote it as 2+2+2+1+2, but it would 
be nice to write it as 2+2+2+(1+2).

If I write
  \time 9/8
  \set beatStructure = 2,2,2,3
  \set subdivideBeams = ##t
then it ends up with all 2 = 1+1, and 3 = 1+1+1.

So such examples may occur even if there is not a composer trying to do 
something special.

Re: nested beaming

[Carl Sorensen]

[Adding back to list]

On Wed, Apr 10, 2024 at 9:23 AM Paul Scott  wrote:

> Version 2.25.14
>
> Are there parameters to change?  It would seem that there would several
> possibilities even though I got the one I wanted this time.
>
> Paul
>
>
> You can read about the parameters in the 2.25 Notation Reference:
https://lilypond.org/doc/v2.25/Documentation/notation/setting-automatic-beam-behavior

See the selected snippet Subdividing Beams

Carl

Re: nested beaming

[Carl Sorensen]

Forwarding to keep on list.

On Wed, Apr 10, 2024 at 11:35 AM Hans Åberg  wrote:

>
> > On 10 Apr 2024, at 19:00, Carl Sorensen 
> wrote:
> >
> > On Wed, Apr 10, 2024 at 10:22 AM Hans Åberg  wrote:
> >
> > > So is the issue that you would like to have the final [2 3] beamed
> with a pair of beamed 16th notes joined to a trio of beamed sixteenth notes
> by a single beam?
> >
> > Yes.
> >
> > This works out of the box now, as 4+5 with subdivisions and 4+3 with
> subdivisions
> >
> > \version "2.25.11"
> > {
> >\time 9/16
> >\set beatStructure =  #'(4 5)
> >\set subdivideBeams = ##t
> >\repeat unfold 9 a'16
> >
> >\time 7/16
> >\set beatStructure = 4,3
> >\repeat unfold 7 a'16
> > }
>
> This works for the 9=(2+2)+(2+3); I attach a file that compiles, in case
> you want to check. I need to check the 7/16 later. One could also have the
> 3 in other places. like 9 = (2+2)+(3+2) or (3+2)+(2+2). They exist in
> Turkey and Macedonia in slower forms without the sub-beaming, but in
> theory, it is possible.
>

I think that it will not work if you want to subdivide with the 3 in the
first position.  I can imagine that there could be some sort of flag that
would allow it to work correctly with the 3 in the first position, but that
will require some extra development.  If you think it's important, I could
ping Jason Yip (who did the new autobeam functionality) to see if he has
any ideas about it.

Thanks,

Carl

Re: nested beaming

[Hans Åberg]

> On 10 Apr 2024, at 17:13, Carl Sorensen  wrote:
> 
>> On Tue, Apr 9, 2024 at 10:23 AM Hans Åberg  wrote:
>> 
>>> On 8 Apr 2024, at 18:46, Simon Albrecht  wrote:
>>> 
>>> On 08.04.24 18:22, Paul Scott wrote:
 Many years ago I could nest square brackets in Lilypond. How can I write 
 this now incorrect code:
 
 a16[[ 16 16] 16[ 16 16]]  i.e. two groups of 3 beamed 16th notes joined by 
 a single beam.
>>> 
>>> The question is: what is the context and why do you want this?
>> 
>> In the past, it was possible to give 9/16 the beat structure [[2 2] [2 3]], 
>> as a 2/4 with an extra 1/16 at the end, like in the Bulgarian Daichovo, but 
>> currently it is only possible with [4 2 3] as in:
>> \time 9/16
>> \set beatStructure = #'(4 2 3)
>> Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read.
>> 
>>> Normally, this is called subdividing beams and there is a context property 
>>> to turn it on. This is explained in the NR at Rhythms -> Beams -> Setting 
>>> automatic beam behaviour (or similar). There have recently been significant 
>>> improvements to how LilyPond handles this, but IIRC it’s not fully ‘there’ 
>>> yet and in some situations manual intervention is needed besides defining 
>>> baseMoment etc.
>> 
>> But this has not yet been implemented?
> 
> So is the issue that you would like to have the final [2 3] beamed with a 
> pair of beamed 16th notes joined to a trio of beamed sixteenth notes by a 
> single beam?

Yes.

>  I could see that such a notation might be easy to read, but it violates the 
> mathematical beaming convention since the two subgroups joined by the single 
> beam are not each 1/8 in duration.  I'm not saying this notation is 
> incorrect; I'm just saying that to implement it we would need to bypass the 
> normal convention

The meter is like 2/4 but with one extra 1/16 on the last 1/8 metric sub-accent 
(or sub-beat), so the final [2 3] should be beamed together to properly express 
the relationship: If using 4+2+3, it suggests that the two last metric beats 
are equal. Likewise, (2+2)+(3+2) is a different meter, and 4+5 with no 
sub-beaming on the 5 would not make clear the metric beat structure.

One can do the opposite, take away 1/16 on the last beat, 7 = (2+2)+3, as in 
the Bulgarian rachenitsa. Then I use 7 = 4+3, which looks fine, but it does not 
show the sub-beat in the 4 = 2+2. Using 7 = 2+2+3 would be wrong, because that 
suggests the beats between the last 2 and 3 are about equal.

Re: nested beaming

[Hans Åberg]

> On 10 Apr 2024, at 16:54, Carl Sorensen  wrote:
> 
> On Tue, Apr 9, 2024 at 10:23 AM Hans Åberg  wrote:
> 
> In the past, it was possible to give 9/16 the beat structure [[2 2] [2 3]], 
> as a 2/4 with an extra 1/16 at the end, like in the Bulgarian Daichovo, but 
> currently it is only possible with [4 2 3] as in:
>  \time 9/16
>  \set beatStructure = #'(4 2 3)
> Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read.
> 
> Can you tell me a version where you could do this, and provide some sample 
> code that uses it?

It was so long time ago that I do not remember. The new interface is much 
simpler, so I felt it was not a crucial point. One sees sheet music with the 
beaming division 9 = 4+2+3. Bela Bartok used this meter, and it may have that 
latter written meter and beaming.

Re: nested beaming

[Carl Sorensen]

On Tue, Apr 9, 2024 at 10:23 AM Hans Åberg  wrote:

>
> > On 8 Apr 2024, at 18:46, Simon Albrecht  wrote:
> >
> > On 08.04.24 18:22, Paul Scott wrote:
> >> Many years ago I could nest square brackets in Lilypond. How can I
> write this now incorrect code:
> >>
> >> a16[[ 16 16] 16[ 16 16]]  i.e. two groups of 3 beamed 16th notes joined
> by a single beam.
> >
> > The question is: what is the context and why do you want this?
>
> In the past, it was possible to give 9/16 the beat structure [[2 2] [2
> 3]], as a 2/4 with an extra 1/16 at the end, like in the Bulgarian
> Daichovo, but currently it is only possible with [4 2 3] as in:
>  \time 9/16
>  \set beatStructure = #'(4 2 3)
> Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read.
>
> > Normally, this is called subdividing beams and there is a context
> property to turn it on. This is explained in the NR at Rhythms -> Beams ->
> Setting automatic beam behaviour (or similar). There have recently been
> significant improvements to how LilyPond handles this, but IIRC it’s not
> fully ‘there’ yet and in some situations manual intervention is needed
> besides defining baseMoment etc.
>
> But this has not yet been implemented?
>

So is the issue that you would like to have the final [2 3] beamed with a
pair of beamed 16th notes joined to a trio of beamed sixteenth notes by a
single beam?  I could see that such a notation might be easy to read, but
it violates the mathematical beaming convention since the two subgroups
joined by the single beam are not each 1/8 in duration.  I'm not saying
this notation is incorrect; I'm just saying that to implement it we would
need to bypass the normal convention

Thanks,

Carl

Re: nested beaming

[Carl Sorensen]

On Tue, Apr 9, 2024 at 10:23 AM Hans Åberg  wrote:

>
>
>
> In the past, it was possible to give 9/16 the beat structure [[2 2] [2
> 3]], as a 2/4 with an extra 1/16 at the end, like in the Bulgarian
> Daichovo, but currently it is only possible with [4 2 3] as in:
>  \time 9/16
>  \set beatStructure = #'(4 2 3)
> Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read.
>

Can you tell me a version where you could do this, and provide some sample
code that uses it?

Thanks,

Carl

Re: \epsfile and SVG output

[Alex Harker]

Thanks - the idea about post-processing is particularly interesting.

In the long run it would be great to be able to add SVGs directly, but I 
suspect that would be too big a dev job (in terms of understanding the lily 
pond codebase) for me to get into at the moment.

Alex


> On 10 Apr 2024, at 15:03, Jean Abou Samra  wrote:
> 
>> Many thanks for the clarification that this approach will not work and
>> alternative suggestions.
>> 
>> I presume that /image will only include PNGs in a SVG output and not EPS (the
>> documentation reads a little unclearly on this as the section on backends is
>> elided with comments on coloured backgrounds)?
> 
> 
> In fact, PNG in \image works in all output formats/backends
> (it is only if you want transparency that it has limitations,
> but the default is to add a white background, so there is no
> limitation in the default settings).
> 
> 
>> For context I am using SVG output because my display target is a custom IOS
>> app that uses skia as a backend. SKIA can be used to display SVGs easily
>> within the context that I am working. SKIA does have a pdf backend but it
>> isn’t exposed directly by the framework I’m using.
>> 
>> The reason to use EPS is that I want to bring in vector graphics made in
>> Inkscape using a graphics tablet. It is a little frustrating that I can’t get
>> these vector graphics into Lilypond SVG output, as they are basically SVG in
>> the first place, but from what I understand so far that isn’t possible.
> 
> 
> Yes, unfortunately the SVG backend isn't as well-developed as the
> other backends and in particular doesn't support including SVG
> (which it could easily do). The Cairo backend also supports outputting
> SVG, but doesn't support including SVG either.
> 
> 
>> Therefore, if I understand correctly my current options would be:
>> 
>> - render to pdf and work on a system to render pdfs within the framework I’m
>> using (this is probably possible, but involves lots of unknowns)
>> - rasterise the images and display as PNG, thus include the rasterised 
>> version
>> in the SVG (not optimal in terms of file size or speed of render, but
>> possible)
>> - work on a system to convert SVG paths to Lilypond/Scheme paths in order to
>> be able to draw in a vector within Lilypond to any backend.
> 
> 
> That sounds right. Alternatively, you might be able to add a tag
> with a specific id using the output-attributes property, then post-process
> the file to replace the tag with that id with your custom content or
> something like that.
> 

Re: \epsfile and SVG output

[Henning Hraban Ramm]

Am 10.04.24 um 15:50 schrieb Alex Harker:
Many thanks for the clarification that this approach will not work and 
alternative suggestions.


I presume that /image will only include PNGs in a SVG output and not EPS 
(the documentation reads a little unclearly on this as the section on 
backends is elided with comments on coloured backgrounds)?


For context I am using SVG output because my display target is a custom 
IOS app that uses skia as a backend. SKIA can be used to display SVGs 
easily within the context that I am working. SKIA does have a pdf 
backend but it isn’t exposed directly by the framework I’m using.


The reason to use EPS is that I want to bring in vector graphics made in 
Inkscape using a graphics tablet. It is a little frustrating that I 
can’t get these vector graphics into Lilypond SVG output, as they are 
basically SVG in the first place, but from what I understand so far that 
isn’t possible.


Therefore, if I understand correctly my current options would be:

- render to pdf and work on a system to render pdfs within the framework 
I’m using (this is probably possible, but involves lots of unknowns)
- rasterise the images and display as PNG, thus include the rasterised 
version in the SVG (not optimal in terms of file size or speed of 
render, but possible)
- work on a system to convert SVG paths to Lilypond/Scheme paths in 
order to be able to draw in a vector within Lilypond to any backend.

*
*
Have I missed anything?


Maybe include EPS, use LiyPond’s PDF backend and convert PDF to SVG with 
Inkscape?


Hraban

Re: \epsfile and SVG output

[Jean Abou Samra]

> Many thanks for the clarification that this approach will not work and
> alternative suggestions.
> 
> I presume that /image will only include PNGs in a SVG output and not EPS (the
> documentation reads a little unclearly on this as the section on backends is
> elided with comments on coloured backgrounds)?


In fact, PNG in \image works in all output formats/backends
(it is only if you want transparency that it has limitations,
but the default is to add a white background, so there is no
limitation in the default settings).


> For context I am using SVG output because my display target is a custom IOS
> app that uses skia as a backend. SKIA can be used to display SVGs easily
> within the context that I am working. SKIA does have a pdf backend but it
> isn’t exposed directly by the framework I’m using.
> 
> The reason to use EPS is that I want to bring in vector graphics made in
> Inkscape using a graphics tablet. It is a little frustrating that I can’t get
> these vector graphics into Lilypond SVG output, as they are basically SVG in
> the first place, but from what I understand so far that isn’t possible.


Yes, unfortunately the SVG backend isn't as well-developed as the
other backends and in particular doesn't support including SVG
(which it could easily do). The Cairo backend also supports outputting
SVG, but doesn't support including SVG either.


> Therefore, if I understand correctly my current options would be:
> 
> - render to pdf and work on a system to render pdfs within the framework I’m
> using (this is probably possible, but involves lots of unknowns)
> - rasterise the images and display as PNG, thus include the rasterised version
> in the SVG (not optimal in terms of file size or speed of render, but
> possible)
> - work on a system to convert SVG paths to Lilypond/Scheme paths in order to
> be able to draw in a vector within Lilypond to any backend.


That sounds right. Alternatively, you might be able to add a tag
with a specific id using the output-attributes property, then post-process
the file to replace the tag with that id with your custom content or
something like that.



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

Re: \epsfile and SVG output

[Alex Harker]

Many thanks for the clarification that this approach will not work and 
alternative suggestions.

I presume that /image will only include PNGs in a SVG output and not EPS (the 
documentation reads a little unclearly on this as the section on backends is 
elided with comments on coloured backgrounds)?

For context I am using SVG output because my display target is a custom IOS app 
that uses skia as a backend. SKIA can be used to display SVGs easily within the 
context that I am working. SKIA does have a pdf backend but it isn’t exposed 
directly by the framework I’m using.

The reason to use EPS is that I want to bring in vector graphics made in 
Inkscape using a graphics tablet. It is a little frustrating that I can’t get 
these vector graphics into Lilypond SVG output, as they are basically SVG in 
the first place, but from what I understand so far that isn’t possible.

Therefore, if I understand correctly my current options would be:

- render to pdf and work on a system to render pdfs within the framework I’m 
using (this is probably possible, but involves lots of unknowns)
- rasterise the images and display as PNG, thus include the rasterised version 
in the SVG (not optimal in terms of file size or speed of render, but possible)
- work on a system to convert SVG paths to Lilypond/Scheme paths in order to be 
able to draw in a vector within Lilypond to any backend.

Have I missed anything?

Alex


> On 10 Apr 2024, at 12:33, Jean Abou Samra  wrote:
> 
>> An alternative, if you can use raster graphics, would be a PNG file added
>> with the \image command.
> 
> 
> P.S. \image is new in 2.25
> https://lilypond.org/doc/v2.25/Documentation/notation/graphical-markup
> (and I remember now that I wrote down what does and doesn't
> support EPS in the 2.25 documentation, in the description of \image)

Re: \epsfile and SVG output

[Henning Hraban Ramm]

Am 10.04.24 um 14:31 schrieb Jean Abou Samra:

It would be possible to convert EPS to SVG with pstoedit or via PDF and
Inkscape. Both would avoid rastering vectors into a pixel image.


True, but LilyPond so far doesn't support including SVG images either.
(It does support \markup \path in SVG though.)


Ah, I didn’t know.

Hraban

Re: English Note names alternatives

[APNOE-Verteiler]

On 06.04.24 21:58, Carl Sorensen wrote:


On Sat, Apr 6, 2024 at 12:54 PM Fr. Samuel Springuel 
mailto:rpspring...@gmail.com>> wrote:


I just discovered that in English, there’s a shorter way to name 
notes that would normally be specified with “-sharp” or “-flat”: “s”

 and “f”.  E.g. “f-sharp” can be written as “fs” and “b-flat” can be
 written as “bf”.

However, I noticed that this is not documented in the Music Glossary:
 
https://lilypond.org/doc/v2.24/Documentation/music-glossary/pitch-names



In principle this sounds like a good idea. There is, however, a similar 
scheme in place since 10 years or longer for certain notes in Turkish 
makam scales with its 1/9 intervals. I don't have time to do this now 
but if this idea shall be pursued further, any ambiguous overlap should 
be investigated and avoided (or is it avoided by using of the makam 
definitions file already? - gosh it's been quite some time that I've 
used lilypond).


Andreas

Re: \epsfile and SVG output

[Jean Abou Samra]

> It would be possible to convert EPS to SVG with pstoedit or via PDF and 
> Inkscape. Both would avoid rastering vectors into a pixel image.



True, but LilyPond so far doesn't support including SVG images either.
(It does support \markup \path in SVG though.)



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

Re: \epsfile and SVG output

[Henning Hraban Ramm]

Am 10.04.24 um 13:29 schrieb Jean Abou Samra:

I am trying to include an epsfile as a top-level markup (it is not in
a score) and then output as SVG.



You can't (this should indeed be mentioned in the documentation). EPS files
are included by basically inlining them into the PS code that LilyPond 
generates,
which is then converted to PDF. In the SVG backend, LilyPond generates SVG
code directly and skips \epsfile markups. The Cairo backend is yet another
beast but it doesn't support outputting \epsfile other than in PS/EPS output.

An alternative, if you can use raster graphics, would be a PNG file added
with the \image command.


It would be possible to convert EPS to SVG with pstoedit or via PDF and 
Inkscape. Both would avoid rastering vectors into a pixel image.


Hraban

Re: \epsfile and SVG output

[Jean Abou Samra]

> An alternative, if you can use raster graphics, would be a PNG file added
> with the \image command.


P.S. \image is new in 2.25
https://lilypond.org/doc/v2.25/Documentation/notation/graphical-markup
(and I remember now that I wrote down what does and doesn't
support EPS in the 2.25 documentation, in the description of \image)


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

Re: \epsfile and SVG output

[Jean Abou Samra]

> I am trying to include an epsfile as a top-level markup (it is not in
> a score) and then output as SVG.


You can't (this should indeed be mentioned in the documentation). EPS files
are included by basically inlining them into the PS code that LilyPond 
generates,
which is then converted to PDF. In the SVG backend, LilyPond generates SVG
code directly and skips \epsfile markups. The Cairo backend is yet another
beast but it doesn't support outputting \epsfile other than in PS/EPS output.

An alternative, if you can use raster graphics, would be a PNG file added
with the \image command.

HTH
Jean



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

\epsfile and SVG output

[Alex Harker]

I am trying to include an epsfile as a top-level markup (it is not in a score) 
and then output as SVG.

If I render to pdf I see the eps file part, but if I render to SVG I don’t see 
it - everything else is included. If I examine the SVG as text I don’t appear 
to see anything relating to the epsfile.

I can’t see anything in the docs that would suggest that I should expect this.

Can anyone shed any light on this matter at all?

Many thanks

Alex

Re: PianoPedalBracket.to-barline doesn't always work as expected

[Kieren MacMillan]

Hi all,

Might I suggest that “to-barline” is potentially misleading/confusing…?

On the other hand:
end-at-barline, for a pedal coded for release on a note **just after** a 
barline, might be more clearly descriptive of the current behaviour; and
extend-to-barline, for a pedal coded for release on a note **just before** 
a barline, might be more suggestive of the behaviour Maurits was expecting.

Is there any technical reason both of these different-but-related properties 
can’t/shouldn’t be made available?

Cheers,
Kieren.
__

My work day may look different than your work day. Please do not feel obligated 
to read or respond to this email outside of your normal working hours.

Re: PianoPedalBracket.to-barline doesn't always work as expected

[Maurits Lamers via LilyPond user discussion]

Hi Jean,

Of course you are right. Let me explain how I got to this to explain my 
confusion.


My first attempt was to add it to the next note without using \override 
Staff.PianoPedalBracket.to-barline = ##t (as I wasn't aware of it 
existence at that point). What I discovered however is that when the 
tremolo is the last bar of that system, the bracket is continued on the 
next system. Example:


%%%

\score {
  \new Staff {
    \clef bass
    \time 6/8
    \relative c' {
  c8 b a g e c |
  \set Staff.pedalSustainStyle = #'mixed
  \repeat tremolo 12 { b,32\sustainOn b' } |
  \repeat tremolo 12 { b,32 b'  } | \break
  c8\sustainOff e f g a
    }
  }
}

%%

That is confusing because it means for the player that it is not 
immediately obvious where to lift the sustain pedal. This lead to me 
moving the \sustainOff back to the last note of the tremolo, and trying 
to extend it to the end of the barline.


It is indeed the case that if you set it to the next note (the c8 in the 
example) AND set \override Staff.PianoPedalBracket.to-barline = ##t, it 
works as expected. To me it was not immediately obvious that this is the 
correct solution. When trying to find a solution, I was surprised to 
only find a reference to this type of solution on the mailing list in a 
post of 2015, and it didn't feature the end of system situation. I 
expected that this kind of issue would have come up more frequently. 
Perhaps this solution might deserve a mention in the Pedal department of 
the Lilypond documentation. Happy to contribute that mention.


cheers

Maurits

Op 10-04-2024 om 12:01 schreef Jean Abou Samra:

Le mardi 09 avril 2024 à 23:55 +0200, Maurits Lamers via LilyPond user 
discussion a écrit :

Hey all,

I encountered a situation where the PianoPedalBracket setting to-barline
doesn't always do what you'd expect. Given the following code, the pedal
bracket is not extended to the end of the bar:

%%%

\version "2.24.0"
\score {
    \new Staff {
  \clef bass
  \time 6/8
  \relative c' {
    c8 b a g e c |
    \set Staff.pedalSustainStyle = #'mixed
    \override Staff.PianoPedalBracket.to-barline = ##t
    \repeat tremolo 12 { b,32\sustainOn b' } |
    \repeat tremolo 12 { b,32 b'\sustainOff  } |
    c8 e f g a
  }
    }
}


Correct syntax is

\version "2.24.0"
\score {
\new Staff {
  \clef bass
  \time 6/8
  \relative c' {
c8 b a g e c |
\set Staff.pedalSustainStyle = #'mixed
\override Staff.PianoPedalBracket.to-barline = ##t
\repeat tremolo 12 { b,32\sustainOn b' } |
\repeat tremolo 12 { b,32 b' } |
c8\sustainOff e f g a
  }
}
}


The \sustainOff command is placed on the note where you *release*
the pedal. And because LilyPond uses post-fix syntax, it comes just
*after* that note.

Best,
Jean

Re: PianoPedalBracket.to-barline doesn't always work as expected

[Jean Abou Samra]

Le mardi 09 avril 2024 à 23:55 +0200, Maurits Lamers via LilyPond user 
discussion a écrit :
> Hey all,
> 
> I encountered a situation where the PianoPedalBracket setting to-barline 
> doesn't always do what you'd expect. Given the following code, the pedal 
> bracket is not extended to the end of the bar:
> 
> %%%
> 
> \version "2.24.0"
> \score {
>    \new Staff {
>  \clef bass
>  \time 6/8
>  \relative c' {
>    c8 b a g e c |
>    \set Staff.pedalSustainStyle = #'mixed
>    \override Staff.PianoPedalBracket.to-barline = ##t
>    \repeat tremolo 12 { b,32\sustainOn b' } |
>    \repeat tremolo 12 { b,32 b'\sustainOff  } |
>    c8 e f g a
>  }
>    }
> }


Correct syntax is

\version "2.24.0"
\score {
   \new Staff {
 \clef bass
 \time 6/8
 \relative c' {
   c8 b a g e c |
   \set Staff.pedalSustainStyle = #'mixed
   \override Staff.PianoPedalBracket.to-barline = ##t
   \repeat tremolo 12 { b,32\sustainOn b' } |
   \repeat tremolo 12 { b,32 b' } |
   c8\sustainOff e f g a
 }
   }
}


The \sustainOff command is placed on the note where you *release*
the pedal. And because LilyPond uses post-fix syntax, it comes just
*after* that note.

Best,
Jean



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

Re: PianoPedalBracket.to-barline doesn't always work as expected

[Maurits Lamers via LilyPond user discussion]

Hi Aaron,

Yes it does. It is just unexpected that this would be necessary.

cheers

Maurits

Op 10-04-2024 om 00:12 schreef Aaron Hill:

Does the empty chord construct help?

  <>\sustainOff

(I'm away from my normal environment, so I cannot test this locally to 
confirm.)



-- Aaron Hill