Hello,
I added issues #185 a few years ago. Originally I contended this was a bug.
But it's marked as a low priority enhancement. If you run the sample code I
would still contend that it is a bug. What it renders is simply incorrect,
weird, bogus, notation (a note with two heads).
I'm on a p
The 11th (or 4th) if stated, always implies a suspended chord where the 3rd
(10th) is omitted. A 13 alone also rules that the 7th is flatted, same with
9 or 7 making the chord a dom7. 9/add13 is confusing and non-standard, it
should be just 13 as any player would know to flat the 7th and optiona
n rhythmic staff
to show the rhythm...
Thanks, Rick
Graham Percival-2 wrote:
>
> Thanks for the report! This is a feature request, not a bug, but it's
> worth adding:
> http://code.google.com/p/lilypond/issues/detail?id=185
>
> Cheers,
> - Graham
>
> Rick Hans
Luc wrote:
>
> Fingerings and stringnumbering don't avoid collision with accidentals!
>
> \version "2.11.0" % on Windows XP
>
> \paper {ragged-right = ##t }
>
> {\set fingeringOrientations= #'(left) }
> {\set strokeFingerOrientations = #'(left) }
> {\set stringNumberOrientations
The RhythmicStaff is not squashing out all the noteheads like it should be.
It is common to want to re-use the notes of a chord progression as either a
rhythmic staff or a notes staff (to avoid having to write more music just
for the rhythmic staff). When you use chords on RhythmicStaff it is no
Version 2.11.2 on windows 2000 and also on windows XP
This example produces a hard crash if the \keepWithTag is set to "Flop" but
works fine if the \keepWithTag is set to Flip. But it works fine with Flop
if I simply reverse the order of the Flip and Flop lines in the music, (but
then Flip will
v2.11.2 Windows...
In the following example one tag filter works but the other fails.
If you use the "chordfret" filter name to generate the chord inversions it
fails, but if you use the "chordname" tag filter to generate those chord
inversions it works. Conversely I also tried \removeWithTag
v2.11.0 Windows 2000 and Windows XP.
If I try to use the tagged variable called \varNamesFrets with the desired
tag filter, LilyPond suffers a hard crash with this message:
The instruction at "0x00554e42" referenced memory at "0x000c" the memory
could not be "read".
The example below wil
v2.11.0 Windows 2000 and Windows XP.
If I try to use the tagged variable called \varNamesFrets with the desired
tag filter, LilyPond suffers a hard crash with this message:
The instruction at "0x00554e42" referenced memory at "0x000c" the memory
could not be "read".
The example below wil
Hernan-7 wrote:
>
> In my first try with Lilypond (2.10.0), I seem to have met a bug that is
> driving
> me crazy. A pair of ties randomly appears and desappears from the output
> (png o
> pdf).
> Well, not really randomly, but small changes in the score (seemingly
> unrelated)
> makes the tie
FYI,
when doing \parenthesize of a note in a chord...
If the note has an accidental then the opening paranthesis should also
encompass the accidental. Currently the accidental and opening paranthesis
are printing on top of each other. The closing paranthesis appears to be
fine.
--
View this
This bug is simple to fix until the installer is changed, just use Windows
explorer to register files with .ly extension to invoke the lilypond exe.
Go to Windows Explorer / Tools / File Options - on that panel you will
notice that .ly files have no "association" with any known exe. Just
select/
ar1.ly
cd "..\When I Fall In Love"
Music_Guitar1.ly
cd "..\When Sunny Gets Blue"
Music_Guitar1.ly
cd "..\When You Wish Upon A Star"
Music_Guitar1.ly
cd "..\Yesterday"
Music_Guitar1.ly
REM Assemble the books
cd "..\_Jobs\BuildAll"
gs @_BookAs
When I try to run a .ly file from a BAT script, I get an error that says
"myMusic.ly" is not a vaid Win32 application.
Version 2.9.21
--
View this message in context:
http://www.nabble.com/Lilypond-does-not-work-with-Windows-anymore-tf2386478.html#a6652592
Sent from the Gnu - Lilypond - Bugs
" sounds
like a negative number which would make it an invalid memory location on
WindowsXP?
Rick Hansen (aka RickH) wrote:
>
> I'm using the following markup to set my headings, the markup for page 1
> causes lily to hard crash whenever I try to change the \fontsize#4.3
&
I'm using the following markup to set my headings, the markup for page 1
causes lily to hard crash whenever I try to change the \fontsize#4.3
statement to any value above #4.3. But this only happens on some of my
songs, other songs let me get up to larger or smaller font sizes. Is this a
known b
I thought of that but thought it would fail because if your offset number is
an odd number it messes up the even/odd checking. adding an even number
offset value still retains the even/odd-ness of the original number, an odd
offset would invert even/odd-ness. But I guess it's fixed now anyway.
at far.
thanks
Rick
Joe Neeman-2 wrote:
>
> On Wed, 2006-09-27 at 14:42 -0700, Rick Hansen (aka RickH) wrote:
>> It appears that the "first-page-number" property is not working, here is
>> an
>> example: Note that the first page number (\fromproperty
>&
It appears that the "first-page-number" property is not working, here is an
example: Note that the first page number (\fromproperty
#'page:page-number-string) in the odd/even mirrored footers always comes out
as 1, even when setting the first-page-number property to a different value
like #4. (v
pects
both/all system-count's. Actually this is pretty good because it gives you
a handy way to limit and control longer ossias. Please disregard this bug
report.
Rick Hansen (aka RickH) wrote:
>
> v2.9.17
>
> I believe I have uncovered a bug when using the \markup { \score
v2.9.17
I believe I have uncovered a bug when using the \markup { \score { ... } }
capability. In the following example I assign a markup score of 2 measures
to a variable called "varFreeFormOssia". Then in the main music I apply
that markup variable to a note. I would expect 2 measures of ma
Yes, I am using polyphony with voiceOne, voiceTwo, voiceFour and oneVoice,
also assigning the lyrics using \lyricsto to the melody voice. My
work-around was to simply break up the complex expression and put some of
the notes in voiceTwo that form the chord.
I may just put it back the way it was
Actually the grace note is not the problem, rather the lyrics are ignoring a
quarter note expressed as a complex expression.
Here is the quarter note being ignored by lyrics:
<< { \acciaccatura fs16 \stemUp g4 } \\ { \acciaccatura fs,16 \stemUp g4 }
>>
Also the following beat gets ignored, so t
v2.8.5
If you have lyrics that align properly, then add an \acciaccatura to one of
the notes that the lyrics are assigned to. The lyrics ignore that graced
note and scoot up to the next note. This then causes the lyrics to be off
by one note for the remainder of the score. If you need an exam
v2.8.5
The alternative bracket is not continuing onto the subsequent line whenever
a line break occurs within the alternative ending.
thanks
Rick
--
View this message in context:
http://www.nabble.com/Volta-%5Calternative-bracket-getting-lost-on-line-%5Cbreak-tf1986337.html#a5451324
Sent from
The Windows file system is responding to the way both Adobe and LP opened the
file. LP maybe opens it as New Write with Exclusive Control after issuing a
Delete request. I know Adobe opens it as Read/Share, but the file being
opened at all would conflict with another program trying to delete it,
Laura Conrad wrote:
>
>> "Geoff" == Geoff Horton <[EMAIL PROTECTED]> writes:
>
> >> Nobody in the USA uses Old Roman or even learns it in grade
> >> school.
> Geoff> "Nobody" is a little strong. I knew about it :)
>
> I didn't know there was an extreme version where there was n
nts.
Nicolas Sceaux wrote:
>
> "Rick Hansen (aka RickH)" <[EMAIL PROTECTED]> writes:
>
>> I'm using 2.8.0
>>
>> This is a minor bug, probably easy to fix...
>>
>> For guitar fret board markup, the position marker
>>
>> When
I'm using 2.8.0
This is a minor bug, probably easy to fix...
For guitar fret board markup, the position marker
When the 4th fretting postion is called for, it prints "" instead of
"iv", there is no such thing as roman numeral "". I'm pretty sure all
the other roman numerals are ok.
Actually I deleted this post, because shortly after I posted it I discovered
a syntax error in the setting of one of the variables to some markup. But
the funny thing was that there was no compiler error, the program just said
parsing... then it ended 7 seconds later. I discovered the bug by cop
I've made a \include file of chord fret diagrams that could possibly contain
about 10,000 assignment variables when I'm all done.
I've been testing this \include file with about 150 variables and it fails
to compile, but when I reduce the number of variables to about 80 or so the
same unchanged s
I'm entering a chordNameSeparator of space however lilypond seems to be
trimming it to an empty string anyway. The following two examples both
render chord names with no separation, the first example should be placing a
space between each chord name interval, the second example is working ok.
Ex
A couple of previous threads were dealing with the issues of trying to use
9x12 (standard sheet music size) paper with LilyPond PDF output
Is there a fix available for this at this time, or will a fix be included in
any version after 2.8.0?
Can a non-programmer print properly onto 9x12 paper
If it's any help to the debuggers. I installed 2.8.0 on Win XP this week,
and my PDF files are pretty small, around 50k for a 1 page song sheet with
chords lyrics and 3 voice polyphony. Prior to installing, my machine had
pretty much nothing on it except Microsoft applications, so I assume it
in
I'm new so please forgive me.
How do I submit bug reports and their supporting .ly and .pdf (input/output)
documents?
Can I just send an Email to somewhere with the documents attached?
If so to where?
I've learned LiliPond quicly, but am running into items that appear to be
real bugs and was t
Here is a work-around that I'm using for now:
\override Score.RehearsalMark #'break-align-symbol = #'clef
\mark \markup{ \hspace #0 \raise #1.5 "Bossa Nova" }
--
View this message in context:
http://www.nabble.com/Rehearsal-marks-buglist-t1375778.html#a3738691
Sent from the Gnu - Lilypond - Bu
I want to print on standard sheet music paper in the USA, which is 9x12
inches. I added this form to the "paper.scm" file and also set the correct
width and height in my .ly file. However all the printed output to PDF
still behaves as though the paper is 8.5x11 and margin properties do not
refle
37 matches
Mail list logo
