problem with midi
hi everybody i don't understand how to fix the error : (De)crescendo with unspecified starting volume in MIDI someone can help me? thanx fabio ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with midi
Il 28/08/2012 16:15, fabio gabbianelli ha scritto: hi everybody i don't understand how to fix the error : (De)crescendo with unspecified starting volume in MIDI someone can help me? Not me, I never use (de)crescendo. I can just say, as a translator, that this message has been added recently. Try reading here: http://lilypond.org/doc/v2.16/Documentation/notation/controlling-midi-dynamics If you have problems, please write a minimal example. -- Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with midi
Please reply to the list (or to all recipients): you'll probably have a
good answer from someone else (than me) in this mailing list.
Your example is messed up and can't compile. Save it in a .ly file and
attach it to the email.
Anyway, I think you are using the wrong command.
Dynamic is a kind of markup style:
http://lilypond.org/doc/v2.16/Documentation/notation/font#index-_005cdynamic-3
The dynamic commands are explained here:
http://lilypond.org/doc/v2.16/Documentation/notation/expressive-marks-attached-to-notes#dynamics
Save this link in your bookmarks:
http://lilypond.org/doc/v2.16/Documentation/notation/lilypond-index
and use it to search key terms
Il 28/08/2012 16:39, fabio gabbianelli ha scritto:
i try reading there yet but nothing. the error report is this:
(De)crescendo with unspecified starting volume in MIDI.
{\dynamic p \italic armonioso}}(g cis e a4.
\\arpeggio
i used \dynamic p, not (de)crescendo
Il giorno 28/ago/2012, alle ore 16.37, Federico Bruni ha scritto:
Il 28/08/2012 16:15, fabio gabbianelli ha scritto:
hi everybody i don't understand how to fix the error : (De)crescendo with
unspecified starting volume in MIDI
someone can help me?
Not me, I never use (de)crescendo.
I can just say, as a translator, that this message has been added recently.
Try reading here:
http://lilypond.org/doc/v2.16/Documentation/notation/controlling-midi-dynamics
If you have problems, please write a minimal example.
--
Federico
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Federico
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: The problem with midi command delay in 2.14.2
On Sun, 08 Jan 2012 13:32:14 +0700 Michael Pozhidaev m...@altlinux.ru wrote: Yes, it's almost sad. Although I don't know is it really convenient way to write additional separate dynamics marks. maybe it is not so bad idea to have one more entire file for midi only, where dynamics are written among all notes. Maybe you don't need a file, but you may want a separate Dynamics object or two. I tried making nice sounding Lilypond files recently. My approach is to have a separate Dynamics object with hidden dynamics text. I can put Dynamics marks before the place where they appear in the score. Here's the latest example: http://sp.red-bean.com/proski/lilypond/Ich_will_meine_Seele_tauchen/seele.ly If you put Dynamics objects above voices in the midi section, they affect the first note. If you put them below voices, the first note is too loud. I believe Lilypond should be able to generate much better MIDI files with less tweaks. The infrastructure is there. We can specify how every note looks, so we should be able to specify how every note sounds. -- Regards, Pavel Roskin ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
The problem with midi command delay in 2.14.2
Hi!
After the migration from 2.12.2 up to 2.14.2 I have faced interesting
problem and cannot decide is it a wrong behaviour or everything is OK
and now there is another approach to write separate midi dynamics. In
the snippet below there are four notes. When I generate the midi file
the \p command is applied only to second note when it should to the
first one as it was in 2.12.2. Please, help me, do I write something
wrong?
In midi output and generated with timidity wave file the volume of first
note and second is significantly different. What can cause this problem?
Here is the lilypond snippet and links to the files I've got
after compilation.
Thanks!
\version 2.14.2
One = {
c'4 d'4 e'4 f'4
}
OneMidi = {
s4 \p s4 s4 s4
}
\score {
\new Staff
{\One}
{\OneMidi}
\midi { }
}
ftp://devel.altlinux.org/msp/tmp/problem.midi
ftp://devel.altlinux.org/msp/tmp/problem.wav
ftp://devel.altlinux.org/msp/tmp/problem.ly
--
Michael Pozhidaev. Tomsk, Russia.
Russian info page: http://www.marigostra.ru/
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: The problem with midi command delay in 2.14.2
Michael Pozhidaev msp at altlinux.ru writes:
After the migration from 2.12.2 up to 2.14.2 I have faced interesting
problem and cannot decide is it a wrong behaviour or everything is OK
and now there is another approach to write separate midi dynamics.
I don't know any better way to enter dynamics. I use
\midi { context {\Voice \remove Dynamic_performer }}
so that the dynamics errors don't bother me.
We have it listed as a bug, that first appeared in 2.14, but did not seem
serious enough (compared with the other MIDI bugs) to stop releasing 2.14.
http://code.google.com/p/lilypond/issues/detail?id=1661
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: The problem with midi command delay in 2.14.2
Hello, Keith!
I don't know any better way to enter dynamics. I use
\midi { context {\Voice \remove Dynamic_performer }}
so that the dynamics errors don't bother me.
We have it listed as a bug, that first appeared in 2.14, but did not seem
serious enough (compared with the other MIDI bugs) to stop releasing
2.14.
Yes, it's almost sad. Although I don't know is it really convenient way
to write additional separate dynamics marks. maybe it is not so bad idea
to have one more entire file for midi only, where dynamics are written among
all notes.
Thanks for information!
--
Michael Pozhidaev. Tomsk, Russia.
Russian info page: http://www.marigostra.ru/
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
The Gigsaw has a problem with midi output
Hi, Lilypond version 2.13.51. Could somebody confirms the Lily's midi output has changed. When i read an ascii file of the midi output I see a note Off no longer exists. It is replaced by a note On with vol=0. I can read it from midicomp. Is there a reason why this output is changed? Or is it an unwanted effect of the development version? Thanks in advance. Phil. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: The Gigsaw has a problem with midi output
- Original Message - From: Phil Hézaine philippe.heza...@free.fr To: lilypond-user lilypond-user@gnu.org Sent: Tuesday, March 15, 2011 12:02 PM Subject: The Gigsaw has a problem with midi output Hi, Lilypond version 2.13.51. Could somebody confirms the Lily's midi output has changed. When i read an ascii file of the midi output I see a note Off no longer exists. It is replaced by a note On with vol=0. I can read it from midicomp. Is there a reason why this output is changed? Or is it an unwanted effect of the development version? Thanks in advance. Phil. There's a lot of changes going on in midi output at present. If you depend on it, I'd suggest sticking with an older version for now. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: The Gigsaw has a problem with midi output
Le 15/03/2011 13:12, Phil Holmes a écrit : - Original Message - From: Phil Hézaine philippe.heza...@free.fr To: lilypond-user lilypond-user@gnu.org Sent: Tuesday, March 15, 2011 12:02 PM Subject: The Gigsaw has a problem with midi output Hi, Lilypond version 2.13.51. Could somebody confirms the Lily's midi output has changed. When i read an ascii file of the midi output I see a note Off no longer exists. It is replaced by a note On with vol=0. I can read it from midicomp. Is there a reason why this output is changed? Or is it an unwanted effect of the development version? Thanks in advance. Phil. There's a lot of changes going on in midi output at present. If you depend on it, I'd suggest sticking with an older version for now. -- Phil Holmes Thanks for the quick answer. Is there a list of the changes I could read. I'll like to go on to do something about my little app. Phil. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: The Gigsaw has a problem with midi output
- Original Message - From: Phil Hézaine philippe.heza...@free.fr Thanks for the quick answer. Is there a list of the changes I could read. I'll like to go on to do something about my little app. Phil. There's been considerable discussion on the .devel mailing list. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
problem with midi file export
XP Pro lily 2.8x (1 or 4) but doesn't seem to matter the midi files from 2.6x have the same problem Before switching to a new machine and xp-pro I had to change the extension on the midi files to mid *after* they were produced. But once I did that I could import it/play it via the various software that I have. That is no longer the case when I try to play a midi file produced by lily now I get The specidfied file cannot be played on the specified MCI device. the file may be corrupt, not in the correct format, or no fil Which I have no idea what that means exactly or how to fix it. I haven't figured out a way to change the file extension in XP=pro either and changing it in the lily file didn't work. Jay Jay Hamilton www.soundand.com 206-328-7694 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with midi file export
Jay Hamilton wrote: XP Pro lily 2.8x (1 or 4) but doesn't seem to matter the midi files from 2.6x have the same problem Before switching to a new machine and xp-pro I had to change the extension on the midi files to mid *after* they were produced. But once I did that I could import it/play it via the various software that I have. That is no longer the case when I try to play a midi file produced by lily now I get The specidfied file cannot be played on the specified MCI device. the file may be corrupt, not in the correct format, or no fil Which I have no idea what that means exactly or how to fix it. I haven't figured out a way to change the file extension in XP=pro either and changing it in the lily file didn't work. Thanks for bringing this up. I haven't used midi very much but I have just found this problem and didn't know what to do either. Paul Scott ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
problem in midi file
I have a problem with midi generated files.
After a tie, notes at the same pitch than the tie are shifted to the
left in the midi file.
\paper {
linewidth = 160 \mm
}
\renameinput miditest.ly
\version 2.1.32
\header {
}
\score {
\notes\relative c'' {
\time 4/4
c1 ~ c4 b c d
}
\paper{ raggedright = ##t }
\midi { \tempo 4 = 110 }
}
in the resulting midi file, the last c is shifted to the left :
@+,
Pascal Legris
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Problem with MIDI generation with 2.1.18
[EMAIL PROTECTED] writes:
Hi !
I upgraded to cygwin 2.1.18 yesterday, and experienced two problems:
- \autochange does not seem to work as well as it used to be.
I guess I did something wrong. Here is my PianoStaff:
solo = \context PianoStaff = solo
\property Staff.midiInstrument=vibraphone
\context Staff=up {
\property Staff.midiInstrument=vibraphone
\context Voice=foo{
\notes { \time 4/4 \key b \minor }
\voiceOne
\HighSoloNotes
}
}
\context Staff=down {
\property Staff.midiInstrument=vibraphone
\notes { \time 4/4 \key b \minor }
\clef bass
\autochange \context Voice = bar {\LowSoloNotes}
}
Can you send me a example that I can try for myself?
- MIDI file generation crashes with a stack trace (the log is given below)
I tried to simplify a number of things, assuming that this might be due
to excessively complex data structure, but it did not help.
fixed.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Problem with MIDI generation with 2.1.18
Hi !
I upgraded to cygwin 2.1.18 yesterday, and experienced two problems:
- \autochange does not seem to work as well as it used to be.
I guess I did something wrong. Here is my PianoStaff:
solo = \context PianoStaff = solo
\property Staff.midiInstrument=vibraphone
\context Staff=up {
\property Staff.midiInstrument=vibraphone
\context Voice=foo{
\notes { \time 4/4 \key b \minor }
\voiceOne
\HighSoloNotes
}
}
\context Staff=down {
\property Staff.midiInstrument=vibraphone
\notes { \time 4/4 \key b \minor }
\clef bass
\autochange \context Voice = bar {\LowSoloNotes}
}
- MIDI file generation crashes with a stack trace (the log is given below)
I tried to simplify a number of things, assuming that this might be due
to excessively complex data structure, but it did not help.
This raises a related question about Lilypond's internals:
when are variables expanded ? when I write:
a = \notes {a b c d e f }
b = \notes { \a \a \a }
are the a's in b expanded when declaring b, or when actually using b ?
Cheers,
Darius/.
lilypond (GNU LilyPond) 2.1.18
Opening pipe `/usr/bin/lilypond-bin --version '
Opening pipe `kpsexpand \$TEXMF'
Opening pipe `kpsewhich -expand-path=\$T1FONTS'
Invoking `/usr/bin/lilypond-bin -I /cygdrive/z/concerto -I /cygdrive/z/concerto
-I /cygdrive/z/concerto --no-paper --verbose Ostinato'
lilypond_datadir: `/usr/share/lilypond'
local_lilypond_datadir: `/usr/share/lilypond/2.1.18'
localedir: `/usr/share/locale'
LILYPONDPREFIX: `'
[/usr/share/lilypond/2.1.18/scm/define-music-types.scm][/usr/share/lilypond/2.1.
18/scm/output-lib.scm][/usr/share/lilypond/2.1.18/scm/c++.scm]
[/usr/share/lilypond/2.1.18/scm/chord-ignatzek-names.scm][/usr/share/lilypond/2.
1.18/scm/chord-entry.scm][/usr/share/lilypond/2.1.18/scm/chord-generic-names.
scm][/usr/share/lilypond/2.1.18/scm/molecule.scm][/usr/share/lilypond/2.1.
18/scm/new-markup.scm][/usr/share/lilypond/2.1.18/scm/bass-figure.scm]
[/usr/share/lilypond/2.1.18/scm/music-functions.scm][/usr/share/lilypond/2.1.
18/scm/part-combiner.scm][/usr/share/lilypond/2.1.
18/scm/define-music-properties.scm][/usr/share/lilypond/2.1.18/scm/auto-beam.
scm][/usr/share/lilypond/2.1.18/scm/chord-name.scm][/usr/share/lilypond/2.1.
18/scm/define-translator-properties.scm][/usr/share/lilypond/2.1.
18/scm/translation-functions.scm][/usr/share/lilypond/2.1.18/scm/script.scm]
[/usr/share/lilypond/2.1.18/scm/drums.scm][/usr/share/lilypond/2.1.18/scm/midi.
scm][/usr/share/lilypond/2.1.18/scm/beam.scm][/usr/share/lilypond/2.1.
18/scm/clef
Now processing: `Ostinato.ly'
Parsing...[/usr/share/lilypond/2.1.18/ly/init.ly[/usr/share/lilypond/2.1.
18/ly/declarations-init.ly[/usr/share/lilypond/2.1.18/ly/nederlands.ly]
[/usr/share/lilypond/2.1.18/ly/chord-modifiers-init.ly][/usr/share/lilypond/2.1.
18/ly/script-init.ly][/usr/share/lilypond/2.1.18/ly/scale-definitions-init.ly]
[/usr/share/lilypond/2.1.18/ly/grace-init.ly][/usr/share/lilypond/2.1.
18/ly/midi-init.ly[/usr/share/lilypond/2.1.18/ly/performer-init.ly]]
[/usr/share/lilypond/2.1.18/ly/engraver-init.ly][/usr/share/lilypond/2.1.
18/ly/dynamic-scripts-init.ly][/usr/share/lilypond/2.1.18/ly/spanners-init.ly]
[/usr/share/lilypond/2.1.18/ly/property-init.ly]][/cygdrive/z/concerto/Ostinato.
ly[/usr/share/lilypond/2.1.18/fonts/afm/feta20.afm][/usr/share/lilypond/2.1.
18/fonts/tfm/feta20.tfm]Interpreting music...elapsed time: 0.42 seconds.scm]
[/usr/share/lilypond/2.1.18/scm/slur.scm][/usr/share/lilypond/2.1.18/scm/font.
scm][/usr/share/lilypond/2.1.18/scm/define-grob-properties.scm]
[/usr/share/lilypond/2.1.18/scm/define-grobs.scm][/usr/share/lilypond/2.1.
18/scm/define-grob-interfaces.scm][/usr/share/lilypond/2.1.18/scm/paper.scm]
Backtrace:
In /usr/share/lilypond/2.1.18/scm/part-combiner.scm:
568: 981* [generate-split-list ((# #) (# #) (# #) (# #) ...)]
553: 982 (if (null? event-list) (quote ()) ...)
...
567: 983 [cons (#Mom 271/2 . -1) ...
568: 984* [generate-split-list ((# #) (# #) (# #) (# #) ...)]
553: 985 (if (null? event-list) (quote ()) ...)
...
567: 986 [cons (#Mom 136 . 1) ...
568: 987* [generate-split-list ((# #) (# #) (# #) (# #) ...)]
553: 988(if (null? event-list) (quote ()) ...)
...
567: 989[cons (#Mom 545/4 . 1) ...
568: 990*[generate-split-list ((# #) (# #) (# #) (# #) ...)]
553: 991 (if (null? event-list) (quote ()) ...)
555: 992 (let* (# # # #) (if # # #))
558: 993*[filter #procedure #f (x) (#Music NoteEvent)]
In /usr/share/guile/1.6/srfi/srfi-1.scm:
743: 994 (letrec ((filiter (lambda # #))) (filiter pred list (quote (
...
746: 995 [filiter #procedure #f (x) () ...
747: 996* (cond ((pred (car rest)) (cons (car rest) result)) (#t result))
747: 997* [#procedure #f (x) #Music NoteEvent]
In
problem getting MIDI output from lilypond
Hi,
I'm a new convert to lilypond and have been very pleased with the output
it produces as well as the ease of input. I have a question about
generating MIDI output.
I have included the following in my .ly file
\midi {
\tempo 4=100
}
and have typed
lilypond -m trousers.ly
(where I have chosen -m to suppress the .tex output)
but I get no messages talking about MIDI and no .midi files are created.
Have I typed something wrong, or do I need additional software to use MIDI
with lilypond?
Thanks in advance,
Colin Cotter
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
