Re: midiInstrument changes play one note too late.
Hans Aikema hans.aik...@aikebah.net writes: On 14-3-2012 14:30, Michael Ellis wrote: On Tue, Mar 13, 2012 at 5:26 PM, Michael Ellis michael.f.el...@gmail.com wrote: Is this a known problem? I don't see any prior reports online and I've been seeing it since at least 2.12 but assumed it was because I was doing some fairly complicated things. I took time to reduce it to a minimal example today. It's still present in 2.15.33 as shown by the example below. FWIW, I'm running OS X 10.6.7 and playing the midi with QuickTime. I'm attaching the midi file. Is there a workaround? Thanks, Mike Wow. It's rare not to get a response from this list. Did I phrase the question incredibly poorly? Don't worry, IMHO your phrasing was perfectly clear. Sometimes it just takes more than a day 5:30pm to 9:30am is not more than a day. It is just few hours of daylight. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midiInstrument changes play one note too late.
Michael Ellis michael.f.el...@gmail.com writes: In any case, this seems to me like a fairly serious defect. I hope it's on the list for 2.16. Don't worry. No stock options will be emitted to the responsible developers unless this deficiency is cured before 2.16 gets released. In other words: no, this is not on the list for 2.16. If you are interested in the release criteria for stable releases, they can be found in the Contributor's Guide in the documentation if memory serves me right. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midiInstrument changes play one note too late.
Janek Warchoł janek.lilyp...@gmail.com writes: On Wed, Mar 14, 2012 at 6:01 PM, Michael Ellis michael.f.el...@gmail.com wrote: I'm not sure how I would go about implementing the suggested workaround for my application. I run into the problem primarily when transcribing individual choral parts for my section. It's nice in the midi output if cues from other parts are sounded by a different instrument. Since I don't have time to transcribe the entire score, it's not practical to use the built-in LilyPond cue methods Hmm? IIRC to use the LilyPond method you don't need to transcribe the entire score, just the fragment you want to quote. Be sure to add appropriate number of skips to have it appear at the right moment. In any case, this seems to me like a fairly serious defect. I hope it's on the list for 2.16. I'm sorry if it will sound harsh, but compared to some other things i definitely won't call it serious... And it's not on the list for 2.16, unless you pay someone to fix it (i recommend David Kastrup). I hope this won't discourage you, but i don't expect it to be on 2.18 list, too - i guess it will be fixed in, like, 2 years or so. Our development resources are *really that limited*. So, please seriously consider fixing it yourself (we will provide basic guidance to you) or paying David. Bugs that manifest themselves on proprietary software only (and it sounds like it is a problem with a proprietary player) are not something I could reproduce, so while I thank you for your recommendation, this would not be a task I would have the means to tackle. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
midiInstrument changes play one note too late.
Is this a known problem? I don't see any prior reports online and
I've been seeing it since at least 2.12 but assumed it was because I
was doing some fairly complicated things. I took time to reduce it to
a minimal example today. It's still present in 2.15.33 as shown by the
example below. FWIW, I'm running OS X 10.6.7 and playing the midi
with QuickTime. I'm attaching the midi file.
Is there a workaround?
Thanks,
Mike
%% Minimal Example
%% BUG? Midi instrument changes are delayed by one note.
mymusic = {
\set midiInstrument = acoustic grand
c'1^pno. | % midi ok
\set midiInstrument = cello
d'1^cel. | % wrong : midi plays piano.
\set midiInstrument = acoustic grand
e'1^pno. | % wrong : midi plays cello
c'1^pno. | % midi ok
}
\score {
\new Voice = Test { \mymusic }
\layout {}
\midi {
% This lets us specify instrument in melody
\context {
\Staff
\remove Staff_performer
}
\context {
\Voice
\consists Staff_performer
}
}
}
\version 2.15.33
Cheers,
Mike
midi_late_instrument_change.midi
Description: MIDI audio
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midiInstrument changes play one note too late.
On Tue, Mar 13, 2012 at 5:26 PM, Michael Ellis
michael.f.el...@gmail.com wrote:
Is this a known problem? I don't see any prior reports online and
I've been seeing it since at least 2.12 but assumed it was because I
was doing some fairly complicated things. I took time to reduce it to
a minimal example today. It's still present in 2.15.33 as shown by the
example below. FWIW, I'm running OS X 10.6.7 and playing the midi
with QuickTime. I'm attaching the midi file.
Is there a workaround?
Thanks,
Mike
%% Minimal Example
%% BUG? Midi instrument changes are delayed by one note.
mymusic = {
\set midiInstrument = acoustic grand
c'1^pno. | % midi ok
\set midiInstrument = cello
d'1^cel. | % wrong : midi plays piano.
\set midiInstrument = acoustic grand
e'1^pno. | % wrong : midi plays cello
c'1^pno. | % midi ok
}
\score {
\new Voice = Test { \mymusic }
\layout {}
\midi {
% This lets us specify instrument in melody
\context {
\Staff
\remove Staff_performer
}
\context {
\Voice
\consists Staff_performer
}
}
}
\version 2.15.33
Wow. It's rare not to get a response from this list. Did I phrase the
question incredibly poorly?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midiInstrument changes play one note too late.
On 14-3-2012 14:30, Michael Ellis wrote: On Tue, Mar 13, 2012 at 5:26 PM, Michael Ellis michael.f.el...@gmail.com wrote: Is this a known problem? I don't see any prior reports online and I've been seeing it since at least 2.12 but assumed it was because I was doing some fairly complicated things. I took time to reduce it to a minimal example today. It's still present in 2.15.33 as shown by the example below. FWIW, I'm running OS X 10.6.7 and playing the midi with QuickTime. I'm attaching the midi file. Is there a workaround? Thanks, Mike Wow. It's rare not to get a response from this list. Did I phrase the question incredibly poorly? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user . Michael, Don't worry, IMHO your phrasing was perfectly clear. Sometimes it just takes more than a day for someone to notice a post, vaguely remembering reading something about it a while ago and than googling up the answer ;) But here it is: Yes it's an issue with lilypond, it is already known and there is a documented work-around in the issue. See http://code.google.com/p/lilypond/issues/detail?id=1661 for the details. regards, Hans ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midiInstrument changes play one note too late.
On Wed, Mar 14, 2012 at 11:38 AM, Hans Aikema hans.aik...@aikebah.net wrote:
On 14-3-2012 14:30, Michael Ellis wrote:
On Tue, Mar 13, 2012 at 5:26 PM, Michael Ellis
michael.f.el...@gmail.com wrote:
Is this a known problem? I don't see any prior reports online and
I've been seeing it since at least 2.12 but assumed it was because I
was doing some fairly complicated things. I took time to reduce it to
a minimal example today. It's still present in 2.15.33 as shown by the
example below. FWIW, I'm running OS X 10.6.7 and playing the midi
with QuickTime. I'm attaching the midi file.
Is there a workaround?
Thanks,
Mike
Wow. It's rare not to get a response from this list. Did I phrase the
question incredibly poorly?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
.
Michael,
Don't worry, IMHO your phrasing was perfectly clear. Sometimes it just takes
more than a day for someone to notice a post, vaguely remembering reading
something about it a while ago and than googling up the answer ;)
But here it is: Yes it's an issue with lilypond, it is already known and
there is a documented work-around in the issue.
See http://code.google.com/p/lilypond/issues/detail?id=1661 for the details.
regards,
Hans
Thanks, Hans. I did find that report while searching but I wasn't
sure whether it was the same problem as the report dealt with mapping
dynamic changes to parallel skip sequences. My report deals with
instrument changes in single voice melodies.
I'm not sure how I would go about implementing the suggested
workaround for my application. I run into the problem primarily when
transcribing individual choral parts for my section. It's nice in the
midi output if cues from other parts are sounded by a different
instrument. Since I don't have time to transcribe the entire score,
it's not practical to use the built-in LilyPond cue methods, so I
wrote my own that temporarily changes the instrument, shrinks the
font, and changes the font color, thus:
cueNotes=
#(define-music-function (p l music) (ly:music?)
for printing cue notes in teeny font in color
#{
\set midiInstrument = #(cueInstrument 'get)
\override Accidental #'color = #(x11-color 'maroon)
\override Beam #'color = #(x11-color 'maroon)
\override NoteHead #'color = #(x11-color 'maroon)
\override Rest #'color = #(x11-color 'maroon)
\override Slur #'color = #(x11-color 'maroon)
\override Stem #'color = #(x11-color 'maroon)
\override Tie #'color = #(x11-color 'maroon)
\teeny
$music
\normalsize
\revert Accidental #'color
\revert Beam #'color
\revert NoteHead #'color
\revert Rest #'color
\revert Slur #'color
\revert Stem #'color
\revert Tie #'color
\set midiInstrument = #(mainInstrument 'get)
% Note: cueInstrument and mainInstrument are scheme objects with
a get method
% that returns a string, e.g acoustic grand
#})
and apply it like this:
...
do4 sol mi do |
\cueNotes { do^Sop. 8va re mi fa } |
sol mi do2 |
...
How would I go about applying the workaround from the bug report to this?
In any case, this seems to me like a fairly serious defect. I hope
it's on the list for 2.16.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midiInstrument changes play one note too late.
On 14-3-2012 18:01, Michael Ellis wrote: On Wed, Mar 14, 2012 at 11:38 AM, Hans Aikemahans.aik...@aikebah.net wrote: On 14-3-2012 14:30, Michael Ellis wrote: On Tue, Mar 13, 2012 at 5:26 PM, Michael Ellis michael.f.el...@gmail.comwrote: Is this a known problem? I don't see any prior reports online and I've been seeing it since at least 2.12 but assumed it was because I was doing some fairly complicated things. I took time to reduce it to a minimal example today. It's still present in 2.15.33 as shown by the example below. FWIW, I'm running OS X 10.6.7 and playing the midi with QuickTime. I'm attaching the midi file. Is there a workaround? Thanks, Mike Wow. It's rare not to get a response from this list. Did I phrase the question incredibly poorly? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user . Michael, Don't worry, IMHO your phrasing was perfectly clear. Sometimes it just takes more than a day for someone to notice a post, vaguely remembering reading something about it a while ago and than googling up the answer ;) But here it is: Yes it's an issue with lilypond, it is already known and there is a documented work-around in the issue. See http://code.google.com/p/lilypond/issues/detail?id=1661 for the details. regards, Hans Thanks, Hans. I did find that report while searching but I wasn't sure whether it was the same problem as the report dealt with mapping dynamic changes to parallel skip sequences. My report deals with instrument changes in single voice melodies. You're correct Michael, I misread the report... but I think it's likely that the instrument change is 'a note too late' due to the same issue. I'll do some experimenting on it and will get back to you. regards, Hans ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midiInstrument changes play one note too late.
On 14-3-2012 18:37, Hans Aikema wrote: On 14-3-2012 18:01, Michael Ellis wrote: On Wed, Mar 14, 2012 at 11:38 AM, Hans Aikemahans.aik...@aikebah.net wrote: On 14-3-2012 14:30, Michael Ellis wrote: On Tue, Mar 13, 2012 at 5:26 PM, Michael Ellis michael.f.el...@gmail.comwrote: Is this a known problem? I don't see any prior reports online and I've been seeing it since at least 2.12 but assumed it was because I was doing some fairly complicated things. I took time to reduce it to a minimal example today. It's still present in 2.15.33 as shown by the example below. FWIW, I'm running OS X 10.6.7 and playing the midi with QuickTime. I'm attaching the midi file. Is there a workaround? Thanks, Mike You're correct Michael, I misread the report... but I think it's likely that the instrument change is 'a note too late' due to the same issue. I'll do some experimenting on it and will get back to you. regards, Hans ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user . Michael, This looks like an issue with Quicktime: - When I play your midi it in Windows 7's Media player the instrument changes are at the right time. - When I convert it to a wave-file in Windows using Timidity++ the instrument changes at the right time - When I play it using Noteworthy Composer Viewer (http://www.noteworthysoftware.com/nwc2/viewer.htm) the instrument changes are at the right time - When I play it in Quicktime for Windows 7.7.1 (build 1680.42) the instrument changes a note too late - When I play it in Quicktime Player (7.6.6 (build 1710)) for Mac OS X (10.7.3) the instrument changes a note too late. If you ask me, I see a pattern there ;) regards, Hans ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midiInstrument changes play one note too late.
On Wed, Mar 14, 2012 at 2:50 PM, Hans Aikema hans.aik...@aikebah.net wrote: On 14-3-2012 18:37, Hans Aikema wrote: On 14-3-2012 18:01, Michael Ellis wrote: On Wed, Mar 14, 2012 at 11:38 AM, Hans Aikemahans.aik...@aikebah.net wrote: On 14-3-2012 14:30, Michael Ellis wrote: On Tue, Mar 13, 2012 at 5:26 PM, Michael Ellis michael.f.el...@gmail.com wrote: Is this a known problem? I don't see any prior reports online and I've been seeing it since at least 2.12 but assumed it was because I was doing some fairly complicated things. I took time to reduce it to a minimal example today. It's still present in 2.15.33 as shown by the example below. FWIW, I'm running OS X 10.6.7 and playing the midi with QuickTime. I'm attaching the midi file. Is there a workaround? Thanks, Mike You're correct Michael, I misread the report... but I think it's likely that the instrument change is 'a note too late' due to the same issue. I'll do some experimenting on it and will get back to you. regards, Hans ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user . Michael, This looks like an issue with Quicktime: - When I play your midi it in Windows 7's Media player the instrument changes are at the right time. - When I convert it to a wave-file in Windows using Timidity++ the instrument changes at the right time - When I play it using Noteworthy Composer Viewer (http://www.noteworthysoftware.com/nwc2/viewer.htm) the instrument changes are at the right time - When I play it in Quicktime for Windows 7.7.1 (build 1680.42) the instrument changes a note too late - When I play it in Quicktime Player (7.6.6 (build 1710)) for Mac OS X (10.7.3) the instrument changes a note too late. If you ask me, I see a pattern there ;) regards, Hans Me, too. Thanks very much for digging into it. I confirmed that LilyPondTool's player doesn't have the problem on OS X. QMidi also seems ok. It's kind of wild that there are no reports when I search for QuickTime midi instrument change delay etc. Guess most Mac users don't listen very closely :-) Cheers, Mike ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midiInstrument changes play one note too late.
On 14-3-2012 21:07, Michael Ellis wrote: Thanks very much for digging into it. I confirmed that LilyPondTool's player doesn't have the problem on OS X. QMidi also seems ok. It's kind of wild that there are no reports when I search for QuickTime midi instrument change delay etc. Guess most Mac users don't listen very closely Might also be Mac Lilypond users don't use Quicktime for MIDI playback and Quicktime users only use 'single-instrument-per-track' MIDI-files. regards, Hans ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midiInstrument changes play one note too late.
On Wed, Mar 14, 2012 at 6:01 PM, Michael Ellis michael.f.el...@gmail.com wrote: I'm not sure how I would go about implementing the suggested workaround for my application. I run into the problem primarily when transcribing individual choral parts for my section. It's nice in the midi output if cues from other parts are sounded by a different instrument. Since I don't have time to transcribe the entire score, it's not practical to use the built-in LilyPond cue methods Hmm? IIRC to use the LilyPond method you don't need to transcribe the entire score, just the fragment you want to quote. Be sure to add appropriate number of skips to have it appear at the right moment. In any case, this seems to me like a fairly serious defect. I hope it's on the list for 2.16. I'm sorry if it will sound harsh, but compared to some other things i definitely won't call it serious... And it's not on the list for 2.16, unless you pay someone to fix it (i recommend David Kastrup). I hope this won't discourage you, but i don't expect it to be on 2.18 list, too - i guess it will be fixed in, like, 2 years or so. Our development resources are *really that limited*. So, please seriously consider fixing it yourself (we will provide basic guidance to you) or paying David. cheers, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
