Aw: lilypond-user Digest, Vol 150, Issue 183

[Alexander Deubelbeiss]

> Gesendet: Samstag, 30. Mai 2015 um 18:01 Uhr
> Von: address@hidden
> An: address@hidden
> Betreff: lilypond-user Digest, Vol 150, Issue 183
>
> Send lilypond-user mailing list submissions to
>       address@hidden
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>       https://lists.gnu.org/mailman/listinfo/lilypond-user
> or, via email, send a message with subject or body 'help' to
>       address@hidden
> 
> You can reach the person managing the list at
>       address@hidden
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lilypond-user digest..."
> 
> 
> Today's Topics:
> 
>    1. Fedora issues (Andrew Bernard)
>    2. Re:Color note heads outside nominal  instrument range (Marc Hohl)
>    3. Re:Fedora issues (Kevin Barry)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sat, 30 May 2015 21:08:02 +1000
> From: Andrew Bernard <address@hidden>
> To: lilypond-user Mailinglist <address@hidden>
> Subject: Fedora issues
> Message-ID:
>       <address@hidden>
> Content-Type: text/plain; charset="utf-8"
> 
> Greetings all,
> 
> On Fedora 21 and the recently released Fedora 22, lilypond 2.19.21 crashes
> on my complex score with the following verbose output:
> 
> Drawing systems...lilypond:
> /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/include/interval.hh:226:
> T Interval_t<T>::center() const [with T = double]: Assertion `!is_empty ()'
> failed.
> Aborted (core dumped)
> 
> There is no indication of where this error is being thrown, so I am at a
> loss to know how to localise this issue in order to submit a bug report. I
> am unbale to release the score due to IP issues, and that fact that it is a
> contemporary work in progress.
> 
> This is from the the 2.19.21 release downloaded from lilypond.org. The same
> happens with a locally compiled build.
> 
> Should lilypond users simply abandon Fedora forever? [I ask this in all
> seriousness.]
> 
> Andrew
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://lists.gnu.org/archive/html/lilypond-user/attachments/20150530/140bc67e/attachment.html>
> 
> ------------------------------
> 
> Message: 2
> Date: Sat, 30 May 2015 13:40:13 +0200
> From: Marc Hohl <address@hidden>
> To: address@hidden
> Subject: Re: Color note heads outside nominal  instrument range
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=windows-1252; format=flowed
> 
> Am 30.05.2015 um 12:38 schrieb Peter Gentry:
> >
> > FWIW
> >
> > I have attached a slightly simplified and better version of 
> > instrument_ranges.ly
> 
> I haven't tested your code, but I like the idea of defining 
> instrument-specific tonal ranges quite a lot!
> 
> Some ideas/proposals:
> 
> 1)
> Can you store the tone range for each instrument in an alist?
> 
> (define range-alist
>   '((
>    ("clarinet" . ( -10 . 34 ))
>    ("bass-clarinet-c" . ( ...
> )))
> 
> or even better, use pitches? You can extract upper and lower bounds
> from this alist and don't have to write a conditional check for
> each instrument.
> 
> 2)
> IIUC, the line
> (if (or ( > op 34) (< op -10) ) (begin (set! o (+ o 1))) ))
> 
> adds one octave to the pitch if the note is lower than the lowest
> possible note OR higher than the highest possible note?
> The latter doesn't seem quite right to me ;-)
> 
> (and (< op -10)
>       (set! o (+ o 1)))
> (and (> op 34)
>       (set! o (- o 1)))
> 
> seems to do the trick (untested).
> 
> Apart from that, such a function is a valuable extension for lilypond IMHO.
> 
> Cheers,
> 
> Marc
> 
> 
> >
> > regards
> > Peter Gentry
> >
> >
> >
> > _______________________________________________
> > lilypond-user mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
> >
> 
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Sat, 30 May 2015 13:09:38 +0100
> From: Kevin Barry <address@hidden>
> To: Andrew Bernard <address@hidden>
> Cc: lilypond-user Mailinglist <address@hidden>
> Subject: Re: Fedora issues
> Message-ID:
>       <address@hidden>
> Content-Type: text/plain; charset="utf-8"
> 
> I am on fedora 22 and the current stable version of lilypond (2.18.2) is
> working fine on my scores. I don't normally use unstable versions; should I
> be concerned?
> 
> Kevin
> 
> On Sat, May 30, 2015 at 12:08 PM, Andrew Bernard <address@hidden>
> wrote:
> 
> > Greetings all,
> >
> > On Fedora 21 and the recently released Fedora 22, lilypond 2.19.21 crashes
> > on my complex score with the following verbose output:
> >
> > Drawing systems...lilypond:
> > /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/include/interval.hh:226:
> > T Interval_t<T>::center() const [with T = double]: Assertion `!is_empty ()'
> > failed.
> > Aborted (core dumped)
> >
> > There is no indication of where this error is being thrown, so I am at a
> > loss to know how to localise this issue in order to submit a bug report. I
> > am unbale to release the score due to IP issues, and that fact that it is a
> > contemporary work in progress.
> >
> > This is from the the 2.19.21 release downloaded from lilypond.org. The
> > same happens with a locally compiled build.
> >
> > Should lilypond users simply abandon Fedora forever? [I ask this in all
> > seriousness.]
> >
> > Andrew
> >
> >
> >
> > _______________________________________________
> > lilypond-user mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://lists.gnu.org/archive/html/lilypond-user/attachments/20150530/f6da0022/attachment.html>
> 
> ------------------------------
> 
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> End of lilypond-user Digest, Vol 150, Issue 183
> ***********************************************
>