Re: JEdit Outline Question

[Bertalan Fodor (LilyPondTool)]

You get them if the file is parsed. Make sure that lilypond parsing is 
choosed in the SideKick dockable.

They can disappear if there is a problem in your source file.

Bert

Thermo wrote:

I use JEdit to edit my Lilypond files.

Sometimes I can see the outlining triangles on the left and sometimes not. 
Can anyone tell me how to get them to show?


Thanks
Graham
  





___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: pmx2ly ?

[Mats Bengtsson]

stefanozanobini wrote:

It's a pity.
I had already thought, that I could create the .ly file quite fast
with the .pmx file, but I don't understand why pmx2ly is not more
avaible. It would be useful.
  
As with any open source project, the problem is maintenance. I guess 
that nobody was
interested in maintaining pmx2ly, and when it became too outdated, it 
was removed.


Perhaps you would be interested in maintaining the program. If you know 
some

basics about programming, I guess it's probably not too difficult to do.

   /Mats

However I thank you, david


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
  


--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
   Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bar numbers collide with StaffGroup bracket

[Mats Bengtsson]

Note also that this collision problem is solved automatically if you 
upgrade to the latest

development version 2.11.x.

  /Mats

Trevor Daniels wrote:

You've probably spotted by now that the correct
syntax is

\context { \Score \override BarNumber #'padding = #3 }

Score with a capital S is the name of the context.

Trevor

- Original Message - From: "Frederick Dennis" 
<[EMAIL PROTECTED]>

To: 
Sent: Friday, August 01, 2008 2:55 PM
Subject: Bar numbers collide with StaffGroup bracket



Dear All,
\version "2.10.33"
I've just noticed that the bar numbers are colliding with the StaffGroup
bracket.
I've put
\context {\score \override BarNumber #'padding = #3  }
in the layout block but nothing happens.
I've also put it at the top and in various other places.
Thank you for your attention.




 





___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user





___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
   Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: woodwind harmonics (GDP)

[Mats Bengtsson]

The \flageolet articulation is intended for this purpose. At least in
string music, the resulting circle has the size and layout that I
recognize from string music. I haven't seen any woodwind parts with
harmonics but would be surprised if the circle really was that small
that your example gives. It should be visible at one meter distance,
right? If you want the same symbol as \harmonic but with smaller size,
you can rather use
c^\markup{\small \musicglyph #"scripts.flageolet" }

/Mats

Andrew Hawryluk wrote:
> I'm trying to show how one could specify a harmonic for a woodwind
> instrument (NR 2.6.1.1).
> This looks correct when printed, but it's a bit ugly. Any suggestions?
>
> Note that usually the lower (fingered) pitch is not written, but the
> small circle is always needed.
>
> {
>   2^\markup \fontsize #-8 " ○"
>   2^\markup \fontsize #-8 " ○"
>   1^\markup \fontsize #-8 "  ○"
> }
>
> I wondered if the \flageolet articulation was intended for this
> purpose, but it much larger than the marks I have seen in print.
>
> Andrew
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user
>   

-- 
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Syntax highlighting in LilyPad?

[Mats Bengtsson]

Please always keep the discussion on the mailing list 
lilypond-user@gnu.org,
for the benefit of yourself since you get access to the collected 
expertise on the
list and for the benefit of others who experience similar problems. I 
have never

used LilyPond on a Mac. I hope you have read section
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-program/Text-editor-support#Text-editor-support
which describes several editors with good LilyPond support. You can find 
even more

examples if you search the mailing list archives.

  /Mats


Oliver Popp wrote:

Hey,

have you found a way for syntax highlighting in Lilypad?
I suppose you're using a mac and you prefer the Lilypad app instead of 
the Lilypond editor. Till now I could not find a nice way for editing 
in Lilypond as you have it in TeXShop for example.
I just tried to integrate Lilypond in TeXShop (which should be 
possible), however it didn't work out yet.


Do you have any ideas?

Many greets from Germany,

Oliver


--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
   Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing problem

[Han-Wen Nienhuys]

On Mon, Aug 4, 2008 at 3:18 AM, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> It's not specific to dotted notes but to notes which have longer
> durations, and which get squeezed far too much -- the same problem
> occurs for, say, half notes and whole notes.  I simply want to control
> these squeezing values globally.

The spacing is controlled by 2 values in the end: the ideal length of
the spring, and the width of the fixed part (the remaining is the
stretchable part).  I guess you want to increase the fixed width for
these notes (which also decreases the stretching in case of loose
lines - the springs are symmetric in stretch and shrink).  You could
experiment with

  Spacing_spanner::musical_column_spacing

to tweak the fixed length.

-- 
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: woodwind harmonics (GDP)

[Andrew Hawryluk]

Thanks! The marks I have seen in print are about 70% of the current
\flageolet diameter, but I don't want to trouble anybody with making
new markups and then tweaking them to centre them over the note heads.
I will suggest the original, unaltered articulation.

Andrew

2008/8/4 Mats Bengtsson <[EMAIL PROTECTED]>:
> The \flageolet articulation is intended for this purpose. At least in
> string music, the resulting circle has the size and layout that I
> recognize from string music. I haven't seen any woodwind parts with
> harmonics but would be surprised if the circle really was that small
> that your example gives. It should be visible at one meter distance,
> right? If you want the same symbol as \harmonic but with smaller size,
> you can rather use
> c^\markup{\small \musicglyph #"scripts.flageolet" }
>
> /Mats
>
> Andrew Hawryluk wrote:
>> I'm trying to show how one could specify a harmonic for a woodwind
>> instrument (NR 2.6.1.1).
>> This looks correct when printed, but it's a bit ugly. Any suggestions?
>>
>> Note that usually the lower (fingered) pitch is not written, but the
>> small circle is always needed.
>>
>> {
>>   2^\markup \fontsize #-8 " ○"
>>   2^\markup \fontsize #-8 " ○"
>>   1^\markup \fontsize #-8 "  ○"
>> }
>>
>> I wondered if the \flageolet articulation was intended for this
>> purpose, but it much larger than the marks I have seen in print.
>>
>> Andrew
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> http://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
> --
> =
>Mats Bengtsson
>Signal Processing
>School of Electrical Engineering
>Royal Institute of Technology (KTH)
>SE-100 44  STOCKHOLM
>Sweden
>Phone: (+46) 8 790 8463
>Fax:   (+46) 8 790 7260
>Email: [EMAIL PROTECTED]
>WWW: http://www.s3.kth.se/~mabe
> =
>
>
<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: NR 1.3 Expressive marks, second draft

[Francisco Vila]

2008/8/3 Trevor Daniels <[EMAIL PROTECTED]>:
> Hi Francisco
>
> Not a bad suggestion.  I've tried to fix the
> issues you mentioned - still not perfect, but
> better.  Revised code attached.

Trevor: great.

Measures filled of eighth notes are much prettier in my original, here
I suppose that the shortest common duration is 1/8, otherwise all
noteheads look as if they were left shifted, but I don't know where
exactly to put the setting. This would also fix the two fortissimos
crossed by the bar line.
-- 
Francisco Vila. Badajoz (Spain)
http://www.paconet.org


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Indexing function codes

[Palmer, Ralph]

Hi -

I'm working on indexing, and I have a question for those of us who use
the function index.

When looking for a command such as \repeat or \alternative, which would
you find more helpful: having duplicate index entries (i.e., one with
the backslash and one without) or having an entry only for the exact
command? In other words, option 1 would have all of:

\alternative
\repeat
alternative
repeat

while option 2 would have only

\alternative
\repeat

Thanks for your time and attention,

Ralph

+
Ralph Palmer, CEM
Energy/Administrative Coordinator
Keene State College
Keene, NH 03435-2502
Phone: 603-358-2230
Cell: 603-209-2903
Fax: 603-358-2456
[EMAIL PROTECTED]






___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: NR 1.3 Expressive marks, second draft

[Francisco Vila]

2008/8/4 Francisco Vila <[EMAIL PROTECTED]>:
> Measures filled of eighth notes are much prettier in my original, here
> I suppose that the shortest common duration is 1/8, otherwise all
> noteheads look as if they were left shifted, but I don't know where
> exactly to put the setting. This would also fix the two fortissimos
> crossed by the bar line.

Speaking of, what if LilyPond automatically detects the most common
shortest note per measure? Which is the default shortest note for
spacing? I wonder it is 1/4.
-- 
Francisco Vila. Badajoz (Spain)
http://www.paconet.org


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Indexing function codes

[Francisco Vila]

2008/8/4 Palmer, Ralph <[EMAIL PROTECTED]>:
> Hi -
>
> I'm working on indexing, and I have a question for those of us who use
> the function index.
>
> When looking for a command such as \repeat or \alternative, which would
> you find more helpful: having duplicate index entries (i.e., one with
> the backslash and one without) or having an entry only for the exact
> command? In other words, option 1 would have all of:
>
> \alternative
> \repeat
> alternative
> repeat
>
> while option 2 would have only
>
> \alternative
> \repeat

For me,

\alternative
\repeat% as exact commands, and then
alternatives, repeat
repeats% as common notation words

-- 
Francisco Vila. Badajoz (Spain)
http://www.paconet.org


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Indexing function codes

[Reinhold Kainhofer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am Montag, 4. August 2008 schrieb Palmer, Ralph:
> I'm working on indexing, and I have a question for those of us who use
> the function index.
>
> When looking for a command such as \repeat or \alternative, which would
> you find more helpful: having duplicate index entries (i.e., one with
> the backslash and one without) or having an entry only for the exact
> command? In other words, option 1 would have all of:
>
> \alternative
> \repeat
> alternative
> repeat
>
> while option 2 would have only
>
> \alternative
> \repeat

It depends where the \commands are sorted alphabetically. If "\alternative" is 
sorted in the position where "alternative" would appear, I'm fine with the 
second option. But if all backslashed commands are sorted into their own 
group, then I prefer the first one.

Cheers,
Reinhold

- -- 
- --
Reinhold Kainhofer, Vienna University of Technology, Austria
email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFIlxtoTqjEwhXvPN0RAob1AKDZmWlBjuU09AI7EeHZo20smfZQMQCeOvgs
lxmtn+jqS9MJvyxVq/hupAY=
=Drm4
-END PGP SIGNATURE-


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: First public release of GDP NR 2.7 Chord notation

[Andrew Hawryluk]

It looks good to me. The only nitpick that I found is that the ges in
the headword should be a fis. Thanks for your help on the docs!

Andrew

On Mon, Jul 28, 2008 at 7:53 AM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
> Dear LilyPond Users,
>
> Notation Reference Section 2.7 Chord notation of the GDP has now been
> released for public comment.  The HTML version of the document is available
> at
>
>  tml#Chord-notation>.
>
> Please take a few minutes to carefully review this section.  You may wish to
> try out a few examples, if you've not spent significant time learning to use
> \chordmode or you're unsure about chord naming conventions.  Please let me
> know if you find anything that is unclear or incorrect.
>
> The goal of the GDP is to make the quality of LilyPond's documentation match
> the quality of LilyPond's output.  However, when I write documentation,
> eventually I become blind to its weaknesses.  That's why it's so important
> for the community to review the documentation.
>
> Thanks in advance for your help.  Together, we can continue to improve
> LilyPond.
>
> Thanks,
>
> Carl Sorensen
>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user
>


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: GDP: NR 2.4 Fretted string instruments, first draft

[Andrew Hawryluk]

My only suggestion is in one of the snippets, but I can't edit it (I
guess only contributor or an LSR admin can modify).

Valentin, in the snippet "Stem and beam behavior in tablature" (#494)
can you replace
\override Beam #'damping = #10
with
\override Beam #'damping = #+inf.0

(Rune gets credit for this idea:
http://lists.gnu.org/archive/html/lilypond-user/2007-12/msg00147.html)

Andrew

On Mon, Jul 28, 2008 at 12:20 PM, Jonathan Kulp <[EMAIL PROTECTED]> wrote:
> This typo is not in the Fretted String section, but rather in 1.5.2 Multiple
> Voices.
>
> Jon
>
> Stan Sanderson wrote:
>>
>> Collision resolution section- "Known issues and warnings" there is an
>> (obvious) misspelling.
>>
>> "It is not clear in which circumpstances you can..."
>>
>> Excellent so far!
>>
>> Stan
>>
>>
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> http://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
> --
> Jonathan Kulp
> http://www.jonathankulp.com
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user
>


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: NR 1.3 Expressive marks, second draft

[Andrew Hawryluk]

This looks great!
In the trills section, could you clarify that \startTrillSpan will
always convert the subsequent music expression into grace notes and
also include an example with no visible grace notes:
  c1~\startTrillSpan s c~ c4\stopTrillSpan

Andrew




On Mon, Aug 4, 2008 at 8:55 AM, Francisco Vila <[EMAIL PROTECTED]> wrote:
> 2008/8/4 Francisco Vila <[EMAIL PROTECTED]>:
>> Measures filled of eighth notes are much prettier in my original, here
>> I suppose that the shortest common duration is 1/8, otherwise all
>> noteheads look as if they were left shifted, but I don't know where
>> exactly to put the setting. This would also fix the two fortissimos
>> crossed by the bar line.
>
> Speaking of, what if LilyPond automatically detects the most common
> shortest note per measure? Which is the default shortest note for
> spacing? I wonder it is 1/4.
> --
> Francisco Vila. Badajoz (Spain)
> http://www.paconet.org
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user
>


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: woodwind harmonics (GDP)

[Neil Puttock]

Hi Andrew,

2008/8/4 Andrew Hawryluk <[EMAIL PROTECTED]>:
> Thanks! The marks I have seen in print are about 70% of the current
> \flageolet diameter, but I don't want to trouble anybody with making
> new markups and then tweaking them to centre them over the note heads.
> I will suggest the original, unaltered articulation.

There's a snippet under Expressive which uses the Tweak_engraver to
change the \flageolet size which you could include in `Selected
snippets' for this section; it's preferable to using \markup.

Regards,
Neil


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: woodwind harmonics (GDP)

[Andrew Hawryluk]

That is marvellous. I will definitely include it.

Andrew

On Mon, Aug 4, 2008 at 11:06 AM, Neil Puttock <[EMAIL PROTECTED]> wrote:
> Hi Andrew,
>
> 2008/8/4 Andrew Hawryluk <[EMAIL PROTECTED]>:
>> Thanks! The marks I have seen in print are about 70% of the current
>> \flageolet diameter, but I don't want to trouble anybody with making
>> new markups and then tweaking them to centre them over the note heads.
>> I will suggest the original, unaltered articulation.
>
> There's a snippet under Expressive which uses the Tweak_engraver to
> change the \flageolet size which you could include in `Selected
> snippets' for this section; it's preferable to using \markup.
>
> Regards,
> Neil
>


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: NR 1.3 Expressive marks, second draft

[Patrick McCarty]

On Mon, Aug 4, 2008 at 10:05 AM, Andrew Hawryluk <[EMAIL PROTECTED]> wrote:
> This looks great!
> In the trills section, could you clarify that \startTrillSpan will
> always convert the subsequent music expression into grace notes and
> also include an example with no visible grace notes:
>  c1~\startTrillSpan s c~ c4\stopTrillSpan

I have thought about including an example without the grace notes, but
the result usually doesn't look very good.  I will try your example
though.  Thanks for the suggestion!

-Patrick


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Indexing function codes

[Trevor Daniels]

I would look for a command with the back-slash
if I knew it, or for the topic if I didn't, so
I would suggest:

@funindex \repeat
@cindex repeats

@funindex \alternative
@cindex repeat alternatives
@cindex alternative repeats
@cindex first-time bar
@cindex second-time bar

plus lots more, like,

@cindex repeats, unfolding
@cindex volta repeats
etc

Trevor

- Original Message - 
From: "Palmer, Ralph" <[EMAIL PROTECTED]>

To: 
Sent: Monday, August 04, 2008 2:07 PM
Subject: Indexing function codes


Hi -

I'm working on indexing, and I have a question for those of us who use
the function index.

When looking for a command such as \repeat or \alternative, which would
you find more helpful: having duplicate index entries (i.e., one with
the backslash and one without) or having an entry only for the exact
command? In other words, option 1 would have all of:

\alternative
\repeat
alternative
repeat

while option 2 would have only

\alternative
\repeat

Thanks for your time and attention,

Ralph

+
Ralph Palmer, CEM
Energy/Administrative Coordinator
Keene State College
Keene, NH 03435-2502
Phone: 603-358-2230
Cell: 603-209-2903
Fax: 603-358-2456
[EMAIL PROTECTED]






___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: GDP: NR 2.4 Fretted string instruments, first draft

[Jonathan Kulp]

Good call, Andrew.  This makes the beams "really" horizontal.  Thanks!

Jonathan

Andrew Hawryluk wrote:

My only suggestion is in one of the snippets, but I can't edit it (I
guess only contributor or an LSR admin can modify).

Valentin, in the snippet "Stem and beam behavior in tablature" (#494)
can you replace
\override Beam #'damping = #10
with
\override Beam #'damping = #+inf.0

(Rune gets credit for this idea:
http://lists.gnu.org/archive/html/lilypond-user/2007-12/msg00147.html)

Andrew

On Mon, Jul 28, 2008 at 12:20 PM, Jonathan Kulp <[EMAIL PROTECTED]> wrote:

This typo is not in the Fretted String section, but rather in 1.5.2 Multiple
Voices.

Jon

Stan Sanderson wrote:

Collision resolution section- "Known issues and warnings" there is an
(obvious) misspelling.

"It is not clear in which circumpstances you can..."

Excellent so far!

Stan




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


--
Jonathan Kulp
http://www.jonathankulp.com


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user



--
Jonathan Kulp
http://www.jonathankulp.com


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

RE: Indexing function codes

[Palmer, Ralph]

Thanks, Francisco, Reinhold, and Trevor -

Trevor, I've already included _lots_ of @cindex entries. The question
for me was whether to include the function itself both with and without
the backslash, or just with the backslash. Since I sometimes can
remember the name of the function, but not whether it takes the
backslash or not, and since (as Reinhold was wondering) all the
backslashes sort to one section of the index, I'm currently planning to
add both. It appears to be clear from the context in the NR whether the
backslash is required or not.

Thank you for your replies.

Peace,

Ralph



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing problem

[Joe Neeman]

On Mon, 2008-08-04 at 11:34 -0300, Han-Wen Nienhuys wrote:
> On Mon, Aug 4, 2008 at 3:18 AM, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> > It's not specific to dotted notes but to notes which have longer
> > durations, and which get squeezed far too much -- the same problem
> > occurs for, say, half notes and whole notes.  I simply want to control
> > these squeezing values globally.
> 
> The spacing is controlled by 2 values in the end: the ideal length of
> the spring, and the width of the fixed part (the remaining is the
> stretchable part).  I guess you want to increase the fixed width for
> these notes (which also decreases the stretching in case of loose
> lines - the springs are symmetric in stretch and shrink).

Actually, we can now control the stretching independently of the fixed
width. For example, in Note_spacing::get_spacing, the compression
strength of the spring depends on something that is not quite the fixed
width because we don't count flags for their full width.

Joe



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Chord spacing issues in 2.11 series

[Shamus]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Joe Neeman wrote:
| Try overriding the extra-spacing-width property on the ChordName grob
| (the extra-spacing-width property is part of the item-interface, which
| is supported by ChordName).
|
| You could also try overriding the padding property of the SeparationItem
| grob.
|
| By the way, if you attach a small example that demonstrates the problem,
| it becomes easier to help because I can test to see if my suggestions
| fix the problem.
|
| Joe

Here you go. Look at measures 1-2. The example is contrived, but I've
had situations similar to this arise quite often. The chords are too
close together for comfortable reading, especially for nearly geriatric
musicians like myself. Any help would be appreciated.

Warmest regards,
- -- Shamus

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIl6OUmE5b/O3JjkYRAg+XAKCQpRCSFoyvp66diqsRXBsCiLIuyACgwrd4
lm3LS4DsqqUOqiVZRRf+pDQ=
=VspW
-END PGP SIGNATURE-
% Pop chords as used in English/American popular music
% by James L. Hammons

% Written against \version "2.8.2"

chordFlat = \markup { \hspace #0.2 \tiny \raise #1.0 \flat }
chordSharp = \markup { \hspace #0.1 \teeny \raise #1.0 \sharp }

popChordsMusic =
{
% Triads

-\markup { "5" }
-\markup { "2" }
%   -\markup { "sus2" }
-\markup { "sus" }
%   -\markup { "sus4" }
%   -\markup { \small \raise #1.0 "o" }
-\markup { \raise #0.8 "o" }
%   -\markup { "dim" }
%   -\markup { "aug" } 
% or +

% Sixths

-\markup { "6" }
-\markup { "m6" }

% Sevenths (including altered)

-\markup { "7" }
-\markup { "m7" }
-\markup { "maj7" }
-\markup { "7sus4" }
-\markup { "7sus2" }
-\markup { "7" \chordFlat "5" }
-\markup { "7" \chordSharp "5" }
%   -\markup { "aug7" }
% or +7
-\markup { "m(maj7)" }
%   -\markup { \small \raise #1.0 { "o" } "7" }
-\markup { \raise #0.8 { "o" } "7" }
%   -\markup { "dim7" }
%   -\markup { \small \raise #1.0 { #(ly:export 
(ly:wide-char->utf-8 #x00f8)) } "7" }
%   -\markup { \raise #0.8 { #(ly:export 
(ly:wide-char->utf-8 #x00f8)) } "7" }
-\markup { "m7" \chordFlat "5" }
-\markup { "maj7" \chordFlat "5" }
-\markup { "maj7" \chordSharp "5" }

% Ninths (including altered--incomplete)

-\markup { "9" }
-\markup { "m9" }
-\markup { "maj9" }
-\markup { "add9" }
-\markup { "6/9" }
-\markup { "m6/9" }
-\markup { "m(maj9)" }
-\markup { "7" \chordFlat "9" }
-\markup { "7" \chordSharp "9" }
%dim7add9, dim7b9, dim7#9, 9#5, 9b5, maj9#5, maj9b5, 9sus4, 9sus2

% Elevenths (incomplete)

-\markup { "11" }
-\markup { "m11" }
-\markup { "maj11" }
-\markup { "add11" }
-\markup { "m add11" }
-\markup { "m7add11" }

% Thirteenths (incomplete)

-\markup { "13" }
-\markup { "m13" }
-\markup { "maj13" }
-\markup { "add13" }

% Misc add chords

-\markup { "7" \chordFlat "9" \chordFlat "13" }
-\markup { "7" \chordSharp "5" \chordFlat "9" }
-\markup { "maj9" \chordSharp "11" }
-\markup { "9" \chordSharp "11" }
}

% Add to existing exceptions
popChordsAdd = #(append
 (sequential-music-to-chord-exceptions popChordsMusic #t)
 ignatzekExceptions)

% Bah, can't we set this globally?
% \set chordNameExceptions = #popChords

% Bah, this doesn't work either...
% #(set chordNameExceptions popChords)


% Let's try fixing the accidentals with some Scheme...

#(define (chord-name->pop-markup pitch)

  (let* ((alt (ly:pitch-alteration pitch)))

  (make-line-markup
(list
  (make-simple-markup (vector-ref #("C" "D" "E" "F" "G" "A" "B") 
(ly:pitch-notename pitch)))

  ;; If it's natural, do nothing

  (if (= alt 0)

(make-line-markup (list empty-markup))

(if (= alt FLAT)

  ;; Otherwise, handle adding the flat symbol

  (make-line-markup
(list
  (make-hspace-markup 0.3) ;; WAS: 0.4
  (make-tiny-markup (make-raise-markup 1.0
(make-musicglyph-markup (string-append "accidentals." 
(number->string alt)
)
  )

  ;; or handle adding the sharp symbol

  (make-line-markup
(list
  (make-hspace-markup 0.1) ;; WAS: 0.2
  (make-teeny-markup (make-raise-markup 1.0
(make-musicglyph-markup (string-append "accidentals." 
(number->string alt)
)
  )

)

  )

)
  )

  )
)


popChords =
{
  \set chordNameExceptions = #popChordsAdd
  \set chordRoo

Re: spacing problem

[Han-Wen Nienhuys]

On Mon, Aug 4, 2008 at 7:23 PM, Joe Neeman <[EMAIL PROTECTED]> wrote:

>> The spacing is controlled by 2 values in the end: the ideal length of
>> the spring, and the width of the fixed part (the remaining is the
>> stretchable part).  I guess you want to increase the fixed width for
>> these notes (which also decreases the stretching in case of loose
>> lines - the springs are symmetric in stretch and shrink).
>
> Actually, we can now control the stretching independently of the fixed
> width. For example, in Note_spacing::get_spacing, the compression
> strength of the spring depends on something that is not quite the fixed
> width because we don't count flags for their full width.

Well, yes - I'm not saying that the fixed part of the spring exactly
equals the fixed size of the symbol.

-- 
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: color notehead according to absolute pitch

[Jay Anderson]

Kenny Stephens  yahoo.com> writes:
> Our church has a handbell group whose members are not all musically literate. 
> To
> keep themselves from having to learn to read music, they mark their notes 
> using
> differently colored highlighters.
>
> Is there a means by which I can color the notes based on its absolute pitch 
> ---
> not its pitch class? Some of the music spans three octaves. The requirements 
> are:
>   1) b4 and b5 are different colors.
>   2) b\flat4 and b4 are different colors.
>   3) different pitches can be assigned to the same color (some "ringers" play
> two or more handbells).
>
> I've only been playing around with Lilypond for about a week (though I've 
> logged
> numerous hours) for typesetting organ music; but this is different. I did find
> an example using Scheme and 'staff-position,' but this fails condition 1.
>
> Ideas, suggestions or solutions would be appreciated.

Using the same idea as the example you mentioned
(http://lilypond.org/doc/v2.11/Documentation/user/lilypond-learning/Advanced-tweaks-with-Scheme)
you can base the color on the pitch:

#(define (color-notehead grob)
  (pitch-to-color (ly:event-property (ly:grob-property grob 'cause) 'pitch)))

Now you'd just have to figure out how to implement the pitch-to-color
function. For example this colors all the flat notes blue:

#(define (pitch-to-color pitch)
  (if (eqv? (ly:pitch-alteration pitch) -1/2) (x11-color 'blue)))

You might want to get a little fancy to make sure enharmonic spellings
of the same pitch are the same color, but for most cases that
shouldn't be a problem.

-Jay


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user