http://lilypond.org/doc/v2.17/Documentation/notation/long-repeats#normal-repeats
NR 1.4.1 Normal repeats
If there are more repeats than there are alternate endings, the earliest
repeats are given the first alternative.
A single repeat with one alternate ending:
\repeat volta 2 { c4 d e f | }
I need to create a Voice environment, because I want to use the balloon
engraver to annotate chords inside the staff.
I need only one staff, but get the staff engraved correctly once, and then
two times one octave lower.
Code-snippet:
\new Voice \with {\consists Balloon_engraver}{
Bernadette,
On 06/07/13 08:42, Bernadette wrote:
I need to create a Voice environment, because I want to use the balloon
engraver to annotate chords inside the staff.
I need only one staff, but get the staff engraved correctly once, and then
two times one octave lower.
Code-snippet:
\new
2013/7/6 bb bblo...@arcor.de
As one can see the example source in chapter 2.4.3 Banjo does not show any
stems and /stemDown alone does not work. One needs \tabFullNotation as
well!
So /stemDown stand alone does not make any sense and is missleading!
I think in the example this code would
2013/7/6 Federico Bruni fedel...@gmail.com:
[...]
You are right, thanks for the report.
However, I believe that we should just remove \stemDown, since the default
view is not tabFullNotation and the example wants to demonstrate
tablatureFormat.
Also, \stemDown is already the default
2013/6/23 Thomas Morley thomasmorle...@gmail.com:
2013/6/23 Danny dbpolyph...@gmail.com:
I'm not top posting.
\version 2.16.2
% If a clef is changed in retrograde it only prints the new clef
% It does not move the notes to their new locations on the staff
% All notes here are the same
Thomas Morley thomasmorle...@gmail.com writes:
General policy-question:
Sometimes I reply to some mails on this list, before a
bug-squad-member answered. (To do some analysis; solve a problem,
which would have better sent to the user-list; etc)
Is this ok? Or should I let a bug-squad-member
Am 06.07.2013 13:23, schrieb Thomas Morley:
2013/7/6 Federico Bruni fedel...@gmail.com:
[...]
You are right, thanks for the report.
However, I believe that we should just remove \stemDown, since the default
view is not tabFullNotation and the example wants to demonstrate
tablatureFormat.
Also,
Le 01/07/2013 21:55, Phil Holmes disait :
Jean-Charles Malahieude wrote...
Most of the cross-references between manuals are broken in the
translated documentation, split version.
Do you think this is a new 2.17.21 problem, or has it been around a while?
OK. Since I had a number of
Jean-Charles Malahieude lily...@orange.fr wrote in message
news:51d81623.7080...@orange.fr...
Le 01/07/2013 21:55, Phil Holmes disait :
Jean-Charles Malahieude wrote...
Most of the cross-references between manuals are broken in the
translated documentation, split version.
Do you think this
2013/7/6 Thomas Morley thomasmorle...@gmail.com
I slightly disagree.
Being a professional guitarist for more than 30 years, I'm not able to
read/play any Tablature without rhythm, because half of the musical
information is omitted.
In our Docs the tablatures always use a second common \Staff
Le 06/07/2013 15:45, Phil Holmes disait :
Jean-Charles Malahieude wrote...
I'll try to narrow this large window (slowly because of my box's
power) and let you know.
If you have less of a restriction with download limits,
http://download.linuxaudio.org/lilypond/binaries/documentation/ might
musicxml2ly cannot recover from some timing errors. From that point,
it stops making chords for the remainder of the score.
This is a serious problem, as no adjustments to the broken measure
made in the musicxml2ly output would fix the consecutive output.
musicxml2ly loses information
Hi Pavel,
musicxml2ly does not like wrong timing information. The problem here is that
SharpEye 2 obviously has issues with its MusicXML export. SharpEye 2 exported
the wrong duration value in the backup element in the first measure. It also
assigned the f (half note) to the same voice as d
oops, note f should be assigned to voice1/voice and note d to
voice2/voice to fix the wrong stem direction.
On 06.07.2013, at 20:58, pls p.l.schm...@gmx.de wrote:
Hi Pavel,
musicxml2ly does not like wrong timing information. The problem here is that
SharpEye 2 obviously has issues with its
Quoting pls p.l.schm...@gmx.de:
Hi Pavel,
musicxml2ly does not like wrong timing information.
That's understandable. What's not understandable is corrupting the
rest of the output (I mean the lilypond input, not just the pdf).
The problem here is that SharpEye 2 obviously has issues
On 06.07.2013, at 22:26, Pavel Roskin pro...@gnu.org wrote:
Quoting pls p.l.schm...@gmx.de:
Hi Pavel,
musicxml2ly does not like wrong timing information.
That's understandable. What's not understandable is corrupting the rest of
the output (I mean the lilypond input, not just the
Quoting pls p.l.schm...@gmx.de:
I don't care how the faulty markup looks. But MuseScore got the
second measure right. It could recover and musicxml2ly could not.
that's because of the faulty MusicXML markup you provided. the first
measure contained the duration of five quarter notes
18 matches
Mail list logo
