On Fri, Apr 7, 2023 at 2:02 AM Dario Marrini
wrote:
> Hi lilypond people,
> I tried adding these :
>
> midiMinimumVolume = #0.05
> midiMaximumVolume = #0.95
>
> but I got no so different results;
>
Hmm, with the code below, I got very noticable results:
%%%
\version "2.24.1"
\score {
\new Vo
Hi lilypond people,
I tried adding these :
midiMinimumVolume = #0.05
midiMaximumVolume = #0.95
but I got no so different results; at this point, I should know how to set
a specific output volume to a specific dynamic signs; even because I don't
know default values
regards
Il giorno ven 7 apr 20
Hi lilypond people,
I'm trying to understand how all this works; there is a short code file as
attachment, with midi and pdf ones; I tried to use dynamics and other
signs, but the difference on sound between signed (with 'p' and others
signs) and not signed notes it's quite not hearable; I found i
Thanks Thomas. Your note fixed all.
I found the per-voice association casually, then I even googled "lilypond
dynamics per-voice" but could not find anything specific for 2.19: then,
without your suggestion, given that this default behaviour is not documented
and the official snippets use anoth
Am Mo., 18. Nov. 2019 um 17:00 Uhr schrieb Paolo Prete :
>
> Hello,
>
> Regarding my previous question,
Please link to it.
> I just checked that there's a bug on the dynamics of the produced midi output
> for a piano staff.
> The bug can be reproduced on the 2.19 version. Please, check this sni
It appears to happen because the 2.19 version seems to associate the MIDI
output per-voice instead of per-staff. As a (ugly) workaround I used this
(setting and soon after unsetting a voice):
LilyPond Score
|
|
| |
LilyPond Score
LilyPond Score made using LilyBin.
|
|
|
It works, bu
Hello,
Regarding my previous question, I just checked that there's a bug on the
dynamics of the produced midi output for a piano staff.The bug can be
reproduced on the 2.19 version. Please, check this snippet ( from
http://lsr.di.unimi.it/LSR/Item?id=357 ), with Lilybin
http://lilybin.com/eg70
Thank you for all your help on this. I now have an include file that
does more or less what I want, and of course I can tweak in further in
the future.
David
On Tue, 2019-07-16 at 15:11 +0200, Jean ABOU SAMRA wrote:
>
> \version "2.19.83"
\version "2.19.83"
%{ From
http://lilypond.org/doc/v2.19/Documentation/notation/controlling-midi-dynamics.fr.html
midiMinimumVolume + (midiMaximumVolume - midiMinimumVolume) * fraction
These are the volume coefficients ('fraction' above)
Hi Jean
That's great - I certainly now can get a greater range of dynamic than
before. Thank you very much.
But I find that altering values in 'my-instrument-equalizer-alist' has
no effect at all. How can I adjust the relative volumes of 2 different
instruments - say, 'violin' and 'cello'. (I
Hi David,
Your problem is not with the instrument, it's with the dynamics themselves.
The algorithm that affects a volume to a note does a scale between
midiMinimumVolume and midiMaximumVolume that includes all dynamics.
Mathematically, you can think:
volume = midiMinimumVolume + (midiMaximumVol
\version "2.19.82"
#(define my-instrument-equalizer-alist '())
#(set! my-instrument-equalizer-alist
(append
'(
("trumpet" . (0.01 . 0.99)))
my-instrument-equalizer-alist))
#(define (my-instrument-equalizer s)
(let ((entry
On Thu, Sep 20, 2018 at 05:06:48PM +0100, Peter Toye wrote:
>Guy,
>
>Thanks. I've found the thread. It seems fairly complicated, and as
>I only use MIDI for proof-reading (proof-hearing?) I’ll ignore the
>dynamics altogether! Life's too short.
My usual approach, as always, is to u
Guy,
Thanks. I've found the thread. It seems fairly complicated, and as I only use
MIDI for proof-reading (proof-hearing?) I’ll ignore the dynamics altogether!
Life's too short.
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Thursday, September 20, 2018,
Peter,
Do a search in the list archives. There was an extended discussion about
this very thing in the past month with multiple offered solutions.
Regards,
Guy
On Thu, Sep 20, 2018, 6:34 AM Peter Toye wrote:
> I want to have a Dynamics staff between the music staves on a PianoStaff,
> but thi
I want to have a Dynamics staff between the music staves on a PianoStaff, but
this doesn't change the dynamics on the MIDI output. Is there any way of
getting the MIDI output to use the \Dynamics? In the example below they all
have the same (presumably default) dynamic (at least, when played thr
On 04/02/18 05:19, Abraham Lee wrote:
Hi, Hilary!
On Sat, Feb 3, 2018 at 9:42 PM Hilary Snaden wrote:
I have been trying to get LilyPond to generate MIDI versions of some
piano music. The music script renders nicely, and there are no errors or
warnings, but the MIDI file plays with no dynamic
I'd suggest either moving the DynamicsPerformer to the Staff context or
replacing the \upper with << \upper \dynamics >> (and the same for \lower).
Normally, dynamics only affect the voice they are in, which in your example is
a different voice from the ones the notes are in.
On 02/04/18 01:55,
Hi, Hilary!
On Sat, Feb 3, 2018 at 9:42 PM Hilary Snaden wrote:
> I have been trying to get LilyPond to generate MIDI versions of some
> piano music. The music script renders nicely, and there are no errors or
> warnings, but the MIDI file plays with no dynamics at all. What am I
> doing wrong?
I have been trying to get LilyPond to generate MIDI versions of some
piano music. The music script renders nicely, and there are no errors or
warnings, but the MIDI file plays with no dynamics at all. What am I
doing wrong? (LilyPond 2.18.2.)
\score {
\unfoldRepeats
\new Staff
<<
{ \
Dominicus writes:
> Flaming Hakama by Elaine wrote
>>> I'm dealing with several of these MIDI errors during compilation of a
>>> long
>>> piece.
>>> "programming error: Impossible or ambiguous (de)crescendo in MIDI."
>>>
>>> I tried to get rid of these by placing a starting volume, but alas, it's
#x27;ve spent hours searching for a hairpin in the haystack (pun intended)
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/MIDI-dynamics-parsing-error-tp162479p195255.html
Sent from the User mailing list archive at Nabble.com.
___
nd
> > fixes in 2.19), and recently I noticed that midi dynamics in my
> > piano scores aren't being rendered correctly anymore. Looking into
> > the commit log, I saw this:
> >
> > Issue 4947: Link notes to dynamics in Dynamic_performer rather
&g
Hi,
On Fri, 2016-08-19 at 10:16 -0700, H. S. Teoh wrote:
> I've been using lilypond from git HEAD (mainly because lilypond in my
> distro is too old, still stuck at 2.18, and I need features and fixes
> in 2.19), and recently I noticed that midi dynamics in my piano
> scores aren
I've been using lilypond from git HEAD (mainly because lilypond in my
distro is too old, still stuck at 2.18, and I need features and fixes in
2.19), and recently I noticed that midi dynamics in my piano scores
aren't being rendered correctly anymore. Looking into the commit log,
Hello Knute,
perhaps its just an unusual topic few have experience with?
At least I don’t; yet after a look in the NR section on the topic I
think you’re on the right path with the cond approach. After all, you
want to define a single function to pass it on as
dynamicAbsoluteVolumeFunction. An
I'm wondering why I have gotten no responses. Did I frame the question
poorly? Did it get to the list?
Knute Snortum
(via Gmail)
On Mon, Sep 8, 2014 at 9:48 AM, Knute Snortum wrote:
> I know how to set a single custom dynamic:
>
> #(define (myDynamics dynamic)
>(if (equal? dynamic pTresD
I know how to set a single custom dynamic:
#(define (myDynamics dynamic)
(if (equal? dynamic pTresDouxMarkup )
0.55
(default-dynamic-absolute-volume dynamic
..but do I set two or more dynamics like this:
#(define (myDynamics dynamic)
(cond (equal? dynamic pTresDouxMa
On Tue, 2014-05-20 at 06:41 -0700, Knute Snortum wrote:
> (Note: the above code still emits a warning: Programming error:
> impossible or ambiguous (de) crescendo)
That's true - sorry, I was really commenting only on the "unspecified
starting volume" warning.
> One of the things I really liked ab
Am 20.05.2014 15:41, schrieb Knute Snortum:
(Note: the above code still emits a warning: Programming error:
impossible or ambiguous (de) crescendo)
One of the things I really liked about LilyPond was the ability to
compile sheet music and MIDI from the same source. It seems to me that
this b
(Note: the above code still emits a warning: Programming error: impossible
or ambiguous (de) crescendo)
One of the things I really liked about LilyPond was the ability to compile
sheet music and MIDI from the same source. It seems to me that this
behavior is getting away from that value. I would
On Sun, 2014-05-18 at 10:40 -0700, Paul Morris wrote:
> Conor Cook wrote
> > It is my impression that a decrescendo starts where you are and gets
> > quieter. Does Lilypond not have a default (e.g. mf) MIDI dynamic like
> > Sibelius?
>
> Good point. Wouldn't it make sense to just use a default v
Thomas Morley writes:
> Sorry if I was not clear enough.
> I was looking for a method to circumvent the midi-error, but keep the
> visual output.
>
> Let me be a bit more verbose:
>
> The following gives nice visual output, though triggers an error with midi:
>
> { c'1\> c' c'\! }
>
> Inserting
> Date: Sun, 18 May 2014 12:28:22 +0200
> > From: David Kastrup
> > To: Thomas Morley
> > Subject: Re: MIDI dynamics parsing error
> >
> >
> > If \omit is too strong and \hide leaves too much space, maybe overriding
> > the stencil with point-stencil
e score with a dynamics mark, rather than
issuing this warning?
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/MIDI-dynamics-parsing-error-tp162479p162563.html
Sent from the User mailing list archive at Nabble.com.
___
2014-05-18 16:18 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> 2014-05-18 12:28 GMT+02:00 David Kastrup :
>>> Thomas Morley writes:
>>>
2014-05-18 7:20 GMT+02:00 David Kastrup :
> Knute Snortum writes:
>
>> My situation is I need to transcribe a crescendo starting witho
Patrick or Cynthia Karl writes:
> On May 18, 2014, at 12:28:22 +0200, David Kastrup wrote:
>
>> Message: 1
>> Date: Sun, 18 May 2014 12:28:22 +0200
>> From: David Kastrup
>> To: Thomas Morley
>> Subject: Re: MIDI dynamics parsing error
>>
>>
Am 18.05.2014 16:33, schrieb Patrick or Cynthia Karl:
On May 18, 2014, at 12:28:22 +0200, David Kastrup wrote:
Message: 1
Date: Sun, 18 May 2014 12:28:22 +0200
From: David Kastrup
To: Thomas Morley
Subject: Re: MIDI dynamics parsing error
If \omit is too strong and \hide leaves too much
On May 18, 2014, at 12:28:22 +0200, David Kastrup wrote:
> Message: 1
> Date: Sun, 18 May 2014 12:28:22 +0200
> From: David Kastrup
> To: Thomas Morley
> Subject: Re: MIDI dynamics parsing error
>
>
> If \omit is too strong and \hide leaves too much space, maybe overr
Thomas Morley writes:
> 2014-05-18 12:28 GMT+02:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> 2014-05-18 7:20 GMT+02:00 David Kastrup :
Knute Snortum writes:
> My situation is I need to transcribe a crescendo starting without a
> dynamic
> marking. If I put in a \mf
2014-05-18 12:28 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> 2014-05-18 7:20 GMT+02:00 David Kastrup :
>>> Knute Snortum writes:
>>>
My situation is I need to transcribe a crescendo starting without a dynamic
marking. If I put in a \mf then I don't get warning. If I can hid
t; manuals:
>
> http://lilypond.org/doc/v2.18/Documentation/notation/visibility-of-objects#index-_005chide
>
> HTH,
> -Paul
>
>
>
> --
> View this message in context:
> http://lilypond.1069038.n5.nabble.com/MIDI-dynamics-parsing-error-tp162479p162523.html
> Sent from the
Thomas Morley writes:
> 2014-05-18 7:20 GMT+02:00 David Kastrup :
>> Knute Snortum writes:
>>
>>> My situation is I need to transcribe a crescendo starting without a dynamic
>>> marking. If I put in a \mf then I don't get warning. If I can hide the
>>> dynamic mark, all will be fine. Is there
2014-05-18 7:20 GMT+02:00 David Kastrup :
> Knute Snortum writes:
>
>> My situation is I need to transcribe a crescendo starting without a dynamic
>> marking. If I put in a \mf then I don't get warning. If I can hide the
>> dynamic mark, all will be fine. Is there a \hide syntax that will work?
Knute Snortum writes:
> My situation is I need to transcribe a crescendo starting without a dynamic
> marking. If I put in a \mf then I don't get warning. If I can hide the
> dynamic mark, all will be fine. Is there a \hide syntax that will work?
Anything wrong with
\version "2.18.0"
\score
time to figure out the cause, so thanks for that!
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/MIDI-dynamics-parsing-error-tp162479p162524.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mail
\once \omit DynamicText c-\mf
There's also \hide, but I think you want \omit, more on these in the
manuals:
http://lilypond.org/doc/v2.18/Documentation/notation/visibility-of-objects#index-_005chide
HTH,
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble
On 05/17/2014 07:15 PM, Knute Snortum wrote:
My situation is I need to transcribe a crescendo starting without a
dynamic marking. If I put in a \mf then I don't get warning. If I
can hide the dynamic mark, all will be fine. Is there a \hide syntax
that will work?
Knute Snortum
(via Gmail)
ountered this problem in a composition of my own and just
> ignored the warning, because the MIDI dynamics rendition did not have any
> importance for me.
> As a matter of fact, this notation may seem illogical, but there are many
> occurences of it, and many have asked what it means. I
y own and just
> ignored the warning, because the MIDI dynamics rendition did not have any
> importance for me.
> As a matter of fact, this notation may seem illogical, but there are many
> occurences of it, and many have asked what it means. I find it pretty
> straightforward, once
I recently encountered this problem in a composition of my own and just
ignored the warning, because the MIDI dynamics rendition did not have
any importance for me.
As a matter of fact, this notation may seem illogical, but there are
many occurences of it, and many have asked what it means. I
Well, LilyPond has the same problem as a performer would. If you're
crescendoing, at what dynamic are you starting from?
--
Phil Holmes
- Original Message -
From: Knute Snortum
To: lilypond-user@gnu.org
Sent: Friday, May 16, 2014 3:21 PM
Subject: MIDI dynamics pa
Short Description: I get an error from LilyPond that it can't figure out
the MIDI volume to start a crescendo with in some situations.
Details: The error message is...
(De)crescendo with unspecified starting volume in MIDI.
{ bf4 %{ \mf %}
\< a16 ( \sf gf' f ef ) bf4 %{ \
Am 28.01.2012 17:51, schrieb Christopher R. Maden:
I almost always end up with separate scores for layout and MIDI.
dynamics = { s4\f\> s4*3\! s4\p s4 }
right = \relative c'' { c d e f g a }
left = \relative c' { c d e f g a }
\score {
\new PianoStaff<<
On 01/28/2012 07:45 AM, Helge Kruse wrote:
> In this example the dynamics in the down staff is necessary for MIDI
> but no wanted for the layout.
I almost always end up with separate scores for layout and MIDI.
dynamics = { s4\f\> s4*3\! s4\p s4 }
right = \relative c'' {
Am 28.01.2012 13:45, schrieb Helge Kruse:
Hello,
I want to generate a MIDI file with the correct dynamics. Although it
is possible to have different dynamics in left and tight hand I want
to have the upper staff the same volume as the lower staff. Therefore
I want only to write the dynamics t
Hello,
I want to generate a MIDI file with the correct dynamics. Although it is
possible to have different dynamics in left and tight hand I want to
have the upper staff the same volume as the lower staff. Therefore I
want only to write the dynamics to the upper staff. How can I apply the
sam
> > Yes, it would be very convenient if make-dynamic-script was
> > extended so you also could specify the MIDI interpretation of the
> > new dynamics mark.
>
> Section 3.5.5 "Controlling MIDI dynamics" in the 2.11 docs shows two
> methods for controlling the
imply adjust the MIDI volume manually. However, this
is much more tricky than expected, since LilyPond apparently doesn't
provide a simple means to do that.
Yes, it would be very convenient if make-dynamic-script was extended
so you also could specify the MIDI interpretation of the new dynamic
Hi Mats,
p.s. Mats: is there any way to avoid having the \dynX tweak?
Unfortunately, I've never found a way to code the alignment within
the dynamic script itself…
One alternative is "Solution 6" in the snippet "Horizontally
aligning ..." at http://lilypond.org/doc/v2.11/input/lsr/lilypond
Kieren MacMillan wrote:
p.s. Mats: is there any way to avoid having the \dynX tweak?
Unfortunately, I've never found a way to code the alignment within the
dynamic script itself…
One alternative is "Solution 6" in the snippet "Horizontally aligning
..." at
http://lilypond.org/doc/v2.11/inpu
Hi Werner,
It *is*, since it is one (abbreviated) phrase: `piano espressivo' --
this is not the same as tagging the note with `piano', adding
`espressivo' somewhere else, say, on the top.
I apologise if I've misinterpreted your response, but it seems like
you don't get what Mats is saying…
> >> > if I need a `p espr.' mark, it's probably best (from a
> >> > typographical point of view) to write
> >> >
> >> > c\markup { \dynamic "p" \italic " espr." }
> >>
> >> No, this is not the best solution from a typographical point of
> >> view.
> >
> > It *is*, since it is one (abbreviated) ph
Quoting Werner LEMBERG <[EMAIL PROTECTED]>:
> if I need a `p espr.' mark, it's probably best (from a typographical
> point of view) to write
>
> c\markup { \dynamic "p" \italic " espr." }
No, this is not the best solution from a typographical point of
view.
It *is*, since it is one (abbrevia
> > if I need a `p espr.' mark, it's probably best (from a typographical
> > point of view) to write
> >
> > c\markup { \dynamic "p" \italic " espr." }
>
> No, this is not the best solution from a typographical point of
> view.
It *is*, since it is one (abbreviated) phrase: `piano espressivo' --
Quoting Werner LEMBERG <[EMAIL PROTECTED]>:
Folks,
if I need a `p espr.' mark, it's probably best (from a typographical
point of view) to write
c\markup { \dynamic "p" \italic " espr." }
No, this is not the best solution from a typographical point of view.
If you for example have a hairpi
Folks,
if I need a `p espr.' mark, it's probably best (from a typographical
point of view) to write
c\markup { \dynamic "p" \italic " espr." }
to correctly align the horizontal and vertical distance of the `espr.'
string with the `p' dynamic sign. However, this has the disadvantage
that the
The silent notes will sound properly if you terminate the (de)crescendi
with \! before the next dynamic mark... as in
\relative c'' {
c16\p c c c c\< d e f g\!\f g g g g\> f e d c\!\p c c c c4
}
Magnus
Anders Kaseorg wrote:
If I run the following simple test of dynamics through lilypond
Anders Kaseorg wrote:
> If I run the following simple test of dynamics through lilypond (I've
> tried both 2.6.3 and 2.7.22):
>
> \version "2.6.0"
> \score {
> \relative c'' {
> c16\p c c c c\< d e f g\f g g g g\> f e d c\p c c c c4
> }
> \midi {}
> \layout {}
> }
>
> and play the res
\Voice
\remove "Dynamic_performer"
\remove "Span_dynamic_performer"
}
Linda
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Anders Kaseorg
Sent: Monday, December 12, 2005 11:18 PM
To: lilypond-user@gnu.org
Subject:
If I run the following simple test of dynamics through lilypond (I've
tried both 2.6.3 and 2.7.22):
\version "2.6.0"
\score {
\relative c'' {
c16\p c c c c\< d e f g\f g g g g\> f e d c\p c c c c4
}
\midi {}
\layout {}
}
and play the resulting MIDI file with timidity, all but eight
On Saturday 22 May 2004 01:05 am, J. Garcia wrote:
> Is there now any way to remove all dynamics from a
> MIDI file? The
> \translator { \remove "Dynamic_performer" }
> trick doesn't seem to work anymore. I know this
> question has been posted before, but didn't receive
> any response.
Sounds l
"J. Garcia" <[EMAIL PROTECTED]> writes:
> Is there now any way to remove all dynamics from a
> MIDI file? The
> \translator { \remove "Dynamic_performer" }
> trick doesn't seem to work anymore. I know this
> question has been posted before, but didn't receive
> any response.
\midi {
Is there now any way to remove all dynamics from a
MIDI file? The
\translator { \remove "Dynamic_performer" }
trick doesn't seem to work anymore. I know this
question has been posted before, but didn't receive
any response.
-J. Garcia
74 matches
Mail list logo
