Hey all,
The value 'none' of the element 'group-symbol'
(none) leads to a bus error when the converted
.ly-file is compiled with LilyPond v2.15.14. The compilation fails. There is no
problem with the conversion and compilation of the other group-symbols (brace,
line and bracket). (The MusicXML
Hi Reinhold,
the values "above" and "below" of the 'placement'-attribute don't seem to show
any effect in the -element, e.g. when you substitute "below" for
"above" in the following code the result of the conversion is the same. (See:
33a-Spanners.xml in
http://www.kainhofer.net/musicxml/Music
Hi Reinhold et al.,
this is how musicxml2ly works at the moment:
1) if XML: bli> --> LilyPond: title = bli
2) if XML: bla --> LilyPond: title = bla
3) if XML: (empty) AND
bla --> LilyPond: title = bla
so far so good, but
4) if XML: bli (non-empty!) AND
bla --> LilyPond: title = bli
So any i
Hi Reinhold,
Am 09.09.2011 um 21:43 schrieb Reinhold Kainhofer:
> Am Freitag, 9. September 2011, 21:31:01 schrieb Patrick Schmidt:
>> here is a tiny example to demonstrate the issue: the musicxml2ly-conversion
>> results in a common treble clef instead of a bass clef when the
>
Hey all,
here is a tiny example to demonstrate the issue: the musicxml2ly-conversion
results in a common treble clef instead of a bass clef when the
XML-clef-element contains a number attribute and a value, e.g. . Without the number attribute everything works as expected.
MusicXML allows number
Hey all,
here is a tiny example (see file attached) to demonstrate the issue: the
musicxml2ly-conversion results in a common treble clef instead of a bass clef.
Without the number attribute everything works as expected. MusicXML allows
number attributes in clef elements, so it's valid XML-code.
Hi all,
by accident I noticed that when you try to upgrade a file (to version 2.14.2)
that is already up to date (2.14.0) with
convert-ly myfile.ly > mynewfile.ly
a new but empty file is created. There aren't any error messages. When you fake
an older version number everything works out and a
Hi all,
by accident I noticed that when you try to upgrade a file (to version 2.14.2)
that is already up to date (2.14.0) with
convert-ly myfile.ly > mynewfile.ly
a new but empty file is created. There aren't any error messages. When you fake
an older version number everything works out and a
Am 17.04.2011 um 18:35 schrieb Federico Bruni:
> Il giorno dom, 17/04/2011 alle 16.58 +0200, Patrick Schmidt ha scritto:
>>> Anyway I believe that if you want to hide a note in Staff, you want
>> to
>>> hide the number in TabStaff as well. To me this is the main bug!
&
ly sure it's suitable to introduce a new function (or
>> more exactly, I'm wondering if it shouldn't rather be added to
>> music-function.ly instead). Not being a guitar player, I can't tell.
>>
>
> Some months ago Patrick Schmidt told me that \hideNotes
Am 19.12.2010 um 15:22 schrieb Federico Bruni:
Il giorno dom, 19/12/2010 alle 14.57 +0100, Patrick Schmidt ha
scritto:
I never noticed such behaviour because when I want to hide notes on
Staff I hide notes on TabStaff as well.
Hm, then you must use overrides?! This function has not been
Am 19.12.2010 um 14:44 schrieb Federico Bruni:
Il giorno dom, 19/12/2010 alle 14.28 +0100, Patrick Schmidt ha
scritto:
I didn't notice this behavior in 2.13.42, so maybe it's a
regression?!
I'm using 2.13.42 and I get the same output.
I never noticed such behaviour because
Am 19.12.2010 um 14:28 schrieb Patrick Schmidt:
Hi all,
when \hideNotes is used in tablature either a small vertical line
or a dot is typeset in addition to the tab notehead. Here is a tiny
example:
\version "2.13.44"
bug = {
\hideNotes
g4\3
\unHideNotes
c'4\3
}
Hi all,
when \hideNotes is used in tablature either a small vertical line or
a dot is typeset in addition to the tab notehead. Here is a tiny
example:
\version "2.13.44"
bug = {
\hideNotes
g4\3
\unHideNotes
c'4\3
}
\new TabStaff { \bug }
<<
\new Staff { \bug }
\new TabStaff
Am 23.11.2010 um 00:58 schrieb Carl Sorensen:
On 11/22/10 11:13 AM, "Patrick Schmidt" wrote:
Hi Carl,
sorry, it's me again. I just checked 2.13.40 and found a small issue:
open strings defined in a chord in an alternate fretboard table are
not typeset in tablature. This does
Hi Carl,
sorry, it's me again. I just checked 2.13.40 and found a small issue:
open strings defined in a chord in an alternate fretboard table are
not typeset in tablature. This doesn't happen with the chords defined
in predefined-guitar-fretboards.ly.
It seems as if the problem is relate
Hi all,
the following example doesn't compile with version 2.13.38:
\version "2.13.38"
\include "predefined-guitar-fretboards.ly"
#(define custom-fretboard-table-one (make-fretboard-table))
#(define custom-fretboard-table-two (make-fretboard-table
default-fret-table))
\storePredefinedDiagram
Am 27.09.2010 um 17:32 schrieb Reinhold Kainhofer:
Bass figures can be either added as a separate FiguredBass context
(which has
the drawback that all figures will be shifted up if one of the
notes in the
staff is very high), or directly inside a staff.
In the latter case, all figures will
Am 20.09.2010 um 20:29 schrieb Vicente Solsona:
On Mon, 20 Sep 2010 18:27:37 +0200, "Vicente Solsona"
wrote:
To sumarise:
String numbers, harmonics and right hand fingerings *must* be
defined
inside a chord construct even if there is only a single note.
you can attach finger numbers to s
Am 20.09.2010 um 10:53 schrieb Dmytro O. Redchuk:
On Sat 18 Sep 2010, 16:47 Patrick Schmidt wrote:
It looks to me as if this strange behaviour is caused by the
No, with no \voiceTwo lilypond produces wrong picture, too (dots
can not be
moved).
Thank you, Patrick and Vicente, i've
Am 18.09.2010 um 16:05 schrieb Dmytro O. Redchuk:
Hi!
Here lilypond puts dots "in betweens noteheads", i need both of
them (all of
them) would be in spaces below noteheads:
\version "2.13.33" % 2.12 does the same
\relative c'' {
\time 3/4
\voiceTwo
% neither of two works:
\overri
Am 13.09.2010 um 10:59 schrieb Dmytro O. Redchuk:
On Fri 10 Sep 2010, 22:58 Patrick Schmidt wrote:
Hi all,
when voices get very close to one another ledger lines and/or note
heads seem to change their behavior. In the following example the
note head of the c is too far to the right. The
Hi all,
when voices get very close to one another ledger lines and/or note
heads seem to change their behavior. In the following example the
note head of the c is too far to the right. The ledger lines of the
notes on the left side of the chord are shorter than normal. The
ledger line of
Am 10.09.2010 um 04:16 schrieb Patrick McCarty:
Hi,
On 2010-09-09, Patrick Schmidt wrote:
\version "2.13.31" % on Mac OS X
\paper{ raggedright = ##t }
initialAcciaccatura = \relative c' {
\acciaccatura 8
8
}
initialGrace = \relative c'' {
Good morning LilyPond,
\version "2.13.31" % on Mac OS X
\paper{ raggedright = ##t }
initialAcciaccatura = \relative c' {
\acciaccatura 8
8
}
initialGrace = \relative c'' {
\grace c16
c4
}
initialAppoggiatura = \relative c'' {
\appoggiatura c16
c4
}
Hi Phil,
Am 31.08.2010 um 11:48 schrieb Phil Burfitt:
Hi Patrick,
I'm not familiar with the inner workings of lilypond, but it
seems to me the problem occurs when a TabStaff command
(\set TabStaff.minimumFret) is executed in a Staff context.
using \set minimumFret = #5 instead should solve the
Hi all,
I found two instances in which \set TabStaff.minimumFret = #xy causes
an unwanted TAB-symbol in between a normal Staff and a TabStaff
(\version 2.13.30):
a) no explicit \clef "xy"-command:
music = {
\set TabStaff.minimumFret = #5
c'1
}
\score {
<<
\new Staff {
\m
Am 23.08.2010 um 21:26 schrieb Marc Hohl:
Patrick Schmidt schrieb:
Hi all,
in the following example misplaced tremolos appear in tablature
without \tabFullNotation. With \tabFullNotation the symbols are
placed correctly but IMO in both cases the tremolo symbols are too
massive in
Hi all,
in the following example misplaced tremolos appear in tablature
without \tabFullNotation. With \tabFullNotation the symbols are
placed correctly but IMO in both cases the tremolo symbols are too
massive in tablature (see attached pngs).
\version "2.13.30"
music = {
4:16
\stem
Hi all,
it doesn't seem to be possible to draw arrow-type arpeggios across
several voices. In the following example the arpeggio is drawn but
the arrow is missing.
\version "2.13.30"
musicVoiceOne = {
\arpeggioArrowUp
4\arpeggio
}
musicVoiceTwo = {
%\arpeggioArrowUp
e4\arpeggio
}
Am 17.08.2010 um 05:30 schrieb Carl Sorensen:
On 8/16/10 3:30 PM, "Patrick Schmidt" wrote:
Dear LilyPonders,
while trying to typeset some vocal music I encountered some
difficulties with \autoBeamOff:
1) \autoBeamOff has no effect on other voices when used in a global
vari
Dear LilyPonders,
while trying to typeset some vocal music I encountered some
difficulties with \autoBeamOff:
1) \autoBeamOff has no effect on other voices when used in a global
variable/ghost voice. It has to be turned on explicitly for each
voice. This is probably intentional but AFAIK
Well, I guess my offer was not taken into consideration. So IINM
there are four offers:
1x 75$, 2x 75–150$, 1x 10€
patrick
Am 26.07.2010 um 11:25 schrieb Marc Hohl:
Graham Percival schrieb:
Bug Squad: two bounty offers in this email; please add to tracker.
Three offers - 2x 75$, 1x 10 €
Dear Community,
I get a bus error when I try to invoke 2.13.4.1 from the command-line (Mac OS X
10.4.11). I followed the guidelines in the manual "Program Usage" (section
MacOS X on the command line). Compiling ly-files with a texteditor (jEdit)
works just fine.
Thanks for any hint.
patrick
Hi docwriters,
in version 2.13.3 the default for the automatic beaming of eighth notes in
\time 4/4 seems to have changed. In former versions four eighth notes got one
beam now there are four groups of two eighth notes in a bar. In the Learning
Manual for 2.13.3 in section 2.2.5 (p. 22) the fir
Hi docwriters,
this is just a minor issue but I noticed that the pipe symbol (|) is used in
the Learning Manual (version 2.12.2 and 2.13.3) in various places but I
couldn't find an explanation of it's function in the Learning Manual. The
symbol is also missing in the index. (I know it's functio
Dear developers,
as I quite often engrave Rock Riffs I discovered that it is
comparatively complicated to typeset chord slides (using hidden
voices and spacer notes). From my point of view it would be more
intuitive if it were possible to set glissandi in chords just the way
ties are set,
Dear developers,
thank you all for Lilypond! I'm very fond of it.
While trying to engrave a piece with polyphonic elements both
"traditionally" (with noteheads) and with tablature I found out that
it is not possible to get the tablature right with the following code:
\version "2.13.3"
poly
38 matches
Mail list logo
