Re: finished second draft?
I'm done with Keyboards. Cheers, Andrew On Wed, Aug 6, 2008 at 8:48 AM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote: > Please hold on Fretted String Instruments. > > I'm currently almost done with Predefined Fret Diagrams, which will add a > section to Fretted String Instruments (and will lead to reorganization). > The new organization on Fret Diagrams will be: > Fret Diagram Markups > Predefined Fret Diagrams > Automatic Fret Diagrams. > > Thanks, > > Carl > > > On 8/6/08 1:17 AM, "Graham Percival" <[EMAIL PROTECTED]> wrote: > >> Currently officially on Second draft: >> 1.3 Expressive marks >> >> 1.5 Simultaneous notes >> >> 2.2 Keyboard instruments >> >> 2.4 Fretted string instruments >> >> >> If any of these are finished, let me know and I'll move them into >> the ``finished'' category, and Ralph will start indexing them. >> >> Cheers, >> - Graham > > ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Using parentheses in texinfo node names
On Wed, 6 Aug 2008 13:01:30 +0200 Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > Some texinfo processors are able to treat them correctly, but others > are not (e.g. texi2html writes out a warning). Since the node name > and the displayed section title can be different, I propose to rename > those node names to something without the parentheses. Please do, thanks. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Transposable guitar fret diagrams
On 8/6/08 7:47 PM, "Han-Wen Nienhuys" <[EMAIL PROTECTED]> wrote:
> looks good to me
>
> + (define (flatten l)
> +(cond ((null? l) '())
> + ((pair? l)
> + (append (flatten (car l)) (flatten (cdr l
> + (else (list l
>
> i'd wager we already have this somewhere, if not can you move this to
> scm/lily-library.scm?
We actually had it twice -- as flatten-list in scm/lily-library.scm and as
flatten in scm/song-util.scm.
I deleted it from song-util.scm; I grep'd for usage of flatten and couldn't
find any.
>
>
> On Wed, Aug 6, 2008 at 9:26 PM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
>
>> 2) Can you give me any clues about how to set up LilyPond debugging so that
>> I might be able to track down the source of the error that occurs when I
>> load ly/predefined-fretboards-init.ly in property-init.ly?
>
> try running with --verbose ; that will switch on Scheme stacktraces
> for errors. Or is that not what you mean?
I ran with --verbose, and proved that the error was in parsing
predefined-fretboards-init, but the error didn't make any sense to me.
Here's the relevant part.
[/Users/Carl/lilypond-working/out/share/lilypond/current/ly/predefined-fretb
oards-init.lyBacktrace:
In unknown file:
?: 0* [lilypond-main ("fretboardtest.ly")]
In /Users/Carl/lilypond-working/out/share/lilypond/current/scm/lily.scm:
660: 1* (let* ((failed #)) (if (ly:get-option #) (begin #)) ...)
660: 2* [lilypond-all ("fretboardtest.ly")]
676: 3 (let* ((failed #) (separate-logs #) (ping-log #) ...) (gc) ...)
688: 4* [for-each # ("fretboardtest.ly")]
In unknown file:
?: 5* [# "fretboardtest.ly"]
In /Users/Carl/lilypond-working/out/share/lilypond/current/scm/lily.scm:
690: 6* (let* (# # #) (if separate-logs #) (if ping-log #) ...)
705: 7* [lilypond-file #
"fretboardtest.ly"]
742: 8 [catch ly-file-failed # #]
In unknown file:
?: 9* [#]
In /Users/Carl/lilypond-working/out/share/lilypond/current/scm/lily.scm:
743: 10* [ly:parse-file "fretboardtest.ly"]
In unknown file:
?: 11* [{#}]
/Users/Carl/lilypond-working/out/share/lilypond/current/scm/lily.scm:743:21:
In procedure apply in expression (ly:parse-file file-name):
/Users/Carl/lilypond-working/out/share/lilypond/current/scm/lily.scm:743:21:
Wrong type argument in position 1: #
I considered that I was including the file in two different locations, so I
moved it to the end of ly/declarations-init.ly. When I did this, everything
worked just fine.
I'm a bit concerned about this, because I never did track down the source of
the error. But it does work.
I've pushed the changes to git.
Thanks for all your help on this.
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Transposable guitar fret diagrams
looks good to me + (define (flatten l) +(cond ((null? l) '()) + ((pair? l) + (append (flatten (car l)) (flatten (cdr l + (else (list l i'd wager we already have this somewhere, if not can you move this to scm/lily-library.scm? On Wed, Aug 6, 2008 at 9:26 PM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote: > 2) Can you give me any clues about how to set up LilyPond debugging so that > I might be able to track down the source of the error that occurs when I > load ly/predefined-fretboards-init.ly in property-init.ly? try running with --verbose ; that will switch on Scheme stacktraces for errors. Or is that not what you mean? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Transposable guitar fret diagrams
OK, here's another try. I have now moved the definition of the hash table to property-init.ly, so that it's available for engraver-init.ly and property-init.ly. It works, but I'm not sure I've avoided the leakage between .ly files that you're concerned about. Also, I'd like to be able to automatically load ly/predefined-fretboards-init.ly, but when I do so, I get an error thrown that shows up as an error in lily.scm. So I'm currently loading ly/predefined-fretboards-init.ly manually in my .ly file. Two questions: 1) If I've not yet got the leakage avoidance you'd like, can you give me some sample code that would allow me to do what you'd like? 2) Can you give me any clues about how to set up LilyPond debugging so that I might be able to track down the source of the error that occurs when I load ly/predefined-fretboards-init.ly in property-init.ly? Thanks, Carl 0001-Add-predefined-fret-diagrams-to-fretboards.patch Description: 0001-Add-predefined-fret-diagrams-to-fretboards.patch fretboardtest.ly Description: fretboardtest.ly ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Doc addition: glossary, meter
In the glossary of the online-documentation for 2.11, section `meter' there are two additions it'd be worth making. 1. The UK spelling is `metre' 2. The `meter' (or metre) header line for hymn music refers to the the arrangement of syllables into lines for the corresponding lyrics. Metre can be expressed either as grups of numbers (87.87) or as letters (C.M. == common metre; L.M. or LM == long metre; DCM == double common metre). For example, common metre (C.M.) is 86.86 -- four alternating lines of eight and six syllables, arranged as two couplets. Conventionally, common metre is iambic, i.e., the first syllable is unstressed (and the corresponding music begins with an anacrusis). Example: Amazing Grace is common metre. Some hymns and their tunes are double length versions of a simpler metre: e.g., DCM, double common metre, or 86.86D or 86.86.86.86 Example: `Forest Green' arranged by R. Vaughn Williams (O Little town of Bethlehem) is DCM. -- Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au http://www.ertos.nicta.com.au ERTOS within National ICT Australia ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
doc addition: glossary, `stringendo'
In the glossary, please add `stringendo'. It means, Urging or hastening the time, as to a climax. (webster). It should probably cross-reference accelerando. As I understand it, accelerando means a gradual speeding up; stringendo a more rapid one. -- Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au http://www.ertos.nicta.com.au ERTOS within National ICT Australia ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] MIDI command line option
2008/8/5 Han-Wen Nienhuys <[EMAIL PROTECTED]>: > There is also some code in lily.scm that checks for a windows system. > It's easier to add to there rather than the .nsh I've tried setting 'midi-extension here: (case PLATFORM ((windows) ;; change midi default for Windows (ly:set-option 'midi-extension "mid") (define native-getcwd getcwd) (define (slashify x) (if (string-index x #\\) x (string-regexp-substitute "//*" "/" (string-regexp-substitute "" "/" x ;; FIXME: this prints a warning. (define-public (ly-getcwd) (slashify (native-getcwd (else (define-public ly-getcwd getcwd))) Since I can't check whether this works on Windows, I temporarily moved the option setting to the else clause. Unfortunately, though this overrides the default, setting midi-extension via the command line no longer works. Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: post-GDP doc team
2008/8/6 Trevor Daniels <[EMAIL PROTECTED]>: > Neil > > Further to this, I've just realised that 'layer takes a number, not an > integer, so the variable overprinting of grobs in the same layer could be > due to rounding. In effect we have an infinite number of layers, but grobs > with the same nominal value may be printed in either order. I think that's a mistake, since System::get_paper_system () converts the value to int using robust_scm2int; this is where the default value of 1 is set for all the objects which don't have 'layer set in define-grobs.scm. Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: finished second draft?
Please hold on Fretted String Instruments. I'm currently almost done with Predefined Fret Diagrams, which will add a section to Fretted String Instruments (and will lead to reorganization). The new organization on Fret Diagrams will be: Fret Diagram Markups Predefined Fret Diagrams Automatic Fret Diagrams. Thanks, Carl On 8/6/08 1:17 AM, "Graham Percival" <[EMAIL PROTECTED]> wrote: > Currently officially on Second draft: > 1.3 Expressive marks > > 1.5 Simultaneous notes > > 2.2 Keyboard instruments > > 2.4 Fretted string instruments > > > If any of these are finished, let me know and I'll move them into > the ``finished'' category, and Ralph will start indexing them. > > Cheers, > - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lyrics following split voices
Mats, you wrote, Wednesday, August 06, 2008 1:26 PM
Trevor Daniels wrote:
So, for the example in question, the NR should certainly state
categorically what the voice names are in the various constructs, and
examples showing the differences would be fine. But I don't think
there is any need to put lengthy explanations in the NR - it's a
reference document - they really need to go in the LM.
So maybe we need an explanation of using voice naming in this way
somewhere in the LM. Any suggestions? And the NR should certainly
list all the context names that are assigned by default somewhere.
Perhaps I'll work that into the section on Contexts. What do you think?
Note that the use of the trick
\new Voice = "1" { ... <<{...} \\ {...}>> ... }
only works if you have a single Staff (or at most one Staff with
polyphony), since otherwise
you would have several \new Voice = "1" in the same score, which doesn't
work.
Therefore, it's fairly esoteric and perhaps something that shouldn't be
taught in the LM.
Wise words. Maybe we should stick to describing the
situation regarding Voice names somewhere in the
"Contexts explained" section, way down in NR 5.1.1,
which I'll write as soon as I understand them properly
(although that hasn't stopped me on some earlier
occasions;) That way beginners will be better protected
from wrong impressions.
/Mats
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lyrics following split voices
Trevor Daniels wrote:
So, for the example in question, the NR should certainly state
categorically what the voice names are in the various constructs, and
examples showing the differences would be fine. But I don't think
there is any need to put lengthy explanations in the NR - it's a
reference document - they really need to go in the LM.
So maybe we need an explanation of using voice naming in this way
somewhere in the LM. Any suggestions? And the NR should certainly
list all the context names that are assigned by default somewhere.
Perhaps I'll work that into the section on Contexts. What do you think?
Note that the use of the trick
\new Voice = "1" { ... <<{...} \\ {...}>> ... }
only works if you have a single Staff (or at most one Staff with
polyphony), since otherwise
you would have several \new Voice = "1" in the same score, which doesn't
work.
Therefore, it's fairly esoteric and perhaps something that shouldn't be
taught in the LM.
/Mats
Trevor
- Original Message - From: "Francisco Vila"
<[EMAIL PROTECTED]>
To: "Mats Bengtsson" <[EMAIL PROTECTED]>;
Cc: "Paul Scott" <[EMAIL PROTECTED]>; "LilyPond User"
<[EMAIL PROTECTED]>
Sent: Wednesday, August 06, 2008 12:47 AM
Subject: Re: lyrics following split voices
2008/8/5 Mats Bengtsson <[EMAIL PROTECTED]>:
I'm surprised that nobody answered exactly this question. If you
name your
main voice "1", then the upper voice of the <<{...} \\ {...} >>
construct
will stay the same Voice context as the single voice.
That's true, it is explained in LM 3.2.1 I'm hearing Voices
...tangentially. One has to deduct this when he reads 'The Voice
contexts bear the names "1", "2", etc.'
I propose: to add some lines explaining this very case: how to make
the single voice to keep being the same, although a second voice
arrives. LM 3.2.2 Explicitly instantiating voices does explain that
(the red diamonds example), but does not mention the trick of calling
the voice "1" ! It rather uses a simple << .. \new Voice>> construct.
Note, though that the
<<{...} \\ {...} >> construct will add property settings equivalent
to the
\voiceOne command, so you have to explicitly insert a \oneVoice
afterwards
to revert to the default settings:
Again, this is only tangentially explained in LM 3.2.2 because the
\oneVoice command is used with no previous <<\\>>construct !
I could not have figured this, without your help. Thanks!
Now I suppose I have to take the compromise to write this down in NR
Simultaneous Notes.
--
Francisco Vila. Badajoz (Spain)
http://www.paconet.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Using parentheses in texinfo node names
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to the texinfo manual, a node name cannot contain parentheses: http://www.gnu.org/software/texinfo/manual/texinfo/html_node/Node-Line-Requirements.html Unfortunately, our docs recently added several of these nodes: fundamental.itely:@node Score is a (single) compound musical expression introduction.itely:@node About the Learning Manual (LM) introduction.itely:@node About the Music Glossary (MG) introduction.itely:@node About the Notation Reference (NR) introduction.itely:@node About the Application Usage (AU) introduction.itely:@node About the Snippet List (SL) introduction.itely:@node About the Internals Reference (IR) music-glossary.tely:@node dot (augmentation dot) programming-interface.itely:@node Doubling a note with slurs (example) programming-interface.itely:@node Adding articulation to notes (example) working.itely:@node Troubleshooting (taking it all apart) Some texinfo processors are able to treat them correctly, but others are not (e.g. texi2html writes out a warning). Since the node name and the displayed section title can be different, I propose to rename those node names to something without the parentheses. Cheers, Reinhold - -- - -- Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFImYSKTqjEwhXvPN0RAlV8AJ4w8V8Ysg/h7VU7py8758yjJXeeYgCgothL cjcw6JEx7pep+GzVkKJ6I6I= =YXIS -END PGP SIGNATURE- ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: post-GDP doc team
Neil Further to this, I've just realised that 'layer takes a number, not an integer, so the variable overprinting of grobs in the same layer could be due to rounding. In effect we have an infinite number of layers, but grobs with the same nominal value may be printed in either order. The IR says the value should be between 0 and 2, but values outside this range seem to work fine, even -ve values. Trevor - Original Message - From: "Trevor Daniels" <[EMAIL PROTECTED]> To: "Neil Puttock" <[EMAIL PROTECTED]> Cc: "lily-devel" Sent: Wednesday, August 06, 2008 10:54 AM Subject: Re: post-GDP doc team Thanks Neil. I'll amend the wording to indicate the layering of grobs with the same value of 'layer is indeterminate, and remove the example which is variable. And use the correct info for the default values! Trevor - Original Message - From: "Neil Puttock" <[EMAIL PROTECTED]> To: "Trevor Daniels" <[EMAIL PROTECTED]> Cc: "lily-devel" Sent: Wednesday, August 06, 2008 12:15 AM Subject: Re: post-GDP doc team Right, I've just tested your file using various \repeat unfold settings, and each pdf has barlines under the stave at various points; it seems you can't rely on BarLine always being printed over StaffSymbol when they have the same 'layer setting. Setting BarLine's layer to 1 reliably overwrites StaffSymbol in all cases. Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: post-GDP doc team
Thanks Neil. I'll amend the wording to indicate the layering of grobs with the same value of 'layer is indeterminate, and remove the example which is variable. And use the correct info for the default values! Trevor - Original Message - From: "Neil Puttock" <[EMAIL PROTECTED]> To: "Trevor Daniels" <[EMAIL PROTECTED]> Cc: "lily-devel" Sent: Wednesday, August 06, 2008 12:15 AM Subject: Re: post-GDP doc team Right, I've just tested your file using various \repeat unfold settings, and each pdf has barlines under the stave at various points; it seems you can't rely on BarLine always being printed over StaffSymbol when they have the same 'layer setting. Setting BarLine's layer to 1 reliably overwrites StaffSymbol in all cases. Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lyrics following split voices
Francisco
The LM's role (at least in my view) is to introduce concepts and
explanations in a logical order. It makes no attempt to be either rigorous
or comprehensive, neither should it. The NR's role, in contrast, is to
present complete and accurate facts, sweetened with a smattering of
examples.
So, for the example in question, the NR should certainly state categorically
what the voice names are in the various constructs, and examples showing the
differences would be fine. But I don't think there is any need to put
lengthy explanations in the NR - it's a reference document - they really
need to go in the LM.
So maybe we need an explanation of using voice naming in this way somewhere
in the LM. Any suggestions? And the NR should certainly list all the
context names that are assigned by default somewhere. Perhaps I'll work
that into the section on Contexts. What do you think?
Trevor
- Original Message -
From: "Francisco Vila" <[EMAIL PROTECTED]>
To: "Mats Bengtsson" <[EMAIL PROTECTED]>;
Cc: "Paul Scott" <[EMAIL PROTECTED]>; "LilyPond User"
<[EMAIL PROTECTED]>
Sent: Wednesday, August 06, 2008 12:47 AM
Subject: Re: lyrics following split voices
2008/8/5 Mats Bengtsson <[EMAIL PROTECTED]>:
I'm surprised that nobody answered exactly this question. If you name
your
main voice "1", then the upper voice of the <<{...} \\ {...} >> construct
will stay the same Voice context as the single voice.
That's true, it is explained in LM 3.2.1 I'm hearing Voices
...tangentially. One has to deduct this when he reads 'The Voice
contexts bear the names "1", "2", etc.'
I propose: to add some lines explaining this very case: how to make
the single voice to keep being the same, although a second voice
arrives. LM 3.2.2 Explicitly instantiating voices does explain that
(the red diamonds example), but does not mention the trick of calling
the voice "1" ! It rather uses a simple << .. \new Voice>> construct.
Note, though that the
<<{...} \\ {...} >> construct will add property settings equivalent to
the
\voiceOne command, so you have to explicitly insert a \oneVoice
afterwards
to revert to the default settings:
Again, this is only tangentially explained in LM 3.2.2 because the
\oneVoice command is used with no previous <<\\>>construct !
I could not have figured this, without your help. Thanks!
Now I suppose I have to take the compromise to write this down in NR
Simultaneous Notes.
--
Francisco Vila. Badajoz (Spain)
http://www.paconet.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Request for running texi2pdf in quiet mode
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Mittwoch, 6. August 2008 schrieb Graham Percival: > On Tue, 5 Aug 2008 21:51:20 +0200 > > Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > > Could we maybe change the makefiles to run texi2pdf in quiet mode > > (-q), because currently we get tens of thousands of progress output > > from texi2pdf, mainly which files are included and the current page > > number. > > > > Or is there a good reason to have texi2pdf print out all that stuff > > and clutter the output of make web? > > The only possible reason would be to view any error messages -- I > don't know how much -q hides. texi2pdf --help says: -q, --quiet no output unless errors (implies --batch) > If the texinfo is badly formed (a wrong @node name, missing }, > etc), -q still produce an error message? Hrmpf, you are right, it does not print the error message itself, only "pdfetex exited with bad status, quitting". So I suppose we cannot easily get rid of the excessive output :( > What if the @lilypond section is badly formed? The @lilypond section is processed by lilypond-book (which also produces excessive output, but fortunately only when one of the lilypond snippets changed, while texi2pdf is run if any of the (i)tely files was touched). Cheers, Reinhold - -- - -- Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFImWG+TqjEwhXvPN0RAn2FAJ0XxVwGB/gMQhtTbOm/ZTWzxvxbjQCfeAwc zf4Q9TXvk9gIY/ZFqemWgOQ= =zHL+ -END PGP SIGNATURE- ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
finished second draft?
Currently officially on Second draft: 1.3 Expressive marks 1.5 Simultaneous notes 2.2 Keyboard instruments 2.4 Fretted string instruments If any of these are finished, let me know and I'll move them into the ``finished'' category, and Ralph will start indexing them. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
