Re: Drums broken in 2.0.1?
Quothe R. D. Davis, from writings of Sun, Nov 23, 2003 at 12:01:57PM -0500: > What is happening is that the output from the script is somehow being > transposed down an octave. This script was one that I used for My mistake. Looking over some other .ly files that I wrote, I see that I used \relative c' for the notes to be relative to middle c. Out of curiosity, why isn't just "c" instead of "c'" used for middle c? This just leaves the midi problem, with drums being sent to the last track in the MIDI file instead of track 10. Anyway, at least I've gotten this far using gcc 2.95.2 to build lilypond 2.0.1 on a FreeBSD 4.0 system. :-) -- Copyright (C) 2003 R. D. Davis The difference between humans & other animals: All Rights Reservedan unnatural belief that we're above Nature & [EMAIL PROTECTED] 410-744-4900 her other creatures, using dogma to justify such http://www.rddavis.org beliefs and to justify much human cruelty. ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Drums broken in 2.0.1?
Hi, what I'm using to read the MIDI file is timidity; even though it worked right with the MIDI output from earlier versions of lilypond, and I'm sure was using track 10, I used "-D 10" on the command line to specify that it use that track, and still got the same result: a piano-like sound. However... Quothe Juergen Reuter, from writings of Sun, Nov 23, 2003 at 05:12:50PM +0100: > * if lily really outputs the MIDI drum notes to channel #10; you can check > this e.g. by loading the MIDI file into a MIDI sequencer software and > have a look at what the sequencer displays. Ah, one problem solved. Thanks! :-) Rosegarden shows that Lilypond is putting the drums on the last track, whatever that number happens to be. So, it appears that there may be something strange going on with the midi code. This also shows that I was wrong about it being connected with the notes being transposed down an octave. Hence, these are now two separate, seemingly unrelated, issues. -- Copyright (C) 2003 R. D. Davis The difference between humans & other animals: All Rights Reservedan unnatural belief that we're above Nature & [EMAIL PROTECTED] 410-744-4900 her other creatures, using dogma to justify such http://www.rddavis.org beliefs and to justify much human cruelty. ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Drums broken in 2.0.1?
Quothe Graham Percival, from writings of Sat, Nov 22, 2003 at 09:08:25PM -0800:
> On Sat, 22 Nov 2003 22:16:52 -0500
> "R. D. Davis" <[EMAIL PROTECTED]> wrote:
> > like some other instrument playing tones, not percussion. Similarly,
> > with 2.1.0, the drums no longer sound right in the MIDI output from
Oops... I got the 0 and 1 backwards; should have been 2.0.1; I
apologize for the mixup.
What is happening is that the output from the script is somehow being
transposed down an octave. This script was one that I used for
testing a while back, and I didn't realize at first that the other
instruments didn't sound right in comparison to how they should have
sounded. Apparently the same thing somehow happened to the output of
drums.ly. The postscript and pdf output was also transposed down an
octave. So, perhaps, unless something else is also going on, perhaps
fixing this will fix the problem and make the drums sound like drums
again.
> Did you set the MIDI instrument? Could you send a short example file
> that demonstrates this?
A file that demonstrates this is included in the lilypond
distribution: lilypond-2.0.1/input/regression/drums.ly.
> There's two possible causes:
> 1. The LilyPond syntax for percussion changed between 1.6 and 2.1, and
> convert-ly didn't fix everything.
While at first I was suspecting convert-ly, what I've written in reply
to possibility "2." below makes me question my questioning that.
> 2. There's a bug in the MIDI code for percussion in 2.1
Could there be a bug in the midi code for 2.0.1? Or, is it possible
that the drums.ly example script is wrong for the new version? Has
anyone else tried listening to it with this version?
The reason that I doubt this being a midi problem is that if lilypond
is writing notes for the drums lower than the midi software
(e.g. timidity) expects, then perhaps the midi software tries to play
the note, but there are no samples for the drums that go that low in
frequency, so something else, namely a piano sample, gets
substituted... or, something like that, perhaps.
Also note: convert-ly inserted "#(ly:set-option 'old-relative)" as the
first line in the script, but I don't see where it helps anything, and
there don't appear to be any differences if it's removed.
Also, why does convert-ly add \f after some notes?
Thanks for looking into this. The previous versions were great for
including drums in one's music.
Here's a copy of an .ly file demonstrating the problem. The first
note for the english horn, for example, is an octave below the a below
middle c in the output, and the drums sound more like a piano being
played than drums:
#(ly:set-option 'old-relative)
\version "1.9.8"
\header {
title = " "
subtitle = " "
composer = " "
meter = " "
piece = " "
tagline = " "
}
\include "paper16.ly"
\include "english.ly"
global = \notes {
\time 4/4
}
Key = \notes \key c \major
melody = { \notes {
\addlyrics \notes \relative c {
% set the following to false so that the spacing if lyrics is
% correct when slurs are used:
\property Staff.automaticMelismata = ##f
% r2 r2 r2 r2 r2 r2 r2 r2 f2\f e c1 a2 b4 e f }
}
\context Lyrics \lyrics {
}
}
}
% for stanza numbering:
% see for example input/regression/lyrics-multi-stanza.ly
% -- English Horn --
ehorn = \notes \relative c {
\Key
a b a b
}
englishhorn = {
\global
\property Staff.instrument = #"english horn"
\clef treble
\context Staff <<
\ehorn
>>
}
% -- Bagpipes or maybe Sitar ...maybe use both --
star = \notes \relative c {
\Key
r2 r2 r2 r2 r2 r2
}
sitar = {
\global
\property Staff.instrument = #"sitar"
\property Staff.midiInstrument = #"sitar"
\clef bass
\context Staff <<
\star
>>
}
% -- Drums --
\include "drumpitch-init.ly"
drh = \notes {\repeat "unfold" 20 {hhc8}}
drl = \notes {\repeat "unfold" 20 {bd4} }
\score { \repeat "volta" 2
<<
\context StaffGroup = sing <<
\context Staff = melody \melody
\property Score.BarNumber \override #'break-visibility = #end-of-line-invisible
\property Score.barNumberVisibility = #(every-nth-bar-number-visible 4)
\property Score.BarNumber \override #'molecule-callback =
#(make-molecule-boxer 0.1 0.25 0.25 Text_item::brew_molecule)
\property Score.BarNumber \override #'font-relative-size = #1
>>
\context StaffGroup = horns <<
\context Staff = englishhorn \englishhorn
\context Staff = sitar \sitar
>>
\apply #(drums->paper 'drums) \context Staff=drumst \notes <<
\property Staff.instrument="drums"
\clef "percussion"
\context Voice=voa {\stemUp \drh }
\context Voice=vob {\stemDown \drl }
>>
>>
\paper {
Re: Drums broken in 2.0.1?
Hi! Currently, I don't have time to look further into this, but you may want to check * if your MIDI output device is GM compatible (if it is not older than, say, roughly 5 years, than it should be compatible), * if your MIDI output device is set up to produce drum sounds on channel #10 (such as defined in the GM spec), e.g. by manually creating an appropriate small MIDI file with a MIDI sequencer or playing an existing MIDI file that you a sure of that it emits drum sounds to channel #10, * if lily really outputs the MIDI drum notes to channel #10; you can check this e.g. by loading the MIDI file into a MIDI sequencer software and have a look at what the sequencer displays. Greetings, Juergen On Sun, 22 Nov 2003, R. D. Davis wrote: > After finally getting Lilypond compiled successfully after installing > some more dependencies, nearly everything seemed to be working ok > except for drums, and this includes the drums in the > lilypond-2.0.1/input/regression/drums.ly script. No errors were > produced, and the paper output appears ok; however, the drums sound > like some other instrument playing tones, not percussion. Similarly, > with 2.1.0, the drums no longer sound right in the MIDI output from > other scripts (converted to 2.1.0) that I used with versions 1.6.x and > 1.8.x. Previously, the drums were ok. > > Has anyone else experienced this problem? Is there a simple fix? > > -- > Copyright (C) 2003 R. D. Davis The difference between humans & other animals: > All Rights Reservedan unnatural belief that we're above Nature & > [EMAIL PROTECTED] 410-744-4900 her other creatures, using dogma to justify such > http://www.rddavis.org beliefs and to justify much human cruelty. > > > ___ > Lilypond-devel mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/lilypond-devel > ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond 2.0.1 built ok for FreeBSD 4.0 w/gcc 2.95.2
R. D. Davis([EMAIL PROTECTED])@2003.11.19 22:59:56 +: > Actually, I'm going to have to install it on partition other than > /usr, due to space limitations, so installing from ports may not be a > good idea for me anyway. It's always been my preference to intall I do the same followint way: e.g. you want gcc33 at /opt/compilers/gcc33 just use the PREFIX environment while building through the port - or use --prefix=xxx option of configure directly. Same applies to lilypond. > software from sources rather than ports or packages when possible, > since I get a better feel for the software and know what's what and > what's where... but then, perhaps that's just what I got used to > before ports and packages existed in the land of UNIX. :-) :) absolutely no objections here :) > I don't think that I had autotrace installed, so, that's probably > one thing that was causing a problem. As soon as I get ImageMagick > working (or reload the old version from the BSD 4.0 CD-ROM), I'll > install that (v0.31.1). :) thats the advantage of ports. > Ok, now there's a curiosity: two different version of kpathsea... I'll > have to investigate. have a look if you installed tex and teTex concurrently. that most probably won't work. > :-), I'll try the most recent stable version of the port, but will > need to apply the patches manually by running patch on the necessary > files. Thanks very much. -- regards, Patrick Atamaniuk ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
bug-lilypond-cygwin.sh patch
There was a bug in bug-lilypond-cygwin.sh. Here's the diff. Index: cygwin/bug-lilypond-cygwin.sh === RCS file: /cvsroot/lilypond/lilypond/cygwin/bug-lilypond-cygwin.sh,v retrieving revision 1.6 diff -u -r1.6 bug-lilypond-cygwin.sh --- cygwin/bug-lilypond-cygwin.sh 25 Sep 2003 18:26:17 - 1.6 +++ cygwin/bug-lilypond-cygwin.sh 23 Nov 2003 11:52:32 - @@ -22,8 +22,8 @@ [EMAIL PROTECTED]@/share/doc/[EMAIL PROTECTED]@-1 [ ! -d $docdir ] && [EMAIL PROTECTED]@/doc/[EMAIL PROTECTED]@-1 -[ ! -d $docdir ] && docdir=$(echo @prefix@/share/doc/lilypond-[.-0-9]*) -[ ! -d $docdir ] && docdir=$(echo @prefix@/doc/lilypond-[.-0-9]*) +[ ! -d $docdir ] && docdir=$(echo @prefix@/share/doc/lilypond-[.\-0-9]*) +[ ! -d $docdir ] && docdir=$(echo @prefix@/doc/lilypond-[.\-0-9]*) echo echo Availability of executables ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
