Re: searching score
Hi I am still searching, I did google around, but find only versions with a violin or human voice. I had no luck with the piano solo version. Do you have seen the piano solo. Sorry for bothering. Helge ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: expressive first draft
Trevor Daniels wrote: Add real example If by real you mean having notes other than c, ok. If by real you mean including lots of extra stuff, then you know my opinion. However, we should soon have a mechanism for including all the real examples you could possibly work. Stay tuned. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: pitches second draft
Trevor Daniels wrote: 1. Sharps and flats are used in an example shown in Relative octaves entry and in the text above it before they have been mentioned anywhere. To an English speaker is and es are incomprehansible at first sight. Even in the LM they are used in 2.2.1 before the explanation in 2.2.2. I know the Notation Reference is not meant to be read sequentially, but it will be. Perhaps they should be introduced (as briefly as you like) in the first section on Absolute octave entry. Good catch about the tutorial! I've added this to the list. As far as the user manual goes, I disagree. We need to assume that users have read the learning manual. If they have not, then we officially do not care about those users. That is one of the basic policy decisions that I made about GDP. One of the problems in the previous docs was that I tried to make the user manual sequential. That leads to too many oddities. 2. At the bottom of Accidentals there is a cryptic comment about microtones and MIDI. As neither micro tones nor MIDI have been mentioned so far this seems misplaced. In the example immediately preceding that sentence: \set Staff.extraNatural = ##f ceseh ceh cih cisih 3. The note names table in other languages is poorly formatted (at least in html). What's poorly formatted about it? The table is a bit too wide; is that what you mean? Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: where do we discuss MIDI?
On 18.10.2007 (23:45), Graham Percival wrote: There are two options to this: No, there's only one: 1) Gather everything about MIDI into one section (currently 4.3) and mention everything there :-) -- He who lives without folly is less wise than he believes. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
GDP: where do we discuss MIDI?
There are two options to this:
1) Gather everything about MIDI into one section (currently 4.3) and
mention everything there:
Currently LilyPond MIDI support includes
Dynamicsyes
Repeats no, unless \unfoldRepeats is used
Articulations no
Textno, are you joking?
2) Mention MIDI everywhere in the manual.
Dynamics
blah blah blah\mf blah
Dynamics are supported in MIDI.
Repeats
blah blah \repeat unfold blah {}
@refbugs
Repeats are not supported in MIDI unless you use \unfoldRepeats
...etc...
Opinions? both is not an option, because the docs will become
obsolete and contradictory when people only update one place.
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: where do we discuss MIDI?
Trevor Daniels wrote: Eyolf said: On 18.10.2007 (23:45), Graham Percival wrote: There are two options to this: No, there's only one: 1) Gather everything about MIDI into one section (currently 4.3) and mention everything there I agree Absolutely. -- Mark Knoop ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ReheasalMark in Staff context is broken - can someone verify this snippet is a bug?
The bug has already been reported, see
http://code.google.com/p/lilypond/issues/detail?id=432
In your simple example, it helps to move also the Break_align_engraver
from the Score to the Staff context, but I have no idea if such an operation
will work well also for multi-stave scores or if something else will break.
/Mats
Adam James Wilson wrote:
There is a problem when moving the RehearsalMark to the Staff
context. In the case where the RehearsalMark remains in the Score
context (comment out the layout block below), the first RehearsalMark
aligns to a Clef and the rest align to staff-bars. This is the
correct behavior.
But if you move the RehearsalMark to the Staff context (retain the
layour block below), the opposite (and incorrect) behavior occurs: the
first RehearsalMark aligns to a staff-bar and the rest seem to align
to Clefs.
\version 2.11.34
%%{
\layout {
\context { \Score
\remove Mark_engraver
}
\context { \Staff
\consists Mark_engraver
}
}
%%}
\new Staff {
\bar |
\mark \default
\clef bass
c'4 c'4
\bar |
\mark \default
\clef treble
c'4 c'4
}
Should this be filed as a bug?
Best,
Adam
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: introducing examples
2007/10/19, Hans Aberg [EMAIL PROTECTED]: On 19 Oct 2007, at 14:37, Mats Bengtsson wrote: What you describe sounds like the LSR, which already now has free text search facilities (at least if you stay connected). So how do you find the LSR?... You have the link into the main documentaion page http://lilypond.org/web/documentation and it links to http://lsr.dsi.unimi.it/ -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: introducing examples
On 19 Oct 2007, at 14:37, Mats Bengtsson wrote: What you describe sounds like the LSR, which already now has free text search facilities (at least if you stay connected). So how do you find the LSR? If I search on http://lilypond.org/web/ , it translates to a Goole search site:www.lilypond.org LSR with no matches as a result. I mean, if it is not easy tho find these things, it probably will translate into a lot of question on the LilyPond Users list. :-) Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Church Rests
2007/10/19, Trevor Daniels [EMAIL PROTECTED]: In the section on multi-measure rests the manual talks about church rests, meaning the use of increasing numbers of little rectangles to indicate how many measures are included in the multi-measure rest. In this a generally accepted musical term, or one invented for lily? They are completely usual in orchestral parts since I can remember. Possibly their origin are the choral parts, but as you probably know, choral scores are now usually read in full score, not parts. Church rests were best read in past centuries when the typical written note durations were longer than now are. I can be wrong, though. -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: introducing examples
On 19 Oct 2007, at 16:59, Eyolf Østrem wrote: So how do you find the LSR?... You have the link into the main documentaion page http://lilypond.org/web/documentation and it links to http://lsr.dsi.unimi.it/ ... and in the final GDP, there will be so many LSR links that you're going to moan: Oh, please, Graham -- not another LSR snippet, I can't take it anymore! :-) I suspected that. - So it might be better putting at least the more prominent examples in a special examples PDF, and reference that. The LSR could still be there, for new examples that have not yet worked up the hierarchy. I also brought forward the idea of a Wiki. These are great to put silly little facts one does not know where to put elsewhere. Abbreviations and such, for example. Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: introducing examples
On 19 Oct 2007, at 16:38, Francisco Vila wrote: So how do you find the LSR?... You have the link into the main documentaion page http://lilypond.org/web/documentation and it links to http://lsr.dsi.unimi.it/ Actually, I see now where the problem is: If one follows the shortcuts on the main page http://lilypond.org/web/ then one ends up a page like http://lilypond.org/doc/v2.11/Documentation/ If one then on that page follows Snippets, one ends up with http://lilypond.org/doc/v2.11/input/lsr/collated-files and following the links there, leads to pages with broken images (at least in Safari 3). So this is not the LSR. For that, one has to go to the documents main page. Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: where do we discuss MIDI?
Mats Bengtsson wrote: Graham Percival wrote: 1) Gather everything about MIDI into one section (currently 4.3) and mention everything there: Ok, this option is overwhelmingly favored. We will remove discussion about MIDI from the rest of the manual, and concentrate it in 4.3. Anybody who objects to this policy has until next Monday to voice their objections. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: nothing to do with examples
On 19 Oct 2007, at 23:29, Graham Percival wrote: I suspected that. - So it might be better putting at least the more prominent examples in a special examples PDF, and reference that. The LSR could still be there, for new examples that have not yet worked up the hierarchy. GDP is not on the main lilypond website. Please see our website here: http://web.uvic.ca/~gperciva/ Thanks, I know that. In particular, look at the GDP docs and the policy.txt. So what is Music Glossary and Notation Reference relative to the names listed on: http://opihi.cs.uvic.ca/~gperciva/lilypond/Documentation/index.html I am not particularly interested in reopening any decisions that we have already made. The division of manual into the learning manual, user manual, and program usage is one of those decisions. So then let's drop this discussion. Finally, please change the subject line if you change the subject. We have a lot of emails about GDP, and it quickly becomes much more difficult to keep things straight if people change discussions without modifying the subject line accordingly. I guess I put into the context of GDP. It is hard for me to read you mind. I also brought forward the idea of a Wiki. These are great to put silly little facts one does not know where to put elsewhere. Abbreviations and such, for example. Wikis are worse than useless. Please see previous discussions about them on this list. I am well aware of your particular opinion about the wikis. I use them all the time, as well as netsearching. Even the UNIX standardization team decided to set one up. And LilyPond has the same steep learning curve problem as UNIX, as noted before. Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: nothing to do with examples
Hans Aberg wrote: I suspected that. - So it might be better putting at least the more prominent examples in a special examples PDF, and reference that. The LSR could still be there, for new examples that have not yet worked up the hierarchy. Hans, GDP is not on the main lilypond website. Please see our website here: http://web.uvic.ca/~gperciva/ In particular, look at the GDP docs and the policy.txt. I am not particularly interested in reopening any decisions that we have already made. The division of manual into the learning manual, user manual, and program usage is one of those decisions. Finally, please change the subject line if you change the subject. We have a lot of emails about GDP, and it quickly becomes much more difficult to keep things straight if people change discussions without modifying the subject line accordingly. I also brought forward the idea of a Wiki. These are great to put silly little facts one does not know where to put elsewhere. Abbreviations and such, for example. Wikis are worse than useless. Please see previous discussions about them on this list. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
SOLUTION: Re: scheme function to align time-sig above nearest RehearsalMark?
There is a much easier way to do this thant I originally imagined. I
enclosed the function that I came up with and a snippet to
demonstrate.
When you compile, note that the only problem is that the alignment
behavior of the ReheasalMarks is undesirable, due to the ReheasalMark
being moved to the Staff context.
Marks at the beginning of the line incorrectly align to the bar
instead of the clef, and marks mid-system incorrectly align to
mid-system clefs when they should align to barlines.
I'm willing to sponsor a fix to this if anyone is willing.
This function is useful for proportionalNotation scores because it
automates placement of faux time signatures completely outside the
staff. It is a little hacky because I found that the markformatter
function had to be re-defined in each instance in order to be able to
pass a different timesig argument to it.
Best,
Adam
% START EXAMPLE %%%
\version 2.11.34
#(set-global-staff-size 10)
\paper {
#(set-paper-size letter)
ragged-right = ##t
width = 11\in
height = 8.5\in
}
\layout {
\context { \Score
\remove Mark_engraver
\remove Bar_number_engraver
\remove Metronome_mark_engraver
\remove Timing_translator
\remove Time_signature_engraver
\remove Default_bar_line_engraver
\override SpacingSpanner #'uniform-stretching = ##t
\override SpacingSpanner #'strict-note-spacing = ##t
proportionalNotationDuration = #(ly:make-moment 1 64)
}
\context { \Staff
\consists Timing_translator
\consists Mark_engraver
\consists Time_signature_engraver
\override TimeSignature #'transparent = ##t
\override TimeSignature #'X-extent = #'(0 . 0)
\override TimeSignature #'Y-extent = #'(0 . 0)
\consists Default_bar_line_engraver
%\override RehearsalMark #'self-alignment-X = #-1 %
}
}
markTime = #(define-music-function (parser location timesig) (pair?)
Use this function a the start of every measure to place a barline, set
the measureLength and beatLength of the bar, and draw a false
time signature above the automatically-numbered RehearsalMark. If the
time signature is the same as in the previous bar, then the car of the
pair passed to the function should be set to zero.
(let ((n (car timesig)) (d (cdr timesig)))
(cond
((= (car timesig) 0)
#{
#(define (my-mark-formatter mark context)
(markup
(#:center-align (#:box (#:bold
(number-string mark
)
)
\set Staff.markFormatter = #my-mark-formatter
\bar | \mark \default
#}
)
(( (car timesig) 0)
#{
#(define (my-mark-formatter mark context)
(markup
(#:column
(
(#:center-align (#:raise 3.0
(#:bold
(#:fontsize 5.0
(#:number
(number-string
$n))
(#:center-align (#:raise 1.5
(#:bold
(#:fontsize 5.0
(#:number
(number-string
$d))
(#:center-align (#:box (#:bold
(number-string
mark
)
)
)
)
\set Staff.markFormatter = #my-mark-formatter
\set Timing.beatLength = #(ly:make-moment $n $d)
\set Timing.measureLength = #(ly:make-moment $n $d)
\set Staff.timeSignatureFraction = $timesig
\bar | \mark \default
#}
)
)
)
)
\new Score
\new StaffGroup
\new Staff {
\markTime #'(3 . 4)
\clef treble
c'4 c'4 c'4
\markTime #'(3 . 32)
\clef bass
c'16 c'32
Re: Markup with multi-measure rests
Thanks, this first item has been added as
http://code.google.com/p/lilypond/issues/detail?id=495
Cheers,
- Graham
Mats Bengtsson wrote:
To me it seems a bug that you get collisions in your first example.
The second example can easily be modified to get what you want.
Just add \fatText before the first spacer note.
/Mats
Trevor Daniels wrote:
In the following example of writing a typical part
containing multi-measure rests, the annotation of the rests
in 2.11.34 collides if more notes are added to fill the line
(to simulate this, I've added ragged-right = ##t). This
seems to be a bug.
The collisions can be avoided in 2.11 by attaching the
annotation to zero-length skip notes at the start of the
bar, but only by displacing some of the annotations
vertically (see second example). This results in confusing
annotations. IIRC, in 2.10.20 the bars automatically
expanded to avoid collisions of text attached to skip notes,
keeping the annotation all on one level. This was much
better in this context. Is there a way of doing this in
2.11?
% Example of R markup colliding
\version 2.11.34
\paper { ragged-right = ##t }
{
\set Score.skipBars = ##t
R1*4^Intrumental
R1*24^Solo
R1*4^Instrumental
b'2^Tutti b'4 a'4
}
% Example of R markup displacing vertically
\version 2.11.34
\paper { ragged-right = ##t }
{
\set Score.skipBars = ##t
s1*0^Intrumental R1*4
s1*0^Solo R1*24
s1*0^Instrumental R1*4
b'2^Tutti b'4 a'4
}
Trevor D
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
GDP: output website changed
Hi all, Thanks to a generous offer from Reinhold Kainhofer, we now have a more stable location for the GDP output. You should not need to change any bookmarks, though. The main GDP website is still here: http://web.uvic.ca/~gperciva/ The link to GDP output has been changed from opihi (which was at the mercy of external forces, and which I never actually asked permission for hosting our docs :) to Reinhold's webserver. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: nothing to do with examples
Hans Aberg wrote: On 19 Oct 2007, at 23:29, Graham Percival wrote: In particular, look at the GDP docs and the policy.txt. So what is Music Glossary and Notation Reference relative to the names listed on: Thanks, good catch. Glossary is music glossary. User manual is notation reference. I've fixed this on the index.html.in, but the docs will need to be updated. I've added this to the task list. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ReheasalMark in Staff context is broken - sponsorship of fix?
Hi Mats et al,
(RE: this bug: http://code.google.com/p/lilypond/issues/detail?id=432)
Moving Break_align_engraver to the Staff context works to get the
correct alignment of RehearsalMarks, but the side effect is that if
there is a mid-system Clef change in one Staff and not another, you
get a broken system barline - the Clef pushes aside the bar in its
Staff only, because a multiple-staff column is not created when the
engraver is removed from the Score context.
I tried a workaround of putting hidden clefs in the other staves to
pad them, but this seems impossible - making a Clef transparent or
breaking its visibility is equal to removing its width.
Unless you know another workaround, it seems the best to just get a
fix in place for the problem.
I'm willing to sponsor a fix to this bug; the idea is to be able to 1)
duplicate the default behavior of a Score-living RehearsalMark when it
is moved to the Staff context (at the beginning of a system it should
align to the clef, and then align to staff bars for the rest of the
system), and 2) to be able to explicitly modify the break-align symbol
for the Clef in each Staff at any position in the score.
On 10/19/07, Mats Bengtsson [EMAIL PROTECTED] wrote:
The bug has already been reported, see
http://code.google.com/p/lilypond/issues/detail?id=432
In your simple example, it helps to move also the Break_align_engraver
from the Score to the Staff context, but I have no idea if such an operation
will work well also for multi-stave scores or if something else will break.
/Mats
Adam James Wilson wrote:
There is a problem when moving the RehearsalMark to the Staff
context. In the case where the RehearsalMark remains in the Score
context (comment out the layout block below), the first RehearsalMark
aligns to a Clef and the rest align to staff-bars. This is the
correct behavior.
But if you move the RehearsalMark to the Staff context (retain the
layour block below), the opposite (and incorrect) behavior occurs: the
first RehearsalMark aligns to a staff-bar and the rest seem to align
to Clefs.
\version 2.11.34
%%{
\layout {
\context { \Score
\remove Mark_engraver
}
\context { \Staff
\consists Mark_engraver
}
}
%%}
\new Staff {
\bar |
\mark \default
\clef bass
c'4 c'4
\bar |
\mark \default
\clef treble
c'4 c'4
}
Should this be filed as a bug?
Best,
Adam
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: introducing examples
On 19 Oct 2007, at 16:38, Francisco Vila wrote: So how do you find the LSR?... You have the link into the main documentaion page http://lilypond.org/web/documentation and it links to http://lsr.dsi.unimi.it/ Thank you, but the question is then why the search on the first page did not find it. Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Church Rests
On 19.10.2007 (16:24), Francisco Vila wrote: 2007/10/19, Trevor Daniels [EMAIL PROTECTED]: In the section on multi-measure rests the manual talks about church rests, meaning the use of increasing numbers of little rectangles to indicate how many measures are included in the multi-measure rest. In this a generally accepted musical term, or one invented for lily? They are completely usual in orchestral parts since I can remember. The signs, yes (they go back to mensural notation in the fourteenth century), but the name? I've never heard it before, and Grove doesn't mention it... eyolf -- Creditor, n.: A man who has a better memory than a debtor. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: where do we discuss MIDI?
On 19 Oct 2007, at 15:24, Mark Knoop wrote: On 19 Oct 2007, at 08:45, Graham Percival wrote: [1) Gather everything about MIDI into one section] It seems that this option is favored - and then one can just as well put the MIDI stuff in a separate manual. Um, by who? Sorry for the typo. :-) Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: introducing examples
On 19.10.2007 (16:38), Francisco Vila wrote: 2007/10/19, Hans Aberg [EMAIL PROTECTED]: So how do you find the LSR?... You have the link into the main documentaion page http://lilypond.org/web/documentation and it links to http://lsr.dsi.unimi.it/ ... and in the final GDP, there will be so many LSR links that you're going to moan: Oh, please, Graham -- not another LSR snippet, I can't take it anymore! :-) you'll find it, rest assured. eyolf -- Insults are effective only where emotion is present. -- Spock, Who Mourns for Adonais? stardate 3468.1 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Church Rests
In the section on multi-measure rests the manual talks about church rests, meaning the use of increasing numbers of little rectangles to indicate how many measures are included in the multi-measure rest. In this a generally accepted musical term, or one invented for lily? Or is there a better term? Whatever name we use, I suggest it be added to the glossary. Trevor D ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Markup with multi-measure rests
To me it seems a bug that you get collisions in your first example.
The second example can easily be modified to get what you want.
Just add \fatText before the first spacer note.
/Mats
Trevor Daniels wrote:
In the following example of writing a typical part
containing multi-measure rests, the annotation of the rests
in 2.11.34 collides if more notes are added to fill the line
(to simulate this, I've added ragged-right = ##t). This
seems to be a bug.
The collisions can be avoided in 2.11 by attaching the
annotation to zero-length skip notes at the start of the
bar, but only by displacing some of the annotations
vertically (see second example). This results in confusing
annotations. IIRC, in 2.10.20 the bars automatically
expanded to avoid collisions of text attached to skip notes,
keeping the annotation all on one level. This was much
better in this context. Is there a way of doing this in
2.11?
% Example of R markup colliding
\version 2.11.34
\paper { ragged-right = ##t }
{
\set Score.skipBars = ##t
R1*4^Intrumental
R1*24^Solo
R1*4^Instrumental
b'2^Tutti b'4 a'4
}
% Example of R markup displacing vertically
\version 2.11.34
\paper { ragged-right = ##t }
{
\set Score.skipBars = ##t
s1*0^Intrumental R1*4
s1*0^Solo R1*24
s1*0^Instrumental R1*4
b'2^Tutti b'4 a'4
}
Trevor D
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: where do we discuss MIDI?
On 19 Oct 2007, at 08:45, Graham Percival wrote: 2) Mention MIDI everywhere in the manual. It seems that this option is favored - and then one can just as well put the MIDI stuff in a separate manual. Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: introducing examples
On 19 Oct 2007, at 08:40, Graham Percival wrote: Currently we have a few different ways of introducing examples in the docs. Should we standardize on a particular way, or just let doc writers do whatever they want? I have the idea that there should be created a separate PDF doc with examples, including the snippets (whose pics happen to be broken in my web browser, Safari 3). Then the user manual should reference that, with a list of what the examples manual contains. The idea is based on what I find the easiest way to find programming usage, namely, in the PDF viewer (I use Preview, but I thing it works in Adobe Reader), type a keyword, and looking through all matches. The keyword can be both musical terms as well programming names. So therefore it helps with a manual mentioning these terms, and with directions for further reading Also, the user manual is already somewhat heavy. So having a second manual with examples would be great. In the context of your question, this gives the opportunity to put examples which are too spacious into the examples manual. The user manual should be restricted to examples that illustrate concept of the text. Perhaps there should be a third manual: advanced usage, as well. Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: introducing examples
Graham Percival wrote:
Currently we have a few different ways of introducing examples in the
docs. Should we standardize on a particular way, or just let doc
writers do whatever they want?
Currently we have a combination of four different ways.
1) The text just continues directly into
c'4\mf
2) The text suggests that one may do foo,
c'4^foo
3) The text directs the reader to the following example:
c'4 { e g }
4) The text forms a complete sentence.
c'4^-\mark \default
Should allow all? Specify one method? Disallow one or two methods?
I prefer 4, 3, 2, 1 (in that order). But I don't think standardisation
is necessary, although perhaps an official preference could be specified.
--
Mark Knoop
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: pitches second draft
Graham wrote: Trevor Daniels wrote: 2. At the bottom of Accidentals there is a cryptic comment about microtones and MIDI. As neither micro tones nor MIDI have been mentioned so far this seems misplaced. In the example immediately preceding that sentence: \set Staff.extraNatural = ##f ceseh ceh cih cisih Ah, yes. Missed that. Sorry. 3. The note names table in other languages is poorly formatted (at least in html). What's poorly formatted about it? The table is a bit too wide; is that what you mean? Well, sort of. About half the table, between the Note names and sharp columns, is white space, forcing the right-most columns into the margin and the sharp/flat columns to take up two lines, with '-' on one line and the following 'sharp' on the other, instead of '-sharp', as it should be. These columns could be spread much better by using the central white space so they fit on one line. Cheers, - Graham Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tagging Troubles
I'm not sure that you have correctly understood the syntax of \tag.
For example in
\tag #'woodwinds
...
the tag applies to the full music expression ... , not only to the
end of the line.
/Mats
mojocojo2000 wrote:
I'm trying to create a grand staff around two oboe parts when score.ly is
compiled. The files I'm using are belowed.
% piece.ly
music = {
% oboe I.II
\tag #'woodwinds \new GrandStaff
\tag #'woodwinds \tag #'ob12 \new Staff {
\tag #'woodwinds \tag #'ob12 \set Staff.midiInstrument = oboe
\tag #'woodwinds \set Staff.instrumentName = Oboe I.II
\tag #'woodwinds \set Staff.shortInstrumentName = Ob.I.II
\tag #'woodwinds \tag #'ob12 \global \partcombine \oboeOne \oboeTwo }
% oboe III.IV
\tag #'woodwinds \tag #'ob34 \new Staff {
\tag #'woodwinds \tag #'ob34 \set Staff.midiInstrument = oboe
\tag #'woodwinds \set Staff.instrumentName = Oboe III.IV
\tag #'woodwinds \set Staff.shortInstrumentName = Ob.III.IV
\tag #'woodwinds \tag #'ob34 \global \partcombine \oboeThree \oboeFour
}
\tag #'woodwinds
}
% ob12.ly
\version 2.10.0
\include piece.ly
\header {
instrument = Oboe I.II
}
\score {
\keepWithTag #'ob12 \music
\layout { }
\midi { }
}
% score.ly
\version 2.10.0
\include piece.ly
#(set-global-staff-size 14)
\score {
\new StaffGroup \keepWithTag #'woodwinds \music
\new StaffGroup \keepWithTag #'brass \music
\new StaffGroup \keepWithTag #'percussion \music
\new StaffGroup \keepWithTag #'strings \music
\layout { }
\midi { }
}
The problem is when I compile score.ly I get an error about unexpected .
This of course comes from the line -- \tag #'woodwinds in piece.ly. Is
there anyway to make this work?
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: introducing examples
What you describe sounds like the LSR, which already now has free text search facilities (at least if you stay connected). /Mats Hans Aberg wrote: On 19 Oct 2007, at 08:40, Graham Percival wrote: Currently we have a few different ways of introducing examples in the docs. Should we standardize on a particular way, or just let doc writers do whatever they want? I have the idea that there should be created a separate PDF doc with examples, including the snippets (whose pics happen to be broken in my web browser, Safari 3). Then the user manual should reference that, with a list of what the examples manual contains. The idea is based on what I find the easiest way to find programming usage, namely, in the PDF viewer (I use Preview, but I thing it works in Adobe Reader), type a keyword, and looking through all matches. The keyword can be both musical terms as well programming names. So therefore it helps with a manual mentioning these terms, and with directions for further reading Also, the user manual is already somewhat heavy. So having a second manual with examples would be great. In the context of your question, this gives the opportunity to put examples which are too spacious into the examples manual. The user manual should be restricted to examples that illustrate concept of the text. Perhaps there should be a third manual: advanced usage, as well. Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: where do we discuss MIDI?
Mats Bengtsson wrote: Graham Percival wrote: There are two options to this: 1) Gather everything about MIDI into one section (currently 4.3) and mention everything there: Currently LilyPond MIDI support includes Dynamicsyes Repeatsno, unless \unfoldRepeats is used Articulationsno Textno, are you joking? Lyrics: Yes (not compatible with all MIDI players, though) Opinions? both is not an option, because the docs will become obsolete and contradictory when people only update one place. The docs already contain lots of repeated information, not only related to MIDI. I'd say that the MIDI related stuff is a minor issue in that respect. Well, part of GDP is fixing that. Stuff will be duplicated between the LM and user manual, but within the user manual there should be no duplication (only links). Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: where do we discuss MIDI?
Graham Percival wrote: There are two options to this: 1) Gather everything about MIDI into one section (currently 4.3) and mention everything there: Currently LilyPond MIDI support includes Dynamicsyes Repeatsno, unless \unfoldRepeats is used Articulationsno Textno, are you joking? Lyrics: Yes (not compatible with all MIDI players, though) Opinions? both is not an option, because the docs will become obsolete and contradictory when people only update one place. The docs already contain lots of repeated information, not only related to MIDI. I'd say that the MIDI related stuff is a minor issue in that respect. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Japanese translation
Ishizaki writes:
But make fails as following,
File scripts/format-page.py, line 419, in ?
main ()
File scripts/format-page.py, line 409, in main
read_build_versions (version_db_file_name)
File scripts/format-page.py, line 109, in read_build_versions
(version, b, url) = version_db.get_last_release ('source', branch)
File /scripts/versiondb.py, line 123, in get_last_release
candidates = [(v, b, url) for (name, v, b, url) in self._db[platform]
KeyError: 'source'
Did you do make update-versions?
Jan.
--
Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
