|
From: | philippe hezaine |
Subject: | Re: No Midi w/ crescendo |
Date: | Sun, 29 Oct 2006 13:02:18 +0100 |
User-agent: | Mozilla Thunderbird 1.0.8-1.1.fc4 (X11/20060501) |
Mats Bengtsson wrote:
This is a well-known bug in the MIDI output. The problem is that you never specified any absolute dynamics (like \p or \mf or \ff or ...)At home, I put (de)crescendi in a variable named dynamics, like in the templatebefore the crescendo, so LilyPond has no idea on what dynamics to startthe crescendo. For some silly reason, it then doesn't start at the default dynamics level but keeps the full crescendo almost silent.This very problem isn't documented in the section on "Creating MIDI files", but there you can find descriptions on other similar problems and also a simple way to remove all dynamics handling in the MIDI output while keeping it in the printed output, which makes sense for proof listening./Mats Quoting John Mandereau <address@hidden>:Kamal wrote:I am using lilypond 2.8.6 If I use the following code snippet: a\< b c d\! then a silent passage will be produced in the midi output although the documentation says that unterminated crescendos will produce that. Can can this be overcome?As far as I have experienced with midi players (mainly with Timidity), (de)crescendi mess up MIDI files from LilyPond playing. I don't know if it's LilyPond or Timidity fault. As a workaround, I remove any \<, \< and \! when I want MIDI output. Cheers, -- John Mandereau <address@hidden>
Piano centered dynamics ( in manuel-2.9.23-1, Chapitre D.2.4 ). Then, for the midi block where you have a second score block (see below) I comment or suppress the dynamics for the midi like this: ( %\dynamics ) and I've no problem for the midi file. \score { \unfoldRepeats \context PianoStaff << \context Staff=upper \upper %\dynamics \context Staff=lower << \lower %\dynamics >> >> \midi { \tempo 4=126 \context { \type "Performer_group" \name Dynamics }\context {
\PianoStaff \accepts Dynamics } } }
[Prev in Thread] | Current Thread | [Next in Thread] |