Piano pedal gradual release

[Andrew Bernard]

Is there any support for pedal gradual release when using line and bracket
style where the gradual release ends in a sustain pedal off event? I am
aware that for a sustain on/sustain off event you can simply use bracket
flare settings, but in this case I need to influence the segment to the end
bracket. Does anybody have code or solutions for this scenario?

This is common enough in printed music and handwritten scores, and is one
of the reasons for using line notation for pedalling. It would be great if
lilypond could do this.

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

Pedal bracket to end of note duration

[Andrew Bernard]

How can one get the pedal bracket line to extend to the end of the note
duration for which the sustain off event is given?

Referring to this specific MWE below, I would like the pedal bracket to
extend to just before the barline, similar to what one can do with hairpins.

I suspect this is a FAQ on the list but I have never been able to unearth a
proper solution. And yes, Gould et al. may have rules, but I need this for
the MSS that I engrave all the time. I can achieve the effect using shorten
pair, but this is always trail and error, and therefore tedious and error
prone.

Andrew

== snip

\version "2.19.56"

{
  \set Staff.pedalSustainStyle = #'bracket
  c'4 c'\sustainOn c' c'\sustainOff
  c'1
}

== snip
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Pedal bracket to end of note duration

[Knute Snortum]

I usually do something like this:

<<
{
  c'4 c' c' c'
  c'1
}
{
  \set Staff.pedalSustainStyle = #'bracket
  s4 s \sustainOn s s8 s \sustainOff
}
>>


---
Knute Snortum
(via Gmail)

On Sun, Mar 5, 2017 at 1:52 AM, Andrew Bernard 
wrote:

> How can one get the pedal bracket line to extend to the end of the note
> duration for which the sustain off event is given?
>
> Referring to this specific MWE below, I would like the pedal bracket to
> extend to just before the barline, similar to what one can do with hairpins.
>
> I suspect this is a FAQ on the list but I have never been able to unearth
> a proper solution. And yes, Gould et al. may have rules, but I need this
> for the MSS that I engrave all the time. I can achieve the effect using
> shorten pair, but this is always trail and error, and therefore tedious and
> error prone.
>
> Andrew
>
> == snip
>
> \version "2.19.56"
>
> {
>   \set Staff.pedalSustainStyle = #'bracket
>   c'4 c'\sustainOn c' c'\sustainOff
>   c'1
> }
>
> == snip
>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: tweaking Clefs

[Timothy Lanfear]

On 01/03/17 18:02, Peter Gentry wrote:


It would be nice to be able to change the clef at the same time as 
transposing.


I often forget one or other and it is easier to input data in the 
original clef for checking input.


Having started down this road it has become a challenge…..Any help for 
a ageing muso who has forgotten almost all the scheme/lily learnt last 
year very gratefully received.




No one picked up this one. Perhaps a way to tackle this problem would be 
to define specific contexts for the instruments that automatically have 
the right properties. It's worth reading through all the context 
properties to see which you should set.


--
Timothy Lanfear, Bristol, UK.

\version "2.19.56"

\layout {
  \context {
\Staff
\name "BassClt"
\alias Staff
\clef "treble"
instrumentName = \markup { \center-column { "Bass" "Clarinet" } }
shortInstrumentName = "BCl"
  }
  \context {
\Staff
\name "Bassoon"
\alias Staff
\clef "bass"
instrumentName = "Bassoon"
shortInstrumentName = "Bsn"
  }
  \inherit-acceptability "BassClt" "Staff"
  \inherit-acceptability "Bassoon" "Staff"
}

\midi {
  \context {
\Staff
\name "BassClt"
\alias Staff
instrumentTransposition = #(ly:make-pitch -2 7 -1)
midiInstrument = "clarinet"
  }
  \context {
\Staff
\name "Bassoon"
\alias Staff
midiInstrument = "bassoon"
  }
  \inherit-acceptability "BassClt" "Staff"
  \inherit-acceptability "Bassoon" "Staff"
}

music = { \key c\major c4 d e f g a b c' }

\score {
  \new StaffGroup <<
\new Bassoon { \music }
\new BassClt { \transpose bes c'' \music }
  >>
  \layout{}
  \midi{}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: tweaking Clefs

[David Kastrup]

Timothy Lanfear  writes:

> On 01/03/17 18:02, Peter Gentry wrote:
>>
>> It would be nice to be able to change the clef at the same time as
>> transposing.
>>
>> I often forget one or other and it is easier to input data in the
>> original clef for checking input.
>>
>> Having started down this road it has become a challenge…..Any help
>> for a ageing muso who has forgotten almost all the scheme/lily
>> learnt last year very gratefully received.
>>
>
> No one picked up this one. Perhaps a way to tackle this problem would
> be to define specific contexts for the instruments that automatically
> have the right properties. It's worth reading through all the context
> properties to see which you should set.

Huh, this sounds like a case for what \addInstrumentDefinition was for
(it's been undocumented because there really is no point in not just
defining a music expression doing the same).

Doing a context of its own seems like overkill when you could just be
writing

\new Staff \with \bassclarinet { ... }

instead and put all the respective definitions in \bassclarinet .

-- 
David Kastrup

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

Re: Pedal bracket to end of note duration

[David Nalesnik]

Hi,

On Sun, Mar 5, 2017 at 8:06 AM, Knute Snortum  wrote:
> I usually do something like this:
>
> <<
> {
>   c'4 c' c' c'
>   c'1
> }
> {
>   \set Staff.pedalSustainStyle = #'bracket
>   s4 s \sustainOn s s8 s \sustainOff
> }
>>>
>
>
> ---
> Knute Snortum
> (via Gmail)
>
> On Sun, Mar 5, 2017 at 1:52 AM, Andrew Bernard 
> wrote:
>>
>> How can one get the pedal bracket line to extend to the end of the note
>> duration for which the sustain off event is given?
>>
>> Referring to this specific MWE below, I would like the pedal bracket to
>> extend to just before the barline, similar to what one can do with hairpins.
>>
>> I suspect this is a FAQ on the list but I have never been able to unearth
>> a proper solution. And yes, Gould et al. may have rules, but I need this for
>> the MSS that I engrave all the time. I can achieve the effect using shorten
>> pair, but this is always trail and error, and therefore tedious and error
>> prone.
>>

How about something like the following?

It resets the right bound of the spanner to the next PaperColumn or
NonMusicalPaperColumn.  In so doing it gets a bit close to the
next note, so you can use 'shorten-pair for consistent offsets.


\version "2.19.55"

#(define (encompass-duration grob)
   (let* ((rb (ly:spanner-bound grob RIGHT))
  (sys (ly:grob-system grob))
  (cols (ly:grob-array->list (ly:grob-object sys 'columns)))
  (me-forward (memq rb cols)))
 (if (and me-forward (> (length me-forward) 1))
 (ly:spanner-set-bound! grob RIGHT (cadr me-forward)))
 (ly:piano-pedal-bracket::print grob)))

{
  \override Staff.PianoPedalBracket.stencil = #encompass-duration
  \override Staff.PianoPedalBracket.shorten-pair = #'(0 . 0.5)
  \set Staff.pedalSustainStyle = #'bracket
  c'4\sustainOn c' c' c'\sustainOff
  c'4 c'\sustainOn c'\sustainOff c'
  c'4\sustainOn c' c' c'
  \break
  c'4\sustainOff c' c' c'
}

%%%

Hope this helps.

David

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

Re: tweaking Clefs

[Ralph Palmer]

On Mar 5, 2017 9:24 AM, "Timothy Lanfear"  wrote:

On 01/03/17 18:02, Peter Gentry wrote:



It would be nice to be able to change the clef at the same time as
transposing.

I often forget one or other and it is easier to input data in the original
clef for checking input.

Greetings, Timothy Lanfear and Peter Gentry -

I'm afraid I do not have a solution to your problem(s), but I do have some
input. I'm a violist who plays fiddle tunes and classical music. I also
transpose a lot of fiddle tunes to play on the viola. I agree that it's a
lot easier for me to proofread in the original clef, and I sometimes forget
to change clefs after proofreading. However, I think there would be
problems with doing an automatic clef change with transposition, at least
in classical music. Viola uses both alto and treble clef, and cello uses
bass and tenor. I suspect other instruments use multiple clefs (and
ottava), as well. You would still have to check and change the results of
your transposition, and I, personally, think I have a better chance of
doing that consistently if I have to do it all the time.

Just my 2 cents,

Ralph Palmer
palmer.r.vio...@gmail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Pedal bracket to end of note duration

[David Kastrup]

David Nalesnik  writes:

> How about something like the following?
>
> It resets the right bound of the spanner to the next PaperColumn or
> NonMusicalPaperColumn.  In so doing it gets a bit close to the
> next note, so you can use 'shorten-pair for consistent offsets.
>
> 
> \version "2.19.55"
>
> #(define (encompass-duration grob)
>(let* ((rb (ly:spanner-bound grob RIGHT))
>   (sys (ly:grob-system grob))
>   (cols (ly:grob-array->list (ly:grob-object sys 'columns)))
>   (me-forward (memq rb cols)))
>  (if (and me-forward (> (length me-forward) 1))
>  (ly:spanner-set-bound! grob RIGHT (cadr me-forward)))
>  (ly:piano-pedal-bracket::print grob)))
>
> {
>   \override Staff.PianoPedalBracket.stencil = #encompass-duration
>   \override Staff.PianoPedalBracket.shorten-pair = #'(0 . 0.5)
>   \set Staff.pedalSustainStyle = #'bracket
>   c'4\sustainOn c' c' c'\sustainOff
>   c'4 c'\sustainOn c'\sustainOff c'
>   c'4\sustainOn c' c' c'
>   \break
>   c'4\sustainOff c' c' c'
> }
>
> %%%
>
> Hope this helps.

Shouldn't to-barline do something of that kind?  That would have been my
first suggestion but doesn't appear to work, regardless of whether the
spanner ends with the last note or the following note.

The question is whether it should do something helpful?  The default
documentation suggests that it _shortens_ spanners to the _preceding_
bar-line.  We could make this do something sensible depending on the
grob in question, or we could add a direction or something to make it
possible just which direction a bar-line might sit in order to have an
influence.

-- 
David Kastrup

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

Re: Pedal bracket to end of note duration

[Kieren MacMillan]

Hi David (et al.),

> Shouldn't to-barline do something of that kind?

Yes. =)

> The question is whether it should do something helpful?

Yes.

> We could make this do something sensible depending on the
> grob in question, or we could add a direction or something to make it
> possible just which direction a bar-line might sit in order to have an
> influence.

Either one of those seems like the most organic and useful way to solve this 
[long-standing] problem.

Thanks!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: tweaking Clefs

[Kieren MacMillan]

Hi David (et al.),

>> No one picked up this one. Perhaps a way to tackle this problem would
>> be to define specific contexts for the instruments that automatically
>> have the right properties. It's worth reading through all the context
>> properties to see which you should set.
> 
> Huh, this sounds like a case for what \addInstrumentDefinition was for
> (it's been undocumented because there really is no point in not just
> defining a music expression doing the same).

This is essentially the same problem that has been discussed many times before 
on this list (e.g. the long thread at 
https://lists.gnu.org/archive/html/lilypond-user/2014-05/msg00067.html). There 
is a need for a well-implemented instrument-definition and -switching mechanism 
which would automatically change all relevant context properties, handle 
transpositions and clef issues, etc.

> \new Staff \with \bassclarinet { ... }
> instead and put all the respective definitions in \bassclarinet .

That sounds like it wouldn’t be applicable mid-score.
Am I missing something in what you’re suggesting?

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: tweaking Clefs

[David Kastrup]

Kieren MacMillan  writes:

> Hi David (et al.),
>
>>> No one picked up this one. Perhaps a way to tackle this problem would
>>> be to define specific contexts for the instruments that automatically
>>> have the right properties. It's worth reading through all the context
>>> properties to see which you should set.
>> 
>> Huh, this sounds like a case for what \addInstrumentDefinition was for
>> (it's been undocumented because there really is no point in not just
>> defining a music expression doing the same).
>
> This is essentially the same problem that has been discussed many
> times before on this list (e.g. the long thread at
> https://lists.gnu.org/archive/html/lilypond-user/2014-05/msg00067.html). There
> is a need for a well-implemented instrument-definition and -switching
> mechanism which would automatically change all relevant context
> properties, handle transpositions and clef issues, etc.
>
>> \new Staff \with \bassclarinet { ... }
>> instead and put all the respective definitions in \bassclarinet .
>
> That sounds like it wouldn’t be applicable mid-score.
> Am I missing something in what you’re suggesting?

Uh, { ... \bassclarinet ... } ?

With something like

bassclarinet = {
  \clef F
  \transposition c,
  \set Staff.midiInstrument = "clarinet"
  \set Staff.instrumentCueName = \markup \bf "cl. B"
  \set Staff.instrumentName = "bass clarinet"
  \set Staff.shortInstrumentName = "bc"
}

you should fare reasonably well both per-Staff as well as in-Staff .
instrumentCueName would trigger a spurious cue name however I think: the
instrument cue engraver could be changed to ignore cue names set before
the first call of process-music.

-- 
David Kastrup

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

Re: Pedal bracket to end of note duration

[David Nalesnik]

On Sun, Mar 5, 2017 at 9:36 AM, David Kastrup  wrote:
> David Nalesnik  writes:
>
>> How about something like the following?
>>
>> It resets the right bound of the spanner to the next PaperColumn or
>> NonMusicalPaperColumn.  In so doing it gets a bit close to the
>> next note, so you can use 'shorten-pair for consistent offsets.
>>
>> 
>> \version "2.19.55"
>>
>> #(define (encompass-duration grob)
>>(let* ((rb (ly:spanner-bound grob RIGHT))
>>   (sys (ly:grob-system grob))
>>   (cols (ly:grob-array->list (ly:grob-object sys 'columns)))
>>   (me-forward (memq rb cols)))
>>  (if (and me-forward (> (length me-forward) 1))
>>  (ly:spanner-set-bound! grob RIGHT (cadr me-forward)))
>>  (ly:piano-pedal-bracket::print grob)))
>>
>> {
>>   \override Staff.PianoPedalBracket.stencil = #encompass-duration
>>   \override Staff.PianoPedalBracket.shorten-pair = #'(0 . 0.5)
>>   \set Staff.pedalSustainStyle = #'bracket
>>   c'4\sustainOn c' c' c'\sustainOff
>>   c'4 c'\sustainOn c'\sustainOff c'
>>   c'4\sustainOn c' c' c'
>>   \break
>>   c'4\sustainOff c' c' c'
>> }
>>
>> %%%
>>
>> Hope this helps.
>
> Shouldn't to-barline do something of that kind?  That would have been my
> first suggestion but doesn't appear to work, regardless of whether the
> spanner ends with the last note or the following note.
>
> The question is whether it should do something helpful?  The default
> documentation suggests that it _shortens_ spanners to the _preceding_
> bar-line.  We could make this do something sensible depending on the
> grob in question, or we could add a direction or something to make it
> possible just which direction a bar-line might sit in order to have an
> influence.
>


Since this may bring you or someone else in contact with
PianoPedalBracket stencil code, I should mention that I'm planning to
put a patch up for review in a day or so which fixes the confusing use
of TupletBracket code (a call to TupletBracket::make_bracket here).

-DN

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

Re: function/macro for "on the fly" dynamics+text

[Kieren MacMillan]

Hi Malte (et al.),

> Do you know the \dynamic function from openlilylib?

I didn’t! Thanks (to all) for the reference — and to Janek for the function.

It looks like it does much of the work I want done. There are some improvements 
I’ll have to make — and return to OLL, of course — primarily the 
X-offset/self-alignment-X issue. But it’s a great place to start.

Thanks again,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re:tweaking clefs

[Peter Gentry]

Timothy Lanfear supplied a simple understandable way of achieving my aims.
I was thrown headlong down the route of trying to modify the sequential
music stream as was done for indicating/modifying pitches outside the
"range"  of each instrument. "range" being somewhat arbitrary as it  depends
on the skill of the musician. This employed range  data in the scheme
process and input instrumentname from the lily source  file

 

Appropriate clef and transposition can be easily provided entirely in Lily
data rather than fiddling about with the music stream.

 

The solution provided answers my immediate needs. Thank you very much all.

 

Ps   \inherit-acceptability is new to me I will have a search in the
manuals.

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

Re: tweaking Clefs

[Kieren MacMillan]

Hi David,

> Uh, { ... \bassclarinet ... } ?
> 
> With something like
> 
> bassclarinet = {
>  \clef F
>  \transposition c,
>  \set Staff.midiInstrument = "clarinet"
>  \set Staff.instrumentCueName = \markup \bf "cl. B"
>  \set Staff.instrumentName = "bass clarinet"
>  \set Staff.shortInstrumentName = “bc”

Uh… \bf throws an error…?
Is that a function my copy of 2.19.56 should have?

Without it, and incorporating the rest into a compilable snippet:

%%%  SNIPPET BEGINS
\version "2.19.56"
\language english

bassclarinet = {
 \clef F
 \transposition bf,
 \set Staff.midiInstrument = "clarinet"
 \set Staff.instrumentCueName = \markup "cl. B"
 \set Staff.instrumentName = "bass clarinet"
 \set Staff.shortInstrumentName = "bc"
}

clarinet = {
 \clef G
 \transposition bf
 \set Staff.midiInstrument = "clarinet"
 \set Staff.instrumentCueName = \markup "cl. B"
 \set Staff.instrumentName = "clarinet"
 \set Staff.shortInstrumentName = "cl"
}

global = {
  \key c \major s1
  \key f \major s1
  \key g \major s1
  \key d \major s1
}

clarnotes = {
  \clarinet g1
  \bassclarinet g1
  \clarinet g1
  \bassclarinet g1
}

\new Staff << \global \clarnotes >>
%%%  SNIPPET ENDS

The clef changes are fine… but the transposition doesn’t work as I would 
expect/hope it would.
Is there a way to extend this music-function idea to handle all of the 
requirements of an instrument switch?

> instrumentCueName would trigger a spurious cue name

It does, as seen in the output of the above snippet.

> the instrument cue engraver could be changed to ignore cue names
> set before the first call of process-music.

Is that the cleanest way to handle the problem?

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: tweaking clefs

[Peter Gentry]

\inherit-acceptability is documented in \version "2.19.56" which I have just
downloaded.

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

ANN: OOoLilyPond 0.5.0

[Klaus Blum]

Dear LilyPond community, 

I am happy to announce a new version of OOoLilyPond - an extension for
LibreOffice/OpenOffice. 
OOoLilyPond enables you to enter LilyPond code from within your Office
document. Both the resulting image and its source code will be embedded
within the document. No need to keep any additional files other than the
Writer/Draw/Impress document itself.

The project has been unmaintained during the last few years. With the
agreement of the original author, the development of the project is now
continued under the roof of openlilylib.org:
https://github.com/openlilylib/LO-ly/releases


Changes since v. 0.4.0:

*   fixed: Runtime error "Variable not defined: line 40 CurserPosition=1"
*   additional include paths can be specified
*   added button to save the current code into temporary file and open it in
external editor
*   added button to re-import code from temporary file back to editor window
*   added support for the use of SVG graphics format (please read the
verbose release notes)
*   fixed: wrong size of vector graphics in Impress/Draw
*   size and crop settings of existing graphics can be preserved
*   user now can choose between two different ways to import graphic into
document
*   font name and font size for editor windows can be specified
*   user interface can be translated into other languages


Compatibility:

OOoLilyPond (OLy) works with recent versions of LibreOffice (5.3.0.3) and
OpenOffice (4.1.3). Older versions should work as well. It has even been
tested with OpenOffice 2.4 without issues.

Any content (LilyPond code, templates, OLy configuration files) created
with/for OLy 0.4.x will work with OLy 0.5.x - and vice versa. (Fully
compatible, forward and backward.)
Older snippets created with OLy 0.3.x will also work with 0.4.x and 0.5.x,
but not (necessarily) vice versa.


Direct download:
https://github.com/openlilylib/LO-ly/releases/download/0.5.0/OOoLilyPond-0.5.0.oxt
Verbose release notes:
https://github.com/openlilylib/LO-ly/releases/download/0.5.0/OOoLilyPond-0.5.0-Release-Notes.txt

The project is also listed in the official extension centers for LibreOffice
and OpenOffice:
https://extensions.libreoffice.org/extensions/ooolilypond
http://extensions.openoffice.org/en/project/ooolilypond

I hope this will be useful for many people. 

Cheers, 
Klaus





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/ANN-OOoLilyPond-0-5-0-tp200737.html
Sent from the User mailing list archive at Nabble.com.

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

Re: ANN: OOoLilyPond 0.5.0

[Martin Tarenskeen]

On Sun, 5 Mar 2017, Klaus Blum wrote:


Dear LilyPond community,
(...)
I hope this will be useful for many people.


I am sure it will be, thanks!

--

MT

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

Re: ANN: OOoLilyPond 0.5.0

[Henning Hraban Ramm]

Am 2017-03-05 um 19:26 schrieb Klaus Blum :

> I am happy to announce a new version of OOoLilyPond - an extension for
> LibreOffice/OpenOffice. 

Thank you for the effort!

> Compatibility:
> 
> OOoLilyPond (OLy) works with recent versions of LibreOffice (5.3.0.3) and
> OpenOffice (4.1.3). Older versions should work as well. It has even been
> tested with OpenOffice 2.4 without issues.
> 
> Any content (LilyPond code, templates, OLy configuration files) created
> with/for OLy 0.4.x will work with OLy 0.5.x - and vice versa. (Fully
> compatible, forward and backward.)
> Older snippets created with OLy 0.3.x will also work with 0.4.x and 0.5.x,
> but not (necessarily) vice versa.

In my installation (LibreOffice 5.2.4.2 and LilyPond 2.18.2 on OSX 10.9.5) only 
the SVG mode works; in EPS mode I get an image with two lines of text (Title: 
... / Creator: ...)


Greetlings, Hraban
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net




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

Re: ANN: OOoLilyPond 0.5.0

[Klaus Blum]

Hi Henning, 


Henning Hraban Ramm-3 wrote
> In my installation (LibreOffice 5.2.4.2 and LilyPond 2.18.2 on OSX 10.9.5)
> only the SVG mode works; in EPS mode I get an image with two lines of text
> (Title: ... / Creator: ...)

yes, that's a known limitation of LibreOffice. EPS graphics only work in
OpenOffice (Windows), which is not preferred by everyone.   ;-) 
But we now have SVG versions for all templates inherited from 0.4.0, and
working without the auto-crop feature might be easier than it seems at the
first glance. 
Detailed informations can be found in the verbose release notes
(https://github.com/openlilylib/LO-ly/releases/download/0.5.0/OOoLilyPond-0.5.0-Release-Notes.txt).

Cheers, 
Klaus




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/ANN-OOoLilyPond-0-5-0-tp200737p200740.html
Sent from the User mailing list archive at Nabble.com.

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

Re: ANN: OOoLilyPond 0.5.0

[SoundsFromSound]

Klaus Blum wrote
> yes, that's a known limitation of LibreOffice. EPS graphics only work in
> OpenOffice (Windows), which is not preferred by everyone.   ;-) 
> But we now have SVG versions for all templates inherited from 0.4.0, and
> working without the auto-crop feature might be easier than it seems at the
> first glance. 
> Detailed informations can be found in the verbose release notes
> (https://github.com/openlilylib/LO-ly/releases/download/0.5.0/OOoLilyPond-0.5.0-Release-Notes.txt).
> 
> Cheers, 
> Klaus

Hi Klaus!

This extension works beautifully on Linux Mint, thank you for sharing this
with us! 

However, not sure if it's user error or a bug or something, but on Windows
10 LibreOffice 5, I am constantly seeing an error when trying to simply
enter a small musical example into a document:
*
Error: No png output found*

Just wanted to share this with you, in case you knew what the cause/fix was!






-
composer | sound designer | asmr artist 
LilyPond Tutorials (for beginners) --> http://bit.ly/bcl-lilypond
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/ANN-OOoLilyPond-0-5-0-tp200737p200741.html
Sent from the User mailing list archive at Nabble.com.

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

Re: ANN: OOoLilyPond 0.5.0

[Klaus Blum]

Another thought about graphic file formats: 

The brand new LibreOffice supports importing PDF graphics, *but* embedded
fonts are not yet recognized, which makes this feature not (yet?) usable for
LilyPond-created PDFs. If this changes in the forseable future, using PDF
format might solve all our problems. 

The developer of this LO feature has already made some changes:
https://disqus.com/home/discussion/vmiklos/insert_pdf_as_image_in_libreoffice_53_01/
Maybe his comment means that in LO 5.4.0.0 this might be solved.

There is also a bug report on the LO buglist:
https://bugs.documentfoundation.org/show_bug.cgi?id=106203
A comment there sounds as if someone could confirm the same bug for LO
5.4.0.0... that's all I know about that for the moment. 



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/ANN-OOoLilyPond-0-5-0-tp200737p200742.html
Sent from the User mailing list archive at Nabble.com.

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

Re: tweaking Clefs

[David Kastrup]

Kieren MacMillan  writes:

> Hi David,
>
>> Uh, { ... \bassclarinet ... } ?
>> 
>> With something like
>> 
>> bassclarinet = {
>>  \clef F
>>  \transposition c,
>>  \set Staff.midiInstrument = "clarinet"
>>  \set Staff.instrumentCueName = \markup \bf "cl. B"
>>  \set Staff.instrumentName = "bass clarinet"
>>  \set Staff.shortInstrumentName = “bc”
>
> Uh… \bf throws an error…?
> Is that a function my copy of 2.19.56 should have?

No.  That was a TeXism for \bold .

> The clef changes are fine… but the transposition doesn’t work as I
> would expect/hope it would.

What did you expect/hope?  This is just for Midi.

> Is there a way to extend this music-function idea to handle all of the
> requirements of an instrument switch?

It's not a music function but an expression.  What _are_ "all of the
requirements"?  This does what \instrumentSwitch can do now.

>> instrumentCueName would trigger a spurious cue name
>
> It does, as seen in the output of the above snippet.
>
>> the instrument cue engraver could be changed to ignore cue names
>> set before the first call of process-music.
>
> Is that the cleanest way to handle the problem?

Easiest to explain I guess.

-- 
David Kastrup

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

Re: ANN: OOoLilyPond 0.5.0

[Klaus Blum]

Hi Ben, 


SoundsFromSound wrote
> on Windows 10 LibreOffice 5, I am constantly seeing an error when trying
> to simply enter a small musical example into a document:
*
> Error: No png output found
*
> 
> Just wanted to share this with you, in case you knew what the cause/fix
> was!

could you add the contents of the "Ly Output" window? Maybe this could help.

Cheers, 
Klaus




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/ANN-OOoLilyPond-0-5-0-tp200737p200744.html
Sent from the User mailing list archive at Nabble.com.

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

Re: tweaking Clefs

[Kieren MacMillan]

Hi David,

>> The clef changes are fine… but the transposition doesn’t work as I
>> would expect/hope it would.
> 
> What did you expect/hope?  This is just for Midi.

Well, then… that explains it, since the visuals were therefore not critical.

>> Is there a way to extend this music-function idea to handle all of the
>> requirements of an instrument switch?
> 
> It's not a music function but an expression.  What _are_ "all of the
> requirements"?  This does what \instrumentSwitch can do now.

It doesn’t properly handle key signature changes, in particular those which are 
abstracted (but maybe even those which are inline?). See for example the thread 
at . 
That is one of the main requirements in “all of the requirements” — and perhaps 
the only one that isn’t handled well by any method I’ve seen to date. Your 
interesting work on the “smartkey” function (back in 2013: 
http://lists.gnu.org/archive/html/lilypond-user/2013-10/msg00180.html) gave me 
hope, but then wasn’t fully sufficient to solve the whole instrument-switching 
problem once and for all.

But hitting the ‘reset’ button… Perhaps by now, with all the recent 
improvements in the codebase, there is a single way to make multi-instrumental 
parts easy to code and output (in both transposed and concert versions), 
without being forced to break the music into independent variables, manually 
add redundant key changes, etc.?

Best,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

state-of-the-art multi-instrumental/transposing mechanism

[Kieren MacMillan]

Hi all,

Inspired by the “tweaking clefs” thread, I’m trying again to see if we can 
crowd-source a state-of-the-art multi-instrumentalist mechanism.

The snippet below (minimal, for these purposes?) demonstrates the problem I’m 
trying to solve.

Am I just being too optimistic in hoping that we can find a [relatively] 
dead-simple solution, one that doesn’t require:
  1. the music being broken up into variables and knitted back together;
  2. multiple (and often redundant key signatures/changes and \transpose-itions;
  etc.
??

Has someone already invented this wheel, and I just don’t know about it?

Thanks,
Kieren.

%%%  SNIPPET BEGINS
\version "2.19.56"

\paper { line-width = 6\in }

flute = {
\set Staff.instrumentName = "Flute"
\set Staff.shortInstrumentName = "Fl."
\transposition c
}
altoflute = {
\set Staff.instrumentName = "Alto Flute"
\set Staff.shortInstrumentName = "A. Fl."
\transposition g
}
toF = \markup "take flute"
toAF = \markup "take alto flute"

global = {
\key c \major s1 \break
\key d \major s1 \break
\key e \major s1 \break
}

flutepart = {
\flute
a'2 r^\toAF
\altoflute
a'2 r^\toF
\flute
a'2 r
}
flutepart_tr = {
\key c \major
\flute
a'2 r^\toAF \break
\altoflute
\transpose c f { \key d \major a'2 r^\toF } \break
\flute
\key e \major
a'2 r
}

\markup \bold "C score:"
\score {
\new Staff << \global \flutepart >>
}

\markup \vspace #4
\markup \bold "Transposed score/part (incorrect):"
\score {
\new Staff << \global \flutepart >>
}

\markup \vspace #4
\markup \bold "Transposed score/part SHOULD look like:"
\score {
\new Staff \flutepart_tr
}
%%%  SNIPPET ENDS



Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

balloon text applied to spanners?

[Jeffery Shivers]

Hi,

Is it possible to engrave balloon text to slurs, hairpins, etc? This
doesn't work:

\version "2.19.56"

music = {
  \new Voice \with { \consists "Balloon_engraver" } {
  \balloonGrobText #'NoteHead #'(-1 . -1) \markup { bla }
c'4
  \balloonGrobText #'Slur #'(1 . -2) \markup { not engraved }
d'2( c'4)
  }
}

\score {
  \music
}

Since footnotes can be applied to spanners, is there a small remedy /
alteration that can be made to the balloon text engraver to accomplish
it as well?

Best,
Jeffery

-- 

Jeffery Shivers
 jefferyshivers.com
 soundcloud.com/jefferyshivers

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

Re: state-of-the-art multi-instrumental/transposing mechanism

[Urs Liska]

Hi Kieren,

admittedly it's too late for me right now to properly understand the
issue but I wanted to direct you to Jan-Peter's
https://github.com/openlilylib/snippets/tree/master/editorial-tools/auto-transpose,
not knowing if it's even *related* to your question.

Best
Urs

Am 06.03.2017 um 00:13 schrieb Kieren MacMillan:
> Hi all,
>
> Inspired by the “tweaking clefs” thread, I’m trying again to see if we can 
> crowd-source a state-of-the-art multi-instrumentalist mechanism.
>
> The snippet below (minimal, for these purposes?) demonstrates the problem I’m 
> trying to solve.
>
> Am I just being too optimistic in hoping that we can find a [relatively] 
> dead-simple solution, one that doesn’t require:
>   1. the music being broken up into variables and knitted back together;
>   2. multiple (and often redundant key signatures/changes and 
> \transpose-itions;
>   etc.
> ??
>
> Has someone already invented this wheel, and I just don’t know about it?
>
> Thanks,
> Kieren.
>
> %%%  SNIPPET BEGINS
> \version "2.19.56"
>
> \paper { line-width = 6\in }
>
> flute = {
> \set Staff.instrumentName = "Flute"
> \set Staff.shortInstrumentName = "Fl."
> \transposition c
> }
> altoflute = {
> \set Staff.instrumentName = "Alto Flute"
> \set Staff.shortInstrumentName = "A. Fl."
> \transposition g
> }
> toF = \markup "take flute"
> toAF = \markup "take alto flute"
>
> global = {
> \key c \major s1 \break
> \key d \major s1 \break
> \key e \major s1 \break
> }
>
> flutepart = {
> \flute
> a'2 r^\toAF
> \altoflute
> a'2 r^\toF
> \flute
> a'2 r
> }
> flutepart_tr = {
> \key c \major
> \flute
> a'2 r^\toAF \break
> \altoflute
> \transpose c f { \key d \major a'2 r^\toF } \break
> \flute
> \key e \major
> a'2 r
> }
>
> \markup \bold "C score:"
> \score {
> \new Staff << \global \flutepart >>
> }
>
> \markup \vspace #4
> \markup \bold "Transposed score/part (incorrect):"
> \score {
> \new Staff << \global \flutepart >>
> }
>
> \markup \vspace #4
> \markup \bold "Transposed score/part SHOULD look like:"
> \score {
> \new Staff \flutepart_tr
> }
> %%%  SNIPPET ENDS
>
> 
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email: i...@kierenmacmillan.info
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Re: balloon text applied to spanners?

[David Nalesnik]

Hi Jeffery,

On Sun, Mar 5, 2017 at 5:25 PM, Jeffery Shivers
 wrote:
> Hi,
>
> Is it possible to engrave balloon text to slurs, hairpins, etc? This
> doesn't work:
>
> \version "2.19.56"
>
> music = {
>   \new Voice \with { \consists "Balloon_engraver" } {
>   \balloonGrobText #'NoteHead #'(-1 . -1) \markup { bla }
> c'4
>   \balloonGrobText #'Slur #'(1 . -2) \markup { not engraved }
> d'2( c'4)
>   }
> }
>
> \score {
>   \music
> }
>
> Since footnotes can be applied to spanners, is there a small remedy /
> alteration that can be made to the balloon text engraver to accomplish
> it as well?
>

See https://sourceforge.net/p/testlilyissues/issues/2567/

-David

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

Re: state-of-the-art multi-instrumental/transposing mechanism

[Kieren MacMillan]

Hi Urs,

> it's too late for me right now to properly understand the issue

1. Thanks for responding anyway!  =)
2. Looks like you do understand most of the issue.

> but I wanted to direct you to Jan-Peter's
> https://github.com/openlilylib/snippets/tree/master/editorial-tools/auto-transpose,
> not knowing if it's even *related* to your question.

It is!

In the modified snippet (below), I use \autotranspose. It works great EXCEPT 
the [abstracted] key signature part. If we could just figure out how to have 
the key signature properly displayed in the transposed part, I think we’d be 
most of the way to a complete solution (though admittedly I don’t know the 
internals of this engraver yet, so there may be other issues it doesn’t or 
can’t handle.

Thanks!
Kieren.

%%%  SNIPPET BEGINS
\version "2.19.56"
\include "openlilylib/snippets/editorial-tools/auto-transpose/definitions.ily"

\paper { line-width = 6\in }

flute = {
\set Staff.instrumentName = "Flute"
\set Staff.shortInstrumentName = "Fl."
\transposition c'
}
altoflute = {
\set Staff.instrumentName = "Alto Flute"
\set Staff.shortInstrumentName = "A. Fl."
\transposition g
}
toF = \markup "take flute"
toAF = \markup "take alto flute"

global = {
\key c \major s1 \break
\key d \major s1 \break
\key e \major s1 \break
}

flutepart = {
\flute
a'2 r^\toAF
\altoflute
a'2 r^\toF
\flute
a'2 r
}

\markup \bold "C score:"
\score {
\new Staff << \global \flutepart >>
}

\markup \vspace #4
\markup \bold "Transposed score/part (incorrect):"
\score {
\new Staff \with \autoTranspose << \global \flutepart >>
}
%%%  SNIPPET BEGINS



Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

need markup function for arrow at end of curve

[Kieren MacMillan]

Hi all,

Anyone with reasonable \path chops out there? I need a function that outputs a 
markup like this:



In a perfect world, the length, height, Y-direction, X-direction, and line 
thickness would all be parameters… but even one sample would be enough for me 
to riff on.

Thanks!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info 
‣ email: i...@kierenmacmillan.info 
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: need markup function for arrow at end of curve

[Pierre Perol-Schneider]

Hi Kieren,

Here's a first quick draft:

\version "2.19"

 #(define-markup-command (curvedArrow layout props thk mlt) (number?
number?)
  (interpret-markup layout props
   (markup
(#:stencil
 (make-path-stencil
  '(M  3.01 -0.22
C  6.17  1.59  9.88  1.09 13.35  1.05
C 13.47  1.19 12.99  1.75 13.23  1.94
C 14.66  1.15 16.91  0.92 16.93  0.71
C 16.93  0.57 15.13  0.56 13.32 -0.37
C 13.17 -0.09 13.48  0.31 13.35  0.50
C 10.56  0.59  7.90  0.73  5.97  0.33
C  4.04 -0.07 -0.16 -2.02  3.01 -0.22
Z)
   thk mlt mlt #t)

 \markup \curvedArrow #.1 #1

Regarding the length and the height, would they affect the curve and the
arrow or the curve only?

Cheers,
Pierre



2017-03-06 3:58 GMT+01:00 Kieren MacMillan :

> Hi all,
>
> Anyone with reasonable \path chops out there? I need a function that
> outputs a markup like this:
>
>
> In a perfect world, the length, height, Y-direction, X-direction, and line
> thickness would all be parameters… but even one sample would be enough for
> me to riff on.
>
> Thanks!
> Kieren.
> 
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email: i...@kierenmacmillan.info
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: need markup function for arrow at end of curve

[Pierre Perol-Schneider]

Maybe a better shape here:

\version "2.19"

 #(define-markup-command (curvedArrow layout props thk mlt) (number?
number?)
  (interpret-markup layout props
   (markup
(#:stencil
 (make-path-stencil
  '(M  3.01 -0.22
C  6.17  1.59  9.88  1.09 13.35  1.05
C 13.47  1.19 12.99  1.75 13.23  1.94
C 14.66  1.15 16.91  0.92 16.93  0.71
C 16.93  0.57 15.13  0.56 13.32 -0.37
C 13.17 -0.09 13.48  0.31 13.35  0.50
C 10.56  0.59  7.62  0.76  5.69  0.36
C 3.76  -0.04 -0.16  -2.02 3.01 -0.22
Z)
   thk mlt mlt #t)

 \markup \curvedArrow #.1 #1

Cheers,
Pierre

2017-03-06 7:42 GMT+01:00 Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com>:

> Hi Kieren,
>
> Here's a first quick draft:
>
> \version "2.19"
>
>  #(define-markup-command (curvedArrow layout props thk mlt) (number?
> number?)
>   (interpret-markup layout props
>(markup
> (#:stencil
>  (make-path-stencil
>   '(M  3.01 -0.22
> C  6.17  1.59  9.88  1.09 13.35  1.05
> C 13.47  1.19 12.99  1.75 13.23  1.94
> C 14.66  1.15 16.91  0.92 16.93  0.71
> C 16.93  0.57 15.13  0.56 13.32 -0.37
> C 13.17 -0.09 13.48  0.31 13.35  0.50
> C 10.56  0.59  7.90  0.73  5.97  0.33
> C  4.04 -0.07 -0.16 -2.02  3.01 -0.22
> Z)
>thk mlt mlt #t)
>
>  \markup \curvedArrow #.1 #1
>
> Regarding the length and the height, would they affect the curve and the
> arrow or the curve only?
>
> Cheers,
> Pierre
>
>
>
> 2017-03-06 3:58 GMT+01:00 Kieren MacMillan 
> :
>
>> Hi all,
>>
>> Anyone with reasonable \path chops out there? I need a function that
>> outputs a markup like this:
>>
>>
>> In a perfect world, the length, height, Y-direction, X-direction, and
>> line thickness would all be parameters… but even one sample would be enough
>> for me to riff on.
>>
>> Thanks!
>> Kieren.
>> 
>>
>> Kieren MacMillan, composer
>> ‣ website: www.kierenmacmillan.info
>> ‣ email: i...@kierenmacmillan.info
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user