On Fri, Nov 29, 2019 at 10:28:04AM +0100, Sandro Santilli wrote:
> Uhm, I might be still not getting the 2.18.2 compatibility, as this
> is what I get:
>
> warning: type check for `color' failed; value `# Music((origin . #) (void . #t))((name . Music)
> (types general-music)) > ' must be of t
On Thu, Nov 28, 2019 at 10:40:17AM -0800, Aaron Hill wrote:
> On 2019-11-28 9:27 am, Sandro Santilli wrote:
> > On Mon, Nov 25, 2019 at 04:40:12AM -0800, Aaron Hill wrote:
> > > On 2019-11-25 2:26 am, Sandro Santilli wrote:
> > > > I'm trying, for backward compatibility, to keep that
> > > > highli
On 2019-11-28 9:27 am, Sandro Santilli wrote:
On Mon, Nov 25, 2019 at 04:40:12AM -0800, Aaron Hill wrote:
On 2019-11-25 2:26 am, Sandro Santilli wrote:
> I'm trying, for backward compatibility, to keep that
> highlightOutOfRange function, is that possible ?
What compatibility are you needing?
On Mon, Nov 25, 2019 at 04:40:12AM -0800, Aaron Hill wrote:
> On 2019-11-25 2:26 am, Sandro Santilli wrote:
> > I'm trying, for backward compatibility, to keep that
> > highlightOutOfRange function, is that possible ?
>
> What compatibility are you needing?
As I've used the old function in existi
On 2019-11-25 2:26 am, Sandro Santilli wrote:
I'm trying, for backward compatibility, to keep that
highlightOutOfRange function, is that possible ?
What compatibility are you needing?
I intended \highlightPitches to be a significant upgrade to my earlier
\highlightOutOfRange, which I would no
On 2019-11-24 2:40 am, Sandro Santilli wrote:
Like, the following does _not_ work:
altoDesignedWrittenRange = bes g'''
\override NoteHead.color = \highlightOutOfRange
\altoDesignedWrittenRange
The function would need to be modified to support syntax like that.
I took some time to general
On Fri, Nov 15, 2019 at 12:42:46PM +0100, Sandro Santilli wrote:
> On Fri, Nov 15, 2019 at 12:20:51PM +0100, Michael Käppler wrote:
> >
> > melodyRange = \override NoteHead.color = \highlightOutOfRange e' b'
>
> And this is great to build that library, thanks !
I'm building that library, using in
On Fri, Nov 15, 2019 at 12:20:51PM +0100, Michael Käppler wrote:
> Why not put it in the underlying "input" then?
>
> melody = {
> \override NoteHead.color = \highlightOutOfRange e' b'
> \relative c' { c4 d e f }
> }
Yep, that works
> You could even define a shortcut for this:
>
> melod
Why not put it in the underlying "input" then?
melody = {
\override NoteHead.color = \highlightOutOfRange e' b'
\relative c' { c4 d e f }
}
You could even define a shortcut for this:
melodyRange = \override NoteHead.color = \highlightOutOfRange e' b'
melody = {
\melodyRange
\rela
On Fri, Nov 15, 2019 at 12:09:27PM +0100, Sandro Santilli wrote:
>
> The thing is I'm writing multiple scores with the same parts
> replicated (some with all 3 voices, some with just 2 voices)
> so I'd like to avoid the duplication of ranges. A range is
> specific to an instrument so I'd like to s
On Fri, Nov 15, 2019 at 12:00:09PM +0100, Michael Käppler wrote:
> \score {
> <<
> \new Staff \with {
> instrumentName = #"Voice"
>
> } {
> \new Voice = "vocal" \with {
> \override NoteHead.color = \highlightOutOfRange e' b'
> } { \notes }
>
> }
>
> \
notes = \relative c' { c d e f g a b c }
\score {
<<
\new Staff \with {
instrumentName = #"Voice"
} {
\new Voice = "vocal" \with {
\override NoteHead.color = \highlightOutOfRange e' b'
} { \notes }
}
\new Staff \with {
instrumentName = #"Alto"
On Fri, Nov 15, 2019 at 10:45:45AM +0100, Michael Käppler wrote:
> While I would strongly suggest that you update to the latest development
> version, which can regarded
> as very stable, this would work with 2.18.2:
Thanks, this works!
Can I specify a different override for different
voices by na
On Thu, Nov 14, 2019 at 06:02:40PM +0100, k...@aspodata.se wrote:
> Sandro:
> > In order to determine if I'm writing something that can
> > be played by an instrument, is there a way to display
> > on the score the supported range by that instrument ?
> >
> > I'd like to have something that doesn'
While I would strongly suggest that you update to the latest development
version, which can regarded
as very stable, this would work with 2.18.2:
% LilyBin
\version "2.18.2"
highlightOutOfRange = #(define-scheme-function
(parser location color lower upper)
((color? red) ly:pitch? ly:pitch?)
On Thu, Nov 14, 2019 at 09:09:16AM -0800, Aaron Hill wrote:
> \layout {
> \context { \Voice
> \override NoteHead.color = \highlightOutOfRange c' c''
> }
> }
I like the highlighting idea! Is it compatible at all with 2.18.2 ?
It seems not to be: http://lilybin.com/166vv7/1
Parsing.../u
Am 14.11.19 um 18:09 schrieb Aaron Hill:
On 2019-11-14 8:53 am, Sandro Santilli wrote:
In order to determine if I'm writing something that can
be played by an instrument, is there a way to display
on the score the supported range by that instrument ?
I'd like to have something that doesn't c
On 2019-11-14 8:53 am, Sandro Santilli wrote:
In order to determine if I'm writing something that can
be played by an instrument, is there a way to display
on the score the supported range by that instrument ?
I'd like to have something that doesn't change when I
transpose, so to know if transpo
Sandro:
> In order to determine if I'm writing something that can
> be played by an instrument, is there a way to display
> on the score the supported range by that instrument ?
>
> I'd like to have something that doesn't change when I
> transpose, so to know if transpositions are possible
> at al
In order to determine if I'm writing something that can
be played by an instrument, is there a way to display
on the score the supported range by that instrument ?
I'd like to have something that doesn't change when I
transpose, so to know if transpositions are possible
at all...
--strk;
()
20 matches
Mail list logo
