Re: voice sharing the same note on different staves
Vicente Solsona vice...@lavabit.com writes:
On Thu, 04 Nov 2010 05:07:34 +0100, Colin Campbell c...@shaw.ca wrote:
wrote:
please remember to forward to the list.
also please review your examples before posting. your example contains
syntax errors.
there's no E flat in your example. the only common note between voices 2
and 4 is an F (if I've interpreted your example correctly). Here's how I
would mix that F (result attached):
I believe the OP was using english.ly for note names, so the common note
is in fact an E-flat, spelt ef rather than es in the default nederlands
note names.
heck you're right. there's a thing called english which happens to be a
language which happens to be supported by lilypond (and probably even
there's someone out there who happens to speak it)
I'd say there is no point in providing different input languages. On
the other hand, it would look plain ugly to spell a well-known fugue
theme as { bes a c b } rather than using German note names.
It might be argued on that grounds that German note names should be
canonical: I know of no other note name language that has been employed
similarly for silly acronyms and word games.
Well, almost. When writing ut queant laxis
URL:http://en.wikipedia.org/wiki/Ut_queant_laxis, French note names
would be more appropriate. Oh, we don't have them. The Italian note
names use do rather than ut. I have a Swiss accordion score from
1933 here, and it uses ut throughout. Maybe it's just Swiss French,
or obsolete Swiss French.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: voice sharing the same note on different staves
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Nov 05, 2010 at 09:18:05AM +0100, David Kastrup wrote:
[...]
I'd say there is no point in providing different input languages.
Hey! I'm making some effort to provide *yet* another language ;-P
On
the other hand, it would look plain ugly to spell a well-known fugue
theme as { bes a c b } rather than using German note names.
...but I don't know of any similar pun in Balinese music (OTOH -- those
folks are scaringly creative!)
Regards
- - tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFM08U5Bcgs9XrR2kYRAiReAJ9kZqV0LLth8Iyob8CYWmuYOJqvFgCfYEhL
123Euvq7Cu3s+Y4pH5Xq2sU=
=IPt9
-END PGP SIGNATURE-
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: voice sharing the same note on different staves
David Kastrup d...@gnu.org writes: When writing ut queant laxis URL:http://en.wikipedia.org/wiki/Ut_queant_laxis, French note names would be more appropriate. Oh, we don't have them. The Italian note names use do rather than ut. I have a Swiss accordion score from 1933 here, and it uses ut throughout. Maybe it's just Swiss French, or obsolete Swiss French. It also uses si for h, in this case just like Lilypond's italiano. There are solfeges using ti instead, I believe. But one should probably wait until some actual user complains for real before introducing new dialects. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: voice sharing the same note on different staves
Am 05.11.2010 um 10:14 schrieb David Kastrup: David Kastrup d...@gnu.org writes: When writing ut queant laxis URL:http://en.wikipedia.org/wiki/Ut_queant_laxis, French note names would be more appropriate. Oh, we don't have them. The Italian note names use do rather than ut. I have a Swiss accordion score from 1933 here, and it uses ut throughout. Maybe it's just Swiss French, or obsolete Swiss French. It also uses si for h, in this case just like Lilypond's italiano. There are solfeges using ti instead, I believe. True. e.g.: W.H. Swinburne: The New Curwen Method, or Edwin E. Gordon in his books on music learning theory. But one should probably wait until some actual user complains for real before introducing new dialects. -- David Kastrup ___ 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: voice sharing the same note on different staves
On Fri, Nov 5, 2010 at 9:18 AM, David Kastrup d...@gnu.org wrote: It might be argued on that grounds that German note names should be canonical: I know of no other note name language that has been employed similarly for silly acronyms and word games. Ravel isn't consistent in this regard: in this piece, H means plain b http://imslp.org/wiki/Menuet_sur_le_nom_d%27Haydn_%28Ravel,_Maurice%29 in this other piece, B means plain b http://imslp.org/wiki/Berceuse_sur_le_nom_de_Gabriel_Faur%C3%A9_%28Ravel,_Maurice%29 Well, almost. When writing ut queant laxis URL:http://en.wikipedia.org/wiki/Ut_queant_laxis, French note names would be more appropriate. Oh, we don't have them. The Italian note names use do rather than ut. I have a Swiss accordion score from 1933 here, and it uses ut throughout. Maybe it's just Swiss French, or obsolete Swiss French. I don't know about Swiss French, but here in France we rarely use ut at all; it is merely used by snobbish people when referring to a piece's tonality: Sonate en Ut Majeur (but regular people will just say Do Majeur). Cheers, Valentin. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: voice sharing the same note on different staves
Valentin Villenave valen...@villenave.net writes: I don't know about Swiss French, but here in France we rarely use ut at all; it is merely used by snobbish people when referring to a piece's tonality: Sonate en Ut Majeur (but regular people will just say Do Majeur). Interesting, because it is not snobbish at all to say quatre-vent-dix-neuf which other French-speaking nations have replaced by nonante-neuf long ago. In English, one would be considered snobbish when starting a sentence with, say, Four score and seven, let alone Four score and nineteen. In contrast, ut rather than do appears harmless. To a foreigner, that is. Doh. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: voice sharing the same note on different staves
2010/11/5 David Kastrup d...@gnu.org: It might be argued on that grounds that German note names should be canonical: I know of no other note name language that has been employed similarly for silly acronyms and word games. This comes to my mind: Vive le roi, ut mi ut re re sol mi from Josquin Granted, they're only vowels and even ut for 'v'. [unrelated?] In Spanish we have a funny mnemonic for the eight dominants of Gregorian modes: La farola de Laredo (stands for The lamppost of Laredo, a town), for La Fa Do La Do La Re Do. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: setting TabStaff.minimumFret causes MIDI channel wrap
On 11/4/10 8:36 PM, Steve Yegge steve.ye...@gmail.com wrote:
I've been getting hundreds of these warnings in each of my music files:
warning: MIDI channel wrapped around
warning: remapping modulo 16
I'm not sure about the source of these warnings, and I don't do any work
with the MIDI code, so I'm not sure exactly why the warning occurs.
These warnings begin to accumulate as I add calls to set the minimumFret.
It seems to be related to the transposition calls I'm doing as well, since
removing them makes the warning go away.
It seems to work just fine to write your music all an octave lower (i.e. in
the sounding pitch, which you eventually get to by transposing) and put it
on a staff with a treble_8 clef.
I make an effort to try to keep my music files warning free, so it pains me
to see hundreds of these scroll by on every compile. If I'm structuring my
files wrong (e.g. the way I'm instantiating the staffs or doing the
transpositions)
I'm happy to change them.
Using the treble_8 clef is the way to go. But while we're at it, you create
a whole lot of unnecessary complexity in your file by adding unnecessary
and { } levels.
Here's what it looked like when I was done with it:
\version 2.13.10
music = \relative c {
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
\set TabStaff.minimumFret = #1 c
}
\score {
\new Staff {
\clef treble_8
\music
}
\new TabStaff {
\music
}
}
\score {
\music
\midi {}
}
HTH,
Carl
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Switching staves with \times looks odd
I'm not sure this doesn't qualify as a bug (bug squad: look at issue
279 and 696 for example).
Here's how to reproduce the behavior:
% The tupletNumber is printed too far away from the beam.
% A workaround exists: http://lsr.dsi.unimi.it/LSR/Item?id=646
% but do we really want to keep the attached default output?
\version 2.13.37
\layout { ragged-right = ##f }
\new PianoStaff
\new Staff = RH {
s4
}
\new Staff = LH
\relative c {
\clef bass
\times 2/3 {b8 b\change Staff=RH \stemDown e' e'}
}
Cheers,
Valentin.
Thanks, Richie and Valentin -
This has been accepted as Issue # 1380 :
http://code.google.com/p/lilypond/issues/detail?id=1380
Pondly,
Ralph
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
footnote example
Hello list,
here is a snippet, wich creates footnotes. It is not tested very much!!!
If you like, try it and tell me how it works! If you have improvements,
tell the list :-)
I don't know what happens, when you use it extensibly in a large book
with several pages - if there are X pages and Y footnotes, the
footer-items markup has to loop X*Y through the list of notes!
I will try later ...
First I was trying to get the piece field in the footer with several
scores in one bookpart. I looked through the lily-files in /usr/share
and used some code of toc-init.ly (\label) define-markup-commands.scm
(\page-ref) and thought of using a global running variable to keep this
info available for the footer ...
Then I received my first printed book of lily-scores I typesetted ( I am
10cm larger now ;-) ) and I see, the piece info in the footer is not
that important.
But my tries made me think of footnotes. So I made this little script.
Regards,
Jan-Peter
--snip--
\version 2.12.3
% Trying to get small(!) footnotes with excerpts from
define-markup-commands.scm and toc-init.ly
% This is a first try!
% TODO take gauge-stencil from page-width?
% TODO parameter for markup styles in paper{} (like 'tocItemMarkup)
% PROBLEM if there are X pages and Y footnotes, the footer-items markup
has to loop X*Y through the list of notes!
% PROBLEM the gauge-stencil always uses the same space! Also if there
are no notes on the page!
% define the footnote counter
#(define footnr 0)
% to be defined in a closure later (see toc-init.ly)
#(define-public (add-foot-item! dir text) #f)
#(define-public (foot-items) #f)
% define add item and get list functions
#(let ((foot-item-list (list)))
(set! add-foot-item!
(lambda (dir text)
(let ((label (gensym foot)))
(set! footnr (+ footnr 1))
(set! foot-item-list
(cons (list label text footnr)
foot-item-list))
(make-music 'EventChord
'page-marker #t
'page-label label
'elements (list
(make-music 'LabelEvent 'page-label label)
(make-music 'TextScriptEvent 'direction dir
'text (markup #:super #:circle (number-string footnr)))
)
(set! foot-items (lambda ()
(reverse foot-item-list
% conditionally add text markup, if we are on the right page
#(define (runfi pagelist cur-page table label text fnnr)
(let ((label-page (and (list? table) (assoc label table
(if (and label-page (= cur-page (cdr label-page)))
(markup pagelist #:super (number-string fnnr) text)
pagelist
)
)
)
% define markup command to be used in footerMarkup
% delayed stencil-evaluation like in page-ref - so we know the
pagenumber of the label and the current page
% needs 'gauge'-stencil --- is hardcoded right now
#(define-markup-command (footer-items layout props)()
markup footer items
(let* ((gauge-stencil (interpret-markup layout props (markup #:super
1 XXX)))
(x-ext (ly:stencil-extent gauge-stencil X))
(y-ext (ly:stencil-extent gauge-stencil Y)))
(ly:make-stencil
`(delay-stencil-evaluation
,(delay (ly:stencil-expr
(let* ((table (ly:output-def-lookup layout
'label-page-table))
(cur-page (inexact-exact (string-number
(chain-assoc-get 'page:page-number-string props
(pagelist (markup))
(page-number -1))
(map (lambda (fn)
(let ((label (car fn))
(text (cadr fn))
(fnnr (caddr fn)))
(set! pagelist (runfi
pagelist cur-page table label text fnnr))
)
) (foot-items))
(interpret-markup layout props (markup
pagelist))
)
)
)) x-ext y-ext)))
% the footnote function
% takes direction (UP/DOWN) and markup
% other layout properties can be set via [\once] \override TextScript
#'... = ...
addfoot = #(define-music-function (parser location dir text)(integer?
markup?)
(begin (add-foot-item! dir text)
))
\paper {
#(set-paper-size a5 'landscape)
oddHeaderMarkup =
evenHeaderMarkup =
oddFooterMarkup = \markup { \fill-line {
\concat { \fromproperty #'header:composer , \bold
\fromproperty #'header:title }
% fill in footer-items
\footer-items
\fromproperty #'page:page-number-string
}
}
evenFooterMarkup = \markup { \fill-line {
\fromproperty #'page:page-number-string
% fill in
LilyPond Report #22
Greetings everybody, as you may already know, the LilyPond Report is back, with some surprises and exciting news for the whole LilyPond community! To be found in this issue is an up-to-date, complete list of all LilyPond mailing lists and forums around the world — and we do mean: complete. Also, for the very first time our special guest today is LilyPond’s co-founder and core developper Jan Nieuwenhuizen, who has been busy these past months — read on to find out what for! Follow this link to read the full issue: http://news.lilynet.net/The-LilyPond-Report-22 Enjoy! Valentin. PS. Some people have recently reported having problems with our anti-spam filter; hopefully this has been addressed and you should be able to post comments without a glitch. So, do feel free to post comments at the bottom of the page! ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: footnote example
Very useful, I will test it.
If this is a good implementation, maybe consider it for the next release?
2010/11/5 Jan-Peter Voigt jp.vo...@gmx.de:
Hello list,
here is a snippet, wich creates footnotes. It is not tested very much!!! If
you like, try it and tell me how it works! If you have improvements, tell
the list :-)
I don't know what happens, when you use it extensibly in a large book with
several pages - if there are X pages and Y footnotes, the footer-items
markup has to loop X*Y through the list of notes!
I will try later ...
First I was trying to get the piece field in the footer with several scores
in one bookpart. I looked through the lily-files in /usr/share and used some
code of toc-init.ly (\label) define-markup-commands.scm (\page-ref) and
thought of using a global running variable to keep this info available for
the footer ...
Then I received my first printed book of lily-scores I typesetted ( I am
10cm larger now ;-) ) and I see, the piece info in the footer is not that
important.
But my tries made me think of footnotes. So I made this little script.
Regards,
Jan-Peter
--snip--
\version 2.12.3
% Trying to get small(!) footnotes with excerpts from
define-markup-commands.scm and toc-init.ly
% This is a first try!
% TODO take gauge-stencil from page-width?
% TODO parameter for markup styles in paper{} (like 'tocItemMarkup)
% PROBLEM if there are X pages and Y footnotes, the footer-items markup has
to loop X*Y through the list of notes!
% PROBLEM the gauge-stencil always uses the same space! Also if there are no
notes on the page!
% define the footnote counter
#(define footnr 0)
% to be defined in a closure later (see toc-init.ly)
#(define-public (add-foot-item! dir text) #f)
#(define-public (foot-items) #f)
% define add item and get list functions
#(let ((foot-item-list (list)))
(set! add-foot-item!
(lambda (dir text)
(let ((label (gensym foot)))
(set! footnr (+ footnr 1))
(set! foot-item-list
(cons (list label text footnr)
foot-item-list))
(make-music 'EventChord
'page-marker #t
'page-label label
'elements (list
(make-music 'LabelEvent 'page-label label)
(make-music 'TextScriptEvent 'direction dir 'text
(markup #:super #:circle (number-string footnr)))
)
(set! foot-items (lambda ()
(reverse foot-item-list
% conditionally add text markup, if we are on the right page
#(define (runfi pagelist cur-page table label text fnnr)
(let ((label-page (and (list? table) (assoc label table
(if (and label-page (= cur-page (cdr label-page)))
(markup pagelist #:super (number-string fnnr) text)
pagelist
)
)
)
% define markup command to be used in footerMarkup
% delayed stencil-evaluation like in page-ref - so we know the pagenumber of
the label and the current page
% needs 'gauge'-stencil --- is hardcoded right now
#(define-markup-command (footer-items layout props)()
markup footer items
(let* ((gauge-stencil (interpret-markup layout props (markup #:super 1
XXX)))
(x-ext (ly:stencil-extent gauge-stencil X))
(y-ext (ly:stencil-extent gauge-stencil Y)))
(ly:make-stencil
`(delay-stencil-evaluation
,(delay (ly:stencil-expr
(let* ((table (ly:output-def-lookup layout
'label-page-table))
(cur-page (inexact-exact (string-number
(chain-assoc-get 'page:page-number-string props
(pagelist (markup))
(page-number -1))
(map (lambda (fn)
(let ((label (car fn))
(text (cadr fn))
(fnnr (caddr fn)))
(set! pagelist (runfi pagelist
cur-page table label text fnnr))
)
) (foot-items))
(interpret-markup layout props (markup pagelist))
)
)
)) x-ext y-ext)))
% the footnote function
% takes direction (UP/DOWN) and markup
% other layout properties can be set via [\once] \override TextScript #'...
= ...
addfoot = #(define-music-function (parser location dir text)(integer?
markup?)
(begin (add-foot-item! dir text)
))
\paper {
#(set-paper-size a5 'landscape)
oddHeaderMarkup =
evenHeaderMarkup =
oddFooterMarkup = \markup { \fill-line {
\concat { \fromproperty #'header:composer , \bold \fromproperty
#'header:title }
% fill in footer-items
Re: footnote example
Jan-Peter Voigt wrote: Hello list, here is a snippet, wich creates footnotes. It is not tested very much!!! If you like, try it and tell me how it works! If you have improvements, tell the list :-) sounds interesting! however - using your example with version 2.13.38 - the last footer gets scrambled! http://old.nabble.com/file/p30142289/footer.pdf footer.pdf -- View this message in context: http://old.nabble.com/footnote-example-tp30141914p30142289.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
Re: footnote example
Hello Eluze, hello list, thanks for the test! I will install a dev-version and test - right now I am only using the stable version for my projects. It seems, the fill-line spacing has changed - if you change the footerMarkup to contain only the footer-items and the page-number, it should run fine? But it points to an inherent problem. The markup-stencil is of a fixed size. If it is filled with too many notes on one page, the markup might cross stencil/page borders. Regards, Jan-Peter On 05.11.2010 16:30, -Eluze wrote: Jan-Peter Voigt wrote: Hello list, here is a snippet, wich creates footnotes. It is not tested very much!!! If you like, try it and tell me how it works! If you have improvements, tell the list :-) sounds interesting! however - using your example with version 2.13.38 - the last footer gets scrambled! http://old.nabble.com/file/p30142289/footer.pdf footer.pdf ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: footnote example
Jan-Peter Voigt wrote:
Hello Eluze, hello list,
thanks for the test! I will install a dev-version and test - right now I
am only using the stable version for my projects. It seems, the
fill-line spacing has changed - if you change the footerMarkup to
contain only the footer-items and the page-number, it should run fine?
But it points to an inherent problem. The markup-stencil is of a fixed
size. If it is filled with too many notes on one page, the markup might
cross stencil/page borders.
indeed - if i remove items it works better.
wouldn't it anyway be nicer to have each item on an own line, as well as the
composer and title?
you can achieve this with
\column {
{note1}
{note2}
{note3}
…
}
and - if necessary - add a \wordwrap for each item.
hope this can help a little!
--
View this message in context:
http://old.nabble.com/footnote-example-tp30141914p30145463.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
Re: setting TabStaff.minimumFret causes MIDI channel wrap
On Fri, Nov 5, 2010 at 6:54 AM, Carl Sorensen c_soren...@byu.edu wrote:
On 11/4/10 8:36 PM, Steve Yegge steve.ye...@gmail.com wrote:
These warnings begin to accumulate as I add calls to set the minimumFret.
It seems to be related to the transposition calls I'm doing as well,
since
removing them makes the warning go away.
It seems to work just fine to write your music all an octave lower (i.e. in
the sounding pitch, which you eventually get to by transposing) and put it
on a staff with a treble_8 clef.
Cool! Will do.
Using the treble_8 clef is the way to go. But while we're at it, you
create
a whole lot of unnecessary complexity in your file by adding unnecessary
and { } levels.
Oops -- those were leftovers from removing extraneous stuff from what's
an otherwise fairly complex file.
Thanks much for the workaround!
-steve
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
