Re: Retrieve (remaining) duration of beam (in C++)

2015-12-18 Thread Carl Sorensen
On 12/18/15 12:52 PM, "Urs Liska" wrote: > > >Am 18.12.2015 um 18:35 schrieb Carl Sorensen: >> >> On 12/18/15 9:49 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org >>on >> behalf of Urs Liska" >on >> behalf of u...@openlilylib.org> wrote: >> >> >>> If I could either retrieve the start_mom

Re: Retrieve (remaining) duration of beam (in C++)

2015-12-18 Thread Urs Liska
Am 18.12.2015 um 18:35 schrieb Carl Sorensen: > > On 12/18/15 9:49 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on > behalf of Urs Liska" behalf of u...@openlilylib.org> wrote: > > >> If I could either retrieve the start_moment of the note *after* the >> current beam *or* the duration

Re: Retrieve (remaining) duration of beam (in C++)

2015-12-18 Thread Carl Sorensen
On 12/18/15 9:49 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on behalf of Urs Liska" wrote: > >If I could either retrieve the start_moment of the note *after* the >current beam *or* the duration of the last item in infos_ I could >calculate the value I need (I think). Or maybe there

Re: Retrieve (remaining) duration of beam (in C++)

2015-12-18 Thread Urs Liska
Am 18.12.2015 um 17:49 schrieb Urs Liska: > I have > infos_[i].start_moment_ > to determine the moment of the *current* beam Oops, that should of course read "the current *stem*" ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.

Retrieve (remaining) duration of beam (in C++)

2015-12-18 Thread Urs Liska
Hi, I just looked again at my attempts to get beam subdivision on the right track. Unfortunately I need some help understanding Beaming_pattern::beamify in beaming-pattern.cc. If I'm not mistaken the calculation of the beam count iterates over the infos_ struct, whose members contain information

Re: SOLVED (Re: stepmake in lilypond)

2015-12-18 Thread Richard Shann
On Fri, 2015-12-18 at 13:19 +0100, David Kastrup wrote: > Villum Sejersen writes: > > > On 18-12-2015 09:31, David Kastrup wrote: > > > >> Villum Sejersen writes: > >>> [...] > Nope. What parts of stepmake LilyPond needs are included in LilyPond > itself. > >>> Well, that's good to kno

Re: SOLVED (Re: stepmake in lilypond)

2015-12-18 Thread David Kastrup
Villum Sejersen writes: > On 18-12-2015 09:31, David Kastrup wrote: > >> Villum Sejersen writes: >>> [...] Nope. What parts of stepmake LilyPond needs are included in LilyPond itself. >>> Well, that's good to know, but where is it documented? >> Documenting all non-dependencies would b

SOLVED (Re: stepmake in lilypond)

2015-12-18 Thread Villum Sejersen
On 18-12-2015 09:31, David Kastrup wrote: Villum Sejersen writes: If it did any difference to my system I would be glad, but that is apparently /*not*/ the case! root@Villums14:/usr/local/src/lilypond# ./autogen.sh --noconfigure processing . Running autoconf ... Skipping configure process.

Re: Musicians prefer LilyPond scores, study finds

2015-12-18 Thread karl
Francisco Vila: > I just gained my PhD. My humble thesis tells the design and results of > an experiment with a number of musicians, comparing lilypond scores > with the originals which those scores were copied from. ... > A 20Mb PDF (in Spanish) is privately available for those who ask for it. ...

Re: stepmake in lilypond

2015-12-18 Thread David Kastrup
Villum Sejersen writes: > If it did any difference to my system I would be glad, but that is > apparently /*not*/ the case! > > root@Villums14:/usr/local/src/lilypond# ./autogen.sh --noconfigure > processing . > Running autoconf ... > Skipping configure process. > > root@Villums14:/usr/local/src/