Re: Articulate script plus grace notes following multiple voices results in timing errors

[David Baptista]

Thank you, I reckon it might not be a bug encountered often, but since it
is a consistently reproducible issue, it seemed worth of listing in the
issue tracker.

Best regards,
David Baptista

James Lowe <address@hidden> escreveu no dia quarta, 24/10/2018 à(s)
11:28:

> David,
> On 24/10/2018 10:53 am, David Baptista wrote:
>
> I think it is a single issue, but because it happens at the music
> expression level, it can manifest itself in both engraving and midi
> "rendering". Essentially the articulate script introduces wrong musical
> content, that is not present at the input, under certain conditions (an
> hypothetical parallel to help categorize the issue would be if articulate
> always added a whole bar full of C#'s to the music - it would be a glich
> present in both midi and engraving output). In this case we are talking
> about adding extra time/pause/rests to the music when articulate processes
> a music expression where grace notes follow the use of multiple voices.
> Examples:
>
> http://lilybin.com/97o636/2 - Here you cannot see the glitch visually
> because the articulate output is not engraved, only used for midi output.
> But you can hear from the midi output that extra time has been added to the
> top staff after the grace note, resulting in that staff being out of sync
> with the staff below.
>
> http://lilybin.com/97o636/1 - Here you can see the glitch visually
> because I rendered the articulate output (I understand no one in their
> right mind would do this in a normal scenario, but I believe it is helpful
> here because we can visualize the extra time that has been added,
> confirming that this is not a midi rendering problem, but a problem with
> articulate script introducing wrong musical content not present at the
> input).
>
> (Because GNU's mailing lists archives aren't always easy to follow, an
> easy to follow thread archive with the previous discussion of this issue is
> available at
> http://lilypond.1069038.n5.nabble.com/Articulate-script-plus-grace-notes-following-multiple-voices-results-in-timing-errors-td212650.html
> )
>
> Where does this manifest in regular use? Essentially in piano and
> orchestral scores, where use of multiple voices within a staff are common
> and grace notes are relatively common. Users with this use case relying on
> articulate to produce "better than bland" midi output will suffer from midi
> output with timing issues (essentially resulting in wrong playback with
> some staves being out of time with the rest of the music). The workaround
> as of now requires rewriting the music to avoid having grace notes
> following multiple voices (in my case this forced me to have different
> musical expressions for engraving and for midi output).
>
> Best regards,
> David Baptista
>
> Thank you for that.
>
> I'll take what you have written here and us it to create a new tracker for
> this and send an email to the list with the URL/number.
>
> Jamess
>
>
>
>
> James Lowe <address@hidden> escreveu no dia quarta, 24/10/2018 à(s)
> 09:16:
>
>> Hello,
>>
>> On 22/10/2018 5:57 pm, David Baptista wrote:
>> > Did this bug end up being materialized on the tracker? (I was looking if
>> > there had been any follow-up on the sourceforge bug tracker but was
>> unable
>> > to find it there).
>> >
>> > Best regards,
>> > David Baptista
>>
>> No it does not look like anything was added to the tracker based on the
>> date of this thread.
>>
>> However I am having a struggle understanding what the 'concise' request
>> is here, to be able to add something - i.e. is it an output / engraving
>> issue or an 'audio' / midi-specific issue or both (in which case we
>> probably need two trackers).
>>
>> Thank you.
>>
>> James
>>
>>
>> > Torsten Hämmerle <address@hidden> escreveu no dia sexta,
>> > 4/05/2018 à(s) 14:01:
>> >
>> >> David Baptista wrote
>> >>> Thank you for the speedy reply.
>> >> Ok, I admit it was too speedy...
>> >> Yes, you are right, I confirm to have the same effect here.
>> >>
>> >> That, indeed, calls for a tracker issue.
>> >>
>> >> All the best and thanks for the hint,
>> >> Torsten
>> >>
>> >>
>> >>
>> >> --
>> >> Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html
>> >>
>> >> _______________________________________________
>> >> bug-lilypond mailing list
>> >> address@hidden
>> >> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>> >>
>> > _______________________________________________
>> > bug-lilypond mailing list
>> > address@hidden
>> > https://lists.gnu.org/mailman/listinfo/bug-lilypond
>>
>