Menu

#3154 option to specify the name of Midi files for each \score block

Accepted
nobody
Bounty (37)
Enhancement
2015-07-21
2013-02-05
Anonymous
No

Originally created by: *anonymous

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

Reported by Javier:
http://lists.gnu.org/archive/html/bug-lilypond/2013-02/msg00016.html

Currently LilyPond allows to set the name of Midi files only for book blocks, using boookOutputSuffix or bookOutputName.
Javier is asking to add a similar feature for the \score block.

Discussed on lilypond-user:
http://lists.gnu.org/archive/html/lilypond-user/2013-02/msg00028.html

Here's the feature request:

Requesting adding the ability to state a filename for midi output from within
score's midi block (or other score-specific block).

\book{
  \bookpart{
      ...some markup
      \score{
         .....music for ScoreOne
         \layout{}
         \midi{ \set midifilename = "chap1-piece-one" }
      }
      ...more markup
      \score{
         .....music for ScoreTwo
         \layout{}
         \midi{ \set midifilename = "chap1-piece-two" }
      }
   }
  \bookpart{
      ...more markup
      \score{
         .....music for ScoreThree
         \layout{}
         \midi{ \set midifilename = "chap2-piece-one" }
      }
      ...more markup
      \score{
         .....music for ScoreTwo
         \layout{}
         \midi{ \set midifilename = "chap2-piece-two" }
      }
   }
}

Allows one to build a single book.ly file (collection of scores) that produces
a single "book.pdf" output, as well as individual midi files with user-
selected names significant to their content/context (i.e. chapter number,
composer, opus, etc.).

Discussion

  • Google Importer

    Google Importer - 2013-03-17

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

    The fix for issue 2343 added the ability to change the overall output file name and output file suffix via properties in the \paper block. It should be possible to write a patch to generate midi file names and suffixes as in the following example: 

    % In source file mymusic.ly
    \book {
        \paper {
           output-file="first-file"
         }
        \bookpart{
          %...some markup
          \score{
             .....music for ScoreOne
             \layout{}
             \midi{ output-file = "movement-one" }
          }
          %...more markup
          \score{
           %  .....music for ScoreTwo
             \layout{}
             \midi{ output-file = "movement-two" }
          }
        }
        % files generated:
        %   first-file.pdf
        %   movement-one.midi
        %   movement-two.midi
        %
    }

    \book {
      % No output-file specified
        \bookpart{
          %...some markup
          \score{
             .....music for ScoreOne
             \layout{}
             \midi{ output-suffix = "movement-three" }
          }
          %...more markup
          \score{
           %  .....music for ScoreTwo
             \layout{}
             \midi{ output-suffix = "movement-four" }
          }
        }
        % files generated:
        %   mymusic.pdf
        %   mymusic-movement-three.midi
        %   mymusic-movement-four.midi
        %
    }

    \book {
       \paper {
           output-file="third-file"
       }
       \bookpart {
          \score {
          % music for score
          \layout {}
          \midi  {}
          }
          \score {
          % music for score
          \layout {}
          \midi  {}
           }
          }
        }
        %   third-file.pdf     - Inherited from \book or \bookpart output-file property
        %   third-file-1.midi  - suffix defaulted from number of midi files generated in
        %                       current \book or \bookpart block
        %   third-file-2.midi  - suffix defaulted from number of midi files generated in
        %                       current \book or \bookpart block
        %
       \bookpart {
          \score {
          % music for score
          \layout {}
          \midi  {
                     output-suffix="fifth-movement"
            }
          }
          \score {
          % music for score
            \layout {}
            \midi  {
                     output-suffix="sixth-movement"
             }
           }
          }
        }
        %   third-file.pdf     - Inherited from \book or \bookpart output-file property
        %   third-file-fifth-movement.midi  - suffix specified in \midi block
        %   third-file-sixth-movement.midi  - suffix specified in \midi block
        %
    }

    Owner: ianhuli...@gmail.com

     
  • Google Importer

    Google Importer - 2013-04-08

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

    Work started.

    Status: Started

     
  • Google Importer

    Google Importer - 2014-02-03

    Originally posted by: jav...@olion.com

    Inquiring on status of this enhancement.  Thank You.

     
  • Google Importer

    Google Importer - 2014-12-01

    Originally posted by: jav...@olion.com

    Offering a $100 bounty on this enhancement

     
  • Google Importer

    Google Importer - 2014-12-03

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

    I add €30 bounty

    Labels: Bounty

     
  • Google Importer

    Google Importer - 2015-01-29

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

    On 29/01/15 07:20, Federico Bruni wrote:> Hi Javier
    >
    > I don't know if it's appropriate to reclassify it back to accepted.
    > Anyone interested in this issue can still see the date of last comment
    > and ask to be assigned to it..
    >
    > Perhaps "patch abandoned" is the best label to choose.
    > I put in Cc James and Phil, who know what to do better than me.
    >
    > Btw, IIRC Ian had an operation last year or so which kept him away from
    > LilyPond development. Then he came back..
    >
    > Il 29/gen/2015 02:27 "Javier Ruiz-Alma" <javier@ruiz-alma.com
    > <mailto:javier@ruiz-alma.com>> ha scritto:
    >
    >     Hi Federico,
    >     I suspect Ian may have abandoned the midi enhancement tracker he
    >     signed up to tackle.
    >     I reached out to him several weeks ago, but got no response.
    >     Is there a process or person that can decide if/when it's
    >     appropriate to reclassify this back to "accepted"?
    >     Javier Ruiz
    >     javier@ruiz-alma.com <mailto:javier@ruiz-alma.com>
    >
    >
    >     On Monday, January 12, 2015 11:48 PM, Javier Ruiz-Alma
    >     <javier@ruiz-alma.com <mailto:javier@ruiz-alma.com>> wrote:
    >
    >
    >
    >         Hello Ian,
    >
    >         My apologies for reaching out to you directly.  I volunteer for
    >         the Mutopia Project <http://www.mutopiaproject.org/>.
    >
    >         A couple years ago I requested an enhancement to LilyPond to
    >         improve midi file-naming for our orchestral and multi-score
    >         templates:
    >         https://code.google.com/p/lilypond/issues/detail?id=3154
    >
    >         The behaviour you commented on the bug tracker captured exactly
    >         the capability we hope to have.
    >
    >         Were you able to make some headway on a solution?
    >
    >         Thanks in advance for taking the time to look into this,  Javier
    >
    >         Javier Ruiz-Alma
    >         javier@ruiz-alma.com <mailto:javier@ruiz-alma.com>
    >
    >

     
  • Google Importer

    Google Importer - 2015-01-29

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

    (No comment was entered for this change.)

    Owner: ---
    Status: New

     
  • Google Importer

    Google Importer - 2015-07-21

    Originally posted by: simon.al...@mail.de

    (No comment was entered for this change.)

    Status: Accepted

     
MongoDB Logo MongoDB