lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Appoggiatura or no


From: kliewe
Subject: Appoggiatura or no
Date: Sat, 20 Jul 2013 10:17:48 -0400

David,  

Yes I like your approach much better. I had forgotten about the difference 
between using \times and using multiplication to show a tuplet.

--John K

Sent from my iPod

On Jul 16, 2013, at 2:52 AM, address@hidden wrote:

> Send lilypond-user mailing list submissions to
>    address@hidden
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    https://lists.gnu.org/mailman/listinfo/lilypond-user
> or, via email, send a message with subject or body 'help' to
>    address@hidden
> 
> You can reach the person managing the list at
>    address@hidden
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lilypond-user digest..."
> 
> 
> Today's Topics:
> 
>   1. Re:fermata on dotted notes on the top line (SoundsFromSound)
>   2. Re:fermata on dotted notes on the top line (Richard Shann)
>   3. Re:Appoggiatura or not appoggiatura? (David Rogers)
>   4. feature request: abs-fontsize available for all text grobs
>      (Kieren MacMillan)
>   5. Uneven note spacing (Andrew Bernard)
>   6. Re:feature request: abs-fontsize available for all text grobs
>      (Marc Hohl)
>   7. LSR preview broken? (Werner LEMBERG)
>   8. Dash one sibling of a slur/PhrasingSlur/Tie (Urs Liska)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 15 Jul 2013 09:38:39 -0700 (PDT)
> From: SoundsFromSound <address@hidden>
> To: address@hidden
> Subject: Re: fermata on dotted notes on the top line
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
> 
> Hmm, that does like quite bad.
> 
> But Eluze has the right idea:
> I would just use something like 
> 
> f''4.- \tweak #'padding #1 \fermata 
> 
> ...as a temporary fix :)
> 
> -Ben
> 
> 
> 
> Eluze wrote
>> 
>> Richard Shann wrote
>>> I don't know if this is the right forum for posting unfortunate examples
>>> of LilyPond's output but I came across this one:
>>> 
>>> \version "2.16"
>>> \score {
>>> f''4.\fermata
>>> }
>>> 
>>> The fermata seems connected visually with the dot on the note, it looks
>>> better to me dragged further away, which I have done for the score in
>>> question using Denemo.
>> this looks a bit ugly  - I'vel added an issue to the tracker
>> https://code.google.com/p/lilypond/issues/detail?id=3456&thanks=3456&ts=1373898751.
>> 
>> two quick workarounds:
>> 
>> f''4.- \tweak #'padding #2 \fermata
>> 
>> or
>> 
>> \dotsDown  f''4. \fermata
>> 
>> thank your Robert for reporting this
>> 
>> Eluze
> 
> 
> 
> 
> 
> -----
> composer | sound designer
> --
> View this message in context: 
> http://lilypond.1069038.n5.nabble.com/fermata-on-dotted-notes-on-the-top-line-tp148048p148050.html
> Sent from the User mailing list archive at Nabble.com.
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 15 Jul 2013 18:08:16 +0100
> From: Richard Shann <address@hidden>
> To: SoundsFromSound <address@hidden>
> Cc: address@hidden
> Subject: Re: fermata on dotted notes on the top line
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset="us-ascii"
> 
> What I actually used was a tweak to the offset, as I hadn't got round to
> adding padding as an option in Denemo; Eluze has pricked my conscience
> about this and I have now added an option to tweak the padding of such
> objects by right clicking on the typeset score and choosing Padding from
> the pop-up menu.
> 
> Richard
> 
> 
> On Mon, 2013-07-15 at 09:38 -0700, SoundsFromSound wrote:
>> Hmm, that does like quite bad.
>> 
>> But Eluze has the right idea:
>> I would just use something like 
>> 
>> f''4.- \tweak #'padding #1 \fermata 
>> 
>> ...as a temporary fix :)
>> 
>> -Ben
>> 
>> 
>> 
>> Eluze wrote
>>> 
>>> Richard Shann wrote
>>>> I don't know if this is the right forum for posting unfortunate examples
>>>> of LilyPond's output but I came across this one:
>>>> 
>>>> \version "2.16"
>>>> \score {
>>>> f''4.\fermata
>>>> }
>>>> 
>>>> The fermata seems connected visually with the dot on the note, it looks
>>>> better to me dragged further away, which I have done for the score in
>>>> question using Denemo.
>>> this looks a bit ugly  - I'vel added an issue to the tracker
>>> https://code.google.com/p/lilypond/issues/detail?id=3456&thanks=3456&ts=1373898751.
>>> 
>>> two quick workarounds:
>>> 
>>> f''4.- \tweak #'padding #2 \fermata
>>> 
>>> or
>>> 
>>> \dotsDown  f''4. \fermata
>>> 
>>> thank your Robert for reporting this
>>> 
>>> Eluze
>> 
>> 
>> 
>> 
>> 
>> -----
>> composer | sound designer
>> --
>> View this message in context: 
>> http://lilypond.1069038.n5.nabble.com/fermata-on-dotted-notes-on-the-top-line-tp148048p148050.html
>> Sent from the User mailing list archive at Nabble.com.
>> 
>> _______________________________________________
>> lilypond-user mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Mon, 15 Jul 2013 10:48:24 -0700
> From: David Rogers <address@hidden>
> To: "address@hidden" <address@hidden>
> Subject: Re: Appoggiatura or not appoggiatura?
> Message-ID: <address@hidden>
> Content-Type: text/plain
> 
> John Kliewe <address@hidden> writes:
> 
>> Many thanks to the lilypond-user group for their advice on measure #47
>> of the Chopin Nocturne #3 (Op 9 No 3). Urs' article on voices was
>> particularly helpful.
>> 
>> My next challenge appeared in measure #69. This is working for me :
>> 
>> \version "2.16.0"
>> \relative c'
>> { \clef treble
>> \time 6/8
>> \key b \major
>> ais'4.\p \once \override Slur #'stencil = ##f \appoggiatura {b8[\( ais
>> gisis ais]} 
>> << 
>> {dis4 b8} 
>> \new Voice 
>> {\stemUp 
>> \once \override TupletBracket #'bracket-visibility = ##f 
>> \once \override TupletNumber #'stencil = ##f 
>> \times 1/2 
>> {dis8 \teeny d cis c} 
>> \normalsize b8} 
>> \oneVoice
>> ais4 gis8\)
>> }
>> 
>> At first I assumed that both tuplets were appoggiatura, but I couldn't
>> get that to work. I also tried cue notes, but merging the head of a
>> cue note with a full-size note head was no good either. So my final
>> version (above) treats the first tuplet as an appoggiatura, but the
>> second is a new voice in a smaller font.
>> 
>> I'm delighted with the results. But I do wonder if anyone in the group
>> thinks I may have missed a better approach?
> 
> 
> Not better, but another possible way:
> 
> \version "2.16.0"
> \relative c'
> { \clef treble
> \time 6/8
> \key b \major
> ais'4.\p \once \override Slur #'stencil = ##f \appoggiatura {b8[\( ais
> gisis ais]} 
> << 
> {dis4 b8} 
> \new Voice 
> {\stemUp 
> { dis8*1/2[ \teeny d cis c} 
> \normalsize b8]} 
> \oneVoice
> ais4 gis8\)
> }
> 
> 
> -- 
> David R
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Mon, 15 Jul 2013 14:30:25 -0400
> From: Kieren MacMillan <address@hidden>
> To: Lilypond-User Mailing List <address@hidden>
> Subject: feature request: abs-fontsize available for all text grobs
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hello,
> 
> There are a lot of places where I would like to use abs-fontsize: 
> InstrumentName, LyricText, etc.
> 
> It would be nice if there were a built-in, intuitive, consistent, direct 
> method of setting an absolute font size, e.g.,
>    \override InstrumentName.font-size = #(abs-fontsize . 10)
> 
> How difficult would this be to implement?
> (I'm happy to contribute a few euros in sponsorship funds.)
> 
> Thanks,
> Kieren.
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Tue, 16 Jul 2013 14:14:12 +1000
> From: Andrew Bernard <address@hidden>
> To: lilypond-user <address@hidden>
> Subject: Uneven note spacing
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
> 
> Greetings List,
> 
> In the following example from a piece I am setting, the composer wants 
> the notes in the tuplets exactly evenly spaced, but I see considerable 
> unevenness here. There are two questions. First, is this really the 
> classical and canonical way to space tuplet notes when in the cross 
> staff situation here? Secondly, even if it is, how can I make them 
> evenly spaced out?
> 
> If I use proportional notation, the only way to spread them out evenly 
> is to use such a large value that the score becomes ridiculously widely 
> spaced.
> 
> The dodecaphonic accidental style is required in this piece.
> 
> Any help appreciated!
> 
> Andrew
> 
> ====
> 
> \version "2.17.21"
> 
> 
> \paper {
>   ragged-right = ##t
> }
> 
> % move to upper staff, stems down
> upsd = #(define-music-function (parser location) ()
>           #{
>             \change Staff = upper
>             \stemDown
>           #}
>           )
> 
> % move to lower staff, stems up
> downsu = #(define-music-function (parser location) ()
>             #{
>               \change Staff = lower
>               \stemUp
>             #}
>             )
> 
> 
> upper = \relative c'' {
>   \clef bass
>   \time 1/4
> 
>   s4 s4 s4 s4 s4 s4
> }
> 
> lower = \relative c {
>   \clef bass
>   \time 1/4
> 
>   \override TupletBracket.bracket-visibility = ##t
>   \tupletDown
> 
>     \tuplet 7/8 {
>     r16. a32^.[
>     \once \override Stem.beaming = #(cons (list 0 1 2) (list 1 2)) 
> \upsd g'_.
>     \once \override Stem.beaming = #(cons (list 0 1) (list -1 0 1)) f_.
>     \downsu bes,^.]
>   }
> 
>   \stemUp
>   \tuplet 7/8 {
>     ces32[ \upsd ces ces \downsu ces \upsd ces \upsd ces \downsu ces]
>   }
> 
>   c4 c4 c4 c4
> }
> 
> \score {
> 
>   <<
>     \new Staff = "upper" { \upper }
>     \new Staff = "lower" { \lower }
>   \layout {
>     \context {
>       \Score
>       \accidentalStyle Score.dodecaphonic
>     }
>   }
> }
> 
> 
> 
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://lists.gnu.org/archive/html/lilypond-user/attachments/20130716/3d271f10/attachment.html>
> 
> ------------------------------
> 
> Message: 6
> Date: Tue, 16 Jul 2013 08:22:38 +0200
> From: Marc Hohl <address@hidden>
> To: address@hidden
> Subject: Re: feature request: abs-fontsize available for all text
>    grobs
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=windows-1252; format=flowed
> 
> Am 15.07.2013 20:30, schrieb Kieren MacMillan:
>> Hello,
>> 
>> There are a lot of places where I would like to use abs-fontsize: 
>> InstrumentName, LyricText, etc.
>> 
>> It would be nice if there were a built-in, intuitive, consistent, direct 
>> method of setting an absolute font size, e.g.,
>>     \override InstrumentName.font-size = #(abs-fontsize . 10)
> 
> I had thought of such a feature some months ago; my syntax proposal
> would be something like
> 
> \set fontScaling = #absolute
> 
> or
> 
> \set fontScaling = #relative
> 
> perhaps with a better keyword.
> 
> By the way, a feature like this would come in handy for eps inclusions,
> too ? I remember that I had to define a \epsfile-mm command in
> analogy to the implemented \epsfile to allow for dimensions to be set
> in millimeters.
> 
>> 
>> How difficult would this be to implement?
> 
> My estimations in such situations go horribly wrong each time, so
> I just state "I don't know" for safety reasons ;-)
> 
> Marc
>> (I'm happy to contribute a few euros in sponsorship funds.)
>> 
>> Thanks,
>> Kieren.
>> _______________________________________________
>> lilypond-user mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> 
> 
> ------------------------------
> 
> Message: 7
> Date: Tue, 16 Jul 2013 08:34:49 +0200 (CEST)
> From: Werner LEMBERG <address@hidden>
> To: address@hidden
> Subject: LSR preview broken?
> Message-ID: <address@hidden>
> Content-Type: Text/Plain; charset=us-ascii
> 
> 
> I've just added a snippet to the LSR (`Percent repeat counters for
> piano music'), but I'm not able to preview it.  Since I don't have a
> 1.14 lilypond binary, I can't check whether the problem is in the file
> (it compiles fine with 1.16 and the current development version).
> However, even adding a very simple lilypond snippet which certainly
> displays fine doesn't succeed.  I thus wonder whether the LSR preview
> for non-approved snippets currently work at all...
> 
> 
>    Werner
> 
> 
> 
> ------------------------------
> 
> Message: 8
> Date: Tue, 16 Jul 2013 08:52:40 +0200
> From: Urs Liska <address@hidden>
> To: Lilypond-User <address@hidden>
> Subject: Dash one sibling of a slur/PhrasingSlur/Tie
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
> 
> Hi,
> 
> in an edition I prepare I often have the situation that I want to dash 
> one sibling of a Slur (because the original edition forgot to start a 
> slur  before the line break.
> 
> Is there a convenient way to do so without having to define two curves 
> and tweak them independently?
> 
> Thanks
> Urs
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> End of lilypond-user Digest, Vol 128, Issue 53
> **********************************************



reply via email to

[Prev in Thread] Current Thread [Next in Thread]