Re: Enhancement request

2010-03-19 Thread Carl Sorensen 
On 3/19/10 8:40 AM, "Phil Holmes"  wrote:

> According to the documentation for 2.12.3 "There is no support for chords
> where the same note occurs with different accidentals in the same chord."  I
> have a situation where this is required and would like to add it as an
> enhancement request.

I've copied this to bug-lilypond so an issue can get made on the tracker,
but I doubt this will get worked on in the near future.

As a workaround, you can move out of chord mode into note mode and enter the
chord explicitly:



This works just fine, but the naming is a bit off right now.

HTH,

Carl



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

Re: Enhancement request

2010-03-20 Thread Mats Bengtsson 

Quoting Carl Sorensen :


On 3/19/10 8:40 AM, "Phil Holmes"  wrote:


According to the documentation for 2.12.3 "There is no support for chords
where the same note occurs with different accidentals in the same chord."  I
have a situation where this is required and would like to add it as an
enhancement request.


I've copied this to bug-lilypond so an issue can get made on the tracker,
but I doubt this will get worked on in the near future.


This issue has been discussed on the mailing lists several times over 
the years. The first question is what layout such a feature would use. 
One option is shown in http://lsr.dsi.unimi.it/LSR/Item?id=505, but I 
guess there's no single established typesetting practice for these 
situations.


  /Mats



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

Re: Enhancement request

2010-03-20 Thread Bernard Hurley 
On Sat, Mar 20, 2010 at 12:39:14PM +0100, Mats Bengtsson wrote:
> Quoting Carl Sorensen :
>
>> On 3/19/10 8:40 AM, "Phil Holmes"  wrote:
>>
>>> According to the documentation for 2.12.3 "There is no support for chords
>>> where the same note occurs with different accidentals in the same chord."  I
>>> have a situation where this is required and would like to add it as an
>>> enhancement request.
>>
>> I've copied this to bug-lilypond so an issue can get made on the tracker,
>> but I doubt this will get worked on in the near future.
>
> This issue has been discussed on the mailing lists several times over  
> the years. The first question is what layout such a feature would use.  
> One option is shown in http://lsr.dsi.unimi.it/LSR/Item?id=505

This is the way one sees this in a lot of Stravinsky scores and seems fairly 
common. If this layout were used to start with, others could be added as 
options later if there is any call for them.

Bernard


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

Re: Enhancement request

2010-03-20 Thread Kieren MacMillan 
Hi Phil,

> The attached image is how this appears in the Chappell version of "The 
> Mikado".

Your example isn't technically a situation where "the same note occurs with two 
different accidentals in the same chord" -- it has two different voices!

Cheers,
Kieren.

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

Re: Enhancement request

2010-03-20 Thread Kieren MacMillan 
Hi Phil,

> understood it to mean that when there are 2 notes in 2 voices but which have 
> the same fundamental note, only differing in an accidental, then LilyPond 
> doesn't support this.

Nope -- but we should adjust the documentation if it's unclear.

> I do have the chords set in different voices and it shows as in the attached 
> clip - it incorrectly makes the first note of the 2nd voice a natural.

That's a different issue:

\score {
  \new Staff <<
\new Voice { \voiceOne fis'8[ g'] }
\new Voice { \voiceTwo #(set-accidental-style 'voice) 8[ ] }
  >>
}

See 

 for more information.

Hope this helps!
Kieren.

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

Re: Enhancement request

2010-03-20 Thread Carl Sorensen 
On 3/20/10 9:43 AM, "Kieren MacMillan" 
wrote:

> Hi Phil,
> 
>> understood it to mean that when there are 2 notes in 2 voices but which have
>> the same fundamental note, only differing in an accidental, then LilyPond
>> doesn't support this.
> 
> Nope -- but we should adjust the documentation if it's unclear.
> 
>> I do have the chords set in different voices and it shows as in the attached
>> clip - it incorrectly makes the first note of the 2nd voice a natural.
> 
> That's a different issue:
> 
> \score {
>   \new Staff <<
> \new Voice { \voiceOne fis'8[ g'] }
> \new Voice { \voiceTwo #(set-accidental-style 'voice) 8[ ] }
>>> 
> }

It seems to me that this is a bug; the fis' and the f' are not the same
note, and therefore the note-heads should not be merged.

Thanks,

Carl



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

Re: Enhancement request

2010-03-20 Thread Kieren MacMillan 
Hi Carl,

> It seems to me that this is a bug; the fis' and the f' are not the same
> note, and therefore the note-heads should not be merged.

Yes, *that's* the bug (not the accidental handling).  =)

For the record, I [quickly] tried a number of shifting attempts, but couldn't 
duplicate the original sample -- both accidentals kept shifting with the 
left-most note column.

Cheers,
Kieren.

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

Re: Enhancement request

2010-06-20 Thread Phil Holmes 
Added to the tracker as 
http://code.google.com/p/lilypond/issues/detail?id=1134


--
Phil Holmes
Bug Squad


"Kieren MacMillan"  wrote in message 
news:blu0-smtp29bccfd7e138e2118598f594...@phx.gbl...

Hi Carl,


It seems to me that this is a bug; the fis' and the f' are not the same
note, and therefore the note-heads should not be merged.


Yes, *that's* the bug (not the accidental handling).  =)

For the record, I [quickly] tried a number of shifting attempts, but 
couldn't duplicate the original sample -- both accidentals kept shifting 
with the left-most note column.


Cheers,
Kieren.= 




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

Re: Enhancement Request for Lilygit-Tcl

2010-12-16 Thread Graham Percival 
On Thu, Dec 16, 2010 at 01:27:16PM +, James wrote:
> 
> > On 15/12/2010 17:57, Carl Sorensen wrote:
> >
> > On 12/15/10 10:50 AM, "James"  wrote:
> >
> >> Now if we could configure LilyGit.tcl to have another button to 'compile
> >> (doc) for the first time'
> >>
> >> It could run ./autogen.sh and then make ; make doc.
> >>
> >
> > Please add it as an enhancement request.  We may be able to do it
> (although
> > it might only work for lilybuntu, so we may not *want* to do it).
> I think
> > some discussion would be very helpful.

I disagree.  The new CG 3.1 compiling with lilybuntu   should be
so incredibly clear that there's no doubt whatsoever.  (I'm not
saying that the new section *is* incredibly clear yet; just that
it *should* be)

If there's evidence that contributors find this confusing, even
after a couple of rounds of drafts, then I may re-evaluate.  But
at the moment, I forsee little benefit to adding this to
lily-git.tcl.

Cheers,
- Graham

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

Re: Enhancement request: alternative segno symbol

2008-08-17 Thread Werner LEMBERG 

> as remarked on the user list and seconded by Werner, I propose a new
> symbol for dal segno, as shown in the attached pictures, which is
> not in the current feta font.

Registered as #659.

  http://code.google.com/p/lilypond/issues/detail?id=659

Thanks.


Werner


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

Re: [Enhancement request] NoteNames speaks only Dutch

2012-06-24 Thread -Eluze 


Jean-Charles Malahieude-2 wrote:
> 
> Hi all,
> 
> How would it be possible for the note-Name-engraver to change his mind 
> thanks to an additional argument or, at least, adopt the specified
> language?
> 
> \language "italiano"
> scale = \relative do' {
>lab4 sid dobb redd
>mi4 fa solb lad
> }
> 
> \new Staff {
><<
>  \scale
>  \context NoteNames {
>\scale
>  }
>>>
> }
> 
> gives: aes bis ceses disis e f ges ais
> 
> I was expecting at least: lab sid dobb redd mi fa solb lad
> 
> 

so would I!

there's already an issue with that topic:
https://code.google.com/p/lilypond/issues/detail?id=1367&can=1&q=NoteNames&colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary

Eluze
-- 
View this message in context: 
http://old.nabble.com/-Enhancement-request--NoteNames-speaks-only-Dutch-tp34059728p34063158.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: [Enhancement request] NoteNames speaks only Dutch

2012-06-24 Thread Colin Hall 
On Sat, Jun 23, 2012 at 08:06:37PM +0200, Jean-Charles Malahieude wrote:
> Hi all,
> 
> How would it be possible for the note-Name-engraver to change his
> mind thanks to an additional argument or, at least, adopt the
> specified language?
> 
> \language "italiano"
> scale = \relative do' {
>   lab4 sid dobb redd
>   mi4 fa solb lad
> }
> 
> \new Staff {
>   <<
> \scale
> \context NoteNames {
>   \scale
> }
>   >>
> }
> 
> gives: aes bis ceses disis e f ges ais
> 
> I was expecting at least: lab sid dobb redd mi fa solb lad

Thanks for the suggestion, Jean-Charles.

Thanks also to Eluze for spotting that this enhancement was already requested 
and accepted as issue tracker 1367.

http://code.google.com/p/lilypond/issues/detail?id=1367

I've added a comment linking back to your bug report, Jean-Charles.

Cheers,
Colin.

-- 

Colin Hall

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request - lookup of sub-properties

2013-01-04 Thread Marek Klein 
Hello,

2013/1/4 Nick Payne 

> See comment 13 of issue 3056:
> http://code.google.com/p/lilypond/issues/detail?id=3056. At the moment,
> when constructing an event function for a text spanner, one can't rely on
> using ^ or _ to set the direction of the spanner if one wants to tweak
> bound-details.right.text according to the direction, as that sub-property
> is not looked up - the direction has to be passed as an additional
> parameter - see comment 7 as an example of doing that.
>

Thank you for the report, it has been added as
http://code.google.com/p/lilypond/issues/detail?id=3086

Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request: automatic polyphony in TabStaff context

2009-08-20 Thread Valentin Villenave 
2009/8/13 Patrick Schmidt :
> quite handy (and logical) if it were possible to apply << {} \\ {} >> to
> tabVoice if it's in a tabStaff context (especially when the piece doesn't
> contain an awful lot of polyphonic bars).

Note to myself:
Marc has a patch about this on
http://lists.gnu.org/archive/html/lilypond-user/2009-08/msg00588.html

If it doesn't get applied within two days, I'll open a tracker page
and mark it as Started.

Valentin


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

Re: Enhancement request: Automatic glissando marks in chords

2009-08-20 Thread Valentin Villenave 
2009/8/13 Patrick Schmidt :
> From my point of view it would be more intuitive if it were possible to set
> glissandi in chords just the way ties are set, e.g.: \glissando a>
> resulting in one glissando mark for each voice in chords. But this is
> probably hard to implement ...

Yes, we already have it in our tracker:
http://code.google.com/p/lilypond/issues/detail?id=291

Thanks anyway :)

Regards,
Valentin


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

Re: Enhancement request: stretched text in text spanners

2013-05-22 Thread Ralph Palmer 
On Wed, May 15, 2013 at 7:51 AM, Peter Toye  wrote:

> I want to put text like rallen---tan---do into some music. I've
> noticed that the mailing list also had someone who wanted to put
> cres---cendo similarly.
>
> The current text spanner cannot do this, and various people have suggested
> workarounds. The main problem is that with a simple text spanner, each item
> of text is separate from the next, and the heights can vary.
>
> I'm a newbie to Lilypond, so I'm afraid that I can't really help by
> suggesting a syntax for a replacement that would be compatible with LP's
> design methods, but I'm sure that someone here can do this!


Greetings, Peter Toye -

This has been added as Issue 3373 :
https://code.google.com/p/lilypond/issues/detail?id=3373

Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request: point-and-click for clefs

2016-09-10 Thread Thomas Morley 
2016-09-10 22:34 GMT+02:00 Simon Albrecht :
> Hello everybody,
>
> currently, clef changes (as in { 1 \clef F 1 }) don’t have point-and-click
> support. However, this would sometimes be useful to have. I’d open an issue,
> but maybe it’s better to ask first: What are the technical reasons? Or is it
> not there by design?
>
> Best, Simon



There is `pointAndClickTypes', but it expects an event. And we don't
have a clef-event...
Same problem as for quoting/cues concerning BarLines and probably others.

Cheers,
  Harm

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request: point-and-click for clefs

2016-09-10 Thread Simon Albrecht 

On 10.09.2016 23:54, Thomas Morley wrote:

2016-09-10 22:34 GMT+02:00 Simon Albrecht :

Hello everybody,

currently, clef changes (as in { 1 \clef F 1 }) don’t have point-and-click
support. However, this would sometimes be useful to have. I’d open an issue,
but maybe it’s better to ask first: What are the technical reasons? Or is it
not there by design?

Best, Simon

There is `pointAndClickTypes', but it expects an event. And we don't
have a clef-event...
Same problem as for quoting/cues concerning BarLines and probably others.


Then I’d like if we don’t take that obstacle for granted. Why don’t we 
have an event? I can imagine the reason: because the clef or bar line 
isn’t actually a musical event, but only an element of visualisation… as 
for the clef also because it mainly changes some context properties… But 
either we be so pragmatic and make them be Events nevertheless (maybe 
such as aren’t carried into Midi, or are they?), or we need to ask: why 
does it need an event for point-and-click?


Best, Simon

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request: point-and-click for clefs

2016-09-12 Thread Paul 

On 09/10/2016 07:54 PM, Simon Albrecht wrote:

Then I’d like if we don’t take that obstacle for granted. Why don’t we 
have an event? I can imagine the reason: because the clef or bar line 
isn’t actually a musical event, but only an element of visualisation… 
as for the clef also because it mainly changes some context 
properties… But either we be so pragmatic and make them be Events 
nevertheless (maybe such as aren’t carried into Midi, or are they?), 
or we need to ask: why does it need an event for point-and-click?


It always seemed odd to me that there wasn't a clef event.  It would be 
nice to have point-and-click for clefs, but I can't claim to understand 
the larger implementation implications one way or another.


-Paul

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request: point-and-click for clefs

2016-09-12 Thread David Kastrup 
Paul  writes:

> On 09/10/2016 07:54 PM, Simon Albrecht wrote:
>
>> Then I’d like if we don’t take that obstacle for granted. Why don’t
>> we have an event? I can imagine the reason: because the clef or bar
>> line isn’t actually a musical event, but only an element of
>> visualisation… as for the clef also because it mainly changes some
>> context properties… But either we be so pragmatic and make them be
>> Events nevertheless (maybe such as aren’t carried into Midi, or are
>> they?), or we need to ask: why does it need an event for
>> point-and-click?
>
> It always seemed odd to me that there wasn't a clef event.  It would
> be nice to have point-and-click for clefs, but I can't claim to
> understand the larger implementation implications one way or another.

Clefs are incidental.  If you have

phrase = { \clef "bass" ... }

<<
  \new Staff { \clef "treble" ... \phrase \clef "treble" ... }
  \new Staff { \clef "bass" ... \phrase \clef "bass" ... }
>>

then the second insertion of \phrase does not show repeated clefs.  They
appear when at least one of a set of properties changes.  Such changes
are detected at a time where the property-changing command itself is no
longer available.

I think that we did something for \time which is implemented in a
somewhat similar way.

-- 
David Kastrup

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request: scheme function to scale a stencil

2009-10-29 Thread Valentin Villenave 
On Wed, Oct 28, 2009 at 12:25 PM, Robin Bannister  wrote:
>        I feel that these two should be complemented by a third
> transformation along the lines of the postscript operator:  x y scale.

Nice idea! Added as http://code.google.com/p/lilypond/issues/detail?id=888

Cheers,
Valentin


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

Re: Enhancement request: make-markup-command cleanup and docs

2009-12-20 Thread Valentin Villenave 
On Sun, Dec 20, 2009 at 11:01 AM, David Kastrup  wrote:
> The current state of make-markup-command is less than satisfactory since
> make-markup-command and make-builtin-markup-command have different
> syntaxes and semantics, making the latter an "insider" command that
> complicates the transition from advanced user to Lilypond contributor.

Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=941

Cheers,
Valentin


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

Re: Enhancement request: make-markup-command cleanup and docs

2009-12-21 Thread David Kastrup 
Valentin Villenave  writes:

> On Sun, Dec 20, 2009 at 11:01 AM, David Kastrup  wrote:
>> The current state of make-markup-command is less than satisfactory since
>> make-markup-command and make-builtin-markup-command have different
>> syntaxes and semantics, making the latter an "insider" command that
>> complicates the transition from advanced user to Lilypond contributor.
>
> Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=941

It appears that Nicolas dived in and did all of the listed job.  As a
somewhat related cleanup, independent documentation has become simpler.
After checking for disappearance of the described features in the code
with grep, I came up with the following cleanup.  If there is need for a
more elaborate form (git commit message, reviewable patch on Rietveld)
or similar, please holler.  This was just easiest to do right now.

diff --git a/Documentation/contributor/programming-work.itexi b/Documentation/contributor/programming-work.itexi
index 936057d..f9e8c60 100644
--- a/Documentation/contributor/programming-work.itexi
+++ b/Documentation/contributor/programming-work.itexi
@@ -1250,37 +1250,26 @@ foo = 1
 @end example
 
 @noindent with @code{\paper}, @code{\midi} and @code{\header} being
-nested scope inside the .ly file-level scope.  @w...@code{foo = 1}} is
-translated in to a scheme variable definition.
+nested scope inside the @file{.ly} file-level scope.  @w...@code{foo = 1}}
+is translated in to a scheme variable definition.
 
 This implemented using modules, with each scope being an anonymous
 module that imports its enclosing scope's module.
 
-The reason to put some functions (@qq{builtin}) outside the .ly level,
-is that in case of
+Lilypond's core, loaded from @file{.scm} files, is usually placed in the
+...@code{lily} module, outside the @file{.ly} level.  In the case of
 
 @example
 lilypond a.ly b.ly
 @end example
 
 @noindent
-we want to reuse the built-in definitions, without changes
-effected in a.ly leaking into the processing of b.ly.
-
-Maintaining this scoping when one .ly file can be included in another
-.ly file can be challenging.  A @code{define-public-toplevel} macro
-has been created in order to handle a difficulty caused by the modules
-being not the same when a .ly file is included into another.
-This provided a way to define all markup commands in the same module.
-At this time, we have found no easier way to define a function in a given
-module (not the current one) than to define this macro.
-
-With this architecture, the guile module system is not bypassed:
-module-define!, module-export!  and module-ref are all guile module
-primitives.
-
-A second reason for using this current architecture is to avoid memory
-leaks that could occur when running multiple files if toplevel
-functions were registered permanently.
-
-
+we want to reuse the built-in definitions, without changes effected in
+user-level @file{a.ly} leaking into the processing of @file{b.ly}.
+
+The user-accessible definition commands have to take care to avoid
+memory leaks that could occur when running multiple files.  All
+information belonging to user-defined commands and markups is stored in
+a manner that allows it to be garbage-collected when the module is
+dispersed, either by being stored module-locally, or in weak hash
+tables.


-- 
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request: LilyPond GUI for Mac OS X

2012-05-23 Thread Marek Klein 
Hello Raphael,

2012/5/23 Raphael Frey 

> It would be great if the LilyPond GUI for Mac OS X could be enhanced
> with following features:
>
> * syntax highlighting
> * option to adjust tab stop width and insert spaces instead of tabs
>

See this paragraph from http://lilypond.org/text-input.html :

> Easier editing environments
>
> LilyPond is primarily concerned with producing top-quality engraved sheet
> music; creating a Graphical User Interface (GUI) would distract us from
> this goal. However, there are other projects aimed at making it easier to
> create LilyPond input files.
>
> Some editing environments include syntax highlighting, automatic command
> completion, and pre-made templates. Other programs actually provide a GUI
> which allows direct manipulation of a graphical score. For more
> information, see Easier editing .
>
>
There are some efforts to create installer of Frescobaldi for Mac OS X, you
can read about it in this thread:
http://lists.gnu.org/archive/html/lilypond-user/2012-03/msg00635.html

HTH

Marek,
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request for web page http://lilypond.org/manuals.html

2012-10-12 Thread Graham Percival 
On Fri, Oct 12, 2012 at 06:15:23PM +, Jim Long wrote:
> The following patches to http://lilypond.org/manuals.html illustrate a design
> mock-up of how the manuals.html page might look after 

Thanks for the mock-up, but that design makes the page much
"busier" and doesn't allow the reader to see all manuals on the
same screen at once.

I suggest adding a table like on the community->development
webpage to the manuals->all page.  That way, new readers will see
the current nice design, while experienced users could just
bookmark the "all" page.

- Graham

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request for web page http://lilypond.org/manuals.html

2012-10-12 Thread Marek Klein 
Hello,
2012/10/12 Jim Long 

> Recently and historically, several users have commented that the web page
> at
> reference could be enhanced by having conspicuous links to downloadable PDF
> versions of the lilypond documentation.
>
> The following patches to http://lilypond.org/manuals.html illustrate a
> design
> mock-up of how the manuals.html page might look after
>

Thank you for your proposal, this has been added as
http://code.google.com/p/lilypond/issues/detail?id=2895

Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request/partial patch: Document the MIDI backend

2012-12-03 Thread Colin Hall 
On Sun, Dec 02, 2012 at 12:00:11PM +0100, Johannes Rohrer wrote:
> Dear LilyPond developers,
> 
> a month ago, on a tangent to the Issue #687 discussion 
> , I got tempted 
> to have a look at the LilyPond MIDI backend, only to be scared away by 
> the utter lack of documentation.
> 
> However, I have looked again a few times since then. Now I would like to 
> file a wish to improve that situation, and offer some help.
> 
> At least, I would like to see the following enhancements:
> 
> 1. Improve performer documentation in the Internals Reference to 
> engraver standards:
> 
>a) document performer/context relations as specified
>   in ly/performer-init.ly
> 
>b) document which music types are accepted by performers
> 
>c) document Audio Items (analogously to grobs) produced by performers
> 
> 2. Provide at least a short MIDI backend overview in the Contributor's 
> Guide.
> 
> 
> Here is a patch that implements 1 a) and b).
> 
> 
> 
> Should you accept it, I am ready to tackle 1 c).
> 

Thanks very much for the patch, Johannes. It seems that this doc
enhancement is distinct from all the other recent work on MIDI and so
I have created tracker 3003 for it.

http://code.google.com/p/lilypond/issues/detail?id=3003

Cheers,
Colin.

-- 

Colin Hall

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: enhancement request, page-breakers account for requested system spacing

2010-10-28 Thread Joe Neeman 
On Thu, Oct 28, 2010 at 1:22 PM, Keith E OHara  wrote:

> Dear but list,
>
> Current behavior (2.12 and 2.13) is to populate pages with as many systems
> as will fit with tight spacing, meaning that only the last page has enough
> space to honor the requested system-system-spacing #'space.
>

You're too late. This was already fixed as part of bug 1285, so it will
appear in 2.13.38.

Cheers,
Joe
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: enhancement request, page-breakers account for requested system spacing

2010-10-28 Thread Keith E OHara 

On Thu, 28 Oct 2010 14:26:26 -0700, Joe Neeman  wrote:


You're too late. This was already fixed as part of bug 1285, so it will
appear in 2.13.38.


Thanks!
Surely, I must have read your clear explanation attached to 1285,
but today I misremembered this use of 'space as something I wanted to try out 
on -37.

That's a symptom of filling the brain too fast with new concepts, so this 
evening I'll take time to re-read the same old concepts in the new form of 
Mark's latest doc revision.
-Keith


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

Re: enhancement request, page-breakers account for requested system spacing

2010-10-29 Thread David Kastrup 
"Keith E OHara"  writes:

> Dear but list,
>
> Current behavior (2.12 and 2.13) is to populate pages with as many
> systems as will fit with tight spacing, meaning that only the last
> page has enough space to honor the requested system-system-spacing
> #'space.

Oh, by the way: it would be nice to have an option to let Lilypond use
the same space stretching on the last page (in case it fits) than on the
last non-ragged-bottom page.  It really does not make much aesthetical
sense to have just the last page tighter than the rest if the gained
bottom space is not actually required for anything.

-- 
David Kastrup


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

Re: enhancement request, page-breakers account for requested system spacing

2010-10-29 Thread Xavier Scheuer 
On 29 October 2010 09:56, David Kastrup  wrote:
>
> Oh, by the way: it would be nice to have an option to let Lilypond use
> the same space stretching on the last page (in case it fits) than on the
> last non-ragged-bottom page.  It really does not make much aesthetical
> sense to have just the last page tighter than the rest if the gained
> bottom space is not actually required for anything.

Agree.
And if this is possible, then I'd vote to make this the default
behaviour.

Cheers,
Xavier

-- 
Xavier Scheuer 

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

Re: enhancement request, page-breakers account for requested system spacing

2010-11-02 Thread Keith E OHara 

On Thu, 28 Oct 2010 14:26:26 -0700, Joe Neeman  wrote:


On Thu, Oct 28, 2010 at 1:22 PM, Keith E OHara  wrote:

Current behavior (2.12 and 2.13) is to populate pages with as many systems
as will fit with tight spacing, meaning that only the last page has enough
space to honor the requested system-system-spacing #'space.



You're too late. This was already fixed as part of bug 1285, so it will
appear in 2.13.38.



This aspect of the 1285 fix (listening to 'space) did not make it into the 
2.13.38 alpha release, judging by its behavior.

That is,  { \clef bass \repeat unfold 25 {s1 \break} }  still squeezes staves 
on first page 8 staffspaces apart ('minimum-distance) while the second page is 
spaced at 12 ('space).

I will assume the change will come in a future release, and until then continue 
the workaround of copying 'space to 'minimum-distance :
\paper { page-breaking-system-system-spacing = #'(
  (space . 12) (minimum-distance . 12) (padding . 1)) }


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

Re: enhancement request, page-breakers account for requested system spacing

2010-11-02 Thread David Kastrup 
Valentin Villenave  writes:

> On Fri, Oct 29, 2010 at 9:56 AM, David Kastrup  wrote:
>
> Greetings David,
>
>> Oh, by the way: it would be nice to have an option to let Lilypond use
>> the same space stretching on the last page (in case it fits) than on the
>> last non-ragged-bottom page.  It really does not make much aesthetical
>> sense to have just the last page tighter than the rest if the gained
>> bottom space is not actually required for anything.
>
> Added as http://code.google.com/p/lilypond/issues/detail?id=1377
>
> (An example of a score where disabling ragged-last-bottom produces
> unnecessarily tight spacing would be nice to illustrate this request,
> though. -- I'm sure it's just me, but I had to read your proposal a
> number of times before beginning to understand what you were
> suggesting.)

Uh, your description of the example does not make me confident that you
did understand what I have been trying to say.  If I take the artistic
liberty of using the horizontal whitespace in a line to symbolize the
vertical filling of the page, the objectionable (default) behavior is

system   system   system|(end of page 1)
system   system   system|(end of page 2)
system system   |(end of page 3)

-- 
David Kastrup

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

Re: enhancement request, page-breakers account for requested system spacing

2010-11-02 Thread Valentin Villenave 
On Fri, Oct 29, 2010 at 9:56 AM, David Kastrup  wrote:

Greetings David,

> Oh, by the way: it would be nice to have an option to let Lilypond use
> the same space stretching on the last page (in case it fits) than on the
> last non-ragged-bottom page.  It really does not make much aesthetical
> sense to have just the last page tighter than the rest if the gained
> bottom space is not actually required for anything.

Added as http://code.google.com/p/lilypond/issues/detail?id=1377

(An example of a score where disabling ragged-last-bottom produces
unnecessarily tight spacing would be nice to illustrate this request,
though. -- I'm sure it's just me, but I had to read your proposal a
number of times before beginning to understand what you were
suggesting.)

Cheers,
Valentin.

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

Re: enhancement request, page-breakers account for requested system spacing

2010-11-05 Thread Joe Neeman 
On Tue, Nov 2, 2010 at 1:02 AM, Keith E OHara  wrote:

> On Thu, 28 Oct 2010 14:26:26 -0700, Joe Neeman 
> wrote:
>
>  On Thu, Oct 28, 2010 at 1:22 PM, Keith E OHara 
>> wrote:
>>
>>> Current behavior (2.12 and 2.13) is to populate pages with as many
>>> systems
>>> as will fit with tight spacing, meaning that only the last page has
>>> enough
>>> space to honor the requested system-system-spacing #'space.
>>>
>>>
>> You're too late. This was already fixed as part of bug 1285, so it will
>> appear in 2.13.38.
>>
>>
> This aspect of the 1285 fix (listening to 'space) did not make it into the
> 2.13.38 alpha release, judging by its behavior.
>

Yup, it looks like I forgot to push some of it. It should be in 2.13.39.

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

Re: Enhancement request -- make TabStaff work properly with non-monotonic stringTunings

2008-10-29 Thread Valentin Villenave 
2008/10/29 Carl D. Sorensen <[EMAIL PROTECTED]>:

> I'm posting this because I don't think this change should be made before
> 2.12, but I want to have something to tickle my memory.

OK, let's do the tickling on
http://code.google.com/p/lilypond/issues/detail?id=703

:-)

Cheers,
Valentin


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