Frescobaldi Preview Modes
Dear friends, some people asked for a simple way to disable the preview debug modes in current git (2.0.12dev) for a while without unselecting all the checkboxes, but keeping the point and click links (i.e. the good old Preview mode). Also some wished that point and click could be disabled for a while, while keeping some preview debug options, hence the maybe somewhat confusing option "Disable Point and Click links" in the preview mode panel. What do you think of a third main mode: - Preview mode (just point and click, as it has been) - Publish mode (no point and click) - Debug mode: this mode listens to the settings in the Debug mode panel. Also settings like: Verbose and English Messages (currently in Preferences) could move to the debug panel. The debug panel should get a title like "Debugging options". The custom engrave dialog and the LilyPond preferences page can be simplified a little then. Shall I do it? Please give me green light :) -- Wilbert Berendsen http://www.wilbertberendsen.nl/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi Preview Modes
Am 29.10.2013 09:49, schrieb Wilbert Berendsen: Dear friends, some people asked for a simple way to disable the preview debug modes in current git (2.0.12dev) for a while without unselecting all the checkboxes, but keeping the point and click links (i.e. the good old Preview mode). Also some wished that point and click could be disabled for a while, while keeping some preview debug options, hence the maybe somewhat confusing option "Disable Point and Click links" in the preview mode panel. What do you think of a third main mode: - Preview mode (just point and click, as it has been) - Publish mode (no point and click) - Debug mode: this mode listens to the settings in the Debug mode panel. Also settings like: Verbose and English Messages (currently in Preferences) could move to the debug panel. The debug panel should get a title like "Debugging options". The custom engrave dialog and the LilyPond preferences page can be simplified a little then. Shall I do it? Please give me green light :) This sounds good, I like the conceptual separation of Preview and Debug mode. But I have one question: How would Debug mode relate to point-and-click? Janek's request was to compile in Debug mode (as of your new suggestion) and be able to switch point-and-click independently from this. My suggestion [if that's not what you intended anyway] is to have a Point-and-Click option on the Debug panel (the contrary of the current way to _disable_ point-and-click). So this would be a checkbox that is usually checked but can be unchecked on demand. In addition I suggest adding a tool button on the panel to compile in debug mode. While of course shortcuts are most convenient to trigger compilation it is rather probable that one is on the panel already before compiling. If you start doing that I will keep my hands off from that area for a while. (Git is cool but if one can help preventing conflicts ...) Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] Re: Frescobaldi Preview Modes
op 29-10-13 10:06, Urs Liska schreef: Am 29.10.2013 09:49, schrieb Wilbert Berendsen: Dear friends, some people asked for a simple way to disable the preview debug modes in current git (2.0.12dev) for a while without unselecting all the checkboxes, but keeping the point and click links (i.e. the good old Preview mode). Also some wished that point and click could be disabled for a while, while keeping some preview debug options, hence the maybe somewhat confusing option "Disable Point and Click links" in the preview mode panel. What do you think of a third main mode: - Preview mode (just point and click, as it has been) - Publish mode (no point and click) - Debug mode: this mode listens to the settings in the Debug mode panel. Also settings like: Verbose and English Messages (currently in Preferences) could move to the debug panel. The debug panel should get a title like "Debugging options". The custom engrave dialog and the LilyPond preferences page can be simplified a little then. Shall I do it? Please give me green light :) This sounds good, I like the conceptual separation of Preview and Debug mode. But I have one question: How would Debug mode relate to point-and-click? Janek's request was to compile in Debug mode (as of your new suggestion) and be able to switch point-and-click independently from this. My suggestion [if that's not what you intended anyway] is to have a Point-and-Click option on the Debug panel (the contrary of the current way to _disable_ point-and-click). So this would be a checkbox that is usually checked but can be unchecked on demand. Indeed! And also checks for verbose mode and maybe english messages (although I'll keep that last one also in the prefs, I presume some people prefer the english LilyPond messages) In addition I suggest adding a tool button on the panel to compile in debug mode. While of course shortcuts are most convenient to trigger compilation it is rather probable that one is on the panel already before compiling. Yes, I also thought of this. I will also make a menu action that could be set to a shortcut. But the same action will be put as a button on the debug mode panel. If you start doing that I will keep my hands off from that area for a while. (Git is cool but if one can help preventing conflicts ...) I will do it. I already did some reorganization to make multiple mainwindows with different debug mode settings working correctly. Thanks! Wilbert -- Wilbert Berendsen http://www.wilbertberendsen.nl/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to combine accidental glyphs for new note names?
On 29.10.2013, at 07:52, ArnoldTheresius wrote:
> Hello,
> I see two options:
>
> 1. Build your own font which includes the additional glyphs (and all the
> other accidental glyphs, too).
> Then make LILYPOND use this new font for all accidentals.
>
> 2. Replace the stencil function of the Accidentals by your own scheme
> procedure.
> This will return your "combined stencil" for your additions, but will call
> the original stencil function for all the other standard glyphs. I expect,
> you will have to "wrap" some other callback functions of this GROB in the
> same way.
>
> You may find some more information how to solve it if your search for:
> sagittal (uses microtonal accidentals from an extra font)
> lilyJAZZ (also uses it's own notation font, as far as I've noticed)
> bold tenuto in the LSR (wraps the stencil function for articulations to
> return stencils build of simple geometry for tenuto and portato)
>
> I hope, this information will help you to proceed,
> ArnoldTheresius
Hi Arnold,
thanks for your hints!
MeanwhileI found a third solution. It's somewhat dirty but it does the
(visual) job without me having to define new note names. So in case someone
runs into the same problem:
\version "2.17.29"
sharpdoublesharp = {
\once \override Accidental.stencil = #ly:text-interface::print
\once \override Accidental.text = \markup {
\concat {
\musicglyph #"accidentals.sharp"
\musicglyph #"accidentals.doublesharp"
}
}
\once \override Staff.AccidentalPlacement #'right-padding = #1.25
}
{
\sharpdoublesharp
cisis'
}
cheers
patrick
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RhythmicStaff followed by Staff in the same score block
Yes i did understund that..and i used it quite well..
what i wanted to do was:
\score {
<<
\new ChordNames { c1 }
\new RhythmicStaff { s1 }
\new Lyrics { \lyricmode { What8 a ni -- ce day2 } }
>>
\layout {}
}
\score {
<<
\new ChordNames { g1 }
\new Staff { c'4 d' e' f' }
\addlyrics { It's a ni -- ce }
>>
\layout {}
}
to be in a same score block..so i dont wast paper with empty staff..
i will try something out combing difrenet barlines..
On 10/28/2013 06:26 PM, Trevor Daniels wrote:
Stjepan Horvat wrote Monday, October 28, 2013 4:38 PM
Hi guys..Is this possible..
I'm dealing with speaking music which has chords and duration..something
like poetry over music..and afterwords singing parts..
i know that i can separate score blocks but it would be better if it
could be in the same..then i wouldnt have problems with bar numbers and
\mark \default staff..
thanks..
Possible, but can be tricky. See
http://www.lilypond.org/doc/v2.17/Documentation/notation/opera-and-stage-musicals#dialogue-over-music
for a starting point.
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: New "make-path-stencil" function
On Tue, Oct 29, 2013 at 1:48 AM, David Kastrup wrote: > > In the process of working on adding niente circles to Ferneyhough > hairpins > > (Issue 3357), I noticed that these hairpins don't work with line breaks. > > (They are simply duplicated.) The routine which draws them uses > > make-connected-path-stencil. Since the latter starts everything from (0 > > 0), you can't draw broken pieces which are open at both ends. > > Why not? You know about ly:translate-stencil, right? Well, sure. Guess I shouldn't have written "can't". I just thought it would be a bit simpler with such a function. --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: On creating "title pages" and the like
I ran convert-ly -ed as suggested, and then ran lilypond on the resulting file to have a look at the embedded example. Here's the resulting error message (lilypond 2.16.2 on OSX 10.6.8): Processing `book-titling.ily' Parsing.../Applications/LilyPond.app/Contents/Resources/bin/../share/guile/1.8/ice-9/regex.scm:180:45: In procedure make-regexp in expression (make-regexp regexp): /Applications/LilyPond.app/Contents/Resources/bin/../share/guile/1.8/ice-9/regex.scm:180:45: illegal byte sequence LilyPond terminated in 0.673 seconds. Curiously, before spotting the suggested "-ed" options to convert-ly, I had tried adding a \version "2.14.0" statement to the top of the file and running convert-ly without options. Eeek! $ /Applications/LilyPond.app/Contents/Resources/bin/convert-ly book-titling-a.ily > book-titling-a.convert-ly.ily convert-ly (GNU LilyPond) 2.16.2 convert-ly: Processing `book-titling-a.ily'... Applying conversion: 2.15.7, 2.15.9, 2.15.10, 2.15.16, 2.15.17, 2.15.18, 2.15.19, 2.15.20, 2.15.25, 2.15.32, 2.15.39, 2.15.40, 2.15.42, 2.15.43, 2.16.0 Traceback (most recent call last): File "/Applications/LilyPond.app/Contents/Resources/bin/convert-ly", line 374, in main () File "/Applications/LilyPond.app/Contents/Resources/bin/convert-ly", line 362, in main do_one_file (f) File "/Applications/LilyPond.app/Contents/Resources/bin/convert-ly", line 316, in do_one_file outfile.write (result) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/codecs.py", line 351, in write data, consumed = self.encode(object, self.errors) UnicodeDecodeError: 'utf8' codec can't decode byte 0x8e in position 1331: invalid start byte and, in a spirit of inquiry, thought I might have a look inside convert-ly: $ file /Applications/LilyPond.app/Contents/Resources/bin/convert-ly /Applications/LilyPond.app/Contents/Resources/bin/convert-ly: ERROR: line 163: regex error 17, (illegal byte sequence) I suspect that there might be a problem with convert-ly on OSX. kind regards -- Graham King On Mon, 2013-10-28 at 07:54 +0100, David Kastrup wrote: > Kevin Tough writes: > > > My lilypond install of 2.16.2 cannot parse the input file. It hangs at > > fatal error: failed files: "SnippetForBookWithTitleAndTOC" > > (4 of 29): error: unknown escaped string: *\markuplines' > > Did you run > > convert-ly -ed > > on the file in order to upgrade the syntax to version 2.16.2 ? > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
\parenthesize command looks puny compared with reminder accidental
Consider
\version "2.16"
MvmntIVoiceI = {
f'?4 \parenthesize g'4
}
\score {
\MvmntIVoiceI
}
The output has a rather puny looking parenthesis around the notehead
while the reminder accidental is boldly parenthesized.
Do people think this constitutes a bug? And, in any case suggestions on
how to beef up the \parenthesize to look in keeping with the reminder
accidental would be appreciated.
Richard Shann
parens.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: On creating "title pages" and the like
I have no idea how to do that. I'm using MacOSX, and I'm not familiar with internals. IC, Josh On Mon, Oct 28, 2013 at 1:54 AM, David Kastrup wrote: > Kevin Tough writes: > > > My lilypond install of 2.16.2 cannot parse the input file. It hangs at > > fatal error: failed files: "SnippetForBookWithTitleAndTOC" > > (4 of 29): error: unknown escaped string: *\markuplines' > > Did you run > > convert-ly -ed > > on the file in order to upgrade the syntax to version 2.16.2 ? > > -- > David Kastrup > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \parenthesize command looks puny compared with reminder accidental
Some suggestion of how to tweak the parentheses:
\version "2.16"
{
% controls the size of the parenthesis, default value = around -6
\override Score.ParenthesesItem.font-size = 0
% controls the sepparation between the parentheses, default value = 0
\override Score.ParenthesesItem.padding = 0.05
f'?4 \parenthesize f'4
}
Regards,
Gilberto
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/parenthesize-command-looks-puny-compared-with-reminder-accidental-tp153097p153099.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \parenthesize command looks puny compared with reminder accidental
2013/10/29 Richard Shann :
> Consider
>
> \version "2.16"
>
> MvmntIVoiceI = {
> f'?4 \parenthesize g'4
> }
>
> \score {
> \MvmntIVoiceI
> }
>
> The output has a rather puny looking parenthesis around the notehead
> while the reminder accidental is boldly parenthesized.
>
> Do people think this constitutes a bug? And, in any case suggestions on
> how to beef up the \parenthesize to look in keeping with the reminder
> accidental would be appreciated.
>
> Richard Shann
Hi,
this is slightly related to
issue 1451
issue 155
In general, \parenthesize determines the extent for the parent from
the extent of the object which should be parenthesized.
As a workaround for your example-case you might want to use:
\override ParenthesesItem #'font-size = #-1
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: On creating "title pages" and the like
Josh, you can run convert-ly from the command line (/Applications/Utilities/Terminal.app) using the commands in my previous post to this thread this afternoon. I hope you have better luck than I had! -- Graham On Tue, 2013-10-29 at 11:41 -0500, Joshua Nichols wrote: > I have no idea how to do that. I'm using MacOSX, and I'm not familiar > with internals. > > > IC, > > Josh > > > > > On Mon, Oct 28, 2013 at 1:54 AM, David Kastrup wrote: > > Kevin Tough writes: > > > My lilypond install of 2.16.2 cannot parse the input file. > It hangs at > > fatal error: failed files: "SnippetForBookWithTitleAndTOC" > > (4 of 29): error: unknown escaped string: *\markuplines' > > > > Did you run > > convert-ly -ed > > on the file in order to upgrade the syntax to version 2.16.2 ? > > -- > David Kastrup > > > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi Preview Modes
Wilbert Berendsen-4 wrote > What do you think of a third main mode: > - Preview mode (just point and click, as it has been) > - Publish mode (no point and click) > - Debug mode: this mode listens to the settings in the Debug mode panel. I think this makes sense. My only suggestion is to consider using something besides "Debug" for the name of the third mode, since that might give an unfortunate connotation. Maybe something like "Editing mode" or "Advanced Editing mode"? -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/Frescobaldi-Preview-Modes-tp153086p153102.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi Preview Modes
Paul Morris schrieb: >Wilbert Berendsen-4 wrote >> What do you think of a third main mode: >> - Preview mode (just point and click, as it has been) >> - Publish mode (no point and click) >> - Debug mode: this mode listens to the settings in the Debug mode >panel. > >I think this makes sense. My only suggestion is to consider using >something >besides "Debug" for the name of the third mode, since that might give >an >unfortunate connotation. Maybe something like "Editing mode" or >"Advanced >Editing mode"? > What we were always using internally for these visualizations was "draft mode". How about that? Urs >-Paul > > > >-- >View this message in context: >http://lilypond.1069038.n5.nabble.com/Frescobaldi-Preview-Modes-tp153086p153102.html >Sent from the User mailing list archive at Nabble.com. > >___ >lilypond-user mailing list >lilypond-user@gnu.org >https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Enharmonic cue notes in choral music.
Could this be something like a trill notation where you also often parenthesize the secondary note? David Toms schrieb: >Hello, > >I have been publishing mainly vocal music for over 10 years with >Sibelius. This year I have ditched it for Lilypond, and I am pleased >to say that my first effort using it, a book of vocal music with piano, >is at the printers. The composer says it is the "most elegant >engraving he has ever seen", so well done to everybody! > >I'm well into my second book now, which is SATB choral music >unaccompanied, and I have just come across the first problem that I >haven't been able to solve by recourse to documentation and snippets, >so I have just joined the mailing list in the hope that someone can >point me in the right direction. > >The music makes frequent harmonic changes, and in a lot of places the >composer helps the singers by 'reminding' them with a cue that, for >example, the A sharp they have just sung is the same note as B flat. >This helps singers over difficult modulations. I have looked at a lot >of printed vocal music and this occurs quite often - I'm reluctant to >say I could do it fairly easily with Sibelius! > >The requirement is to produce a small notehead at the enharmonic pitch, >immediately after the preceding note, with both the accidental and the >notehead in parentheses. The notehead is really "text", and should not >affect midi playback, attract lyrics, etc. I tried using markups but >it is nearly impossible to get the notes in the right place on the >staff. After much searching, and trial and error, I got a "nearly >right" >solution, but as the attached snipped shows, the problem with using >"aftergrace" is that the "parenthesised" note can be a long way from >it's parent. > >I suspect that this is something I am missing, probably because I don't >know exactly how to describe the problem so I don't really know where >to >look in the documentation. > >Any suggestions gratefully received. > >David > > > >___ >lilypond-user mailing list >lilypond-user@gnu.org >https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Enharmonic cue notes in choral music.
On Oct 29, 2013, at 8:52 PM, Urs Liska wrote:
> Could this be something like a trill notation where you also often
> parenthesize the secondary note?
>
Right on the money.
\paper { ragged-right = ##f }
\relative c'' {
\override TrillSpanner #'stencil = ##f
\pitchedTrill
d2\startTrillSpan fis
d2
c2\stopTrillSpan
r2
}
Cheers,
MS
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Enharmonic cue notes in choral music.
David Toms writes: Put something like afterGraceFraction = 1/8 before your music, assuming that this is the only use for \afterGrace you have. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: New "make-path-stencil" function
Hi David N, David Nalesnik-2 wrote > Thank you for posting this! > > In the process of working on adding niente circles to Ferneyhough hairpins > (Issue 3357), I noticed that these hairpins don't work with line breaks. > (They are simply duplicated.) The routine which draws them uses > make-connected-path-stencil. Since the latter starts everything from (0 > 0), you can't draw broken pieces which are open at both ends. You're welcome! Glad you find it potentially useful. It sounds like it would make it simpler to deal with that problem with the Ferneyhough hairpins where you need a single stencil that includes two unconnected paths, neither of which end up being located at, or rather passing through (0 0). -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/New-make-path-stencil-function-tp153077p153108.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Frescobaldi preview with two "window"-modes
Hello, Frescobaldi is definitely great, thanks, many thanks! My reqest is, if it is possible to considere two score-previewer-width for two "sizes" of the Frescobaldi-window (switching between two modes). Actually, When I redimension frescobaldi (reduce width, with button or with mouse) the viewer keeps same absolut size, or at least try to stay the biggest it can. For typesetting from pdf scores on screen, opened in - lets say, acrobat - it would be usefull to have a very narrow viewer (or none) for entering code looking at the pdf the same time (narrowed frescobaldi), and 2 a wide viewer when frescobaldi occupies full with. Best with a keyboard-shortcut. Specially useful for cleaning a code too. Thanks in advance, Francois ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
LilyPond score publication
Hi all, I hope you'll not consider this post as spam, but as I'll tell you later I think it _does_ have some general relevance to LilyPond ;-) I have just released a post on lilypondblog.org starting a little series of reports on the ominous "Fried project" that was mentioned every now and then on this list or similar places: http://lilypondblog.org/2013/10/oskar-fried-complete-songs/ This project is the scholarly edition of a volume with the complete songs of Oskar Fried (http://en.wikipedia.org/wiki/Oskar_Fried) which we're about to finish right now. This volume has been completely (with the exception of the cover) prepared using text based tools (LilyPond and LaTeX), and apart from being a beautiful specimen of LilyPond's capabilities it may have some relevance to LilyPond itself: this project was triggering Janek's "Tie Crusade" and his current work on improving the \shape function, and the new Preview modes in Frescobaldi also have their origin in this project. In the post I repeated the subscription offer that I had released way too long ago (when we still hoped to release in 2012 ...), and I would like to make a modified repeat of that offer. As an expression of gratitude for the generous help we have always received from this list we offer copies of the new edition at cost price for subscribers of the lilypond-user list. We still have to calculate this price, which will also depend on the number of printed copies. This won't comprise any editor's fees but in addition to the net printing costs there are some items to consider like reference copies, banking fees, registrations etc. If I'd have to make an estimate I'd say it will be around 10 Euro for the softcover and 20 for the hardcover version (but particularly the hardcover price is due to changes in response to the number of copies). The volume will be +/- 120 pages (94 pages of music), contains 26 songs (three of them being duets), pictures and a meticulous revision report. It will be printed on beautiful and robust yellowish paper and processed with thread-stitching. In the post you can view two score samples and listen to the corresponding audio samples. This offer is open until Dec 1. Regards Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi Preview Modes
Urs Liska writes: > Paul Morris schrieb: >>Wilbert Berendsen-4 wrote >>> What do you think of a third main mode: >>> - Preview mode (just point and click, as it has been) >>> - Publish mode (no point and click) >>> - Debug mode: this mode listens to the settings in the Debug mode >>panel. >> >>I think this makes sense. My only suggestion is to consider using >>something >>besides "Debug" for the name of the third mode, since that might give >>an >>unfortunate connotation. Maybe something like "Editing mode" or >>"Advanced >>Editing mode"? >> > > What we were always using internally for these visualizations was > "draft mode". How about that? "draft mode" tends to be a name for low quality mode. How about "Inspect"? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: New "make-path-stencil" function
Carl Sorensen-3 wrote > Cool idea! Thanks! >>- allow "unconnected" paths with multiple segments. (i.e. allow (r)moveto >>in the middle of the path expression) > > Seems to allow simplification of complex stencils. Indeed, it lets you put things where you want them in the first place, both in relation to each other and to (0 0), while working in a single coordinate plane. This provides fewer moving parts to figure out and less ambiguity about the output. For example, currently you would have to define separate stencils that both start at (0 0) and then combine them into a single stencil while spacing them just right in relation to each other, etc. It would make that kind of thing a lot simpler. >>- allow use of different "cap" and "join" styles, not just round. > > It's part of the LilyPond engraving aesthetic to use round caps and joins. > Engraving on metal plates doesn't have sharp corners. That's why we > don't have the other styles. If you look at all of our box stencils, > you'll see they have rounded corners. So I don't think we should support > other cap and join styles. But I could certainly be overruled here. Hmmm... ok, although these are just optional arguments that default to round caps and joins, so I don't see the harm in making it possible to use the other styles, even if the practice is not to use them in LilyPond. My approach was to make it possible to do anything with this function that you can do with ly:make-stencil and a path expression. > Does it also work with output-ps.scm? I think so. It works the same as make-connected-path-stencil as far as that goes. > It seems like we would replace make-connected-path-stencil with > make-path-stencil. It can do everything that make-connected-path-stencil does, so that would be possible. > I haven't tried to rewrite your code, but when I first learned Scheme I > was told that anytime you saw lots of set! expressions in the code, you > were trying to write procedural code (I.e. c) instead of functional code > (Scheme). Your code seems to have lots of set! expressions; it may be > possible to rewrite it in a more functional manner. That's a helpful tip, thanks! > Anyway, this is a nice contribution! Thanks again, -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/New-make-path-stencil-function-tp153077p153111.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: make-connected-path-stencil with variables and connected paths
2013/10/25 Paul Morris : > Thomas Morley-2 wrote >> many thanks for your snippet. >> It has a very useful description! > > Hi Harm, > Glad you like it. > > > Thomas Morley-2 wrote >> Though, two suggestions: >> 1) I'd rename the note-head-stencil. 'diamond is already taken for a >> note-head-style >> 2) The stem-attachment while using this stencil doesn't fit, should be >> readjusted. > > Good points! I decided to change the shape so that adjusting the stem > attachment is not needed. That keeps things focused on how to use the > function. Exit diamonds, and enter bowties: > http://lsr.dsi.unimi.it/LSR/Item?u=1&id=891 > > Maybe impractical as a note head shape, but at least it shows how to do > curves! > > Cheers, > -Paul Hi, approved as http://lsr.dsi.unimi.it/LSR/Item?id=891 Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi Preview Modes
Just a short opinion: 2013/10/29 Wilbert Berendsen : > [...] > What do you think of a third main mode: > - Preview mode (just point and click, as it has been) > - Publish mode (no point and click) > - Debug mode: this mode listens to the settings in the Debug mode panel. For me, "preview" and "debug" modes are similar enough that they should be one thing. I.e. they are both things you use when still working on the score, as opposed to "publish". But my opinion is not very strong. 2013/10/29 Urs Liska : > My suggestion [if that's not what you intended anyway] is to have a > Point-and-Click option on the Debug panel (the contrary of the current way > to _disable_ point-and-click). So this would be a checkbox that is usually > checked but can be unchecked on demand. I like this. Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond score publication
2013/10/29 Urs Liska : > Hi all, > > I hope you'll not consider this post as spam, but as I'll tell you later I > think it _does_ have some general relevance to LilyPond ;-) > > I have just released a post on lilypondblog.org starting a little series of > reports on the ominous "Fried project" that was mentioned every now and then > on this list or similar places: > http://lilypondblog.org/2013/10/oskar-fried-complete-songs/ When published, this should definitely be listed in http://www.lilypond.org/productions.html Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: announcement: OpenLilyLib Snippet Repository is open!
Hi Simon, 2013/10/16 Urs Liska : > Am 16.10.2013 15:08, schrieb Simon Bailey: >> [] >> so basically, is there an intention at some point, to create a >> _library_ version of the snippets github (i.e. leave the examples in >> the files as usage documentation, but commented out so that they don't >> create output)? In the LSR it makes sense to have the examples >> compilable, as the images are automagically generated, but that isn't >> the case with github. > > > Actually there _is_ this intention, and we have already (slowly) started > updating the existing content of the repository. > The idea is to turn the snippets into includable .ily files and move the > usage examples (or anything that disturbs \include-ing the file in a > real-world score) into a compilable snippet-name-example.ly file. As you may have noticed, we recently reorganized the repository and now it should work more or less like you described. I hope you'll like it! best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: announcement: OpenLilyLib Snippet Repository is open!
Hiya, > On 29 Oct 2013, at 23:36, Janek Warchoł wrote: > > As you may have noticed, we recently reorganized the repository and > now it should work more or less like you described. I hope you'll > like it! i checked out the repository in exactly this way on Sunday. ;) (i needed the stem attachment snippet). a question: how stable will the organisation remain? revisiting scores in say a year or so, using includes from openlilylib, should still work… Thanks! I like it! :D regards, sb ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: announcement: OpenLilyLib Snippet Repository is open!
Am 29.10.2013 23:56, schrieb Simon Bailey: Hiya, On 29 Oct 2013, at 23:36, Janek Warchoł wrote: As you may have noticed, we recently reorganized the repository and now it should work more or less like you described. I hope you'll like it! i checked out the repository in exactly this way on Sunday. ;) (i needed the stem attachment snippet). a question: how stable will the organisation remain? revisiting scores in say a year or so, using includes from openlilylib, should still work… There's no guarantee about the stability of openlilylib. Currently I'm the 'owner' of the domain openlilylib.org. I also have registered the Github organization, but there are others with admin rights too. I can't seriously promise that I'll be still around in a year. (I don't have any differing intentions, but I just can't _seriously_ promise). But if not, chances are high that I've handed ownership to someone else before vanishing. And if everything should fail: You probably already have a copy of the repository, either through Git or by downloading. _This_ will work as long as you're able to accomodate any future LilyPond syntax changes ... Best Urs Thanks! I like it! :D regards, sb ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "smart" transposition of key signatures
David Kastrup writes:
> Janek Warchoł writes:
>
>> Also, you may be interested in this:
>> https://github.com/openlilylib/snippets/blob/master/input-shorthands/late-evaluation-of-variables.ly
>
> I can hardly count the number of ways in which this would have blown up
> in 2.14. I don't consider most uses of eval a good idea anyway, but
> making bad ideas work as expected is still an impressive feat.
Actually, since there is Scheme syntax creeping in anyway, it might make
more sense to use Scheme macros here and have less quoting blurb, and in
particular not the ugly eval:
\version "2.16.2" % absolutely necessary!
\header {
snippet-title = "Late evaluation of variables"
snippet-author = "Kristóf Marussy"
% taken from https://gist.github.com/kris7topher/6038247
% featured on Lilypond blog (provide reference)9
snippet-description = \markup {
“Late-bind” variables using an arity-0 music function that looks up
values at function call time instead of variable assignment time.
}
status = "unfinished"
% TODO: tell Kristof about the snippet, reorganize description
% add comma-separated tags to make searching more effective:
tags = "arity-0, score organization, variable, transposition, lilypond blog"
}
%%
% here goes the snippet: %
%%
beginning = \relative c'' {
\key as \major
c1
}
middlesection = \relative gis' {
\key e \major
gis1
}
end = \relative c'' {
\key as \major
c1
\bar "|."
}
% ``Late-bind'' variables using an arity-0 music function that looks up values
% at function call time instead of variable assignment time.
#(define-macro (late embedded-lilypond)
`(define-music-function
(parser location)
()
,embedded-lilypond))
music = #(late #{
\beginning
\middlesection
\end
#})
\score {
% The music without the enharmonic change---complex key signature!
\new Staff \transpose as g \music
\layout {}
}
% Apply enharmonic transposition to \middlesection.
middlesection = \transpose e fes \middlesection
\score {
% Because variables in \music are ``late-bound'', the enharmonic
% transposition is now respected.
% The point is that the reassignment of middlesection variable
% is respected despite the fact that \music was defined earlier!
\new Staff \transpose as g \music
\layout {}
}
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
