Menu

#2877 Doc: NR section 3.5.x MIDI file creation tidy up

Verified
nobody
Documentation
2015-05-12
2012-10-03
Anonymous
No

Originally created by: *anonymous

Originally created by: ma...@gregoriana.sk
Originally owned by: pkx1...@gmail.com

Reported by Federico Bruni:
http://lists.gnu.org/archive/html/bug-lilypond/2012-09/msg00138.html

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 for \layout and one for \midi?

So the visual output won't be altered.

There's any reason why you didn't make this suggestion?

Related

Issues: #4381

Discussion

1 2 3 > >> (Page 1 of 3)
  • Google Importer

    Google Importer - 2012-10-03

    Originally posted by: paconet....@gmail.com

    (No comment was entered for this change.)

    Owner: paconet....@gmail.com

     
  • Google Importer

    Google Importer - 2012-12-09

    Originally posted by: fedel...@gmail.com

    Look at this report:
    http://lists.gnu.org/archive/html/lilypond-user/2012-12/msg00143.html

    "If I include "articulate.ly" then beamed aftergrace notes have a tenuto articulation and are not rendered smaller, even though I never called the \articulate macro."

    We may also suggest to put the \include "articulate.ly" after the notes and just before the score block where \articulate is used.

     
  • Google Importer

    Google Importer - 2012-12-09

    Originally posted by: paconet....@gmail.com

    Agreed. Sorry, this is an open issue I own and I had forgotten.

     
  • Google Importer

    Google Importer - 2013-01-20

    Originally posted by: fedel...@gmail.com

    checked with latest master:
    [r8328cbc8d443bf66309e7d321f2ae636d59a25b3]

    bug is still there

     
  • Google Importer

    Google Importer - 2013-01-20

    Originally posted by: lemzw...@googlemail.com

    (No comment was entered for this change.)

    Summary: articulate.ly: documentation issues and incorrect rendering of grace notes

     
  • Google Importer

    Google Importer - 2014-01-05

    Originally posted by: pkx1...@gmail.com

    I've looked over this and the midi section in the NR.

    Notes about having a a separate \score section (one with the normal music + \layout) and one with just \midi is already mentioned in the repeats in MIDI section.

    However I feel this whole 3.5.x section is slightly messy in terms of its ordering and there are a some 'doc policy' issues (@seealso and spacing discrepancies across the 3.5.x sections) that I am going to tidy up first in a separate tracker (not yet created).

    Then I suggest we move the Articulate script section from its current position of 3.5.8 to 3.5.5 (so every other section shifts down accordingly) and then remove/move/merge (as appropriate) information that pertains to the Articulate script from the other now-proceeding sections into the new 3.5.5/Articulate script section or possibly simplify the Articulate script section further and just make the examples/explanations in 3.5.6-8 better/consistent.

    Owner: pkx1...@gmail.com
    Status: Started

     
  • Google Importer

    Google Importer - 2014-08-02

    Originally posted by: pkx1...@gmail.com

    Doc: NR section 3.5.x MIDI file creation tidy up

    Issue 2877

    This issue is specific to the articulate.ly
    documentation but I feel we're just trying
    to constantly patch a messy section. So this
    is an attempt to tidy up this section.

    No new information has been added apart from more
    @cindex or @seealso references; and nothing
    (technical) has been removed either.

    Tthere has been a re-titling and re-ordering
    of the @nodes in an attempt to make the MIDI
    explanations follow a more step-by-step, logical
    order.

    The introduction has been shortened and @knownissues
    have been moved. Where technical information has
    been 'deleted', it will have been moved to either
    a more appropriate place in the subsection, or into a
    different subsection within @node.

    http://codereview.appspot.com/120480043

    Labels: Patch-new

     
  • Google Importer

    Google Importer - 2014-08-02

    Originally posted by: pkx1...@gmail.com

    (No comment was entered for this change.)

    Labels: -Patch-new Patch-needs_work

     
  • Google Importer

    Google Importer - 2014-08-02

    Originally posted by: pkx1...@gmail.com

    More edits - Patch not yet finalized.

    http://codereview.appspot.com/120480043

    Labels: -Patch-needs_work Patch-new

     
  • Google Importer

    Google Importer - 2014-08-02

    Originally posted by: pkx1...@gmail.com

    (No comment was entered for this change.)

    Labels: -Patch-new Patch-needs_work

     
  • Google Importer

    Google Importer - 2014-08-03

    Originally posted by: pkx1...@gmail.com

    More tightening up. New snippet added and text taken from 'documentation' and added directly as comments in the Articulate script

    http://codereview.appspot.com/120480043

    Labels: -Patch-needs_work Patch-new

     
  • Google Importer

    Google Importer - 2014-08-03

    Originally posted by: pkx1...@gmail.com

    (No comment was entered for this change.)

    Labels: -Patch-new Patch-needs_work

     
  • Google Importer

    Google Importer - 2014-08-19

    Originally posted by: pkx1...@gmail.com

    more tidying up - this now compiles

    http://codereview.appspot.com/120480043

    Labels: -Patch-needs_work Patch-new

     
  • Google Importer

    Google Importer - 2014-08-19

    Originally posted by: pkx1...@gmail.com

    Still need to spell check and make sure there is no duplicated information, also to check the sectioning follows the CG

    Labels: -Patch-new Patch-needs_work

     
  • Google Importer

    Google Importer - 2014-09-07

    Originally posted by: pkx1...@gmail.com

    Rebase with current master

    http://codereview.appspot.com/120480043

    Labels: -Patch-needs_work Patch-new

     
  • Google Importer

    Google Importer - 2014-09-07

    Originally posted by: pkx1...@gmail.com

    Doc: NR section 3.5.x MIDI file creation tidy up

    Issue 2877

    This issue is specific to the articulate.ly
    documentation but I feel we're constantly
    updating a 'messy' chapter that doesn't really
    follow many of the CG guidelines and could
    be better organized.

    So this is an attempt to tidy up. Apart from
    some @cindex or @seealso references no new
    information has been added and nothing
    technical has been removed but some of it
    has been moved around so that it is grouped
    more logically.

    I realise this is a big patch and I did
    try to figure out how to make it in smaller
    bite-size chunks but it would have been
    hard to keep it coherent while undergoing
    the change (and is probably why no one has
    really tackled this section to tidy it up).

    In the end after some editing I just decided
    to carry on a complete the chapter as a whole.

    Some snippets have been created from the
    main text as they were inappropriate for the
    NR and the Articulate script now contains
    some additional comments based on previously
    added NR @knownissues that were just a list
    of things that the script didn't support and
    which I felt were better *in* the articulate
    file itself.

    The @lilypond examples have been simplified
    and turned into @examples instead as the
    engraving output is largely irrelevant
    in a section about MIDI; it also saves a lot
    of space.

    There is a longer introduction and the sections
    have been organized in such a way that it starts
    with how to create MIDI files with the default
    empty MIDI block, then explains how to use
    repeats and multiple voicces in MIDI (again
    still with no MIDI block modifications).
    The next subsection then moves to enhancing
    the MIDI output by adding Instruments and then
    talks about setting MIDI block properties
    finally moving onto the Articulate script.

    The last part of the chapter then talks about
    Dynamics and Volume - it seemed more sensible
    to group those two together and as some of the
    volume settings are more complex they are at
    the end of the chapter.

    http://codereview.appspot.com/120480043

     
  • Google Importer

    Google Importer - 2014-09-07

    Originally posted by: pkx1...@gmail.com

    Fails make doc :(

    Labels: -Patch-new Patch-needs_work

     
  • Google Importer

    Google Importer - 2014-09-27

    Originally posted by: pkx1...@gmail.com

    compiles doc (thanks Heikki)

    http://codereview.appspot.com/120480043

    Labels: -Patch-needs_work Patch-new

     
  • Google Importer

    Google Importer - 2014-09-27

    Originally posted by: pkx1...@gmail.com

    Passes make, make check and a full make doc

    Labels: -Patch-new Patch-review

     
  • Google Importer

    Google Importer - 2014-09-27

    Originally posted by: pkx1...@gmail.com

    Corrections from Heikki and Marc (thanks)

    http://codereview.appspot.com/120480043

    Labels: -Patch-review Patch-new

     
  • Google Importer

    Google Importer - 2014-09-28

    Originally posted by: dak@gnu.org

    Patchy the autobot says: Fails make with lilypond-book.py: error: file not found: creating-custom-dynamics-in-midi.ly

    Labels: -Patch-new Patch-needs_work

     
  • Google Importer

    Google Importer - 2014-09-28

    Originally posted by: pkx1...@gmail.com

    Patchy doesn't do makelsr.py :)

    This passes make and a full make doc (when built manually).

    Labels: -Patch-needs_work Patch-review

     
  • Google Importer

    Google Importer - 2014-09-28

    Originally posted by: pkx1...@gmail.com

    Mark H's comment about unfoldrepeats

    http://codereview.appspot.com/120480043

    Labels: -Patch-review Patch-new

     
  • Google Importer

    Google Importer - 2014-09-29

    Originally posted by: pkx1...@gmail.com

    Passes make, make check and a full make doc

    Labels: -Patch-new Patch-review

     
1 2 3 > >> (Page 1 of 3)
MongoDB Logo MongoDB