Re: Function for note string to fraction?
Thanks a lot! On 2014-05-20 00:49, Mark Polesky wrote: Peter Bjuhr wrote: And from there it would be easy to get the moment with 'ly:duration->string'. I don't think you need ly:duration->string; I think you can just skip that step. Yes, that was indeed a rambling. I meant I could get the moment with 'ly:duration-length'. And as far as I know, you do need to copy out the definition of parse-simple-duration, and above it add: #(use-modules (ice-9 regex)) Hope that helps. - Mark It works great! Best Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Function for note string to fraction?
Thanks a lot! On 2014-05-20 00:50, Thomas Morley wrote: Is it possible to include and use >'parse-simple-duration' in a local script (without copy and pasting it)? Well, I would have no problem to c/p 'parse-simple-duration', though yes, it is possible: #(define (note-to-moment notestr) (let ((parsed ((@@ (lily) parse-simple-duration ) notestr))) (ly:duration-length (ly:make-duration (car parsed) (cadr parsed) #(write (note-to-moment "4.")) --> # Though, quoting guile-manual: — syntax: @@ module-name binding-name Refer to the binding named binding-name in module module-name. The binding must not have been exported by the module. This syntax is only intended for debugging purposes or as a last resort. !! Cheers, Harm Part of the problem with copy and pasting was that it didn't work. I got the final piece of the puzzle though by Mark. I would still prefer this solution, but what you're saying is that it isn't really suitable to use this kind of syntax and that it is better to copy-and-paste!? Best Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [bug?] Unnecessary avoid-slur warning
See also http://code.google.com/p/lilypond/issues/detail?id=3729 – it’s
the same, only that it’s about accidentalSuggestion, not about
trillPitchAccidental. Perhaps you add a comment there?
Best, Simon
Am 20.05.2014 05:44, schrieb James Harkins:
It appears that LilyPond 2.18.2 prints a warning if a trill pitch
occurs under a slur, regardless of the chance of collision.
\relative c' {
% OK
\pitchedTrill d2\startTrillSpan ~ e d4. r8\stopTrillSpan
% warning: Ignoring grob for slur: TrillPitchAccidental. avoid-slur
not set?
% But the slur is nowhere near colliding with the trill pitch accidental!
c4 ( \pitchedTrill d4\startTrillSpan e ~ d4. ) r8\stopTrillSpan
}
This fixes it:
\override TrillPitchAccidental.avoid-slur = #'inside
But shouldn't this be a default? When would you seriously want a trill
pitch accidental to be outside the slur? Not to mention that it would
make no sense to put the trill pitch accidental outside, and the trill
pitch head inside.
Small issue, work-around-able, but seems a bit untidy.
hjh
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Function for note string to fraction?
Mark Polesky writes:
> Then you would use it like this:
>
> \set Timing.baseMoment = #(note-to-moment "4.")
Anything wrong with
{
\set Timing.baseMoment = #(ly:duration-length #{ 4. #})
\unset Timing.beamExceptions
c8 c8 c8 c8 c8 c8 c8 c8
}
here? Ok, you need 2.19 for it, but it seems like one of the cheaper
ways to ask the parser for input.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Function for note string to fraction?
On 2014-05-20 10:26, David Kastrup wrote:
Mark Polesky writes:
Then you would use it like this:
\set Timing.baseMoment = #(note-to-moment "4.")
Anything wrong with
\set Timing.baseMoment = #(ly:duration-length #{ 4. #})
Ok, you need 2.19 for it, but it seems like one of the cheaper
ways to ask the parser for input.
Thanks, indeed it is cheaper. But I'm not sure if I can use it. This is
part of a larger whole. Basically the user is intended to input a string
with the duration, and the string will be used both for
\set Timing.baseMoment
and for markup via
\note
I'll present the script shortly...
Best
Peter
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Function for note string to fraction?
Peter Bjuhr writes:
> On 2014-05-20 10:26, David Kastrup wrote:
>> Mark Polesky writes:
>>
>>> Then you would use it like this:
>>>
>>> \set Timing.baseMoment = #(note-to-moment "4.")
>> Anything wrong with
>>
>> \set Timing.baseMoment = #(ly:duration-length #{ 4. #})
>>
>>
>> Ok, you need 2.19 for it, but it seems like one of the cheaper
>> ways to ask the parser for input.
>>
>
> Thanks, indeed it is cheaper. But I'm not sure if I can use it. This
> is part of a larger whole. Basically the user is intended to input a
> string with the duration, and the string will be used both for
>
> \set Timing.baseMoment
>
> and for markup via
>
> \note
We probably should let \note accept a duration, but it's not actually
hard to pick apart and use \note-by-number on the parts.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Temporary disable \RemoveEmptyStaffContext for individual staffs
Yes, it seems to adress the same question. However, I don't know how to apply the answer to my SATB setup where every staff line has about the same properties. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Temporary-disable-RemoveEmptyStaffContext-for-individual-staffs-tp162585p162598.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Function for note string to fraction?
On 2014-05-20 12:02, David Kastrup wrote: Thanks, indeed it is cheaper. But I'm not sure if I can use it. This >is part of a larger whole. Basically the user is intended to input a >string with the duration, and the string will be used both for > >\set Timing.baseMoment > >and for markup via > >\note We probably should let \note accept a duration, but it's not actually hard to pick apart and use \note-by-number on the parts. One should always be careful with the word 'part' in musical circumstances... Maybe you misunderstood me!? I meant that the functionality was intended for a larger script... Best Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Function for note string to fraction?
Peter Bjuhr writes: > On 2014-05-20 12:02, David Kastrup wrote: >>> Thanks, indeed it is cheaper. But I'm not sure if I can use it. This >>> >is part of a larger whole. Basically the user is intended to input a >>> >string with the duration, and the string will be used both for >>> > >>> >\set Timing.baseMoment >>> > >>> >and for markup via >>> > >>> >\note >> We probably should let \note accept a duration, but it's not actually >> hard to pick apart and use \note-by-number on the parts. > > One should always be careful with the word 'part' in musical > circumstances... Maybe you misunderstood me!? I meant that the > functionality was intended for a larger script... So? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Function for note string to fraction?
On 2014-05-20 12:23, David Kastrup wrote:
We probably should let \note accept a duration, but it's not actually
>>hard to pick apart and use \note-by-number on the parts.
>
Maybe you misunderstood me!? I meant that the
>functionality was intended for a larger script...
So?
Maybe it was me that misunderstood you instead! Did you mean to use
\note like in your previous example:
\markup { \note { 4. } }
?
But why should \note-by-number be used for the parts, I didn't follow that?
Best
Peter
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Function for note string to fraction?
Peter Bjuhr writes:
> On 2014-05-20 12:23, David Kastrup wrote:
We probably should let \note accept a duration, but it's not actually
>>hard to pick apart and use \note-by-number on the parts.
>>> >
>>> Maybe you misunderstood me!? I meant that the
>>> >functionality was intended for a larger script...
>> So?
>
> Maybe it was me that misunderstood you instead! Did you mean to use
> \note like in your previous example:
>
> \markup { \note { 4. } }
>
> ?
>
> But why should \note-by-number be used for the parts, I didn't follow that?
You want to enter a duration in a simple manner and use it in several
contexts. One as markup, one as a duration or length.
The suggestion was to let LilyPond see it not as a string but as a
duration and go from there instead of writing your own duration parser.
I don't understand the problem you have with that.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Function for note string to fraction?
On 2014-05-20 12:51, David Kastrup wrote: You want to enter a duration in a simple manner and use it in several contexts. One as markup, one as a duration or length. The suggestion was to let LilyPond see it not as a string but as a duration and go from there instead of writing your own duration parser. I don't understand the problem you have with that. I think the suggestion is great, at least for the purpose of the script I'm trying to write! Best Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!
On Monday, May 19, 2014 6:50:31 PM UTC+2, Davide Liessi wrote: > The main problems are: > - PortMIDI is not included in the bundle, and even if it is included > (with the appropriate option of py2app) Frescobaldi cannot see the > MIDI ports provided by SimpleSynth or FluidSynth; > What about bundling, say, FluidSynth and the soundfont from MuseScore so that MIDI playback would work "out of the box" as it does in the Windows version of Frescobaldi? For that matter, I also think the latest stable version of LilyPond itself should be included. For the majority of potential Frescobaldi users, getting comfortable with LilyPond is the biggest barrier to entry. It would be better if there were not additional barriers on top of that. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!
On Tuesday, May 20, 2014, Jeff Holland wrote: > > On Monday, May 19, 2014 6:50:31 PM UTC+2, Davide Liessi wrote: > >> The main problems are: >> - PortMIDI is not included in the bundle, and even if it is included >> (with the appropriate option of py2app) Frescobaldi cannot see the >> MIDI ports provided by SimpleSynth or FluidSynth; >> > > What about bundling, say, FluidSynth and the soundfont from MuseScore so > that MIDI playback would work "out of the box" as it does in the Windows > version of Frescobaldi? > Or just communicating with the QuickTime synthesizer directly? > > > For that matter, I also think the latest stable version of LilyPond itself > should be included. For the majority of potential Frescobaldi users, > getting comfortable with LilyPond is the biggest barrier to entry. It would > be better if there were not additional barriers on top of that. > That may not be a bad idea. But then how would you handle Lilypond upgrades? -- Marnen Laibow-Koser mar...@marnen.org http://www.marnen.org Sent from Gmail Mobile ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!
On Tuesday, May 20, 2014 2:46:08 PM UTC+2, Marnen Laibow-Koser wrote: Or just communicating with the QuickTime synthesizer directly? > Sure, whatever works. (I just thought the combination I mentioned sounded better.) > That may not be a bad idea. But then how would you handle Lilypond > upgrades? > People could always install newer versions and add them in Preferences > LilyPond Preferences. Frescobaldi already handles multiple versions of LilyPond intelligently, which is helpful. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!
Am 20.05.2014 14:55, schrieb Jeff Holland: On Tuesday, May 20, 2014 2:46:08 PM UTC+2, Marnen Laibow-Koser wrote: Or just communicating with the QuickTime synthesizer directly? Sure, whatever works. (I just thought the combination I mentioned sounded better.) That may not be a bad idea. But then how would you handle Lilypond upgrades? People could always install newer versions and add them in Preferences > LilyPond Preferences. Frescobaldi already handles multiple versions of LilyPond intelligently, which is helpful. We already had the idea of letting Frescobaldi handle the LilyPond installation in order to offer an easier entry path. On startup it would try to determine if a working LilyPond is installed, and if not, offer to download and install it. In the same line there could be a function "look for LilyPond updates". IIRC we postponed the idea until there is an end-user friendly way to install Frescobaldi on Mac. I think directly bundling LilyPond wouldn't be that good because it definitely bloats the package even more, without being useful for _every_ user. Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!
jeff235 wrote > On Tuesday, May 20, 2014 2:46:08 PM UTC+2, Marnen Laibow-Koser wrote: > >> Or just communicating with the QuickTime synthesizer directly? > > Sure, whatever works. (I just thought the combination I mentioned sounded > better.) +1, especially if MIDI playback that works "out-of-the-box" is just as easy (or easier?) to do than getting Frescobaldi to see the MIDI ports provided by SimpleSynth or FluidSynth (the current problem). jeff235 wrote >> That may not be a bad idea. But then how would you handle Lilypond >> upgrades? > > People could always install newer versions and add them in Preferences > > LilyPond Preferences. Frescobaldi already handles multiple versions of > LilyPond intelligently, which is helpful. Yes, and also wouldn't it work to just include a new stable release of LilyPond in a new release of Frescobaldi? At least for those who are using the stable releases. Or I just saw Urs' message with a different idea... At any rate this could be a future addition (in one way or another) after the initial "1.0" release of the mac app bundle. -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/Mac-testers-needed-for-Frescobaldi-tp161735p162609.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!
2014-05-20 15:03 GMT+02:00 Urs Liska : > We already had the idea of letting Frescobaldi handle the LilyPond > installation in order to offer an easier entry path. On startup it would > try to determine if a working LilyPond is installed, and if not, offer to > download and install it. In the same line there could be a function "look > for LilyPond updates". > https://github.com/wbsoft/frescobaldi/issues/313 > IIRC we postponed the idea until there is an end-user friendly way to > install Frescobaldi on Mac. > I think that this is about the proposal to suggest more strongly Frescobaldi on lilypond.org: http://code.google.com/p/lilypond/issues/detail?id=3716 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!
2014-05-20 15:03 GMT+02:00 Urs Liska : > I think directly bundling LilyPond wouldn't be that good because it > definitely bloats the package even more, without being useful for _every_ > user. I agree. I believe that the best solution will be to keep the installers separated and implement https://github.com/wbsoft/frescobaldi/issues/313. Best wishes. Davide ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: MIDI dynamics parsing error
(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 think that in piano and
choral music if you create a temporary voice, not only do you want the
original dynamic to carry over into the temporary, you want any dynamic
mark to carry over back into the original after the temporary is over.
If I understand you correctly, the only way to set a dynamic change while
temporary voices are active is to set the mark on one voice, set and omit
it on the other(s), and set and omit it on the original voice once the
temporary voices are done. This seems unnecessarily complex for a
situation that I would think happens many times.
Knute Snortum
(via Gmail)
On Mon, May 19, 2014 at 12:34 PM, Heikki Tauriainen wrote:
> 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 volume for
> MIDI,
> > if it has not been specified in the score with a dynamics mark, rather
> than
> > issuing this warning?
> >
> > -Paul
>
> When this warning is shown, LilyPond will actually use the middle of the
> available note velocity range as the starting velocity ("volume").
>
> (This is an exception to most other MIDI settings, such as the MIDI
> instrument, where no defaults are enforced if they are not set
> explicitly. However, for note velocities LilyPond likely needs to
> always use *some* value for MIDI output, which is probably why a default
> is used in this case.)
>
> However, one purpose of the warning is to direct the user's attention to
> input locations where the MIDI output is possibly not what the user
> might expect: for example, since every Voice has by default a separate
> dynamic performer for MIDI, the default volume can easily take effect
> "accidentally" in temporary polyphonic passages such as follows:
>
> \version "2.18.2"
>
> \score {
> \new Staff {
> \new Voice {
> % ... a long monophonic passage
> c'1\p
> <<
> \new Voice {
> c''2\> % starts at the default velocity, not \p
> g'2\!
> }
> \new Voice {
> c'1% this note also gets the default velocity
> }
> >>
> % ... continue with a single Voice
> }
> }
> \layout { }
> \midi { }
> }
>
> In this case the warning could be helpful in signaling the user that
> LilyPond may need some additional help in guessing the "correct" initial
> note velocities for the Voices in the temporary polyphonic passage.
>
> As to the original problem of including the \mf only in MIDI to suppress
> the warning, one could of course also use tags as a workaround, however
> at the cost of duplicating part of the music and the entire \score block
> (personally I nevertheless usually use this approach since, after the
> initial \score setup, it allows customizing MIDI output independently
> from the layout whenever needed):
>
>
> \version "2.18.2"
> \language "english"
>
> upper = \relative c {
> | gf16-. \f ef-. df-. cf-. bf ( \sf df cf af )
> gf-. \sf ef-. df-. cf-. bf ( \sf df cf af )
> |
> <<
> { \tag #'layout { bf4\< } \tag #'midi { bf4\mf\< } a16 ( \sf gf' f
> ef ) bf4 %{ \mf %} \< a16 ( \sf gf' f ef ) }
> \\
> { 16 q q q a4 16 q q q a4 }
> >>
> }
>
> \score {
> \new Staff = "up" {
> \clef treble
> \keepWithTag #'layout \upper
> }
> \layout {
> }
> }
>
> \score {
> \new Staff = "up" {
> \keepWithTag #'midi \upper
> }
> \midi {
> \tempo 4 = 120
> }
> }
>
>
> Now that I looked at the original example, it looks like this example
> also triggers the creation of separate dynamic performers for the upper
> and lower parts of the << { ... } \\ { ... } >> passage. Therefore the
> crescendos in the upper part will probably have no effect on the notes
> in the lower part, all of which will then sound with the "default"
> volume (since no initial volume has been specified). If this is not
> what is intended (possibly not if looking at the typeset output), the
> explicit initial volume and the crescendos should be repeated also in
> the lower part to have them applied to these notes in MIDI...
>
> --
> Heikki Tauriainen
>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!
2014-05-20 14:46 GMT+02:00 Marnen Laibow-Koser : > On Tuesday, May 20, 2014, Jeff Holland wrote: >> On Monday, May 19, 2014 6:50:31 PM UTC+2, Davide Liessi wrote: >>> >>> The main problems are: >>> - PortMIDI is not included in the bundle, and even if it is included >>> (with the appropriate option of py2app) Frescobaldi cannot see the >>> MIDI ports provided by SimpleSynth or FluidSynth; I did not say that it is impossible to bundle a working PortMIDI with Frescobaldi: I just haven't been able yet because it does not work in the most obvious way. >> What about bundling, say, FluidSynth and the soundfont from MuseScore so >> that MIDI playback would work "out of the box" as it does in the Windows >> version of Frescobaldi? This would require a working PortMIDI anyway. > Or just communicating with the QuickTime synthesizer directly? Being able to use QuickTime as MIDI synthesizer would be good: I still would prefer FluidSynth, but QuickTime support would avoid depending on external software and would give working MIDI playback out of the box. But I believe that this also would require PortMIDI. Before implementing new Mac-specific features in Frescobaldi, I would like to solve the current problems of the bundle (PortMIDI and convert-ly) and be able to publish an official Frescobaldi application bundle with the next release. Best wishes. Davide ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!
On Tuesday, May 20, 2014 4:19:34 PM UTC+2, Davide Liessi wrote: > I did not say that it is impossible to bundle a working PortMIDI with > Frescobaldi > I know. My suggestions were only a related tangent. Your current predicament got me thinking is all. I didn't mean to add any distractions from the task at hand. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
midi
I've had no luck w/ midi. I'm running version 2.14.2 on Ubuntu Linux 64-bit and, although it appears to be processing, there is no sound. I'm otherwise enchanted with Frescobaldi and LilyPond. I would be grateful for any suggestions on how I can get midi up and running. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midi
On Tue, 20 May 2014 11:57:14 -0400 Norm wrote: > I've had no luck w/ midi. I'm running version 2.14.2 on Ubuntu Linux > 64-bit and, although it appears to be processing, there is no sound. What have you tried? Also, does sound work for other things? Make sure that you are debugging the right thing. I simply installed timidity and it worked out of the box. -- D'Arcy J.M. Cain Big Smoke Music http://BigSmokeMusic.com/ IM:da...@vex.net ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midi
Ubuntu has a small difficulty in that you might have also the added nonsense of not all midi instruments are callable as the default midi sound set is incomplete. So certain instruments or voices do not work. example "string ensemble 2 " doesn't work. There are others. That just happens to be the one that comes to mind. Also timidity is your friend. and further you might need to check your midi connections in Frescobaldi preferences to make sure it is piping out to the correct midi port. Which for me is usually "TiMidity port 0" You can use the refresh button and that will find out what ports are available. Shane On Tue, May 20, 2014 at 12:09 PM, D'Arcy J.M. Cain wrote: > On Tue, 20 May 2014 11:57:14 -0400 > Norm wrote: >> I've had no luck w/ midi. I'm running version 2.14.2 on Ubuntu Linux >> 64-bit and, although it appears to be processing, there is no sound. > > What have you tried? Also, does sound work for other things? Make > sure that you are debugging the right thing. > > I simply installed timidity and it worked out of the box. > > -- > D'Arcy J.M. Cain > Big Smoke Music > http://BigSmokeMusic.com/ IM:da...@vex.net > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: MIDI dynamics parsing error
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 behavior is getting away from that value. I would think that in piano and choral music if you create a temporary voice, not only do you want the original dynamic to carry over into the temporary, you want any dynamic mark to carry over back into the original after the temporary is over. If I understand you correctly, the only way to set a dynamic change while temporary voices are active is to set the mark on one voice, set and omit it on the other(s), and set and omit it on the original voice once the temporary voices are done. This seems unnecessarily complex for a situation that I would think happens many times. Perhaps it’s possible to move the Dynamics_engraver and _performer to staff level for this purpose? Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: #(ly:expect-warning "")
Am 18.05.2014 13:46, schrieb David Nalesnik: Hi Simon, On Sun, May 18, 2014 at 5:57 AM, Simon Albrecht mailto:simon.albre...@mail.de>> wrote: Hello, I just tried to suppress a series of expected warnings, but the scheme function seems to suppress only the first of a kind. See attached file. Why is this? Each call suppresses a single instance, so you need to repeat it for each warning. I don't know the rationale for this. Now you say it: it does make sense, since when there is one occurence of a warning that you already know of and want to suppress, you might still be happy to see it when the same warning is issued another time from an unrelated reason. In any case, you could put something like this at the head of your file. I guess copy-and-paste would be equally effective :) #(define (suppress message x) (let loop ((c x)) (if (> c 0) (begin (ly:expect-warning message) (loop (1- c)) #(suppress "MIDI channel wrapped around" 5) #(suppress "remapping modulo 16" 5) Note there's also a warning for expected error NOT encountered. HTH, David Thanks a lot, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: MIDI dynamics parsing error
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 about LilyPond was the ability to
> compile sheet music and MIDI from the same source.
That's exactly the same thought that I had when I started learning to
use LilyPond - the idea of producing multiple different kinds of output
for different purposes from the same source feels very attractive.
> It seems to me that this behavior is getting away from that value. I
> would think that in piano and choral music if you create a temporary
> voice, not only do you want the original dynamic to carry over into
> the temporary, you want any dynamic mark to carry over back into the
> original after the temporary is over.
I've often wondered the same thing - the default behavior of having a
separate dynamic performer per every Voice context probably works well
in cases where a Staff never contains more than a single Voice, but
especially with piano music, where it's convenient to use temporary
polyphony with new Voice contexts to achieve the intended layout, the
default behavior of Voices can easily give unsatisfactory (or even
surprising, if one doesn't know what's going on) results for MIDI unless
extra care is taken to work around this behavior.
> If I understand you correctly, the only way to set a dynamic change
> while temporary voices are active is to set the mark on one voice, set
> and omit it on the other(s), and set and omit it on the original voice
> once the temporary voices are done. This seems unnecessarily complex
> for a situation that I would think happens many times.
This is indeed a cumbersome solution, but at least it'll likely do the
job...
An alternative might be to try to remove the dynamic performer from all
Voice contexts, and add one to the Staff containing the voices instead
(this example still uses tags to reset the MIDI velocity level from \sf
to \mf to avoid the warnings):
\version "2.18.2"
\language "english"
upper = \relative c \new Voice \with { \remove "Dynamic_performer" }
{
| gf16-. \f ef-. df-. cf-. bf ( \sf df cf af )
gf-. \sf ef-. df-. cf-. bf ( \sf df cf af )
|
<<
\new Voice \with { \remove "Dynamic_performer" } { bf4 -\tag #'midi
\mf -\< a16 ( \sf gf' f
ef ) bf4 -\tag #'midi \mf \< a16 ( \sf gf' f ef ) }
\new Voice \with { \remove "Dynamic_performer" } { 16 q q q
a4 16 q q q a4 }
>>
}
\score {
\new Staff = "up" {
\clef treble
\keepWithTag #'layout \upper
}
\layout {
}
}
\score {
\new Staff = "up" \with { \consists "Dynamic_performer" } {
\keepWithTag #'midi \upper
}
\midi {
\tempo 4 = 120
}
}
However, I'm not entirely sure how reliably this is guaranteed to work
(if at all) since I believe that at least some of the MIDI-related
performers are targeted to work correctly only within a particular type
of context and therefore cannot really be moved entirely freely between
different contexts. With this particular example, however, the end
result sounds to me as if the dynamic changes would get applied to all
Voices in the parallel music expression.
--
Heikki Tauriainen
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
omit time signature when time doesn't change
Hi everyone!
I have a score with some time changes. I'm using variables for the various song
section. Each section has it's own time (more useful than declaring it each
time there is a time change). What happens is that the time signature will be
printed any time it is declared, even when no time changes occurs. Here is a
simple example:
%
\version "2.18.0"
verse = { \time 4/4 c2 c2 | c2 c2 | }
verseFirstEnd = { \time 4/4 d2 d2 | }
verseSecondEnd = { \time 2/4 c2 | }
song = {
\new Staff
{
\relative c'
{
\verse % First measure; print time signature, of course
\verseFirstEnd % Same time; I don't wont time signature printed
\verse % Same time; I don't wont time signature printed
\verseSecondEnd % Time change; print the new time signature
\verse % Time change; print the new time signature
}
}
}
\score {
\song
}
%
I suppose (didn't tried yet) that I can use the an "omit" command (or similar)
to omit it locally, but it is not very useful to operate this way (is just like
declaring the time outside the variables when needed).
Is there any command that says "omit all time signature when there is no time
changes"?
Thanks!
MIX
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: omit time signature when time doesn't change
Hi Carlo,
when I asked that question I got this as a result :-)
https://bitbucket.org/beautifulscores/das-trunkne-lied/src/e29b4a0fdb61232ad0dfce1c27ec33d5f0270f0c/library/ly/to-lilylib/suppressRedundantTimeSigEngraver.ily?at=master
HTH
Urs
Am 20.05.2014 23:38, schrieb Carlo Vanoni:
Hi everyone!
I have a score with some time changes. I'm using variables for the various song
section. Each section has it's own time (more useful than declaring it each
time there is a time change). What happens is that the time signature will be
printed any time it is declared, even when no time changes occurs. Here is a
simple example:
%
\version "2.18.0"
verse = { \time 4/4 c2 c2 | c2 c2 | }
verseFirstEnd = { \time 4/4 d2 d2 | }
verseSecondEnd = { \time 2/4 c2 | }
song = {
\new Staff
{
\relative c'
{
\verse % First measure; print time signature, of course
\verseFirstEnd % Same time; I don't wont time signature printed
\verse % Same time; I don't wont time signature printed
\verseSecondEnd % Time change; print the new time signature
\verse % Time change; print the new time signature
}
}
}
\score {
\song
}
%
I suppose (didn't tried yet) that I can use the an "omit" command (or similar)
to omit it locally, but it is not very useful to operate this way (is just like declaring
the time outside the variables when needed).
Is there any command that says "omit all time signature when there is no time
changes"?
Thanks!
MIX
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midi
This sometimes happens to me, too. As nice as it is to just be able to have bug-free immediate playback in Frescobaldi, I have grown accustomed to simply calling timidity in a console with something like: timidity mysong.midi and that has never NOT worked for me. I've also found that once I do this (assuming one of the other suggestions doesn't work) then the midi player within Frescobaldi also starts working. Kinda weird how that happens. Regards, Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/midi-tp162615p162632.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midi
Don't know if this is related, but since testing the download package, my original has been having trouble with ports. I have to choose a different port from Frescobaldi's preferences drop down tab, but then it works. ~Conor Cook > On May 20, 2014, at 5:59 PM, tisimst wrote: > > This sometimes happens to me, too. As nice as it is to just be able to have > bug-free immediate playback in Frescobaldi, I have grown accustomed to > simply calling timidity in a console with something like: > > timidity mysong.midi > > and that has never NOT worked for me. I've also found that once I do this > (assuming one of the other suggestions doesn't work) then the midi player > within Frescobaldi also starts working. Kinda weird how that happens. > > Regards, > Abraham > > > > -- > View this message in context: > http://lilypond.1069038.n5.nabble.com/midi-tp162615p162632.html > Sent from the User mailing list archive at Nabble.com. > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: omit time signature when time doesn't change
I know you say you don't want to have the time signatures outside of the
variables, but could you expand on why?
\version "2.18.0"
verse = { c2 c2 | c2 c2 | }
verseFirstEnd = { d2 d2 | }
verseSecondEnd = { c2 | }
\relative c'
{
\time 4/4
\verse
\verseFirstEnd
\verse
\time 2/4
\verseSecondEnd
\time 4/4
\verse
}
Knute Snortum
(via Gmail)
On Tue, May 20, 2014 at 2:38 PM, Carlo Vanoni wrote:
> Hi everyone!
>
> I have a score with some time changes. I'm using variables for the various
> song section. Each section has it's own time (more useful than declaring it
> each time there is a time change). What happens is that the time signature
> will be printed any time it is declared, even when no time changes occurs.
> Here is a simple example:
>
> %
> \version "2.18.0"
>
> verse = { \time 4/4 c2 c2 | c2 c2 | }
> verseFirstEnd = { \time 4/4 d2 d2 | }
> verseSecondEnd = { \time 2/4 c2 | }
>
> song = {
> \new Staff
> {
> \relative c'
> {
> \verse % First measure; print time signature, of course
> \verseFirstEnd % Same time; I don't wont time signature
> printed
> \verse % Same time; I don't wont time signature printed
> \verseSecondEnd % Time change; print the new time signature
> \verse % Time change; print the new time signature
> }
> }
> }
>
> \score {
> \song
> }
> %
>
> I suppose (didn't tried yet) that I can use the an "omit" command (or
> similar) to omit it locally, but it is not very useful to operate this way
> (is just like declaring the time outside the variables when needed).
> Is there any command that says "omit all time signature when there is no
> time changes"?
>
> Thanks!
> MIX
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: combining cue notes and full measure rests….
Hi Paul,
I suspect, there is something wrong with spacer rests. At least this
snippet works:
\version "2.18.2"
\addQuote musi \relative c'' { R1 c4 b a g f e d c R1 }
{
\compressFullBarRests
<<
{ R1*4 } \\
{ s1*2 \cueDuring musi #UP { s2. } }
>>
}
But I wonder, why you use a <<{}\\{}>> construct?
Normally I would just use
{ R1*2 \cueDuring musi #UP { R1 } R1 }
And first I highly recommend to upgrade to latest stable! I only checked
in 2.18.2 - there might be a problem 2.14?
Cheers, Jan-Peter
Am 21.05.14 02:29, schrieb Paul Malcolm:
Dear All, I am trying to neatly combine piano cue notes and full measure
rests for the intsrument not in play (here the Viola).
I have attached my very crude and failed attempt. This section shows
the piano
cue notes in blue at measures 81 & 82. What I would like to do is add
a full measure rest (black) in each of these bars and place the rests
(as usual) right in
the middle of the stave. The attempt I show here used two voices <<{}
\\ {} >> etc but that did not work.
I checked snippet libraries but didn't find any examples that shed
light on this
little problem ?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: omit time signature when time doesn't change
@Urs Liska
Your code did the trick, thanks.
@Knute Snortum
Well, I think that the time is a property of the song section that I'm defining
in the variable, so it is more correct to define it in the variable itself.
Furthermore, if the variable defines one (as in the example) or more measures
that cointains a fixed number of beats, so the variable can't be used as part
of another measure with a yet unknown time but just as a song section with a
given time, it is more obvious to declare it in the variable definition since
this section can't use a different time.
Of course, I won't do it if there are no time changes within the song: here the
time is a song feature and will be declared in the song section.
What you think about it?
Il Mercoledì 21 Maggio 2014 1:33, Knute Snortum ha scritto:
I know you say you don't want to have the time signatures outside of the
variables, but could you expand on why?
\version "2.18.0"
verse = { c2 c2 | c2 c2 | }
verseFirstEnd = { d2 d2 | }
verseSecondEnd = { c2 | }
\relative c'
{
\time 4/4
\verse
\verseFirstEnd
\verse
\time 2/4
\verseSecondEnd
\time 4/4
\verse
}
Knute Snortum
(via Gmail)
On Tue, May 20, 2014 at 2:38 PM, Carlo Vanoni wrote:
Hi everyone!
>
>
>I have a score with some time changes. I'm using variables for the various
>song section. Each section has it's own time (more useful than declaring it
>each time there is a time change). What happens is that the time signature
>will be printed any time it is declared, even when no time changes occurs.
>Here is a simple example:
>
>
>%
>\version "2.18.0"
>
>verse = { \time 4/4 c2 c2 | c2 c2 | }
>verseFirstEnd = { \time 4/4 d2 d2 | }
>verseSecondEnd = { \time 2/4 c2 | }
>
>song = {
> \new Staff
> {
> \relative c'
> {
> \verse % First measure; print time signature, of course
> \verseFirstEnd % Same time; I don't wont time signature printed
>
\verse % Same time; I don't wont time signature printed
> \verseSecondEnd % Time change; print the new time signature
> \verse % Time change; print the new time signature
> }
> }
>}
>
>\score {
> \song
>}
>%
>
>
>I suppose (didn't tried yet) that I can use the an "omit" command (or similar)
>to omit it locally, but it is not very useful to operate this way (is just
>like declaring the time outside the variables when needed).
>Is there any command that says "omit all time signature when there is no time
>changes"?
>
>
>Thanks!
>MIX
>
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
