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 ki
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 rec
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-
On Sun, 08 Jan 2012 13:32:14 +0700
Michael Pozhidaev 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 not
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 MI
Michael Pozhidaev 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 dynami
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 com
- Original Message -
From: "Phil Hézaine"
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
__
Le 15/03/2011 13:12, Phil Holmes a écrit :
> - Original Message - From: "Phil Hézaine"
>
> To: "lilypond-user"
> Sent: Tuesday, March 15, 2011 12:02 PM
> Subject: The Gigsaw has a problem with midi output
>
>
>> Hi,
>>
>> Lily
- Original Message -
From: "Phil Hézaine"
To: "lilypond-user"
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
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 u
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
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 sof
[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
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"
\con
15 matches
Mail list logo
