Re: Telemann's "Strich"
I think he should adhere to the original look and feel. After all the work is entirely embedded in the 18c cultural milieu – figured bass practice, can’t get much more 18c than that – and the urge to squash everything into our Barenreiter Common Era practice look and feel should be relaxed somewhat occasionally. This is really closely related to the seemingly unpopular thread recently on curved beams. I for one take effort to make my contemporary scores match the aesthetic of the composer they are from, and my 18c scores to have some sort of 18c feel where possible. Perhaps I should buy some copper sheet and a set of gravers. :-) Andrew On 21/12/2015, 11:10, "Simon Albrecht" wrote: For a reengraving it’s definitely better to have them outside the staff, together with the actual figures. One shouldn’t try sticking too closely to the appearance of 18th century writing/engraving. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Telemann's "Strich"
How about this:
\version "2.19.33"
{
\clef bass
\time 3/8
c8 a, gis,
\stemUp a,8 \stemDown a^\markup { \draw-line #'(4 . -1) } g
}
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Telemann's "Strich"
Hi Andrew, Decapitated arrows as stiff slurs. Why not? Perhaps I would like to try it, some day. (But as a LilyPond newbie there are many more urgent things I have to learn now.) But also I have to decide whether or not to copy Telemann's Strich in the modern version. That depends on whether they are really and only figured bass extenders, as has been argued in this thread, for which there is a more official visual marking, or whether it is just Telemann's way of indicating that the accompaying keyboard player should not play or add chords beyond the first note of such a "slurred" bass progression. As for your last remark: I would consider it as a very harmless manifestation of human greed. Best regards, Robert PS While I was writing this reply your next mail(s) arrived. Ref.: "I think he should adhere to the original look and feel." I fully agree, and that is what I intend to do, the more so since "Telemann's Strich" does not seem to be identical with a figured bass extender in all occurrences. Thanks for this comment. On 21 Dec 2015, at 00:16 , Andrew Bernard wrote: > Interesting! > > I have a generalised arrow drawing function that draws arrows of any length > in any rotational position, done in Scheme. If I removed the arrowhead, do > you think that would be useful? My arrows are not tapered lines, but of > uniform thickness. > > Amusingly, recently we wanted curved beams. Now we want straight slurs! > > Andrew > > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Telemann's "Strich"
Andrew Bernard writes: > I think he should adhere to the original look and feel. After all the > work is entirely embedded in the 18c cultural milieu – figured bass > practice, can’t get much more 18c than that – and the urge to squash > everything into our Barenreiter Common Era practice look and feel > should be relaxed somewhat occasionally. This is really closely > related to the seemingly unpopular thread recently on curved beams. I > for one take effort to make my contemporary scores match the aesthetic > of the composer they are from, and my 18c scores to have some sort of > 18c feel where possible. Perhaps I should buy some copper sheet and a > set of gravers. :-) The point of an Urtext is to convey the same musical information as the original (usually a manuscript) using modern typography. That very much is in line with "squash everything into our Barenreiter Common Era practice look and feel". Realistically, that's what a program like LilyPond is able to support reliably with realistic effort. If you instead want to reinvent 18th century visual aesthetics, you'll either be writing and maintaining your own versions of computer typesetting programs and algorithms, or you are indeed best served with acquiring the traditional tools of the trade. However, don't underestimate the tool set of the 18th century: you'll invest a lot of money and effort to come anywhere even close to best practices. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Telemann's "Strich"
On 21 Dec 2015, at 09:43 , Andrew Bernard wrote:
> How about this:
>
> \version "2.19.33"
>
> {
> \clef bass
> \time 3/8
> c8 a, gis,
> \stemUp a,8 \stemDown a^\markup { \draw-line #'(4 . -1) } g
> }
>
> Andrew
>
Beautiful!
Many thanks.
Robert___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-user Digest, Vol 157, Issue 92
ctive. That's what I learned in my clarinet and saxophone lessons. HTH, Klaus -- View this message in context: http://lilypond.1069038.n5.nabble.com/saxophon-multiphonic-how-to-tp184913p184925.html Sent from the User mailing list archive at Nabble.com. -- Message: 3 Date: Mon, 21 Dec 2015 10:16:56 +1100 From: Andrew Bernard To: Robert Blackstone , Subject: Re: Telemann's "Strich" Message-ID: <1aec1967-e341-4588-913c-88b57cef5...@gmail.com> Content-Type: text/plain; charset="utf-8" Interesting! I have a generalised arrow drawing function that draws arrows of any length in any rotational position, done in Scheme. If I removed the arrowhead, do you think that would be useful? My arrows are not tapered lines, but of uniform thickness. Amusingly, recently we wanted curved beams. Now we want straight slurs! Andrew -- next part -- An HTML attachment was scrubbed... URL: <http://lists.gnu.org/archive/html/lilypond-user/attachments/20151221/576c14ec/attachment.html> -- Message: 4 Date: Mon, 21 Dec 2015 00:25:18 +0100 From: Thomas Morley To: Kieren MacMillan Cc: Lilypond-User Mailing List Subject: Re: big (?) challenge: multi-segment / multi-angle OttavaBracket Message-ID: Content-Type: text/plain; charset=UTF-8 2015-12-20 23:50 GMT+01:00 Kieren MacMillan : HOLY MOLY! This is fabulous. Glad you like it. 1. Yes, it appears (at least, from your snippet) to do exactly what I want; I will test it ?in production", and report back ASAP. Though, I'm afraid you will surely notice the disadvantages soon. 2. Let me know (off-line, if desired) what a reasonable fee is for your work; I?ll definitely pay you something. This code isn't ready to be implemented into the source, maybe (and its a big maybe) into LSR. It's an extended variation of some code I made for a user in the german forum some time ago and based on Mike Solomon's fix for https://sourceforge.net/p/testlilyissues/issues/3230/ No need for any payment to me. You may want to donate something to David K. who really needs it. Without his fabulous work I would be far less effective helping on the user-list. His work is not always directly noticeable/user-accessible, but every time I look up how codings were done in past lily-versions I see again how good LilyPond developed, most basic work was David's! Speaking only for me, bounties doesn't attract me. An interesting problem, good presented (sic) and I'm on it. Well, if I've the time for it... Every layout-change will likely result in the need of readjusting? That?s fine by me, at least in the short term: I can do all of the tweaking in the edition-engraver (post-layout). I didn't use the edition-engraver so far, can't say if it will work It would be far simpler if one could add an option to make-path-stencil to draw dashed lines. But I found no way to do so. Thus I defined `make-dashed-line-stencil' and `make-connected-dashed-line-stencil' first. With `kneed-line' I try to give you a little easier to use code at hand, but I'm really not convinced. Well, if anyone else finds this idea worth pursuing/sponsoring, perhaps we can crowd-source your code into an awesome patch!? I'm not sure a patch will be possible, at least with _this_ approach. But maybe with some other, lemme think about it ... Thanks again! I?ll report back soon. Cheers, Kieren. Cheers, Harm -- Message: 5 Date: Mon, 21 Dec 2015 10:34:37 +1100 From: Andrew Bernard To: Robert Blackstone , Subject: Re: Telemann's "Strich" Message-ID: <0dfc5414-2210-4e64-a7d1-53b05960d...@gmail.com> Content-Type: text/plain; charset="utf-8" Of course I just realised you don?t need the full generality of my arrow function. You can just use the draw-line function. It?s in the section ?Graphic notation inside markup?. Andrew -- next part -- An HTML attachment was scrubbed... URL: <http://lists.gnu.org/archive/html/lilypond-user/attachments/20151221/fa27ebd9/attachment.html> -- Message: 6 Date: Sun, 20 Dec 2015 19:02:44 -0500 From: Kieren MacMillan To: Thomas Morley Cc: Lilypond-User Mailing List Subject: Re: big (?) challenge: multi-segment / multi-angle OttavaBracket Message-ID: <800e24c0-31d1-46da-a15e-2e0728f8d...@sympatico.ca> Content-Type: text/plain; charset=utf-8 Hi Harm, Though, I'm afraid you will surely notice the disadvantages soon. Well, maybe I already have? but it?s still impressive. =) You may want to donate something to David K. who really needs it. There seems to be a problem with PayPal at the moment; as soon as it clears up, I will send DK a payment. More anon, Kieren. Kieren MacMillan, com
Digest quoting (was: lilypond-user Digest, Vol 157, Issue 92)
Simon Albrecht writes: > Pardon, did you want to include any text with this e-mail? > Also please remember editing the subject line. Simon, how many copies of this weekly digest do you think we'll want fully quoted in the next weekly digest? Chain letters tend to include some "don't break the chain" admonishment. With regard to digest fullquotes, it is _essential_ to break the chain. Thank you. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Digest quoting
On 21.12.2015 10:24, David Kastrup wrote: Simon Albrecht writes: Pardon, did you want to include any text with this e-mail? Also please remember editing the subject line. Simon, how many copies of this weekly digest do you think we'll want fully quoted in the next weekly digest? Chain letters tend to include some "don't break the chain" admonishment. With regard to digest fullquotes, it is _essential_ to break the chain. Sorry for not doing so and thanks for doing so :-) Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Digest quoting
Simon Albrecht writes: > On 21.12.2015 10:24, David Kastrup wrote: >> Simon Albrecht writes: >> >>> Pardon, did you want to include any text with this e-mail? >>> Also please remember editing the subject line. >> Simon, how many copies of this weekly digest do you think we'll want >> fully quoted in the next weekly digest? >> >> Chain letters tend to include some "don't break the chain" admonishment. >> With regard to digest fullquotes, it is _essential_ to break the chain. > > Sorry for not doing so and thanks for doing so :-) It will be broken if nobody fullquotes this week's digest after it has come out. The jury is still out on that one. I merely did not inflate the number of fullquoted digests this week from 2 to even more. Let's hope that next week's number will be 0. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Writing converter to display Notes as Numbers
Hello
I was very happy when I found lilypond . It is ingenious and simple and can
be carried out so versatile . Since a while I 'm looking for a software
with which I can write notes in numbers .
something like that:
#(define Ez_numbers_engraver
(make-engraver
(acknowledgers
((note-head-interface engraver grob source-engraver)
(let* ((context (ly:translator-context engraver))
(tonic-pitch (ly:context-property context 'tonic))
(tonic-name (ly:pitch-notename tonic-pitch))
(grob-pitch
(ly:event-property (event-cause grob) 'pitch))
(grob-name (ly:pitch-notename grob-pitch))
(delta (modulo (- grob-name tonic-name) 7))
(note-names
(make-vector 7 (number->string (1+ delta)
(ly:grob-set-property! grob 'note-names note-names))
#(set-global-staff-size 26)
\layout {
ragged-right = ##t
\context {
\Voice
\consists \Ez_numbers_engraver
}
}
\relative c' {
\easyHeadsOn
c4 d e f
g4 a b c \break
\key a \major
a,4 b cis d
e4 fis gis a \break
\key d \dorian
d,4 e f g
a4 b c d
}
but I need more than only display numbers in noteheads. My intension is to
write songs which looks like this:
https://www.dropbox.com/s/0zw7cszpbi29wwb/01_SILENT%20NIGHT.PDF?dl=0
I would be very happy, finding anyone who could help me to write a
converter to make it possible switching for a note to a number sight.
Thanks!
Waldemar
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Writing converter to display Notes as Numbers
Merk Waldemar writes: > but I need more than only display numbers in noteheads. My intension is to > write songs which looks like this: > https://www.dropbox.com/s/0zw7cszpbi29wwb/01_SILENT%20NIGHT.PDF?dl=0 You presumably mean Jianpu https://en.wikipedia.org/wiki/Numbered_musical_notation>. If I remember correctly, there are no finished solutions. One would likely take a look at how tablatures are implemented and work from there. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Writing converter to display Notes as Numbers
Am 21.12.2015 um 12:12 schrieb David Kastrup: You presumably mean Jianpu https://en.wikipedia.org/wiki/Numbered_musical_notation>. From the article: “There are technical methods of printing numbered notation (in various forms) with GNU LilyPond.[10][11][12]” You might want to look at these references 10 to 12 ;) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Writing converter to display Notes as Numbers
Malte Meyn writes: > Am 21.12.2015 um 12:12 schrieb David Kastrup: >> You presumably mean Jianpu >> https://en.wikipedia.org/wiki/Numbered_musical_notation>. > > From the article: > “There are technical methods of printing numbered notation (in various > forms) with GNU LilyPond.[10][11][12]” > > You might want to look at these references 10 to 12 ;) I'm years behind getting the stuff I actually use working in LilyPond, so it's certainly not me who is going to do the bulk of the implementation. I'm likely to contribute occasional help to such an endeavor, particularly when there are hard roadblocks. But I'm not going to be the driving force. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-user Digest, Vol 157, Issue 92
> On Dec 21, 2015, at 3:10 AM, Simon Albrecht wrote: > > Pardon, did you want to include any text with this e-mail? > Also please remember editing the subject line. > > Yours, Simon > No, it was an error, completely inadvertent. Please accept my abject apologies. Pat Karl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
tweaking only the broken part of a pedal bracket
Hello all, What is the right incantation for tweaking just the broken part of a pedal bracket/line, e.g., \once \override PianoPedalBracket.broken.extra-offset = #’(0 . 1) ?? I’m on 2.19.31, in case that makes a difference. 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 only the broken part of a pedal bracket
Hi Kieren, On Mon, Dec 21, 2015 at 4:30 PM, Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hello all, > > What is the right incantation for tweaking just the broken part of a pedal > bracket/line, e.g., > > \once \override PianoPedalBracket.broken.extra-offset = #’(0 . 1) > > ?? > > I’m on 2.19.31, in case that makes a difference. > Try \alterBroken extra-offset #'(() (0 . 1)) Staff.PianoPedalBracket See http://lilypond.org/doc/v2.19/Documentation/notation/modifying-broken-spanners HTH, David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tweaking only the broken part of a pedal bracket
Hi David, > See > http://lilypond.org/doc/v2.19/Documentation/notation/modifying-broken-spanners Perfect. Apologies that I didn’t find that myself… but at least now the answer is here in the list archive! ;) Cheers, 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
