Re: where can one find the default settings
On Thu, 10 Jul 2008 10:14:21 -0700 Patrick McCarty [EMAIL PROTECTED] wrote: On Thu, Jul 10, 2008 at 9:17 AM, Kieren MacMillan [EMAIL PROTECTED] wrote: Once again, I would like to suggest that all settings for a given grob should be available in a single documentation page ___ e.g., the grob LayoutObject page ___ so that users don't have to hunt them down in fourteen different places, assuming they even know where to look to begin with. [This list of settings should be *automatically* generated, of course, so that no one would have to manually build it for each new Lilypond version...] Since new users are expected to read the Learning Manual, the method to *hunt down* the grob settings is documented. I agree that the process to *find* the correct page can be difficult though. Improving the IR is so ridiculously far down on the list it's not funny. Ask again in Nov or Dec; by then, people with the required skills *might* have the required time. This will absolutely not be attempted as part of GDP. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: where can one find the default settings
For most grobs LilyPondTool's code completion and instant help function provides the default values by automatically walking the interface tree and parsing the documentation and the SCM files. LilyPondTool's most important goal is to reduce the tedious seeking in the reference manual. However one limitation is that currently there is no public interface for generating the code completion database for arbitrary LilyPond version, so for the newer grobs the instant help documentation and default values may be missing. Anyway, I hope you tried LilyPondTool before asking for the default value. :-) Bert --- Original Message --- From: Patrick McCarty [EMAIL PROTECTED] To: Kieren MacMillan [EMAIL PROTECTED] Sent: 08/07/10/, 19:14:21 Subject: Re: where can one find the default settings On Thu, Jul 10, 2008 at 9:17 AM, Kieren MacMillan [EMAIL PROTECTED] wrote: Just wondering if there's any documentation on where to find the default settings for a given grob — for example, I don't know where to look to find the default BreathingSign #'font-size setting (which I need right now). [I can easily drill down to the font-interface page, but no specific answer can be found there, because it's an interface shared by so many different grobs...] This is explained in LM 4.2.2. If the 'font-size property is not listed on the BreathingSign page, then it uses the global default setting for 'font-size (which is 0, according to the font-interface page). On the other hand, there are many grob properties with unlisted default values. Does this imply that they are undocumented, or that their values are grob-dependent? I'm not sure if this is documented anywhere. Once again, I would like to suggest that all settings for a given grob should be available in a single documentation page — e.g., the grob LayoutObject page — so that users don't have to hunt them down in fourteen different places, assuming they even know where to look to begin with. [This list of settings should be *automatically* generated, of course, so that no one would have to manually build it for each new Lilypond version...] Since new users are expected to read the Learning Manual, the method to *hunt down* the grob settings is documented. I agree that the process to *find* the correct page can be difficult though. Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Y-coordinates don't work in offset function
I couldn't figure out how
to use extra-offset in the function (I'm very new at this,
clearly...).
Not so easy with extra-offset indeed, because the syntax
#'extra-offset = #'($offsetX $offsetY ) doen't work .
(don't know why !?!)
It seems to work with the cons syntax
%%
fingerOffset = #(define-music-function (parser location offsetX offsetY)
(number? number?)
#{
\once \override Voice.Fingering #'extra-offset = #(cons $offsetX
$offsetY )
#})
\relative c''' {
\override Fingering #'staff-padding = #'()
\set fingeringOrientations = #'(down)
\fingerOffset #0.7 #-3.5
c-44
\fingerOffset #'0.7 #'0.0
g-3
\fingerOffset #'0.7 #'3.0
d-22
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Y-coordinates don't work in offset function
Jonathan
Try
\version 2.11.51
fingerOffset =
#(define-music-function (parser location offsets) (pair?)
#{
\once \override Fingering #'extra-offset = #$offsets
#})
% \fingerOffset #'-0.2 #'-0.3 % moves fingering .2 spaces left and .3 down
\relative c''' {
\override Fingering #'staff-padding = #'()
\set fingeringOrientations = #'(down)
\fingerOffset #'(0.7 . -3.5)
%\once \override Fingering
% #'extra-offset = #'(0.7 . -0.6)
c-44
\fingerOffset #'(0.7 . 0.0)
g-3
\fingerOffset #'(0.7 . 3.0)
d-22
}
- Original Message -
From: Jonathan Kulp [EMAIL PROTECTED]
To: lilypond-user@gnu.org
Sent: Friday, July 11, 2008 5:33 AM
Subject: Y-coordinates don't work in offset function
Dear Lilyponders,
I'm working on a snippet of guitar music for use as Inspirational
Headword of the fretted strings section of GDP. The default placement of
fingerings is not very good, so I'm placing them manually but have tried
to create a function to help me. The function is supposed to allow me to
specify X and Y offset for each fingering. The problem is that the Y
offset doesn't work. The X offset works just fine, and it's very close to
what I want, but it would really help to get vertical fine-tuning as well.
I've been searching the documentation and experimenting for two hours with
no luck. A minimal example appears below, including my function (probably
where the problem lies). I've commented out a tweak that does what I want
using extra-offset adjustment, but I couldn't figure out how to use
extra-offset in the function (I'm very new at this, clearly...).
If anyone can point out my error and a solution I'd be most grateful.
Best,
Jonathan
--
Jonathan Kulp
http://www.jonathankulp.com
\version 2.11.51
fingerOffset =
#(define-music-function (parser location offsetX offsetY) (number?
number?)
#{
\once \override Fingering #'X-offset = $offsetX
\once \override Fingering #'Y-offset = $offsetY
#})
% \fingerOffset #'-0.2 #'-0.3 % moves fingering .2 spaces left and .3 down
\relative c''' {
\override Fingering #'staff-padding = #'()
\set fingeringOrientations = #'(down)
\fingerOffset #0.7 #-3.5
%\once \override Fingering
% #'extra-offset = #'(0.7 . -0.6)
c-44
\fingerOffset #'0.7 #'0.0
g-3
\fingerOffset #'0.7 #'3.0
d-22
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Some Midi Output Problems
You're right (I think), I can't make dynamics work in the ChordMode context
either.
However, if all you want to do is to silent the chords you can try removing
the Note_performer, like this:
\midi {
\context {
\ChordNameVoice
\remove Note_performer
}
}
Writing a music function is described in Section 6.1 of the 2.11 docs. Be
prepared for a long haul, though :) The example in 6.3.3 shows the sort of
thing you might need.
Trevor
- Original Message -
From: grick [EMAIL PROTECTED]
To: Trevor Daniels [EMAIL PROTECTED]
Cc: lilypond-user@gnu.org
Sent: Thursday, July 10, 2008 6:41 PM
Subject: Re: Some Midi Output Problems
You can reduce the volume of the default piano in the same way, by
setting
midiMinimumVolume and midiMaximumVolume in the piano staff. Note,
though,
that these controls only take effect on encountering a dynamic mark,
so be
sure you have a mark at the beginning of the piano notes.
There is no piano staff, only a chordmode section (something like this):
--
Accordi = \chordmode
{
\repeat unfold 60 {
f2:9+ bes2:7
}
\repeat unfold 2 {
f1
f1
ees1
ees1
}
}
--
Nor \set Staff.midiXVolume nor \ppp on chords (like f1\ppp) works.
Just to know this chordmode section is included in the staff this way:
--
\score {
\new StaffGroup
\new ChordNames {
\set chordChanges = ##t
\Accordi
}
\new Staff \WithChords \global \Tromba
\new Staff \WithChords \global \Alto
\new Staff \WithChords \global \Tenore
\new Staff \WithChords \global \Baritono
\layout { }
}
--
BTW, an easier way may be to simply use quieter dynamic marks on the
music
of the instruments you want to reduce - these also affect the MIDI
volume.
The Control MIDI dynamic marks are printed in the sheet (and, by the
way, i have to replace the real dynamics). I want to avoid this.
To do this i use often staccato notes (a4-. a4-. a4-. a4-.).
I expect my midi output sound like (a8 r8 a8 r8 a8 r8 a8 r8) but
sadly it
does not interpret them at all and sound like a simple (a4 a4 a4
a4).
I can simple write (a8 r8) version everywhere but the sheet become
really
difficult to read for the performers.
Is there a way to avoid to mantain a double version of the sheets?
(one
for the performers with a4-. version and one for the midi output
with a8
r8 one?)
Sorry, apart from using separate versions I don't know how to do this
other
than by writing a Scheme procedure to add the staccato marks in the
midi
\score block.
Can you point me to some docs about this Scheme procedures? Something
specific for lilypond i found a general intro on the guile site.
Trevor
Thank you Trevor for the answers!
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Single-digit with vertical slash
I found that MusiXteX has single-digit with vertical slash time signature glyphs - they are used in ancient music. If Lilypond doesn't have them, could I add the vertical slash manually? Thank you. F. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Adding a staff in the middle of a piece
I'm sorry for my telegraph-style question: is it possible to start a piece with, e.g. 3 staves ad add one more some measures later? Thank you F. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Adding a staff in the middle of a piece
Yes. Francesco Spiga wrote: I'm sorry for my telegraph-style question: is it possible to start a piece with, e.g. 3 staves ad add one more some measures later? Thank you F. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Adding a staff in the middle of a piece
Am 09.07.2008 um 17:07 schrieb Francesco Spiga: I'm sorry for my telegraph-style question: is it possible to start a piece with, e.g. 3 staves ad add one more some measures later? Thank you F. There are several ways, you can use \stopStaff and \startStaff or search the manuals for frenched score ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Chord Names — seen but not h eard?
Better late than never!
You can try removing
the Note_performer, like this:
\midi {
\context {
\ChordNameVoice
\remove Note_performer
}
}
Trevor
- Original Message -
From: 99% Perspiration [EMAIL PROTECTED]
To: lilypond-user@gnu.org
Sent: Thursday, July 03, 2008 11:22 PM
Subject: Chord Names — seen but not heard?
Chord Names are preferable to free text because it is transposable.
However, I do not want the clunk of a Piano chord with every chord name
symbol.
This sound occurs even if chord-name is visible as notes or not.
This is not where the actual chord is a composite of notes on various
staves.
Is there a simple way a beginner can turn it off?
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
[SOLVED] Re: Y-coordinates don't work in offset function
Many thanks, Trevor and Gilles!! Both of those solutions work
perfectly. Now the question is which one uses the syntax that would be
most appropriate to appear in the GDP docs. My instinct is to use the
one with #'(0.0 . 0.0) for the coordinates, since this is how I've seen
X-Y coordinates specified most often. Graham, do you have a preference?
Thanks again!
Jon
Trevor Daniels wrote:
Jonathan
Try
\version 2.11.51
fingerOffset =
#(define-music-function (parser location offsets) (pair?)
#{
\once \override Fingering #'extra-offset = #$offsets
#})
% \fingerOffset #'-0.2 #'-0.3 % moves fingering .2 spaces left and .3 down
\relative c''' {
\override Fingering #'staff-padding = #'()
\set fingeringOrientations = #'(down)
\fingerOffset #'(0.7 . -3.5)
%\once \override Fingering
% #'extra-offset = #'(0.7 . -0.6)
c-44
\fingerOffset #'(0.7 . 0.0)
g-3
\fingerOffset #'(0.7 . 3.0)
d-22
}
- Original Message - From: Jonathan Kulp [EMAIL PROTECTED]
To: lilypond-user@gnu.org
Sent: Friday, July 11, 2008 5:33 AM
Subject: Y-coordinates don't work in offset function
Dear Lilyponders,
I'm working on a snippet of guitar music for use as Inspirational
Headword of the fretted strings section of GDP. The default
placement of fingerings is not very good, so I'm placing them manually
but have tried to create a function to help me. The function is
supposed to allow me to specify X and Y offset for each fingering.
The problem is that the Y offset doesn't work. The X offset works
just fine, and it's very close to what I want, but it would really
help to get vertical fine-tuning as well.
I've been searching the documentation and experimenting for two hours
with no luck. A minimal example appears below, including my function
(probably where the problem lies). I've commented out a tweak that
does what I want using extra-offset adjustment, but I couldn't figure
out how to use extra-offset in the function (I'm very new at this,
clearly...).
If anyone can point out my error and a solution I'd be most grateful.
Best,
Jonathan
--
Jonathan Kulp
http://www.jonathankulp.com
\version 2.11.51
fingerOffset =
#(define-music-function (parser location offsetX offsetY) (number?
number?)
#{
\once \override Fingering #'X-offset = $offsetX
\once \override Fingering #'Y-offset = $offsetY
#})
% \fingerOffset #'-0.2 #'-0.3 % moves fingering .2 spaces left and .3
down
\relative c''' {
\override Fingering #'staff-padding = #'()
\set fingeringOrientations = #'(down)
\fingerOffset #0.7 #-3.5
%\once \override Fingering
% #'extra-offset = #'(0.7 . -0.6)
c-44
\fingerOffset #'0.7 #'0.0
g-3
\fingerOffset #'0.7 #'3.0
d-22
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SOLVED] Re: Y-coordinates don't work in offset function
a) if this is inside the inspirational header, do whatever you
want.
b) if this is inside a snippet, do whatever you want, subject to
it making sense to people on -user.
c) if this is inside the main text, I'll actually go and read the
below discussion (which I've totally ignored), but I suspect that
I'd just end up saying this belongs as a snippet instead of the
main text, so see point b).
HTH,
- Graham
On Fri, 11 Jul 2008 06:10:52 -0500
Jonathan Kulp [EMAIL PROTECTED] wrote:
Many thanks, Trevor and Gilles!! Both of those solutions work
perfectly. Now the question is which one uses the syntax that would
be most appropriate to appear in the GDP docs. My instinct is to use
the one with #'(0.0 . 0.0) for the coordinates, since this is how
I've seen X-Y coordinates specified most often. Graham, do you have
a preference?
Thanks again!
Jon
Trevor Daniels wrote:
Jonathan
Try
\version 2.11.51
fingerOffset =
#(define-music-function (parser location offsets) (pair?)
#{
\once \override Fingering #'extra-offset = #$offsets
#})
% \fingerOffset #'-0.2 #'-0.3 % moves fingering .2 spaces left
and .3 down
\relative c''' {
\override Fingering #'staff-padding = #'()
\set fingeringOrientations = #'(down)
\fingerOffset #'(0.7 . -3.5)
%\once \override Fingering
% #'extra-offset = #'(0.7 . -0.6)
c-44
\fingerOffset #'(0.7 . 0.0)
g-3
\fingerOffset #'(0.7 . 3.0)
d-22
}
- Original Message - From: Jonathan Kulp
[EMAIL PROTECTED] To: lilypond-user@gnu.org
Sent: Friday, July 11, 2008 5:33 AM
Subject: Y-coordinates don't work in offset function
Dear Lilyponders,
I'm working on a snippet of guitar music for use as Inspirational
Headword of the fretted strings section of GDP. The default
placement of fingerings is not very good, so I'm placing them
manually but have tried to create a function to help me. The
function is supposed to allow me to specify X and Y offset for
each fingering. The problem is that the Y offset doesn't work.
The X offset works just fine, and it's very close to what I want,
but it would really help to get vertical fine-tuning as well.
I've been searching the documentation and experimenting for two
hours with no luck. A minimal example appears below, including my
function (probably where the problem lies). I've commented out a
tweak that does what I want using extra-offset adjustment, but I
couldn't figure out how to use extra-offset in the function (I'm
very new at this, clearly...).
If anyone can point out my error and a solution I'd be most
grateful. Best,
Jonathan
--
Jonathan Kulp
http://www.jonathankulp.com
\version 2.11.51
fingerOffset =
#(define-music-function (parser location offsetX offsetY) (number?
number?)
#{
\once \override Fingering #'X-offset = $offsetX
\once \override Fingering #'Y-offset = $offsetY
#})
% \fingerOffset #'-0.2 #'-0.3 % moves fingering .2 spaces left
and .3 down
\relative c''' {
\override Fingering #'staff-padding = #'()
\set fingeringOrientations = #'(down)
\fingerOffset #0.7 #-3.5
%\once \override Fingering
% #'extra-offset = #'(0.7 . -0.6)
c-44
\fingerOffset #'0.7 #'0.0
g-3
\fingerOffset #'0.7 #'3.0
d-22
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Guitar pro - Lily
Hi there, Just a few work about a small project I started a few months ago: a way to convert guitar pro file to lilypond. For the moment it parses and convert some GP4 files to Ly ones. A lot of work still needs to be done... You can find the git repository: https://git.chezwam.org:446/?p=guitare-pro.git It is written in python. Hope you'll enjoy. Cheers -- Sébastien Gross ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Guitar pro - Lily
Sébastien Gross wrote: Hi there, Just a few work about a small project I started a few months ago: a way to convert guitar pro file to lilypond. For the moment it parses and convert some GP4 files to Ly ones. A lot of work still needs to be done... You can find the git repository: https://git.chezwam.org:446/?p=guitare-pro.git Interesting. What is a git repostory and how can we use it? Do you know the app Tuxguitar? Did you know the app has a lilypond output option? Did you follow the thread 'notation and tablature (+bend, slide etc.)' ? I did get a few reactions on it, but nothing happend yet... ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: different rhythmic units for tuplet's numerator and denominator
A final point on this thread. These better functions now count the notes in
the tuplet, calculate durations and ratios, and lay it out. It's therefore
a way of filling a time span with a sequence of notes without having to
calculate possibly complex ratios. However, I can't work out why the \once
override line inserted in the makeTuplet function is ignored. Maybe
it should be possible to add a \note to the 'numerator and 'denominator
elements in this block, but I just can't work it out. Can anyone help solve
this? Cheers.
Peter
\version 2.11.49
#(define (count-notes notes)
(
let*(
(es (ly:music-property notes 'elements))
(i (length es))
)
i
))
#(define (transformEachNote chordElt d)
(begin
(if (or (eq? 'NoteEvent (ly:music-property chordElt 'name))
(eq? 'RestEvent (ly:music-property chordElt 'name)))
(set! (ly:music-property chordElt 'duration) d)
)
chordElt
))
#(define (getChords musicElt d)
(begin
(if (eq? 'EventChord (ly:music-property musicElt 'name))
(map
(lambda (x) (transformEachNote x d))
(ly:music-property musicElt 'elements)
)
)
musicElt
))
% Converts duration into ly form - dnl is one of {1 2 4 8 ..} with no .s
attached
#(define (string-duration tdur num den)
(
let*(
(dur (ly:intlog2 tdur)) ;; dur = 0 1 2 3 ..
)
(ly:make-duration dur 0 num den)
))
% Constructs the tuplet
makeTuplet = #(define-music-function (parser location span baseunit notes)
(number? number? ly:music?)
(
let*(
(count (count-notes notes)) ;; number of notes in sequence
(udf (inexact-exact (expt 2 (floor (+ 1 (- (/ (log span) (log
2)) (/ (log
count) (log 2 ;; unit duration factor
(tdur (/ baseunit udf)) ;; tuplet note duration
(num(if ( udf 1)
(/ span udf)
span)) ;; numerator of
tuplet duration ratio
(den(if ( udf 1)
count
(* count udf))) ;;
denominator of tuplet duration ratio
)
(music-map
(lambda (x)
(getChords x (string-duration tdur num den)))
notes
)
#{
\once \override TupletNumber #'text = #(markup #:italic $count
#:fontsize
-5 #:note $tdur 1 : $span #:fontsize -5 #:note $baseunit 1)
#}
(make-music 'TimeScaledMusic
'numerator span
'denominator count
'element notes
)
))
\relative
{
\time 4/4
\autoBeamOff
\override TupletNumber #'text = #tuplet-number::calc-fraction-text
c16 \makeTuplet #11 #16 {d e f g a } b4 | c1
}
--
View this message in context:
http://www.nabble.com/different-rhythmic-units-for-tuplet%27s-numerator-and-denominator-tp18321046p18412866.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
bracketed silence
hello list, i'd need to place brackets around a rest in the score. something like \parenthesize but square brackets [ ]. i tried using a \markup, but no matter what i try, i found no way to place the brackets in the staff around the rest. i tried every tweak i could find in the manual, but it seems to me that lilypond is always smarter and refuses to place the markup _in_ the staff. could anyone help me with this? is it at all possible? best, lj ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: bracketed silence
Hi Luis,
I got the brackets to go inside the staff with this code. If you fiddle
with the markup (change font size, spacing, whatever) and the values
inside the parentheses you can probably get it to look like you want.
Jon
\version 2.11.51
\relative c'' {
\override TextScript #'staff-padding = #'()
\once \override TextScript #'extra-offset = #'(-0.6 . -3.0)
b4\rest^\markup { [ ] }
}
luis jure wrote:
hello list,
i'd need to place brackets around a rest in the score. something like
\parenthesize but square brackets [ ].
i tried using a \markup, but no matter what i try, i found no way to
place the brackets in the staff around the rest. i tried every tweak i
could find in the manual, but it seems to me that lilypond is always
smarter and refuses to place the markup _in_ the staff.
could anyone help me with this? is it at all possible?
best,
lj
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
