On 20-Jul 22:52, MarcM wrote:
I found this thread via google and it dates from few years back.
I include the sample at the end of this mail.
You can compare it with the one here:
http://www.lilypond.org/doc/v2.18/Documentation/learning/string-quartet
The documentation shows a sample for
On 20/07/14 05:23, MarcM wrote:
1) This String quartet example is much nicer than the one in the current
documentation.
http://www.lilypond.org/doc/v2.18/Documentation/learning/string-quartet
Can we include it in the documentation?
Maybe I am going mad but when I am trying to look at
- Original Message -
From: MarcM m...@mouries.net
To: lilypond-user@gnu.org
Sent: Sunday, July 20, 2014 5:23 AM
Subject: Re: Template: String Quartet (score-only), first draft
1) This String quartet example is much nicer than the one in the current
documentation.
http
I found this thread via google and it dates from few years back.
I include the sample at the end of this mail.
You can compare it with the one here:
http://www.lilypond.org/doc/v2.18/Documentation/learning/string-quartet
The documentation shows a sample for string quartet parts which requires
1) This String quartet example is much nicer than the one in the current
documentation.
http://www.lilypond.org/doc/v2.18/Documentation/learning/string-quartet
Can we include it in the documentation?
2) Would anyone already have another template for quartet part that does not
require to
Kieren MacMillan wrote:
One thing I'd look into is whether or not the repeated
\context {
\Score
tempoWholesPerMinute = #(ly:make-moment 110 4)
}
can be centralized, either through a variable, or via a global command
(e.g., at the top of the file).
Thanks! I had that because all
2008/8/17 Kieren MacMillan [EMAIL PROTECTED]:
It's even simpler with my convention. ;-)
Oh, please, let's use already used convention :-)
ps. I like python :o)
And, the question -- why global ?
You set \clef in melody (although it is Staff's property), so why not set
\key and \time in melody
Am 18.08.2008 um 09:14 schrieb Dmytro O. Redchuk:
And, the question -- why global ?
You set \clef in melody (although it is Staff's property), so
why not set
\key and \time in melody (*Notes { ... })?
If you do an open score and closed score version of a choral piece,
the tenor part
Graham Percival wrote Sunday, August 17, 2008 10:49 PM
On Sun, 17 Aug 2008 21:47:28 +0100
Neil Puttock [EMAIL PROTECTED] wrote:
2008/8/17 Graham Percival [EMAIL PROTECTED]:
Why manually number the bars? It's true that users can delete
them easily, but they should be very familiar with
Hi Patrick,
Unfortunate that the midi is by default commented out or else you
could also do:
\new Staff \with { instrumentName= Violin I
midiInstrument=violin }
and get the midi to sound right.
Why can't this be done with the MIDI commented out?
Works fine for me (i.e., doesn't throw
Hi all,
it just makes for easier input to define the clef with the staff.
For me, the reason to put the clef in the music variable (as opposed
to the Staff context) is that the clef may change within the passage
— for example, some of my cello music changes clefs a dozen times or
more
Kieren MacMillan wrote:
Hi Patrick,
Unfortunate that the midi is by default commented out or else you
could also do:
\new Staff \with { instrumentName= Violin I midiInstrument=violin }
and get the midi to sound right.
Why can't this be done with the MIDI commented out?
Works fine for me
Hi Patrick,
I really like the idea and hope you use it.
Since the \midi block will be in the templates anyway, I see no
reason not to include the midiInstrument setting.
Thanks!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
Hi all,
Below is my first draft of a String Quartet template (score only) —
here are my notes, for discussion-prompting purposes:
1. I decided not to include any context names: I think that's a
rather advanced topic that doesn't need to clutter up a template.
2. I've included a \header
On Sun, 17 Aug 2008 09:58:58 -0400
Kieren MacMillan [EMAIL PROTECTED] wrote:
\header
{
The rest of the docs place the { or on the same line:
\header {
Please do the same here.
global = {
s1*4
\bar |.
}
I very rarely include s1*4 \bar |. in my global variable -- is
this good
On Sun, 17 Aug 2008 09:58:58 -0400
Kieren MacMillan [EMAIL PROTECTED] wrote:
\header
{
title = Quartett f__r 2 Violinen, Viola und Violoncell
Oh, forgot one thing: using UTF-8 in the title means that people
whose editors (or email programs, apparently[1]) don't handle utf-8 will
see
Hi Graham,
using UTF-8 in the title means that people whose editors
(or email programs, apparently[1]) don't handle utf-8 will
see weird output, as above.
Good point — I'll try to avoid it.
This is not necessarily a bad thing -- it might be good to force
beginners to set up their
Hi Graham,
The rest of the docs place the { or on the same line:
\header {
Please do the same here.
I will, but I officially file a protest: I find it *much* harder to
visually match delimiters (braces, brackets, etc.) with that
convention, just as I find it harder in Java code (where
Am 17.08.2008 um 21:43 schrieb Graham Percival:
global = {
s1*4
\bar |.
}
I very rarely include s1*4 \bar |. in my global variable -- is
this good practice?
When managing a score with many time signature changes, it's really
useful. You only have to make (or correct) a
On Sun, 17 Aug 2008 16:02:10 -0400
Kieren MacMillan [EMAIL PROTECTED] wrote:
Hi Graham,
The rest of the docs place the { or on the same line:
\header {
Please do the same here.
I will, but I officially file a protest: I find it *much* harder to
visually match delimiters (braces,
2008/8/17 Graham Percival [EMAIL PROTECTED]:
Why manually number the bars? It's true that users can delete
them easily, but they should be very familiar with
one-bar-per-line by now. I definitely like the explicit bar
checks, though. :)
Does that mean I should put back all the bar checks
Hi Graham,
as long as you use proper indentation,
matching blocks of code is simple.
It's even simpler with my convention. ;-)
Welcome to the world of point-and-click? ;)
[...] wasn't it invented for exactly this purpose?
I think it was invented just to bloat the size of my output
On Sun, 17 Aug 2008 21:47:28 +0100
Neil Puttock [EMAIL PROTECTED] wrote:
2008/8/17 Graham Percival [EMAIL PROTECTED]:
Why manually number the bars? It's true that users can delete
them easily, but they should be very familiar with
one-bar-per-line by now. I definitely like the explicit
Am 17.08.2008 um 22:26 schrieb Graham Percival:
Why manually number the bars?
I'll give you my most recent opera score WITH MY CODE BAR NUMBERS
REMOVED, and then ask you to add a cautionary accidental to the
first quarter note in m. 413 of the violin music... ;-)
Welcome to the world of
I have it working with Preview and TextMate. There are others with it
working with other editors. It involves some applescript. There was a
thread earlier this summer on it, here's the link to the thread:
http://lists.gnu.org/archive/html/lilypond-user/2008-07/msg00031.html
I was using
Kieren MacMillan [EMAIL PROTECTED] wrote:
\new Staff \with { instrumentName = "Violin I" }
Unfortunate that the midi is by default commented out or else you could
also do:
\new Staff \with {instrumentName= "Violin I" midiInstrument="violin"}
and get the midi to sound right. I
26 matches
Mail list logo
