Your message dated Tue, 12 Jan 2016 18:22:39 +0100 with message-id <[email protected]> and subject line Actually close this report has caused the Debian Bug report #437267, regarding Buggy handling of dynamics in MIDI output to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 437267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437267 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: lilypond Version: 2.8.7-3.1 Severity: normal Hi, The lilypond documentation states the following: A crescendo mark is started with `\<' and terminated with `\!' or an absolute dynamic. A decrescendo is started with `\>' and is also terminated with `\!' or an absolute dynamic. Yet when we write the following: \score { \new Staff { \relative c' { c8\< d e f g a b c\f c,1\p c8\< d e f g a b\! c\f } } \layout{} \midi{} } Then the two octave renderings look almost the same in the PS/PDF output (safe for a slight difference in alignment); this is expected. However, the MIDI output is completely different. The first bar is inaudible (except for the final note); the final bar is audible, but the crescendo isn't played. Swapping both bars around mutes both the first and final bar (except, again, for their final C). If we change the first bar to c8\p\< d e f g a b\! c\f Then the crescendo is almost rendered correctly: there is now a crescendo effect, but the first C is louder than the D, and the D is so quiet as to be inaudible again. Clearly something is amiss in crescendo/decrescendo handling. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.22-1-powerpc Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lilypond depends on: ii guile-1.8 1.8.1+1-5 The GNU extension language and Sch ii guile-1.8-libs 1.8.1+1-5 Main Guile libraries ii libc6 2.6.1-1 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1.2 generic font configuration library ii libfreetype6 2.3.5-1 FreeType 2 font engine, shared lib ii libgcc1 1:4.2.1-2 GCC support library ii libglib2.0-0 2.12.13-1 The GLib library of C routines ii libgmp3c2 2:4.2.1+dfsg-5 Multiprecision arithmetic library ii libltdl3 1.5.24-1 A system independent dlopen wrappe ii libpango1.0-0 1.16.5-1 Layout and rendering of internatio ii libstdc++6 4.2.1-2 The GNU Standard C++ Library v3 ii lilypond-data 2.8.7-3.1 LilyPond music typesetter (data fi ii python 2.4.4-6 An interactive high-level object-o ii zlib1g 1:1.2.3.3.dfsg-5 compression library - runtime Versions of packages lilypond recommends: ii lilypond-doc 2.8.7-3.1 LilyPond Documentation in HTML, PS -- no debconf information
--- End Message ---
--- Begin Message ---Version: 2.14.2-1 The maintainer claims it's fixed. I didn't check this (because I don't use lilypond anymore, see pmw), but it would make sense to get my "outstanding bugs" page be cleaned up a bit. -- It is easy to love a country that is famous for chocolate and beer -- Barack Obama, speaking in Brussels, Belgium, 2014-03-26
--- End Message ---
