Doc - NR: 3.5.9 - recommendation to \include articulate.ly just before the...

Issue Tracker for LilyPond

Brought to you by: fedelibre, hahnjo, philholmes, tdanielsmusic

#4381 Doc - NR: 3.5.9 - recommendation to \include articulate.ly just before the midi block

Status: Verified

Owner:

Labels: Fixed_2_19_25 (33)

Needs:

Patch:

Type: Enhancement

Updated: 2015-09-01

Created: 2015-05-10

Creator: Anonymous

Private: No

Originally created by: *anonymous

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

I believe that this was not covered by issue #2877, the recent big patch from James (about to be pushed):
https://codereview.appspot.com/120480043

In the Articulate chapter I suggest adding a tip to work around the errors that may be caused by the articulate script: moving the include of articulate.ly after the \score block which contains the \layout and before the \score block which contains the \midi block.

Related

Issues: ~~#2877~~
Issues: ~~#4517~~

Discussion

Google Importer - 2015-07-19

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

Federico, now that the chapter has been updated, can you be more specific with your request here. What 'errors' (or type of 'errors') may occur with this script if it is not placed 'just so'?

Are they benign or are the catastrophic.

At the moment the information is a bit too vague for me to be able to think of what to write.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-07-19

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

Sorry, poor report indeed. I was thinking of some discussions on lilypond-user. For example:
http://lists.gnu.org/archive/html/lilypond-user/2012-12/msg00211.html

Here's an example and the current output on 2.19,23 is attached:

\version "2.19.23"

% If you leave this include here, the file might not compile in some cases.
% When it does, notes are not printed as grace notes and a spurious dash line appears.
%
% If you comment the first include and uncomment the include before the score block,
% file compiles always and \afterGrace works correctly.
\include "articulate.ly"

theMusic = \relative {
c''1 \afterGrace d1 { c16^"these should be grace notes" d }
}

%\include "articulate.ly"

\score {
\new Staff { \theMusic }
\layout{}
}

articulate-after-grace.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-07-19

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

I forgot to add the \midi block in the example above, but the result is the same.

A better recommendation is using two score blocks, it makes sense including articulate just before the score block used for MIDI:

%%%

theMusic = \relative {
c''1 \afterGrace d1 { c16^"these should be grace notes" d }
}

\score {
\new Staff { \theMusic }
\layout{}
}

\include "articulate.ly"

\score {
\new Staff { \theMusic }
\midi{}
}

%%%

This workaround worked in other cases but finding them in the archives is not easy.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-07-19

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

I forgot the \articulate but you got the idea...

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-07-19

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

I do, but is this a bug? We don't @knownissues bugs as a rule. If it is we are better to change this from a doc tracker to a general bug fix.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-07-20

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

I don't think that it's a specific bug but a general limitation.

I read again the documentation, which says that the engraved output is altered when using the articulate script. Users will find it annoying and will report bugs, because they want the nice MIDI sound AND the nice engraving. The workaround above seems to solve this *general problem* (so the problem above is just one of the many possible errors that articulate can produce in the layout).

This is my understanding as a user who does not even use articulate anymore.
I hope that a developer can explain better.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-07-20

Originally posted by: dak@gnu.org

The problem as I understand it is that the output is altered even without using the \articulate command. That should be fixed so that it does not matter where you load articulate.ly as long as you don't call \articulate.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-07-21

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

Added @example and explanation showing how to avoid the articulate script from interfering with engraved output when producing MIDI output at the same time. Also fixed a typo further up the file in a different section.

http://codereview.appspot.com/254330043

Summary: Doc - NR: 3.5.9 - recommendation to \include articulate.ly just before the midi block
Owner: pkx1...@gmail.com
Labels: Patch-new
Status: Started

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-07-22

Originally posted by: dak@gnu.org

This issue would get invalidated if a solution for issue 4517 is found.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-07-22

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

Passes make, make check and a full make doc

Labels: -Patch-new Patch-review

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-07-24

Originally posted by: dak@gnu.org

I've added a patch for issue 4517. As long as the jury is out on that one, it would at least seem to make no sense to invest more work in this issue. So I am setting this to Patch-waiting for now.

Sorry for not coming up (or down) earlier with it. I'm really doing all I can.

Labels: -Patch-review Patch-waiting

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-08-02

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

Is this now invalid sine issue 4517 is now pushed?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-08-02

Originally posted by: dak@gnu.org

Re #12: Hopefully so. Maybe check the given example in comment #2?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2015-08-05

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

(No comment was entered for this change.)

Labels: -Patch-waiting Patch-needs_work

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2015-09-01

Confirmed that

author David Kastrup dak@gnu.org
Thu, 23 Jul 2015 16:15:18 +0000 (18:15 +0200)
committer David Kastrup dak@gnu.org
Thu, 30 Jul 2015 08:10:35 +0000 (10:10 +0200)
commit 55ea0719e3383f52cec434c6fcb5e6776b741d48

Fixes this issue

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2015-09-01

labels: --> Fixed_2_19_25

Description has changed:

Diff:

status: Started --> Verified

assigned_to: pkx166h

Needs: -->

Patch: needs_work -->

Type: Documentation --> Enhancement
If you would like to refer to this comment somewhere else in this project, copy and paste the following link: