Re: Scheme predicative types

[Aaron Hill]

On 2020-09-16 4:13 pm, Aaron Hill wrote:

On 2020-09-16 12:09 pm, Lukas-Fabian Moser wrote:

I'm sure more knowledgeable people will be able to provide more
insightful answers, but for what it's worth: Looking at
lily/parser.yy, I see

tempo_event:
    TEMPO steno_duration '=' tempo_range    {
        $$ = MAKE_SYNTAX (tempo, @$, SCM_EOL, $2, $4);
    }
    | TEMPO text steno_duration '=' tempo_range    {
        $$ = MAKE_SYNTAX (tempo, @$, $2, $3, $5);
    }
    | TEMPO text {
        $$ = MAKE_SYNTAX (tempo, @$, $2);
    } %prec ':'
    ;

which I take to mean: The three forms

 * \tempo 4 = 96
 * \tempo Crazy 4 = 260-270
 * \tempo "Sluggishly slow"

are hardcoded as variants into the parser. My guess is that this might
be hard (or impossible) to accomplish in a music function.


You just need to be a little creative.  Consider:


\version "2.20.0"

#(define (tempo? arg)
  (and (ly:music? arg)
   (not (null? (extract-typed-music arg 'tempo-change-event)

doSomethingWithATempo =
#(define-void-function
  (tempo)
  (tempo?)
  (set! tempo (first (extract-typed-music tempo 'tempo-change-event)))
  (let ((tempo-unit (ly:prob-property tempo 'tempo-unit #f))
(metronome-count (ly:prob-property tempo 'metronome-count #f))
(text (ly:prob-property tempo 'text #f)))
(format #t "\nTempo: ~s"
  (list (cons 'tempo-unit tempo-unit)
(cons 'metronome-count metronome-count)
(cons 'text text)

\doSomethingWithATempo \tempo 4 = 60
\doSomethingWithATempo \tempo "Text" 4 = 60
\doSomethingWithATempo \tempo "Text"



GNU LilyPond 2.20.0
Processing `tempo-function.ly'
Parsing...
Tempo: ((tempo-unit . #) (metronome-count . 60) (text . 
#f))
Tempo: ((tempo-unit . #) (metronome-count . 60) (text . 
"Text"))

Tempo: ((tempo-unit . #f) (metronome-count . #f) (text . "Text"))
Success: compilation successfully completed



Oops, I meant to include a test case for a tempo range:


\doSomethingWithATempo \tempo "Text" 4 = 60-75



Tempo: ((tempo-unit . #) (metronome-count 60 . 75) (text . 
"Text"))



In summary, tempo-unit is ly:duration?; metronome-count is either 
number? or number-pair?; and text is markup?.



-- Aaron Hill

Re: Scheme predicative types

[Aaron Hill]

On 2020-09-16 12:09 pm, Lukas-Fabian Moser wrote:

I'm sure more knowledgeable people will be able to provide more
insightful answers, but for what it's worth: Looking at
lily/parser.yy, I see

tempo_event:
    TEMPO steno_duration '=' tempo_range    {
        $$ = MAKE_SYNTAX (tempo, @$, SCM_EOL, $2, $4);
    }
    | TEMPO text steno_duration '=' tempo_range    {
        $$ = MAKE_SYNTAX (tempo, @$, $2, $3, $5);
    }
    | TEMPO text {
        $$ = MAKE_SYNTAX (tempo, @$, $2);
    } %prec ':'
    ;

which I take to mean: The three forms

 * \tempo 4 = 96
 * \tempo Crazy 4 = 260-270
 * \tempo "Sluggishly slow"

are hardcoded as variants into the parser. My guess is that this might
be hard (or impossible) to accomplish in a music function.


You just need to be a little creative.  Consider:


\version "2.20.0"

#(define (tempo? arg)
  (and (ly:music? arg)
   (not (null? (extract-typed-music arg 'tempo-change-event)

doSomethingWithATempo =
#(define-void-function
  (tempo)
  (tempo?)
  (set! tempo (first (extract-typed-music tempo 'tempo-change-event)))
  (let ((tempo-unit (ly:prob-property tempo 'tempo-unit #f))
(metronome-count (ly:prob-property tempo 'metronome-count #f))
(text (ly:prob-property tempo 'text #f)))
(format #t "\nTempo: ~s"
  (list (cons 'tempo-unit tempo-unit)
(cons 'metronome-count metronome-count)
(cons 'text text)

\doSomethingWithATempo \tempo 4 = 60
\doSomethingWithATempo \tempo "Text" 4 = 60
\doSomethingWithATempo \tempo "Text"



GNU LilyPond 2.20.0
Processing `tempo-function.ly'
Parsing...
Tempo: ((tempo-unit . #) (metronome-count . 60) (text . 
#f))
Tempo: ((tempo-unit . #) (metronome-count . 60) (text . 
"Text"))

Tempo: ((tempo-unit . #f) (metronome-count . #f) (text . "Text"))
Success: compilation successfully completed



-- Aaron Hill

Re: Markups and small staves

[Martín Rincón Botero]

Thank you Lukas, that worked!

Am Mi., 16. Sept. 2020 um 21:29 Uhr schrieb Lukas-Fabian Moser :

> Hi Martín,
> Am 16.09.20 um 20:09 schrieb Martín Rincón Botero:
>
> how can I make a markup that ignores a \magnifyStaff command? Consider:
>
> oboe = \relative c' { c4^"markup" d e f }
> oboePart = \new Staff \with {
>   \magnifyStaff #5/7
> } \oboe
> piano = \relative c' { c4 d e f }\score {
>   <<
> \oboePart
> \piano
>   >>
>   \layout { }
> }
>
> I know I can just make a bigger markup for the magnified staff, but that
> wouldn't be a practical solution in my case, since said markups are gonna
> be in their independent variable (tempi) to be used by both staves.
>
> There is \abs-fontsize, for example:
>
> \version "2.21.6"
>
> oboe = \relative c' { c4^\markup { \abs-fontsize #12 "markup" } d e f }
> oboePart = \new Staff \with {
>   \magnifyStaff #5/7
> } \oboe
> piano = \relative c' { c4^\markup { \abs-fontsize #12 "markup" }  d e f
> }\score {
>   <<
> \oboePart
> \piano
>   >>
>   \layout { }
> }
>
> Best
> Lukas
>


-- 
www.martinrinconbotero.com

Re: Markups and small staves

[Lukas-Fabian Moser]

Hi Martín,

Am 16.09.20 um 20:09 schrieb Martín Rincón Botero:

how can I make a markup that ignores a \magnifyStaff command? Consider:

oboe = \relative c' { c4^"markup" d e f }
oboePart = \new Staff \with {
  \magnifyStaff #5/7
} \oboe
piano = \relative c' { c4 d e f }\score {
  <<
    \oboePart
    \piano
  >>
  \layout { }
}

I know I can just make a bigger markup for the magnified staff, but 
that wouldn't be a practical solution in my case, since said markups 
are gonna be in their independent variable (tempi) to be used by both 
staves.


There is \abs-fontsize, for example:

\version "2.21.6"

oboe = \relative c' { c4^\markup { \abs-fontsize #12 "markup" } d e f }
oboePart = \new Staff \with {
  \magnifyStaff #5/7
} \oboe
piano = \relative c' { c4^\markup { \abs-fontsize #12 "markup" } d e f 
}\score {

  <<
    \oboePart
    \piano
  >>
  \layout { }
}

Best
Lukas

Re: Scheme predicative types

[Martín Rincón Botero]

Thanks Lukas for your answer. I was fearing that it maybe can't be done
:-).

Am Mi., 16. Sept. 2020 um 21:09 Uhr schrieb Lukas-Fabian Moser :

> Hi,
>
> After struggling with understanding Lilypond/Scheme's predicative types,
> of which I found basically no documentation other than a list of them with
> a minimal description here
> http://lilypond.org/doc/v2.20/Documentation/notation/predefined-type-predicates,
> I would like to ask what type of predicatives the \tempo function accepts.
> When you write \tempo 4 = 56, what does "4 = 56" for Scheme mean? This is
> of course something that I'm not using in my script yet, but knowing this
> might let me extend the script, namely that its usage accepts a proper
> tempo definition, so that (maybe with a more elegant syntax that doesn't
> use "" for each argument) I can also use that same number to give to an
> omitted tempo marking for MIDI playback.
>
> I'm sure more knowledgeable people will be able to provide more insightful
> answers, but for what it's worth: Looking at lily/parser.yy, I see
>
> tempo_event:
> TEMPO steno_duration '=' tempo_range{
> $$ = MAKE_SYNTAX (tempo, @$, SCM_EOL, $2, $4);
> }
> | TEMPO text steno_duration '=' tempo_range{
> $$ = MAKE_SYNTAX (tempo, @$, $2, $3, $5);
> }
> | TEMPO text {
> $$ = MAKE_SYNTAX (tempo, @$, $2);
> } %prec ':'
> ;
>
> which I take to mean: The three forms
>
>- \tempo 4 = 96
>- \tempo Crazy 4 = 260-270
>- \tempo "Sluggishly slow"
>
> are hardcoded as variants into the parser. My guess is that this might be
> hard (or impossible) to accomplish in a music function.
>
> Best
> Lukas
>
>
>

-- 
www.martinrinconbotero.com

Re: Markups and small staves

[Martín Rincón Botero]

Hi Xavier,

thank you for your quick answer. This is all related to my messages
regarding the absence of a "tempo spanner" in Lilypond, and the ways I find
to circumvent that absence (namely, a simple "rit. _ _ _ _ quarter note =
X" can't be natively done in Lilypond). Certainly using a \mark command
would be better (also because I could make the tempo attach to the time
signature, instead of messing around with \halign values), but I have no
idea how to make a spanner inside a \mark (the dashed line that connects
the rit. with the new tempo). Is that possible inside a \mark?

Regards,
Martín.

Am Mi., 16. Sept. 2020 um 21:16 Uhr schrieb Xavier Scheuer <
x.sche...@gmail.com>:

> On Wed, 16 Sep 2020 at 20:10, Martín Rincón Botero <
> martinrinconbot...@gmail.com> wrote:
> >
> > Hello again,
> >
> > how can I make a markup that ignores a \magnifyStaff command? Consider:
> >
> > oboe = \relative c' { c4^"markup" d e f }
> > oboePart = \new Staff \with {
> >   \magnifyStaff #5/7
> > } \oboe
> > piano = \relative c' { c4 d e f }\score {
> >   <<
> > \oboePart
> > \piano
> >   >>
> >   \layout { }
> > }
> >
> > I know I can just make a bigger markup for the magnified staff, but that
> wouldn't be a practical solution in my case, since said markups are gonna
> be in their independent variable (tempi) to be used by both staves.
> >
>
> Hello Martin,
>
> I don't get it.
> Your "markup" command is a TextScript object, which is engraved by
> the Text_engraver at the Voice level.
> Voice context is contained within Staff context.
> By using \magnifyStaff command you basically ask LilyPond to reduce the
> size of the objects of this Staff, which apply to the objects of the
> voice(s) contained in this Staff.
>
> So my suggestion would be either to use a proper text mark (command \mark
> or \tempo), which are engraved at the Score level, which would then be
> "above" the Staff context and then not affected by the \magnifyStaff
> command, or to reset the size of the TextScripts within your smaller staff
> (which you dismiss). I would suggest the first solution.
>
> Cheers,
> Xavier
>
> --
> Xavier Scheuer 
>
>

-- 
www.martinrinconbotero.com

Re: Markups and small staves

[Xavier Scheuer]

On Wed, 16 Sep 2020 at 20:10, Martín Rincón Botero <
martinrinconbot...@gmail.com> wrote:
>
> Hello again,
>
> how can I make a markup that ignores a \magnifyStaff command? Consider:
>
> oboe = \relative c' { c4^"markup" d e f }
> oboePart = \new Staff \with {
>   \magnifyStaff #5/7
> } \oboe
> piano = \relative c' { c4 d e f }\score {
>   <<
> \oboePart
> \piano
>   >>
>   \layout { }
> }
>
> I know I can just make a bigger markup for the magnified staff, but that
wouldn't be a practical solution in my case, since said markups are gonna
be in their independent variable (tempi) to be used by both staves.
>

Hello Martin,

I don't get it.
Your "markup" command is a TextScript object, which is engraved by
the Text_engraver at the Voice level.
Voice context is contained within Staff context.
By using \magnifyStaff command you basically ask LilyPond to reduce the
size of the objects of this Staff, which apply to the objects of the
voice(s) contained in this Staff.

So my suggestion would be either to use a proper text mark (command \mark
or \tempo), which are engraved at the Score level, which would then be
"above" the Staff context and then not affected by the \magnifyStaff
command, or to reset the size of the TextScripts within your smaller staff
(which you dismiss). I would suggest the first solution.

Cheers,
Xavier

-- 
Xavier Scheuer 

Re: Scheme predicative types

[Lukas-Fabian Moser]

Hi,

After struggling with understanding Lilypond/Scheme's predicative 
types, of which I found basically no documentation other than a list 
of them with a minimal description here 
http://lilypond.org/doc/v2.20/Documentation/notation/predefined-type-predicates, 
I would like to ask what type of predicatives the \tempo function 
accepts. When you write \tempo 4 = 56, what does "4 = 56" for Scheme 
mean? This is of course something that I'm not using in my script yet, 
but knowing this might let me extend the script, namely that its usage 
accepts a proper tempo definition, so that (maybe with a more elegant 
syntax that doesn't use "" for each argument) I can also use that same 
number to give to an omitted tempo marking for MIDI playback.


I'm sure more knowledgeable people will be able to provide more 
insightful answers, but for what it's worth: Looking at lily/parser.yy, 
I see


tempo_event:
    TEMPO steno_duration '=' tempo_range    {
        $$ = MAKE_SYNTAX (tempo, @$, SCM_EOL, $2, $4);
    }
    | TEMPO text steno_duration '=' tempo_range    {
        $$ = MAKE_SYNTAX (tempo, @$, $2, $3, $5);
    }
    | TEMPO text {
        $$ = MAKE_SYNTAX (tempo, @$, $2);
    } %prec ':'
    ;

which I take to mean: The three forms

 * \tempo 4 = 96
 * \tempo Crazy 4 = 260-270
 * \tempo "Sluggishly slow"

are hardcoded as variants into the parser. My guess is that this might 
be hard (or impossible) to accomplish in a music function.


Best
Lukas

Markups and small staves

[Martín Rincón Botero]

Hello again,

how can I make a markup that ignores a \magnifyStaff command? Consider:

oboe = \relative c' { c4^"markup" d e f }
oboePart = \new Staff \with {
  \magnifyStaff #5/7
} \oboe
piano = \relative c' { c4 d e f }\score {
  <<
\oboePart
\piano
  >>
  \layout { }
}

I know I can just make a bigger markup for the magnified staff, but that
wouldn't be a practical solution in my case, since said markups are gonna
be in their independent variable (tempi) to be used by both staves.

Best regards,
Martín.
-- 
www.martinrinconbotero.com

RE: left-hand marking

[Mark Stephen Mrotek]

Tom, 

 

Welcome.

 

Mark

 

From: Tom Sgouros [mailto:tomf...@as220.org] 
Sent: Wednesday, September 16, 2020 9:08 AM
To: Mark Stephen Mrotek 
Cc: lilypond-user@gnu.org
Subject: Re: left-hand marking

 

Thank you. Had to hunt for "thumbBracket.ily", but this has the output I want, 
even if I was hoping for simpler.

 

And thank you also for the arpeggiobracket suggestion. That might also work.

 

 -Tom

 

On Wed, Sep 16, 2020 at 11:05 AM Mark Stephen Mrotek mailto:carsonm...@ca.rr.com> > wrote:

Tom,

 

I do not know of a canonical way, yet here is code the create “thumb brackets.”

 

Mark

 

https://lists.gnu.org/archive/html/lilypond-user/2015-11/txt6sGQp9BPp7.txt

 

 

 

From: lilypond-user [mailto:lilypond-user-bounces+carsonmark 
 =ca.rr@gnu.org 
 ] On Behalf Of Tom Sgouros
Sent: Wednesday, September 16, 2020 5:28 AM
To: lilypond-user@gnu.org  
Subject: left-hand marking

 

Hello all:

 

How does one mark notes that should be played with the other hand in piano 
music?

 

I'm thinking about notes in the treble clef that should be played with the left 
hand crossed over, or notes at the top of a bass clef chord that should be 
played with the right hand. 

 

I've seen brackets extending from the other clef, for the chord, as well as 
little "L.H" marks. (Or "M.S." or "M.D." depending.) Is there a 
Lilypond-canonical way to indicate this?

 

Thank you,

 

 -Tom

Scheme predicative types

[Martín Rincón Botero]

Dear all,

I just started writing my first scheme function :-). It basically
substitutes for now our lack of a "tempo spanners" syntax, something that I
still find quite irritating in Lilypond. It accepts a quite "clumsy" set of
arguments, namely two markups for tempo and two "numbers" for padding. The
little script looks like this

% usage
% \ritToMetronomeMark "Lilypond duration" "= "$yourtempo" #$left-padding
#$right-padding
% $music\startTextSpan $music\stopTextSpan

ritToMetronomeMark = #(define-music-function
   (parser location notemarkup tempomarkup paddingleft
paddingright)
   (markup? markup? number? number?)
   #{
\once \override TextSpanner #'(bound-details left text) =  \markup \halign
#paddingleft {"rit."}
\once \override TextSpanner #'(bound-details right text) = \markup \halign
#paddingright { \general-align #Y #DOWN \smaller \note #notemarkup #1
\upright #tempomarkup }
   #})

accelToMetronomeMark = #(define-music-function
   (parser location notemarkup tempomarkup paddingleft
paddingright)
   (markup? markup? number? number?)
   #{
\once \override TextSpanner #'(bound-details left text) =  \markup \halign
#paddingleft {"accel."}
\once \override TextSpanner #'(bound-details right text) = \markup \halign
#paddingright { \general-align #Y #DOWN \smaller \note #notemarkup #1
\upright #tempomarkup }
   #})

After struggling with understanding Lilypond/Scheme's predicative types, of
which I found basically no documentation other than a list of them with a
minimal description here
http://lilypond.org/doc/v2.20/Documentation/notation/predefined-type-predicates,
I would like to ask what type of predicatives the \tempo function accepts.
When you write \tempo 4 = 56, what does "4 = 56" for Scheme mean? This is
of course something that I'm not using in my script yet, but knowing this
might let me extend the script, namely that its usage accepts a proper
tempo definition, so that (maybe with a more elegant syntax that doesn't
use "" for each argument) I can also use that same number to give to an
omitted tempo marking for MIDI playback.

Best regards,
Martín.

-- 
www.martinrinconbotero.com

Re: left-hand marking

[Tom Sgouros]

Thank you. Had to hunt for "thumbBracket.ily", but this has the output I
want, even if I was hoping for simpler.

And thank you also for the arpeggiobracket suggestion. That might also work.

 -Tom

On Wed, Sep 16, 2020 at 11:05 AM Mark Stephen Mrotek 
wrote:

> Tom,
>
>
>
> I do not know of a canonical way, yet here is code the create “thumb
> brackets.”
>
>
>
> Mark
>
>
>
> https://lists.gnu.org/archive/html/lilypond-user/2015-11/txt6sGQp9BPp7.txt
>
>
>
>
>
>
>
> *From:* lilypond-user [mailto:lilypond-user-bounces+carsonmark=
> ca.rr@gnu.org] *On Behalf Of *Tom Sgouros
> *Sent:* Wednesday, September 16, 2020 5:28 AM
> *To:* lilypond-user@gnu.org
> *Subject:* left-hand marking
>
>
>
> Hello all:
>
>
>
> How does one mark notes that should be played with the other hand in piano
> music?
>
>
>
> I'm thinking about notes in the treble clef that should be played with the
> left hand crossed over, or notes at the top of a bass clef chord that
> should be played with the right hand.
>
>
>
> I've seen brackets extending from the other clef, for the chord, as well
> as little "L.H" marks. (Or "M.S." or "M.D." depending.) Is there a
> Lilypond-canonical way to indicate this?
>
>
>
> Thank you,
>
>
>
>  -Tom
>

RE: left-hand marking

[Mark Stephen Mrotek]

Tom,

 

I do not know of a canonical way, yet here is code the create “thumb brackets.”

 

Mark

 

https://lists.gnu.org/archive/html/lilypond-user/2015-11/txt6sGQp9BPp7.txt

 

 

 

From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] 
On Behalf Of Tom Sgouros
Sent: Wednesday, September 16, 2020 5:28 AM
To: lilypond-user@gnu.org
Subject: left-hand marking

 

Hello all:

 

How does one mark notes that should be played with the other hand in piano 
music?

 

I'm thinking about notes in the treble clef that should be played with the left 
hand crossed over, or notes at the top of a bass clef chord that should be 
played with the right hand. 

 

I've seen brackets extending from the other clef, for the chord, as well as 
little "L.H" marks. (Or "M.S." or "M.D." depending.) Is there a 
Lilypond-canonical way to indicate this?

 

Thank you,

 

 -Tom

Re: Questions about HorizontalBracket

[Francesco Napoleoni]

In data martedì 15 settembre 2020 12:58:19 CEST, Lukas-Fabian Moser ha 
scritto:
> Hi Francesco,
> 
> > Thank you very much, Lukas! :-) Your answer goes far beyond my
> > expectations: using slurs is a very good point.
> > [...]
> > Anyway, let’s see if I understand the big picture of your code:
> > 1. you define some pure Scheme functions that deal about creating the
> > basic
> > “shapes” (actually the vectors that will be used by the “path” command);
> > 2. then you define the commands that tweak the stencil of a Slur grob;
> > 3. and, like a “tweak” command, you call it just before the parentheses,
> > letting the magic happen, right?
> 
> Yes, that basically is the picture. I created a second version that not
> only should have a clearer structure (because now the creation of the
> shapes is factored out into two custom-made markup functions) but is
> also heavily commented.
> 
> I have a plan to create some examples of "LilyPond programming with
> annotations" (for the dual purpose of enlightening myself and helping
> others on their path), so feel free to comment and ask questions.

That would be great. Indeed for me it’s not as hard to learn the Guile 
language as to understand the internal structures of Lilypond and their 
relation with the language. So, a collection of commented examples could be 
very helpful.


> > By the way, the code does not compile with my old 2.19.83 version
> [...]
> My bad: I hadn't realized that the invaluable \=... mechanism [...] wasn't
> contained in 2.19.83. Sorry.

No problem: as a matter of fact it’s definitely time for me to upgrade my 
software to a more recent version. ;-)

cheers
Francesco Napoleoni

Re: left-hand marking

[Martín Rincón Botero]

Hi Tom,

perhaps \arpeggioBracket does what you want?
https://lilypond.org/doc/v2.20/Documentation/notation/expressive-marks-as-lines#arpeggio

Cheers,
Martín.

On Wed 16. Sep 2020 at 14:30 Tom Sgouros  wrote:

> Hello all:
>
> How does one mark notes that should be played with the other hand in piano
> music?
>
> I'm thinking about notes in the treble clef that should be played with the
> left hand crossed over, or notes at the top of a bass clef chord that
> should be played with the right hand.
>
> I've seen brackets extending from the other clef, for the chord, as well
> as little "L.H" marks. (Or "M.S." or "M.D." depending.) Is there a
> Lilypond-canonical way to indicate this?
>
> Thank you,
>
>  -Tom
>
>
> --
www.martinrinconbotero.com

left-hand marking

[Tom Sgouros]

Hello all:

How does one mark notes that should be played with the other hand in piano
music?

I'm thinking about notes in the treble clef that should be played with the
left hand crossed over, or notes at the top of a bass clef chord that
should be played with the right hand.

I've seen brackets extending from the other clef, for the chord, as well as
little "L.H" marks. (Or "M.S." or "M.D." depending.) Is there a
Lilypond-canonical way to indicate this?

Thank you,

 -Tom

Re: Mail an Charite

[Martín Rincón Botero]

Ich hoffe, Prof. Dr. Blöchl hat festgestellt, dass das hier die
Lilypond-Liste ist ;-).

On Wed 16. Sep 2020 at 11:14 bb  wrote:

>
>
>
>
>
>
>
>
>
>
>
>
> Ich nehme besser direkt Kontakt zu Benjamin Franklin auf? Dann
>
> Dr. med. ASafwan Omran
>
>
>
>
>
>
>
>
>
>
>  Weitergeleitete Nachricht 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Betreff:
>
>
> Mail an Charite
>
>
> Datum:
> Wed, 16 Sep 2020 11:12:09 +0200
>
>
> Von:
> bb  
>
>
> An:
> Ulrike Brodkorb 
> 
>
>
>
>
>
>
>
>
>
>
> Sehr geehrter Prof. Dr. med. univ. Andreas Greiner
>
>
>
>
>
> Meine Untersuchung ergibt den  (Zitat) „Verdacht auf hochgradige
>
> ACI Stenose rechts DD Oklusion“. Nach Mitteilung der beteiligten
>
> Ärzte ist eine Operation erforderlich.
>
>
>
>
>
> Es liegt eine CD mit den CT-Daten der Untersuchung im
>
> CT-MRTinstitut Berlin vor und ein Untersuchungsbericht von Prof.
>
> Dr. med. Clemens Fitzek .
>
>
>
>
>
> Ich bin privat bei der Allianz versichert, Prof. Dr.-Ing. Bernhard
>
> Blöchl, 22.04.1949.
>
>
>
>
>
> Ich bitte zunächst um einen Beratungstermin im Gefäßzentrum und
>
> möglicherweise Vereinbarung eines Operationstermins, falls diese
>
> empfohlen wird.
>
>
>
>
>
> Mit freundlichen Grüßen
>
>
> Prof. Dr-Ing. Bernhard Blöchl
>
>
>
>
>
>
>
>
>
>
>
> --
www.martinrinconbotero.com

Fwd: Mail an Charite

[bb]

Ich nehme besser direkt Kontakt zu Benjamin Franklin auf? Dann Dr. med. 
ASafwan Omran




 Weitergeleitete Nachricht 
Betreff:Mail an Charite
Datum:  Wed, 16 Sep 2020 11:12:09 +0200
Von:bb 
An: Ulrike Brodkorb 



Sehr geehrter Prof. Dr. med. univ. Andreas Greiner

Meine Untersuchung ergibt den  (Zitat) „Verdacht auf hochgradige ACI 
Stenose rechts DD Oklusion“. Nach Mitteilung der beteiligten Ärzte ist 
eine Operation erforderlich.


Es liegt eine CD mit den CT-Daten der Untersuchung im CT-MRTinstitut 
Berlin vor und ein Untersuchungsbericht von Prof. Dr. med. Clemens Fitzek .


Ich bin privat bei der Allianz versichert, Prof. Dr.-Ing. Bernhard 
Blöchl, 22.04.1949.


Ich bitte zunächst um einen Beratungstermin im Gefäßzentrum und 
möglicherweise Vereinbarung eines Operationstermins, falls diese 
empfohlen wird.


Mit freundlichen Grüßen
Prof. Dr-Ing. Bernhard Blöchl

Re: Vertical position of rests in DrumVoice

[David Sumbler]

On Tue, 2020-09-15 at 11:57 +0100, David Sumbler wrote:
> I am having difficulty controlling the vertical postioning of rests
> in
> a DrumStaff which has several DrumVoices representing different
> instruments.
> 
> The easy method of using a note-name followed by '\rest' doesn't seem
> to work in a DrumStaff.  I have tried, for instance, 'sn8\rest', but
> this produces a syntax error.
> 
> The other method I tried is overriding Rest.voiced-position and
> MultiMeasureRest.voiced-position in the relevant Voice context, but
> this seems to work inconsistently - something else is overriding it. 
> And in the case of the MultiMeasureRest nothing I do will move a
> whole-
> bar rest below the bottom line of the staff, even though in the same
> voice minim rests are being placed one or two lines below the staff
> by
> Lilypond itself.
> 
> How do I take full control of the vertical positioning of these
> rests?

My apologies to all on the list for wasting bandwidth.  I eventually
stumbled on the answer to my question, which is to use
\override Rest.staff-position = 6
and
\override MultiMeasureRest.staff-position = 6
or similar.

The relevant variable is hidden away in the Internals Reference under
"staff-symbol-referencer-interface".  I confess that, although I had
looked at the lists of variables under the all the other interfaces
listed at the bottom of the IR pages for Rest etc., I hadn't looked at
this one because the name is so unpromising.

Yet I now find that the only variable listed there is the very one I
wanted!

David

Re: Scrape around rim

[Martín Rincón Botero]

Thank you, Andrew, for the explanation! I was reading yesterday about it
but I couldn't find what to do exactly for this use case. That is so simple
to use is amazing!

Regards,
Martín.

On Wed 16. Sep 2020 at 02:33 Andrew Bernard 
wrote:

> Once you install openlilylib, here's how to do it:
>
>
>
> \version "2.21.5"
>
>
>
> \include "custom-music-fonts/smufl/definitions.ily"
>
>
>
> {
>
>   c''4
>
>   ^\markup { \fontsize #0 \smuflglyph #"pictScrapeAroundRim" }
>
>   c'' c'' c''
>
>
>
> }
>
>
>
> You just use the names in the SmuFL spec pages.
>
>
>
> OLL now has a package system, but this function has not yet been moved
>
> across. Still works fine.
>
>
>
> Obviously you need to set up your path appropriately.
>
>
>
>
>
> Andrew
>
> --
www.martinrinconbotero.com