On Tue, Jul 13, 2010 at 11:05:10PM +0200, Federico Bruni wrote:
Hi,
I've found a small error in documentation.
In Notation 1.8.2, section Graphic notation inside markup:
http://lilypond.org/doc/v2.13//Documentation/notation/formatting-text#graphic-notation-inside-markup
Can anyone please add this new offer to the tracker?
http://code.google.com/p/lilypond/issues/detail?id=1196
Also the offer from Rosea Grammostola is still missing, but I can't
remember how much it was... Rosea, could you remember us?
Thanks,
Federico
Il giorno mer, 04/08/2010 alle 09.56
If I open the index of Notation 2.13:
http://lilypond.org/doc/v2.13/Documentation/notation/lilypond-index
I get the following error:
Content Encoding Error
The page you are trying to view cannot be shown because it uses an invalid
or unsupported form of compression.
Does it happen to you as
@gmail.com
2010/8/26 Federico Bruni fedel...@gmail.com:
If I open the index of Notation 2.13:
http://lilypond.org/doc/v2.13/Documentation/notation/lilypond-index
I get the following error:
Content Encoding Error
The page you are trying to view cannot be shown because it uses
2010/8/26 Graham Percival gra...@percival-music.ca
On Thu, Aug 26, 2010 at 12:39:50PM +0200, Federico Bruni wrote:
And I've just noticed another bigger problem: all the manuals linked in
http://lilypond.org/website/manuals.html (the new website)
are the stable ones (v2.12, see the link
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 when I want to hide notes on
Staff I hide notes on TabStaff as well.
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
implemented in \hideNotes, yet. Look at my
Il giorno dom, 19/12/2010 alle 15.36 +0100, Patrick Schmidt ha scritto:
Well, Carl told me what needs to be changed in the definition of
\hideNotes in order to also hide fret numbers in tablature. So in
future it won't be necessary to define an extra command like
\hideFretNumber...
Hi,
I've seen an error in a snippet in NR 2.4.1, Default tablature:
http://lilypond.org/doc/v2.13/Documentation/notation/common-notation-for-fretted-strings#default-tablatures
The section is Slides in tablature.
There are two errors actually:
- last two 5 and 7 frets are printed badly
Il giorno mer, 13/04/2011 alle 10.05 +0200, Valentin Villenave ha
scritto:
Hi Federico, hi everybody,
here's a patch for the documentation accordingly to what you proposed.
I'm not entirely sure it's suitable to introduce a new function (or
more exactly, I'm wondering if it shouldn't rather
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!
I hope that Patrick will jump in and share his opinion on this
matter.
In
Il giorno dom, 17/04/2011 alle 21.04 +0200, Patrick Schmidt ha scritto:
Last year I found out that I had to set TabNoteHead whiteout
property to
false when I make the TabNoteHead transparent:
it?
http://code.google.com/p/lilypond/issues/detail?id=1459
From cf502c4307263fd2b09d0e098a169d108d98328c Mon Sep 17 00:00:00 2001
From: Federico Bruni fedel...@gmail.com
Date: Mon, 18 Apr 2011 09:03:25 +0200
Subject: [PATCH] hideNotes should hide also TabNoteHead in TabStaff
---
ly/property-init.ly
I disabled emails from lilypond-bug so I hope this has not been reported
already.
The attached snippet worked fine with 2.13.58, it broke since 2.13.60 (I
never tried 2.13.59).
Here's the error message in the console:
programming error: No viable beam quanting found. Using unquanted y
value.
As it said here, chordGlissando is a hack:
http://code.google.com/p/lilypond/issues/detail?id=1617
However it's a nice hack so I hope this bug report will help to make it
better.
If you repeat this music two or more times, the notes of the first chord
are raised by one octave each time:
Thanks Carl,
yes, the issue is related to relative mode
Il giorno gio, 21/04/2011 alle 07.13 -0600, Carl Sorensen ha scritto:
put an octave check on the second chord. That should solve the
problem.
g b e8 a='' d fis
I made several tries but none worked.
This works:
\octaveCheck c'
Il giorno sab, 23/04/2011 alle 19.43 +0100, Graham Percival ha scritto:
On Thu, Apr 21, 2011 at 04:52:52PM +0200, Federico Bruni wrote:
I made several tries but none worked.
This works:
\octaveCheck c'
\chordGlissando
bes cis fis8 b\3 d g
(full snippet attached
Il giorno dom, 24/04/2011 alle 19.43 -0600, Carl Sorensen ha scritto:
I find it simpler to just do
\new TabStaff \relative c' {
\chordGlissando
bes\3 cis\2 fis\18 b\3 d\2 g\1
\chordGlissando
bes='\3 cis\2 fis\18 b\3 d\2 g\1
}
It still gets the warning, but I think it's
Il giorno lun, 25/04/2011 alle 00.09 +0200, Federico Bruni ha scritto:
Or should I rather edit
Documentation/snippets/new/chord-glissando-in-tablature.ly?
I've changed my mind and I think that I should edit this file instead of
fretted-strings.itely.
In the meanwhile I've realized
Is this a bug? (the comments in the example explain everything)
Thanks
\version 2.13.61
music = \relative c' {
% connect wrong strings in TabStaff
dis\2\glissando e\2 a\1
e\2 a\1\glissando dis\2
% glissando direction in TabStaff
e8\2\glissando dis % correct
e\2 a\1\glissando
Phil Holmes wrote:
There are 2 bugs against glissandi in 13.61 - 1639 and 1640. I would
assume your problem is related.
Maybe not.
The two bugs are fixed:
http://codereview.appspot.com/4457042
But I still get the same error using the latest sources... version
2.15.0 (?!?).
Please reply to all
I think that there are some wrong pitches in this snippet:
http://lilypond.org/doc/v2.13/Documentation/snippets/fretted-strings#fretted_002dstring-harmonics-in-tablature
Can you check it?
I would write as in the attached file (see diff).
Thanks,
Federico
---
As you can see in the following example, when using harmonicOn, fret
numbers in TabStaff are not enclosed by angled brackets (while Staff is
ok).
It looks like a bug.
\version 2.15.0
music = \relative c'' {
% Ok, it works in Staff and TabStaff
b\2\harmonic2 e\harmonic
% it works on
Il giorno lun, 23/05/2011 alle 16.34 +0300, Dmytro O. Redchuk ha
scritto:
On Sun 22 May 2011, 21:47 Federico Bruni wrote:
I think that there are some wrong pitches in this snippet:
http://lilypond.org/doc/v2.13/Documentation/snippets/fretted-strings#fretted_002dstring-harmonics-in-tablature
Il giorno mar, 24/05/2011 alle 11.33 +0300, Dmytro O. Redchuk ha
scritto:
On Mon 23 May 2011, 20:17 Federico Bruni wrote:
I think it's pretty clear, but I might be missing something.
So we just need a guitar player, or someone who knows something about
physics (this is definitely not me
Il giorno lun, 13/06/2011 alle 20.10 +0200, Janek Warchoł ha scritto:
Hi,
wish i had not missed this thread and found it earlier...
I found a diff in one of your previous e-mails, but it's kind of
weird, so i'll simply write how things should look.
Hi Janek,
thanks for taking care of it!
Il giorno mar, 14/06/2011 alle 09.44 +0200, Janek Warchoł ha scritto:
2011/6/13 Federico Bruni fedel...@gmail.com:
Il giorno lun, 13/06/2011 alle 20.10 +0200, Janek Warchoł ha scritto:
Concerning the last harmonic: it should be e'' (i.e. note on third
ledger line - remember that guitar
Hi,
the link to 2.12 Docs redirects to 2.14 docs:
http://lilypond.org/all.html
Please fix it, thanks
Federico
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Il giorno mer, 22/06/2011 alle 18.24 +0200, Francisco Vila ha scritto:
2011/6/20 Federico Bruni fedel...@gmail.com:
Hi,
the link to 2.12 Docs redirects to 2.14 docs:
http://lilypond.org/all.html
I see it correctly pointing to 2.12, so it seems that somebody has
fixed it. Right
Il giorno gio, 23/06/2011 alle 19.43 +0100, Graham Percival ha scritto:
The link is correct, but if you
click you are redirected to http://lilypond.org/manuals.html
No, you aren't. Reload the page and/or clear your browser cache,
and try again.
Yes, you are right. It works now.
I
Graham asked me to report this problem here as a critical item.
Background discussion:
http://lists.gnu.org/archive/html/lilypond-devel/2011-07/msg00085.html
Here's the verbose output of the command (which fails occasionally):
fede@fede-laptop:~/lilypond-master/build$ out/bin/lilypond
--verbose
In the second snippet of code:
%%% top of file symphony-cello.ly
\include ../definitions.ily
\include ../Notes/cello.ily
../definitions.ily
should be replaced by
../symphonyDefs.ily
because definitions.ily is not in the directory tree
cheers,
Federico
I think I've found a bug in the doc:
Notation Reference 2.4.3
In the See also subsection there is:
Installed Files: ‘scm/string-tunings-init.scm’ contains predefined
banjo tunings.
That file doesn't exist.
AFAIK, the file is ly/string-tunings-init.ly
Please reply to all, otherwise I won't
Hi,
I've just started translating the NR and I've noticed a small error in
the markup of this snippet:
Documentation/snuppets/new/pitches-headword.ly
\markup \italic { dolce e molto ligato }
/s/ligato/legato
legato is the correct italian word
Cheers,
Federico
Got no answers on -devel, so I forward here (probably more appropriate
place).
Thanks,
Federico
Il 05/01/2012 13:44, Federico Bruni ha scritto:
Issue 1721 reported that @rlsr{Name} keeps the text in english but
translates the link in the translated manuals (no idea where the
translation comes
2012/4/11 Colin Hall colingh...@gmail.com:
On Wed, Apr 11, 2012 at 09:52:18AM +0200, Federico Bruni wrote:
Pull-off and hammer-on are already implemented since 2.13.x version series.
I don't use tablature notation so I had a look in the docs and I see
no mention of these features.
Sorry
I'm CCing the tablature list, in case anyone (Patrick?) has some
suggestions about this doc addition.
Il 12/04/2012 00:40, Colin Hall ha scritto:
I think you are right, I cannot find any mention in the doc.
It should be in NR 2.4.1
Pull-off and hammer-on are slurs.
Hammer-on when the
In the mentioned file, around line 236, the following snippet should be
changed because of the new property introduced by Marc (issue 2348):
@lilypond[quote,ragged-right,verbatim]
\new StaffGroup
\new Staff \relative c {
\clef treble_8
\time 2/4
c16 d e f g4
c,16\5 d\5
forgot to add that there's already a regession file, which explains this
property:
input/regression/tablature-open-string-handling.ly
Il 25/04/2012 00:40, Federico Bruni ha scritto:
In the mentioned file, around line 236, the following snippet should be
changed because of the new property
If I change font (any font) in TabStaff, a slur in TabStaff gets ugly
(only in 2.15.39 and latest git, not in 2.14.2).
It doesn't occur in any slur, just in some.
Find attached the png previews: the problem is in the last two notes.
Here's the minimal example:
## Snippet
global = {
\key d
Another report about slurs and TabStaff.
IIUC, now slurs connect note heads in polyphony (instead of stems).
I _think_ that it's a desired output.
However, it's breaking the TabStaff slurs.
Find attached .png examples (see differences between 2.14.2 and 2.15.40).
here's the minimal example:
Il 04/06/2012 09:11, m...@apollinemike.com ha scritto:
On 4 juin 2012, at 08:05, David Kastrup wrote:
Federico Brunifedel...@gmail.com writes:
Another report about slurs and TabStaff.
IIUC, now slurs connect note heads in polyphony (instead of stems).
I _think_ that it's a desired output.
http://lilypond.org/doc/v2.15/Documentation/notation/long-repeats#index-repeat-and-slur
NR 1.4.1, Normal Repeats, Known issues and warnings
Slurs that span from a \repeat block into an \alternative block will
only work for the first alternate ending.
Why don't suggest a workaround?
I know,
In notation/fretted-strings.itely there are the following index entries:
##
@cindex harmonic indications in tablature notation
@cindex tablature and harmonic indications
@cindex slides in tablature notation
@cindex tablature and
Il 07/06/2012 11:21, m...@apollinemike.com ha scritto:
On 7 juin 2012, at 07:36, Federico Bruni wrote:
Il 04/06/2012 09:11, m...@apollinemike.com ha scritto:
On 4 juin 2012, at 08:05, David Kastrup wrote:
Federico Brunifedel...@gmail.com writes:
Another report about slurs and TabStaff
Il 13/04/2012 11:45, Colin Hall ha scritto:
On Fri, Apr 13, 2012 at 09:08:41AM +0200, Federico Bruni wrote:
I'm CCing the tablature list, in case anyone (Patrick?) has some
suggestions about this doc addition.
Il 12/04/2012 00:40, Colin Hall ha scritto:
I think you are right, I cannot find
I've started using \footnote today, so I might miss something.
Here the footnote is printed twice, first in Staff, then in TabStaff:
\version 2.15.40
#(set-default-paper-size a8landscape)
\header { tagline = ##f }
music = \relative c' {
\footnote #'(1 . 1)
\markup { Text text }
c
}
Il 10/06/2012 14:42, Colin Hall ha scritto:
Hi Federico,
The SVG file you sent looks nothing like the PNG images that you sent
in your original bug report that started this thread. It looks a bit
like the one for your other bug report Ugly slur in TabStaff if font
is changed
Can you clarify
Il 10/06/2012 15:21, m...@apollinemike.com ha scritto:
You can have multiple footnotes at the same moment (just as the notes
are recycled in the staves, so too are the footnotes). You can use
tags as a workaround.
Ok, easy in the minimal example.
I'm having trouble with a real score, but I'll
Il 10/06/2012 17:11, Colin Hall ha scritto:
You'll forgive me, I hope, but my interest begins and ends with
administration of the issue tracker.
So, could you confirm whether there are two distinct bug reports here, or just
one?
they are both about ugly slurs, but they are distinct:
#2587:
Il 21/06/2012 22:07, m...@apollinemike.com ha scritto:
Have you tried to visualize the SVG in several browsers? Could you
confirm if the image is the same or different depending on the
browser?
It's the same in Chromium, Firefox and Inkscape.
See svg attached.
\version 2.15.41
{
\tempo 4
Il 23/06/2012 15:53, Dr. med. Kai Lautenschläger ha scritto:
Hi to all,
If this has been answered before, please point me there. I searched
the manual several times, but couldn't find an answer, that helped
me.
I'm CCing lilypond-bug, because I believe that missing index entries for
book
Il 23/06/2012 17:23, Phil Holmes ha scritto:
Federico Bruni fedel...@gmail.com wrote in message
news:4fe5d2ed.6050...@gmail.com...
Il 23/06/2012 15:53, Dr. med. Kai Lautenschläger ha scritto:
I'm CCing lilypond-bug, because I believe that missing index entries
for book and bookpart doesn't
Il 24/06/2012 11:33, Federico Bruni ha scritto:
Well, it's weird.
I can't see those lines neither in the index nor in the command index
(and I did force the browser cache with Ctrl + F5).
Are you looking at the documentation v2.15 in the website?
See screenshots attached
even better than
Il 24/06/2012 12:50, David Kastrup ha scritto:
git grep -n index book
Documentation/cs/learning/fundamental.itely:107:@funindex \book
Documentation/cs/learning/fundamental.itely:237:@funindex \book
Documentation/de/learning/fundamental.itely:107:@funindex \book
Il 24/06/2012 13:12, David Kastrup ha scritto:
Federico Brunifedel...@gmail.com writes:
Il 24/06/2012 12:50, David Kastrup ha scritto:
git grep -n index book
Documentation/notation/input.itely:273:@funindex \bookOutputSuffix
Documentation/notation/input.itely:274:@funindex
.
As it's a trivial change, I attach a patch.
--
Federico
From 702629cfa9af2be360c8cfb182e141e3f14521f5 Mon Sep 17 00:00:00 2001
From: Federico Bruni fedel...@gmail.com
Date: Sun, 15 Jul 2012 18:56:46 +0200
Subject: [PATCH] stringTunings snippet: TabStaff context is required to
display the right
Hi
in CG 3.2.1, Initializing a repository
the recommended way to download the source code is using clone:
git clone git://git.sv.gnu.org/lilypond.git ~/lilypond-git
git clone sets only the master branch.
Previously the doc contained complex git commands but there were full
instructions for
Il 04/08/2012 02:27, John Mandereau ha scritto:
Il giorno ven, 03/08/2012 alle 01.17 +0200, Federico Bruni ha scritto:
git branch --track translation origin/translation
git checkout translation
FWIW
git checkout origin/translation
is a shorthand for the 2-commands sequence you gave
Hi
in the three harmonics snippets below, the pitches in Staff are not
correct, at least for a guitar:
http://lilypond.org/doc/v2.15/Documentation/notation/common-notation-for-fretted-strings#index-_005charmonic-2
We should add \clef G_8, like in this example:
\layout { \override
Il 07/08/2012 18:53, Graham Percival ha scritto:
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
maybe try following this advice?
git checkout -b
Il 07/08/2012 22:43, Colin Hall ha scritto:
On Tue, Aug 07, 2012 at 07:08:20PM +0200, Federico Bruni wrote:
Il 07/08/2012 18:53, Graham Percival ha scritto:
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command
NR 4.1.6, \paper variable for page breaking
http://lilypond.org/doc/v2.15/Documentation/notation/other-_005cpaper-variables#_005cpaper-variables-for-page-breaking
I'd like to force the add of a blank page in case the number of pages in
a book is odd.
I guess I should use blank-last-page-force.
Hi Colin,
I'm in vacation and without laptop until next friday, that's why I couldn't
reply to Joe's email.
I've just seen that Trevor has made a doc patch, so yes the report is
closed.
Thanks
Il giorno 17/ago/2012 11:48, Colin Hall colingh...@gmail.com ha scritto:
Federico Bruni fedelogy
LM 4.2.1 states:
This Slur page in the IR tells us first that Slur objects are created
by the Slur_engraver. Then it lists the standard settings. Note these
are not in alphabetic order.
Actually, they are in alphabetic order.
Maybe something is changed since the LM was written?
--
Federico
Il 29/08/2012 18:50, Federico Bruni ha scritto:
LM 4.2.1 states:
This Slur page in the IR tells us first that Slur objects are created
by the Slur_engraver. Then it lists the standard settings. Note these
are not in alphabetic order.
Actually, they are in alphabetic order.
Maybe something
Il 29/08/2012 20:29, Marek Klein ha scritto:
Thank you for the report, this has been added as
http://code.google.com/p/lilypond/issues/detail?id=2791
As I translate the chapter, I've found some other small inaccuracies or
typos, already reported in the tracker.
Now I've found something which
By default, tied notes in TabStaff are hidden.
However, if the tied note is in a chord which starts a glissando (and no
glissando starts from this note), the tied note appears.
It is not a regression, it happens in 2.14.2 as well.
But I think that it would be nice if it was fixed, if possible.
Il 08/09/2012 17:54, Trevor Daniels ha scritto:
If not, please add it to issue 2791.
Yes please.
done
I see that James has already uploaded a patch
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Il 08/09/2012 17:50, Federico Bruni ha scritto:
By default, tied notes in TabStaff are hidden.
However, if the tied note is in a chord which starts a glissando (and no
glissando starts from this note), the tied note appears.
It is not a regression, it happens in 2.14.2 as well.
But I think
In NR 3.5.7, The Articulate script:
After altering your input file this way, the visual output is heavily
altered, but the standard \midi block will produce a better MIDI file.
This alteration refers to the use of \unfoldRepeats, I suppose.
Why don't we suggest to use two score blocks, one
As you can see in the attached image, the pull-off sign (slur in
TabStaff) is moved up when using manual beaming.
It looks like Stems in default TabStaff are just made transparent when
using manual beams. Maybe the stem stencil should be set to false also
in this case.
The problem occurs on
2012/11/1 Micah Walter mi...@hsomnibus.com:
I'm trying to use the \markuplines command in my document.
It runs fine on my Mac, but I get the following error
on a Windows machine:
error: unknown escaped string: `\markuplines'
maybe you have an older version of LilyPond on Windows?
I've just stumbled on this converter from .bww to .ly:
http://www.jezra.net/projects/bwwtolily
Jon Kulp already announced this converter in -user list 3 years ago:
http://lists.gnu.org/archive/html/lilypond-user/2009-07/msg00030.html
I don't know anything about bagpipes music, but I think that
Il 03/11/2012 19:04, Jean-Charles Malahieude ha scritto:
Hi John and all,
I just noticed that, because the out of tree build, lilypond.pot gets
polluted by personal path, what does not happen with an in tree build.
e.g. we get, when out of tree :
#: parser.yy:174 parser.yy:188
What about adding the following @cindex in
Documentation/notation/input.itely?
@unnumberedsubsubsec Instrument names
@cindex instrument names
@cindex MIDI, instrument
@funindex Staff.midiInstrument
The new one is:
@cindex MIDI, instrument
Most of the Instrument name links in the index point
2012/11/23 Pierre Perol-Schneider pierre.schneider.pa...@gmail.com
?? Confusing string number 0 ??
Humm ... not sure...
If string number is wanted Thomas should write :
\version 2.17.6
\new TabStaff { d\4 }
Don't you think ?
The bug was found because I was updating a Mutopia file where
If I specify an harmonic using \harmonicByFret or \harmonicByRatio,
point-and-click works fine only if the note following the command is
included inside or {}
Otherwise, point-and-click opens ly/music-functions-init.ly, where these
commands are defined.
Try this snippet:
\version 2.17.7
Il 24/11/2012 10:32, David Kastrup ha scritto:
We'd better use or {} ? The latter, I guess.
No, that's just masking the problem.
URL:http://code.google.com/p/lilypond/issues/detail?id=2974
contains a patch fixing this.
ok, thanks
___
Il 19/11/2012 22:11, Gerard McConnell ha scritto:
Hello,
I understand that I can send information to separate (sequential) MIDI
channels by using different staves.
You can also send each voice to a different channel, see Notation
Reference 3.5.1, Instrument Names, selected snippets (which
Dear Bug Squad
I don't want to push you but I think that you may have missed this
report, hidden inside a reply to a question made in lilypond-user:
http://lists.gnu.org/archive/html/bug-lilypond/2012-11/msg00112.html
I think that midiChannelMapping is not properly documented.
It is listed in
Shouldn't the slur go from the note inside of the chord which it
actually starts on to the note which it
actually ends on?
This question was asked in this thread:
http://lists.gnu.org/archive/html/lilypond-user/2011-06/msg00394.html
I wonder if there's any progress on it or some open issue
Il 10/12/2012 23:17, James ha scritto:
When you run 'configure', it should warn you this is missing.
http://code.google.com/p/lilypond/issues/detail?id=2529
You are right: I forgot to re-run configure before make.
I uninstalled the cyrillic font just to test it and:
ERROR: Please install
Il 11/12/2012 01:26, Colin Hall ha scritto:
On Mon, Dec 10, 2012 at 11:48:11PM +0100, Federico Bruni wrote:
Il 10/12/2012 23:17, James ha scritto:
When you run 'configure', it should warn you this is missing.
http://code.google.com/p/lilypond/issues/detail?id=2529
You are right: I forgot
I'm a bit confused about the use of minimumFret and restrainOpenString.
Maybe adding a warning in the documentation could be a good idea.
The best way I can explain it is pasting this input code (commented).
Problem is in the last measure.
\version 2.17.9
music = \relative c' {
\set
Il 16/12/2012 10:12, Colin Hall ha scritto:
Federico, I reproduced your output, which looks fine to me, but I am
not a fret player.
So, perhaps you could explain exactly what is wrong and I can add your
comment to the tracker? There's a png of the output on the tracker.
New tracker here:
Il 16/12/2012 11:06, Colin Hall ha scritto:
It wasn't clear to me from Keith's post that the re-opened issue
was responsible for what you were seeing.
If you could jointly confirm that issue 2348 will resolve your thing
then yes, we can close off the new tracker.
I confirm it
Il 08/12/2012 19:44, Ralph Palmer ha scritto:
On Sat, Dec 8, 2012 at 5:14 AM, Federico Bruni fedel...@gmail.com
mailto:fedel...@gmail.com wrote:
Shouldn't the slur go from the note inside of the chord which it
actually starts on to the note which it
actually ends
Il 22/12/2012 23:35, Eluze ha scritto:
in
http://www.lilypond.org/doc/v2.17/Documentation/notation/guitar#indicating-harmonics-and-dampened-notes
the 2nd example shows/dampened notes/
IMO this example is overloaded - it first displays 3 chords where the
dampened notes are probably not playable
Il 25/12/2012 11:25, Eluze ha scritto:
I've created a tracker for this documentation enhancement here:
http://code.google.com/p/lilypond/issues/detail?id=3064
… and it has already been declared as invalid - let me try to summarize what
I don't like with this example:
(a) the three chords
In default tablature tied notes are hided. But if a chord contains two
identical pitches (played on different strings), one of them is
displayed (the one with the string number indication).
See this example:
\version 2.17.9
music = \relative c' {
b\3 b g'8 ~ q
g\4 g d'8 ~ q
}
\score {
Il 26/12/2012 16:32, Federico Bruni ha scritto:
In default tablature tied notes are hided. But if a chord contains two
identical pitches (played on different strings), one of them is
displayed (the one with the string number indication).
an obvious workaround is not using the q shortcut
Hi
I have two different questions (quite related to each other)
1) In NR 1.2.2, Full measure rests
The snippet multi-measure-rest-markup.ly says:
Markups attached to a multi-measure rest will be centered above or
below it. Long markups attached to multi-measure rests do not cause the
measure
Il 30/12/2012 14:06, Trevor Daniels ha scritto:
Note that the spacer rest causes a bar line to be inserted.
I cannot understand the last sentence.
I cannot see any change in the bar lines if I comment the spacer rests.
Neither can I. I can't remember what I meant by this. I guess
that
Il 30/12/2012 16:21, Thomas Morley ha scritto:
Hi Federico,
I followed this discussion only cursorily.
If there's need to alter a LSR-snippet I could do it for you. Please
send me revised version.
Maybe Trevor is already working on it.
Anyway, find files attached
BTW, you can alter
In NR 1.2.3, Upbeats:
So \partial 8 becomes:
\time 3/4
\set Timing.measurePosition = #(ly:make-moment -1 8)
e8 | a4 c8 b c4 |
_The property measurePosition contains a rational number indicating how
much of the measure has passed at this point_. Note that this is set to
a negative number by
Il 31/12/2012 00:52, Reinhold Kainhofer ha scritto:
On 2012-12-30 23:59, Federico Bruni wrote:
In NR 1.2.3, Upbeats:
So \partial 8 becomes:
\time 3/4
\set Timing.measurePosition = #(ly:make-moment -1 8)
e8 | a4 c8 b c4 |
_The property measurePosition contains a rational number indicating
Il 31/12/2012 00:23, Trevor Daniels ha scritto:
Federico, you wrote Sunday, December 30, 2012 10:59 PM
In NR 1.2.3, Upbeats:
So \partial 8 becomes:
\time 3/4
\set Timing.measurePosition = #(ly:make-moment -1 8)
e8 | a4 c8 b c4 |
_The property measurePosition contains a rational number
Hi all
while translating this chapter I've come across this sentence:
A new bar is never started within a cadenza, even if one or more \bar
commands are inserted within it. Therefore, reminder accidentals will
need to be added manually. See Accidentals.
c4 d e d
\cadenzaOn
cis4 d cis d
Il 31/12/2012 21:47, Helge Kruse ha scritto:
Am 31.12.2012 18:53, schrieb Federico Bruni:
A new bar is never started within a cadenza, even if one or more \bar
commands are inserted within it. Therefore, reminder accidentals will
need to be added manually. See Accidentals.
So what's
1 - 100 of 533 matches
Mail list logo
