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?
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
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
> (versio
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 sco
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
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
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 i
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"
\t
When I install with the GUB, I can set:
LYEDITOR=emacsclient.emacs-snapshot --no-wait +%(line)s:%(column)s %(file)s
and put "urlCommand "lilypond-invoke-editor %s" into my .xpdfrc,
point-and click works for me in lilypond 10.33 on my Ubuntu Feisty
system with emacs-snapshot installed.
Ho
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
There is http://blog.gmane.org/gmane.comp.gnu.lilypond.general as well.
2007/10/18, Graham Percival <[EMAIL PROTECTED]>:
> What, like this?
>
> http://www.nabble.com/Gnu---Lilypond---User-f1722.html
>
> Cheers,
> - Graham
--
Francisco Vila. Badajoz (Spain)
http://www.paconet.org
___
2007/10/18, Graham Percival <[EMAIL PROTECTED]>:
> The recommended texinfo solution is to always use @ref{} at the end of a
> sentence; for more information, see @ref{foo}. This sometimes leads to
> awkward phrasing.
>
> If we group all the references to other sections in the @seealso
> section,
>
> This is the second draft of Pitches. Please have
> a look; it's been
> significantly updated. Remaining items are
>
> Please let us known if there are any other issues
> that should be addressed.
>
Only three comments, all points of detail; otherwise looks
good:
1. Sharps and flats are used
I don't know if it will lead to changes in the GDP pitches section, but a
few things are nebulous for me about pitches.
Here is the problematic code :
%%%
\version "2.11.34"
frag = \relative c'' {
g'2 b4 d
\tag #'oboe { \octave g'' }
g1
}
{
<<
\new Staff \keepWithTag #'flute \
Of course
(didn't checked)
Sorry for the noise
-a-
On 18 Oct 2007, at 11:08, Graham Percival wrote:
What, like this?
http://www.nabble.com/Gnu---Lilypond---User-f1722.html
Cheers,
- Graham
Andrea Valle wrote:
One can think of archiving the list via Nabble.
http://www.nabble.com/Maili
Graham said:
> This is the first draft of Expressive marks.
> Planned work:
>
> REWRITE
> - articulations. clean up first example, rewrite
> with appendix
>list of articulations in mind.
> - rename to "articulations and ornamentations" ?
Yes.
Explain difference between -., ^. and _.
A
What, like this?
http://www.nabble.com/Gnu---Lilypond---User-f1722.html
Cheers,
- Graham
Andrea Valle wrote:
One can think of archiving the list via Nabble.
http://www.nabble.com/MailingListArchive.html
It has been done e.g. on the SuperCollider mailing list (and many others).
It has proven
Mats Bengtsson wrote:
Graham Percival wrote:
It was originally written this way, but I would rather keep all the
links in the @seealso section at the bottom. If we absolutely must
include some links in the main text, I suppose we could... but I am not
(yet) convinced that this is one such case.
One can think of archiving the list via Nabble.
http://www.nabble.com/MailingListArchive.html
It has been done e.g. on the SuperCollider mailing list (and many
others).
It has proven helpful.
Best
-a-
On 18 Oct 2007, at 10:48, Graham Percival wrote:
M.v.Strien wrote:
Can't there be a
M.v.Strien wrote:
Can't there be a lilypond forum instead of a lilypond mailinglist?
No, this would not be helpful.
Mailinglists are: somewhat dated, far from structured, and posts tend to
become bloated when for instance ppl start quoting quotes of quotes of
quotes of quotes, or simply quot
Graham said:
> This is the first draft of Expressive marks.
> Planned work:
>
> REWRITE
> - articulations. clean up first example, rewrite
> with appendix
>list of articulations in mind.
> - rename to "articulations and ornamentations" ?
Yes.
Explain difference between -., ^. and _.
A
Hi,
Can't there be a lilypond forum instead of a lilypond mailinglist?
Mailinglists are: somewhat dated, far from structured, and posts tend to
become bloated when for instance ppl start quoting quotes of quotes of
quotes of quotes, or simply quote a whole post and add one extra line to
it, e
See http://code.google.com/p/lilypond/issues/detail?id=60
for the bug report and a workaround.
/Mats
Stan Sanderson wrote:
I believe I saw this previously reported, but haven't found the
discussion (or a temporary resolution).
An 8th followed by a 16th rest and 2 or more 16th notes results
Graham Percival wrote:
It was originally written this way, but I would rather keep all the
links in the @seealso section at the bottom. If we absolutely must
include some links in the main text, I suppose we could... but I am not
(yet) convinced that this is one such case.
Why move a hypertex
24 matches
Mail list logo
