Grep for TODO and ugh/ugr/urg.
.* BUGS
-. * header for PS enteredby = "bla <bla@bar.com>"
-. * Hash_table::remove ().
-. * 1. With "lilypond -f ps": The black notes with ledger lines seem to
-> have extra "blobs" over and to the left of them and all the ledger
-> lines from the staff to the note will have a blob too. For example,
-> with the note "a4" there will be a black note at the ledger line where
-> "c" would be too. However, only the "a4" will have the extra blob.
-. * ps/lily.ps
-. * devise standard for functioning of Vertical_align_element.
-. * fix interstaff slurs & beams.
-. * staff size for post/prebreaks
-. * .ly files
-. * input/star-spangled-banner
-. * input/scripts.ly
-. * mutopia/J.S.Bach/wtk1-fugue2.ly
-. * input/test/grace
-. * fix: text on rests: ridiculous dims
-. * clefs.ly
-. * m=\notes\relative c'''{
- \time 2/4;
-
- R2*4 | c2 | c2 | c2 | c2 | c2 | c2 | c2 | c2 | c2 | \break
- <{R2*10}{s2 \mark "A"; }> | % Too narrow space for the first rest in
-1.1.29
- r4 r8 [g16 \p ( a ] |
-[ ) g8-. fis16 ( g ][ ) fis8-. f16 ( g ] |
-[ ) f8-. e16 ( f ][ ) e8-. es16 ( f ] |
-[ ) es8 \f c16 ( d][es8 d16 c ] |
-) d4 r8 [g16 \p ( a ] |
-[ ) g8-. fis16 ( g ][ ) fis8-. f16 ( g ] | \break
-) c2 | c2 | c2 | c2 | c2 | c2 | c2 | c2 | c2 |
-}
+. * junk separate mudela versioning.
+. * petite-ouverture time sig size.
+. * PostScript
+. * header for PS enteredby = "bla <bla@bar.com>"
+. * ps/lily.ps see comments.
+. * By the way, I'm not sure the translation of 'C, G, and F clef'
+> should include Alto, Violin, Bass <clef translated>.
+[..]
-\score{
- \m
- \paper{
- \translator{
- \ScoreContext
- SkipBars = 1;
- }
- \translator {
- \OrchestralPartStaffContext
- }
- }
-}
+I understand your point. It should be changed.
+
+
+>
+> The terms C-clef, G-clef, F-clef stand for the signs, being
+> mutated forms of a C, a G and an F.
+>
+> The terms Violin Clef etc. stand for the signs being used in
+> special positions on the staff.
+>
+> The G-clef-sign indicates g' on the line around which the
+> snake centers. It is a Violin Clef if it is centered around the
+> second line (from below), and a French Violin Clef if it is
+> centered around the lowest.
+>
+> The C-clef indicates c' on the line that gets
+> 'pinched' by it. It is a Soprano, Mezzosoprano (English?), Alto, Tenor
+> and (don't remember exactly, maybe Baritone) Clef, depending on
+> the line (from highest to lowest).
+>
+> The F-clef-sign indicates f on the line between
+> the two dots. If it's on the second line from above, it is called
+> Bass Clef. If it's on the middle line, it is called (maybe
+> Baritone) Clef too, because it indicates the same pitches as the
+> C-Clef on the highest line. So, you could write an Alto Clef by
+> putting the F-clef sign on the lowest line (but that's _very_
+> uncommon).
+>
+> Sorry, this is written very messy because I'm in a hurry,
+> but I hope you understand what I want to say.
+>
+. * didot / big point.
. * midi key.
-. * P.P.S. It can be cool in mudela-book to distinguish in pre,postMudelaExample,
-whether MudelaExample is epsed or not: ( if this fragment is floating eps, than 1,
-otherwise 2). say preMudelaExample[eps]{}, and change it in document body sometimes.
+. * Repeats
+. * input/bugs/rep.ly (moved from test)
+. * unfold broken:
+. * without alternatives: repeat unfold 4 { a b c d }
+. * count > alternatives: repeat unfold 79 { a b c d }
+\alternative { { c c c c } { d d d d } }
+. * kind of 'initial property' iso fold/volta(semi)/unfold strings
. * fix singleStaffBracket
. * declare performers in \midi
. * fix MIDI
. * \shape 1st dim skipped?
. * turn slope-damping on/off
. * tremolo stuff
-. * fix height of / collisions with lyrics (chords),
- see input/test/vertical-text.ly; input/test/repeat.ly
. * We need feta-din*.mf files for more sizes than 10.
-. * latex bla.tex broken (titles / \lilyfooter stuff?
+. * feta-accordeon has some 'strange turning paths' on 300dpi
. * fix dynamics decently, ie. use kerning & ligatures.
-. * support_l_arr_ empty in staff-margin's G_staff_side_item
+. * dots & rest collisions?
+. * mudela-book.py
+. * fix \mudelafile{} to have decent functionality
+. * P.P.S. It can be cool in mudela-book to distinguish in
+pre,postMudelaExample, whether MudelaExample is epsed or not: ( if
+this fragment is floating eps, than 1, otherwise 2). say
+preMudelaExample[eps]{}, and change it in document body sometimes.
+. * use less RE's
. * slurs colllide with lyrics.
-. * minVerticalAlign for StaffGroups.
-. * fix OrchestralScore and Hara-kiri (i.e., fix Coriolan)
+. * Is there any reasonable way to do this: I would like to have one file
+that can generate the same tune in two different modes without having
+to go through and rewrite all the music in the other mode.
+
+Lyrics and scripts collide.
. * Phrasing: Indicating the textual underlay of a piece, or
otherwise dividing a piece into phrases.
There are distinct ways of specifying the first two (although at
present, they're not properly distinguished) but no distinct way to
specify the third. Should there be?
-. * spacing of mmrests.
-. * mem leak: redo p-score object deletion.
+. * rest collision minimum dist.
+. * a note with a circle after it, meaning:
+
+ note + circle = note + 1/4 of its length
+
+5 the circle is like a dot that's not filled in. for example, on
+ page three, the c-sharp on the second line should be a quarter with
+ a circle, not a quarter tied to a sixteenth. is this at all
+ possible with lily?
+. * tuplets that are written as "number : note", for example
+ "3 : [image of a half note here]". possible?
+. * repeat engraver, gallina.ly
+
+. * Matanya's tips:
+. * spacing for prefatory matter
+. * accidentals closer to note head
+. * to space the staffs/staffgroups contained in the score.
+. * heavier beams?
.* Cleanups needed
. * Beam
-. * Stem + Notehead
+. * Stem
. * Slur
-. * Repeats
. * Rhythmic_grouping
. * Duration
-. * Spring generation
. * Collision
. * Rest_collision
+. * clef grav prop's
+. * parser
.* TODO before 1.2
-. * \selectmusic to cut pieces from music.
-. * TODO: merge atom & molecule; make tree from molecule.
+. * Morally pure LilyPond.
+. * Remove mutopia ramblings.
+. * Remove non-free software links.
+. * Remove meta article LilyPond.
. * break priority setting from SCM.
. * Gade score
. * remove [] in favour of auto-beamer
-. * The minimum distance between different staffs works only within
- StaffGroups, not between StaffGroups. The Gade Score looks quite
- strange on the pages where the Timpani and/or Brass sections don't
- play. I've set the minimum distance with:
- \translator {
- \OrchestralScoreContext
- minVerticalAlign = 2.5*\staffheight;
- }
. * hangOnClef with non-breakable clefs.
. * Aha, the problem is the new TeX code generation for changing fonts.
> (The explanation below is mostly intended for Han-Wen and Jan)
> fontencoding OT1 is for the hyphenation mechanism to work, an
> argument that's clearly irrelevant in our application. Yet we
> see the problem for August.
-. * Check gcc 2.8.1 compatibility
. * Abstraction for engravers:
. * make "in-between" engraver (Tie, Extender)
-. * make wide_spanner_engraver (line_group_spanne,r staff_symbol)
+. * make wide_spanner_engraver (line_group_spanner, staff_symbol)
. * remove Interval dim_ from Dimension_cache and rename the struct.
. * do scaled fonts generally
+. * Spacing.
. * The Lilypond accidental symbols are available through the TeX macros,
\textflat, \textsharp and \textnatural defined in the init file
lilyponddefs.tex. All the symbols are defined in the files fetaXX.tex
are installed but they are generated in the mf/out/ directory during the
compilation.
. * make dependencies () a virtual function.
-. * fix Repeated_music design
. * one big ly2dvi input that includes *all* tests.
. * store req -> element, element -> element causes for warnings
. * include examples in RPM.
. * --prefix option?
. * -I option per filetype?
. * kpathsea?
-
. * ly2dvi/lilypond logfile.
-. * How can I specify a chord whose duration is longer than a whole note?
- \type ChordNames { \chord{ A1*2-min } }
-
-gives me a parse error. And \times doesn't work either. I can't use
-a spacer note. So it seems to be impossible to have long chords of
-general length. Of course, in the example above I can use \breve.
-But what if I want a chord that lasts for 3 whole notes? Or what
-about 2.5 whole notes? Is there a mechanism for getting this kind of
-length?
-
. * fractional chord durs.
. * hang Item on Spanner
. * do --safe for PS output?
. * ly2dvi
. * bottomnote for ly2dvi
. * deps for ly2dvi
+
.* STUFF
. * compulsory hshift
+. * Give # lines in linebreaking.
. * arrows on slurs.
+. * rewrite context defs using Scheme
+. * \selectmusic to cut pieces from music.
+. * TODO: merge atom & molecule; make tree from molecule.
. * Align_element::padding ?
-. * uniformise property names...
-. * ydirection <-> yDirection
-. * rather allow '_' in identifiers first (i.e. junk ^ and _),
-and do y_direction?
-. * typo checks on property names?
+. * typo checks on property names?
. * use streambufs and iostream
to provide IO handling for TeX stream, mudela stream, data-file.
. * seriously buffer TeX output (do profile of writing .5 mb TeX file.)
. * zip target for binary windows dist (JBR)
. * junking \skip req in lyrics
. * mi2mu empty staffs.
+. * use Fourier transformation for rhythmic quantisation.
. * horizontal centering of dynamics
. * $DEPENDENCIES_OUTPUT support
-. * Xdvi zooming ?! Try to understand GS garbage collection.
-gs: Error: /undefined in draw_beam
-gs: Operand stack:
. * fix vertical alignment and stafflines
. * declaring Performers
-. * GrandStaff needs more work -- I want a single word
- `harpsichord' to the left of the grandstaff, not one on each
- stave. (Organ staff -- with separate pedal -- but common
- properties may be something to think about. Of course for
- organ you want to be able to give stop indications on the way
- through, so the \property Voice.Instrument would be a stop,
- and \property GrandStaff.instrument would be PipeOrgan...)
. * *.yo: fix pod manpage layout legacy
. * text-items clash with stems/beams
. * --include, -I option for ly2dvi (pass on to lily)
. * fix title/instrument placements; see input/test/title.ly
. * <\voiceone c4. \voicetwo c4>
. * add full cello suites to web site (kom op, Maarten!)
+. * add mudela-book-doc source to webstie.
. * Rethink Time_description
\cadenza , \meter, \grouping should all be \properties
. * rename
. * put errorlevel in Input class
. * junk nesting slurs
. * integrate midi-elts from mi2mu and lily?
+. * distinguish between unset and empty properties.
.* FONT
. * the bracket is ugly (wings are too parabolic, should be more circular)
. * versioning for Feta
+. * rewrite dynamic signs. They're kind of spaghetti now.
. * The `3' in the meter key is a one or two pixels too thin (at 600dpi)
in the middle:
. * design macro for penstroke with rounded endings
. * timesig C: fat yet less curved. Check out relations.
. * design decent macro for bulbed endings
. * printer dependencies.
-. * y-refpoint for rests should be the 4th staffline (gclef: b')
-. * clean-up eight+ rests
. * versioning
. * lo-res fixes.
. * work out sizes of character fonts.
. * coda signs: Segno, O+
. * glissando, arpeggio
. * lengthened trill
-. * 128th flags
. * include important spacing dims in fetalog
+. * scalability: use blot_diameter everywhere, make font chubbier for
+ small sizes.
+
.* 3RD PARTY BUGS
. * GNU diff 2.7: diff -rN does not see a new directory with empty file
. * check out GCC signatures?
thing is fixed
.* PROJECTS
. * Scripts:
-. * fix position of bar number
. * stack scripts in chords:
% fingering: footing:
< a-4 c-2 g-1 > < c-\ltoe e-\lheel >
. * detect of 16/8 bit files
. * examples to go with it.
-. * Spring_spacer:
-. * write a faster Spring_spacer (without matrices if possible)
-. * relate energybound to linelen unitspace fontsize etc.
-. * used fixed point fp?
-
. * \header
. * output header info to MIDI too.
. * a musical dictionary. See Documentation/vocabulary-*, other
- languages:
+languages:
. * explanations
. * italian
. * german
. * add to MIDI output:
. * tempo change
. * ornaments (and trills?)
-. * repeat/volta
. * slurs
. * accents
. * dynamics
> Would it be hard to add support for proper dynamics in MIDI output? I
> would really like to have this feature...
-To answer this, I have to give a little background. Please say so if
-I am being obtuse.
-
-Both audio and notation elements are created decentrally, when
-LilyPond says "Interpreting music ... [8][16] etc." After all
-elements are created, they are processed again to calculate all
-parameters. After that is done, they are dumped onto the output (the
-MIDI stream or the TeX file).
-
-The audio and notation elements are created by objects called
-performer and engraver respectively. They work by taking a chunk of
-input (a so-called request), and using the request to create an audio
-or notation element.
-
-After some processing, the engraver sends the created elements to
-its enclosing notation/performance context.
-
-In the case of notation, engravers can also modify existing elements
-created by sibling engravers. Eg. the beam-engraver will modify stems
-when it creates a beam over a couple of stems. This is done in
-Engraver::do_acknowledge_element () and
-Engraver::do_process_acknowledged ().
-
-In the case of audio, there are no mechanisms to modify existing audio
-elements. After the audio elements are created, they are sent directly
-to the enclosing context (an instance of Performer_group_performer),
-through the method Performer::play ()
-
Concretely spoken, for dynamics you have to write a performer
(Dynamics_performer), that will take the input requests. If I
understand correctly, every MIDI note played must have its dynamic
1 supporting dynamic settings in Audio_note
- 2 mimicking the broadcast/acknowledge mechanism of the Engravers in
- the Performers
-
- 3 using that mechanism to write a Dynamics_performer that will modify
+ 2 Write a Dynamics_performer that will modify
any notes it finds to set appropriate strengths.
-You could also kludge this by deriving from Performer_group_performer
-a performer that also sets dynamics within notes, but that is not the
-elegant way to do it.
-
I'd say that the work involved is not hard, but you have to be fluent
with C++ and need some insight into the working of Notation Contexts
and friends. I guess I could do it in a day or so, but if you are not
the MIDI output (I don't even have a soundcard). But I *do* want to help
you or other people with implementing this, so if you need help, don't
hesitate to ask.
-
. * account for rhythmic position in measure
. * etc.
.* INPUTLANGUAGE
. * \rhythms 4 16 16 16 16; c c c c c -> c4 c16 etc.
. * Language:
-. * \type -> \context ?
. * \translator -> ?
. * fix \partial
. * \bla {} vs \bla ;
.* SMALLISH PROJECTS
+. * Faulenzer sign (% repeat). Perhaps also use \repeat syntax?
+
. * fix confusing naming in Engraver vs Engraver_group_engraver (context)
. * progress when creating MIDI elts.
I hope the above helps,
--russ
-
-
---
-"Even if you are on the right track, you'll get run over
-if you just sit there."
- --Will Rogers (1879-1935)
* OUTLINE SETUP
.* .EMACS
projects / lilypond.git / blobdiff