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
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)
(
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
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 l
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
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
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-
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
>
>
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 Ti
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 th
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
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 durati
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
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
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
> u
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.
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
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
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:/
(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
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 optio
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
fr
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.
__
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
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 o
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
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
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
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 ti
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 everyon
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 th
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 sometim
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
\verseS
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. } }
>>
}
@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
35 matches
Mail list logo
