Re: bleeding

2012-11-18 Thread Marc Hohl
Am 18.11.2012 16:51, schrieb Reinhold Kainhofer: On 2012-11-18 16:42, Marc Hohl wrote: Check the output in the log file and correct the error. That was too fast, I think. Nope, that's exactly the problem. The file compiles fine on my machine, the log on the console says: warning: al

Re: bleeding

2012-11-18 Thread Marc Hohl
Am 18.11.2012 16:52, schrieb Phil Holmes: [...] Check the output in the log file and correct the error. That was too fast, I think. The file compiles fine on my machine, the log on the console says: warning: already have a beam \clef treble bes16 d f aes bes [ c ]

Re: zigzag staffline

2012-12-20 Thread Marc Hohl
Am 20.12.2012 02:14, schrieb Thomas Morley: [...] Hi Gagi, the code below constructs a new StaffSymbol with zigzag-lines at to be specified positions. It is not widely tested, please shout if sth goes wrong. Several explaining comments are added. Kudos for this solution! It works great, and the

Call a score variable by a scheme expression

2012-12-27 Thread Marc Hohl
Hello list, I think this has been answered before, but I don't find it in the archives... Assume I have the following file scoretest.ly: \version "2.17.10" #(define opt-score (or (ly:get-option 'score) "Full")) musicA = \relative f { c''4 d e f | g1 } musicB = \relative f { c'4 b a f |

Re: Call a score variable by a scheme expression

2012-12-27 Thread Marc Hohl
Am 27.12.2012 18:55, schrieb David Kastrup: Marc Hohl writes: [...] Any hints are highly welcome! #(string-append ...) is a string. Maybe you want something like $(module-ref (current-module) (string->symbol ...)) or $(ly:parser-lookup parser (string->symbol ...)) Not particularl

Re: strange error after reducing music rhythm by an half

2012-12-27 Thread Marc Hohl
Am 27.12.2012 22:31, schrieb Federico Bruni: Hi while transcribing a piece of music, I realized that it may work better if written with a different rhythm, so I used the Frescobaldi option which reduces the rhythms by an half. Then I removed all the bar checks. But I cannot compile this mod

Re: FretBoards chordChanges

2013-01-04 Thread Marc Hohl
Am 04.01.2013 22:22, schrieb EmilLask: Thank you again, David. How have I installing the patch file .cc? If you don't have compiled lilypond from source, it would be probably the best to wait for 2.17.11 to be released. If you want to give it a try, though, have a look at http://lilypond.org

Re: FretBoards chordChanges

2013-01-04 Thread Marc Hohl
Am 04.01.2013 22:44, schrieb Phil Holmes: - Original Message - From: "Marc Hohl" To: Sent: Friday, January 04, 2013 9:30 PM Subject: Re: FretBoards chordChanges Am 04.01.2013 22:22, schrieb EmilLask: Thank you again, David. How have I installing the patch file .cc? If

Re: FretBoards chordChanges

2013-01-04 Thread Marc Hohl
Am 05.01.2013 08:13, schrieb EmilLask: Thanks Marc and thanks Phil. Is there an easy guide, step by step, to compiling Lilypond in mac os x and add .cc patch without get in trouble ? I can't speak for MacOS X but I remember that at least in the past this was not a trivial task to get LilyPond c

Re: Repeat in Score and in Midi

2013-01-08 Thread Marc Hohl
Am 08.01.2013 17:02, schrieb EmilLask: Thank you. ex. \parallelMusic #'(voiceA voiceB) { [...] \bar ":|:" \bar "..." tells LilyPond to draw this specific bar line *without* being interpreted musically. To make MIDI work as expected, you'll have to use \repeat ... and \unfoldRepeat

Re: Getting the name of the context a scheme function was called from

2013-01-12 Thread Marc Hohl
Am 12.01.2013 16:28, schrieb Paul Morris: On Jan 12, 2013, at 2:47 AM, David Kastrup wrote: Uh, if you have a _custom_ staff context for which you want particular overrides, you just do \layout { \context { \Staff \name "MyStaff" \alias "Staff" \override ... \override ..

Re: \bar "||" and \repeat around a line break

2013-01-15 Thread Marc Hohl
Am 16.01.2013 04:04, schrieb Frank Steinmetzger: Hello dear list I'm writing a score that has a \bar "||" at the end of a system, and a volta repeat beginning in the following system after the line break. It seems that the \bar command overwrites the |: of the following volta, making that invisi

Re: General bar setup for score

2013-01-15 Thread Marc Hohl
Am 16.01.2013 08:51, schrieb Maarten de Keijzer: Hi, Is it possible to create some general setup for the total number of bars within the score, including time changes? In the example I have a score with two voices on the right (piano) staff with 6/8 and 3/8 bars. When I create in one voic

Re: Unwanted new page at end of score

2013-01-16 Thread Marc Hohl
Am 16.01.2013 12:45, schrieb Peter Gentry: I cannot suppress a page break which looks unnecessary - what am I doing wrong?. I have included the example in the attached file which I hope does not contain too much unnecessary data. This looks like a w*rd document with some binary data in it – I

Re: \bar "||" and \repeat around a line break

2013-01-17 Thread Marc Hohl
Am 17.01.2013 19:39, schrieb Johan Vromans: Frank Steinmetzger writes: Am Donnerstag, 17. Januar 2013, 08:28:37 schrieb Ralph Palmer: In addition, you can specify "||:", which is equivalent to "|:" except at line breaks, where it gives a double bar line at the end of the line and a start repe

Re: \bar "||" and \repeat around a line break

2013-01-17 Thread Marc Hohl
Am 17.01.2013 19:56, schrieb Thomas Morley: 2013/1/17 Johan Vromans : Frank Steinmetzger writes: Am Donnerstag, 17. Januar 2013, 08:28:37 schrieb Ralph Palmer: In addition, you can specify "||:", which is equivalent to "|:" except at line breaks, where it gives a double bar line at the end o

Re: \bar "||" and \repeat around a line break

2013-01-18 Thread Marc Hohl
Am 18.01.2013 06:03, schrieb Jim Long: [...] There is no confusion at all. The source file tells Lilypond exactly where the double bars should be. Lilypond knows that at several places, the source code says: \bar "||" \break As I understood Johan's suggestion, Lilypond should interpret that t

Re: \bar "||" and \repeat around a line break

2013-01-18 Thread Marc Hohl
Am 18.01.2013 09:39, schrieb Johan Vromans: Marc Hohl writes: Except that it does not work with \repeat, AFAIK. Yes, it does. c1 \bar "||:" \break \repeat volta 2 { d2 d } Sorry if I was unclear -- what I meant to say is that IMHO LilyPond should be able to handle this correc

page footer and (on-page ...) in combination with \label

2013-01-20 Thread Marc Hohl
Hello list, I have lilypond file containing several\bookpart entries. For one specific page I have to remove the footer completely. I set \label #'emptypage and oddFooterMarkup = \markup { \fill-line { \on-the-fly #last-page \fromproperty #'header:tagline } \fill-line { \on-the-fly #print

Re: page footer and (on-page ...) in combination with \label

2013-01-21 Thread Marc Hohl
Am 21.01.2013 06:40, schrieb Jay Anderson: On Sun, Jan 20, 2013 at 1:53 PM, Marc Hohl wrote: For one specific page I have to remove the footer completely. I set \label #'emptypage Can the page without a footer be in a book-part of its own? That would be too simple so I'm as

Re: Repeat signs / bar lines in markup

2013-02-07 Thread Marc Hohl
Am 06.02.2013 18:46, schrieb Peter Crighton: Hi List, is there some way to put bar lines, or more specifically repeat signs, inside a text markup? Other than recreating them with the help of \draw-line and \draw-circle? I found a rather clumsy workaround: \markup { \line { Here is a \hsp

Re: Repeat signs / bar lines in markup

2013-02-08 Thread Marc Hohl
Am 08.02.2013 13:01, schrieb Eluze: Thomas Morley wrote below a markup-command to print bar-lines. For now it is limited to bar-lines containing thick-bar-line, thin-bar-line and/or colon-bar-line. Every additional bar-line (dashed, dotted etc) would need an additional construction-procedure. \

Re: Advice on bar numbers

2013-02-25 Thread Marc Hohl
Am 25.02.2013 11:37, schrieb Graham.Okely: Thanks I can see that would work in rehearsals. Working up a drum line is easier if each bar gets a number sequentially. But writing up the drum sequence is only required once. (Usually) So I do not think writing up a fully expanded manuscript for th

Re: Advice on bar numbers

2013-02-25 Thread Marc Hohl
Am 25.02.2013 11:40, schrieb Marc Hohl: Am 25.02.2013 11:37, schrieb Graham.Okely: Thanks I can see that would work in rehearsals. Working up a drum line is easier if each bar gets a number sequentially. But writing up the drum sequence is only required once. (Usually) So I do not think

Re: StaffGroup and GrandStaff: Barlines not connected in version 2.17.*

2013-02-28 Thread Marc Hohl
Am 28.02.2013 09:12, schrieb Thomas Scharkowski: Hi, from the 2.17.13 doc: "In the StaffGroup context, the group is started with a bracket and bar lines are drawn through all the staves." The example below results in all staves not connected. This is also the case in the pdf of the notation d

Re: StaffGroup and GrandStaff: Barlines not connected in version 2.17.*

2013-02-28 Thread Marc Hohl
Am 28.02.2013 09:17, schrieb Marc Hohl: Am 28.02.2013 09:12, schrieb Thomas Scharkowski: Hi, from the 2.17.13 doc: "In the StaffGroup context, the group is started with a bracket and bar lines are drawn through all the staves." The example below results in all staves not connecte

Re: Bar lines

2013-03-06 Thread Marc Hohl
Am 06.03.2013 02:59, schrieb Thomas Morley: 2013/3/5 Noeck : Hi, I tried the (relatively) new bar line interface: \version "2.17.12" \defineBarLine "|:" #'(":||" "" "|:") % a) \defineBarLine ":||" #'(":.." "" " ||") % b) \new StaffGroup << \new Staff { a1 \bar "|:" a \bar "|:" } \new S

Re: Bar lines

2013-03-06 Thread Marc Hohl
Am 06.03.2013 09:38, schrieb David Kastrup: Marc Hohl writes: Am 06.03.2013 02:59, schrieb Thomas Morley: 2013/3/5 Noeck : Hi, I tried the (relatively) new bar line interface: \version "2.17.12" \defineBarLine "|:" #'(":||" "" "|:")

Re: Bar lines

2013-03-06 Thread Marc Hohl
Am 06.03.2013 17:47, schrieb Janek Warchoł: Hi all, i was very surprised by Marc's suggestion to revert his barline interface commit. I'm pretty sure that everyone regards Marc's (and Harm's) work in this area as very valuable and noone thinks of deleting it at all! I am a bit disappointed tha

Re: Bar lines

2013-03-07 Thread Marc Hohl
Am 06.03.2013 21:24, schrieb David Kastrup: Marc Hohl writes: I am a bit disappointed that the discussion about \bar ":|." rises half a year after the patch went through the revision process. If you think this is the first time, you have missed a few times. The revision proces

Re: Pseudo-handwritten font

2013-03-07 Thread Marc Hohl
Am 07.03.2013 00:45, schrieb Thomas Morley: 2013/3/6 Shane Brandes : there was a jazz font patch somewhile ago. http://lists.gnu.org/archive/html/lilypond-user/2010-12/msg00290.html There is some currently unfinished work in the german forum. http://www.lilypondforum.de/index.php?topic=1218.0 B

Re: Bar lines

2013-03-07 Thread Marc Hohl
Am 06.03.2013 21:55, schrieb Noeck: Hi, It is orthogonal to us making \bar "|:" and \bar ":|" well-defined by letting : automatically imply a thick bar since nothing else makes sense. I don't think that this is the problem Joram struggled with. So he is defining a bar type "|:" himself. Yes,

Re: Bar lines

2013-03-07 Thread Marc Hohl
Am 07.03.2013 10:06, schrieb David Kastrup: [...] Ok, here is the deal: I promise to give real thought about a way to _define_ repeat structures in such a straightforward manner that a user would understand how to create repeat structures of his own including working Midi and \expandRepeats as lo

Re: Pseudo-handwritten font

2013-03-07 Thread Marc Hohl
Am 07.03.2013 10:44, schrieb Werner LEMBERG: Wow, very impressive! I hate to admit it, Hehe :-) but it looks like a game changer of strategic importance to me. I hope that this extension will find its way into the official lilypond releases... What needs to be done for this? I don't know,

Re: Bar lines

2013-03-07 Thread Marc Hohl
Am 07.03.2013 17:56, schrieb David Kastrup: Marc Hohl writes: Am 07.03.2013 10:06, schrieb David Kastrup: [...] Ok, here is the deal: I promise to give real thought about a way to _define_ repeat structures in such a straightforward manner that a user would understand how to create repeat

Re: Bar lines

2013-03-07 Thread Marc Hohl
Am 07.03.2013 18:36, schrieb David Kastrup: Noeck writes: We use "|." for the end bar not because of its _visual_ properties, If that is the case, I would say \bar "." is more logical. Zounds. Tell you what: I'd consider that an actual improvement. No – I still would prefer if LilyPond draw

Re: Bar lines

2013-03-07 Thread Marc Hohl
Am 07.03.2013 18:45, schrieb David Kastrup: Marc Hohl writes: Am 07.03.2013 18:36, schrieb David Kastrup: Noeck writes: We use "|." for the end bar not because of its _visual_ properties, If that is the case, I would say \bar "." is more logical. Zounds. Tell yo

Re: Bar lines

2013-03-07 Thread Marc Hohl
Am 07.03.2013 18:52, schrieb Paul Scott: [...] All musical sections do not end with \bar "|." so you do need to explicitly tell her. You, of course can create your own template to do that. How can I write a template for telling lilypond to end my scores with a final bar line? ___

Re: Bar lines

2013-03-07 Thread Marc Hohl
Am 07.03.2013 18:52, schrieb Marc Hohl: Am 07.03.2013 18:45, schrieb David Kastrup: Marc Hohl writes: Am 07.03.2013 18:36, schrieb David Kastrup: Noeck writes: We use "|." for the end bar not because of its _visual_ properties, If that is the case, I would say \bar ".&q

Re: Bar lines

2013-03-07 Thread Marc Hohl
Am 07.03.2013 18:56, schrieb David Kastrup: Marc Hohl writes: Am 07.03.2013 18:45, schrieb David Kastrup: Marc Hohl writes: Am 07.03.2013 18:36, schrieb David Kastrup: Noeck writes: We use "|." for the end bar not because of its _visual_ properties, If that is the case, I

Re: Bar lines

2013-03-07 Thread Marc Hohl
Am 07.03.2013 19:00, schrieb David Kastrup: Marc Hohl writes: Am 07.03.2013 18:52, schrieb Paul Scott: [...] All musical sections do not end with \bar "|." so you do need to explicitly tell her. You, of course can create your own template to do that. How can I write a template f

Re: Proposed new available and recommended behavior of \relative

2013-03-08 Thread Marc Hohl
Am 07.03.2013 20:21, schrieb Werner LEMBERG: One rationale is to stop the "distribution" of the information for the first pitch to potentially quite separate places, like being able to write \new Staff \relative { \key aes \major << % Voice one { c''2 aes4. bes8 } ... instead o

Re: \relative proposal: putting absolute pitches anywhere within \relative block using @-sign

2013-03-13 Thread Marc Hohl
Am 13.03.2013 20:24, schrieb nothingwaver...@gmail.com: This is a breakaway thread from the one with the subject "Proposed new available and recommended behavior of \relative" I am *OPPOSED* to the proposal to change \relative syntax, as the proposal now stands. I think it is confusing to new

Re: Custom footers

2013-03-20 Thread Marc Hohl
Am 20.03.2013 19:19, schrieb Jérôme Plût: Decimo tertio Kalendas Apriles MMXIII scripsit Thomas Morley : in the code below you'll see increasing page-numbers throughout the book as usual. Ooh, now that I have had the time to read your code, I see what you did, and I like it. The \on-the-fly si

Re: how offsets and alignment works: an explanation

2013-03-23 Thread Marc Hohl
Am 23.03.2013 16:07, schrieb Phil Holmes: - Original Message - From: "Janek Warchoł" To: "LilyPond Users" Sent: Saturday, March 23, 2013 2:05 PM Subject: how offsets and alignment works: an explanation Hi, here's an explanation of what's happening when we're using XY-offset, self-al

Re: forcing a specific notehead glyph

2013-03-31 Thread Marc Hohl
Am 01.04.2013 05:56, schrieb luis jure: on 2013-03-31 at 16:50 Neil Puttock wrote: This should just be `0'. hi neil, i'm sorry, but i don't quite understand how to modify the function suggested by harm to address the problem you mention. IIUC, he proposed that you remove the last line in

Re: 2.16: warning: type check for `stencil' failed

2013-04-04 Thread Marc Hohl
Am 04.04.2013 16:27, schrieb James Harkins: It seems that if I write: \override Staff.TimeSignature #'stencil = ##f ... there's no problem. But this: \override Staff.TimeSignature #'stencil = ##t ... produces: warning: type check for `stencil' failed; value `#t' must be of type `stenci

Re: Help with espressivo adjustments

2013-04-13 Thread Marc Hohl
Am 13.04.2013 14:09, schrieb luis jure: on 2013-04-13 at 02:23 Thomas Morley wrote: Ok, I'll try, though, please remember I'm not a programmer. My explanations may be not complete. excellent tutorial, thank you. i found it very instructive. +1 Kudos! Marc _

Re: Lyrics rest in text

2013-04-29 Thread Marc Hohl
Am 29.04.2013 19:02, schrieb Stjepan Horvat: is is possible to put a rest in a lyrics text..?! For example: Ya - ba - da - ba -du He - llo - r8 - r8 - you so that the 8th rest is showen..?! I use something like Hel -- lo \markup { \raise #1 \musicglyph #"rests.3" } you in my scores, but I a

Re: intractable collision of arpeggio and rest

2013-05-22 Thread Marc Hohl
Am 22.05.2013 08:59, schrieb Tom Cloyd: Running Lilypond 2.16.0 - 1. In the following 8 bar snippet, I am arpeggiating across the middle and upper voices. The arpeggio is colliding with the rest that's in the middle voice. I've tried about 9 ways and I cannot get the arpeggio in the right place.

Re: Rest in Lyrics

2015-08-02 Thread Marc Hohl
Am 03.08.2015 um 02:53 schrieb David Kastrup: [...] Alternatively: << \new Voice = "melody" { c''4 d'' e'' f'' } \new Lyrics \with { \consists "Rest_engraver" \override Rest.Y-offset = 0.5 } \lyricsto "melody" { c d \notemode { \parenthesiz

lilypond-book (again) and LyricText font problem

2015-08-03 Thread Marc Hohl
Hi list, I use lilypond-book and lualatex for a project. I have a .ily file with \paper { indent = 0 ragged-right = ##f #(define fonts (make-pango-font-tree "Mala's Handwriting" "Mala's Handwriting" "Mala's Handwriting"

Re: lilypond-book (again) and LyricText font problem

2015-08-03 Thread Marc Hohl
Addendum: I tried to force lilypond to use this font by adding \context { \Score \override LyricText.font-name = "Mala's Handwriting" } to the .ily file, but there's no difference. Properly included in a \layout { ... } environment, of course. Marc ___

Re: lilypond-book (again) and LyricText font problem

2015-08-03 Thread Marc Hohl
Sorry for the noise, I fould the culprit: the standalone snippets were (erroneously) built with the latest self-compiled lilypond, whereas lilypond-book is an older version that did not find the font. Marc Am 03.08.2015 um 18:36 schrieb Marc Hohl: Addendum: I tried to force lilypond to

Re: Errors when using TabStaff with stringTunings

2015-08-24 Thread Marc Hohl
Am 24.08.2015 um 17:36 schrieb Kevin Nowaczyk: I have a lilypond file which used to parse perfectly well several years ago. I recently reinstalled lilypond (2.18.2 from debian-stable) and now I receive an error. I've reduced the file down and determined that setting the stringTunings is the pr

Re: Way to flatten nested \include's?

2015-08-25 Thread Marc Hohl
Am 25.08.2015 um 10:11 schrieb David Kastrup: Andrew Bernard writes: wrote: If all else fails, the lilypond binary itself can serve as a GUILE interpreter. That was the general idea. I posted some instructions about how to add the utility to a lilypond installation for people but in a new

Re: Way to flatten nested \include's?

2015-08-25 Thread Marc Hohl
Am 25.08.2015 um 11:12 schrieb Andrew Bernard: I am not sure I understand. Is having a symlink: flatten-ly -> /home/username/bin/lilypond-wrapper.guile not correct? The convert-ly utility is set up as: convert-ly -> /home/username/bin/lilypond-wrapper.python I think that David meant

Re: a basic question

2015-08-27 Thread Marc Hohl
Am 27.08.2015 um 09:44 schrieb B~M: Sorry to ask this silly little question. I am writing out SATB harmonies for a music exam and Ive decided to colour the bass in blue, just to make it a little more distinct. Based on a recent mail excange on a similar topic, this function may be helpful: o

Re: a basic question

2015-08-27 Thread Marc Hohl
Am 27.08.2015 um 14:48 schrieb Simon Albrecht: Hello Paul, [...] The solution posted by Mark will not work on anything which lives at Score level, e.g. ledger lines and bar lines. Since the OP example shows two different voices sharing one staff, I assumed that the bar lines should not chang

Re: a basic question

2015-08-27 Thread Marc Hohl
Am 27.08.2015 um 16:55 schrieb Marc Hohl: Am 27.08.2015 um 14:48 schrieb Simon Albrecht: Hello Paul, [...] The solution posted by Mark will not work on anything which lives at Score level, e.g. ledger lines and bar lines. Since the OP example shows two different voices sharing one staff, I

Re: a basic question

2015-08-27 Thread Marc Hohl
Am 27.08.2015 um 19:29 schrieb Simon Albrecht: [...] In some way it would be desirable for some cases to have ledger lines at Voice level, e.g. in << a'' \\ c' >> But it becomes unwieldy soon; what about << a \\ f >> ? The only sensible way to deal with this would be creating an association betwe

stacking whole notes of different size

2015-08-31 Thread Marc Hohl
Hello list, I have songs for single voice and wanted to include an optional higher voice for those singers that are able to each the notes and are capable of doing a second voice. Since the doubled part is just at the end of a song, I did not want to fiddle with a separate voice and wrote chords

Re: stacking whole notes of different size

2015-08-31 Thread Marc Hohl
eers, Marc Yours, Simon Am 31.08.2015 um 14:15 schrieb Marc Hohl: Hello list, I have songs for single voice and wanted to include an optional higher voice for those singers that are able to each the notes and are capable of doing a second voice. Since the doubled part is just at the end o

Re: stacking whole notes of different size

2015-08-31 Thread Marc Hohl
? (I tried shifting the smaller notes by \tweak X-offset #-0.25 first, but that does not seem to have any effect.) TIA, Marc Yours, Simon Am 31.08.2015 um 14:15 schrieb Marc Hohl: Hello list, I have songs for single voice and wanted to include an optional higher voice for those singers tha

Re: stacking whole notes of different size

2015-08-31 Thread Marc Hohl
Am 31.08.2015 um 18:50 schrieb Simon Albrecht: Am 31.08.2015 um 18:22 schrieb Marc Hohl: Am 31.08.2015 um 15:41 schrieb Simon Albrecht: Hello Marc, this is a known issue: see <https://sourceforge.net/p/testlilyissues/issues/3900/>. Ok, so I managed to shift the upper note heads by

Re: stacking whole notes of different size

2015-08-31 Thread Marc Hohl
Am 31.08.2015 um 19:09 schrieb Stephen MacNeil: \override NoteColumn.force-hshift = #.65 works but you would have to create a new voice i believe. Yup, creating a new Voice and applying force-hshift works, but the last tie looks quite different than the other ones: a2. fis4 | a1 | << {

Re: stacking whole notes of different size

2015-09-02 Thread Marc Hohl
Hi Harm, hi Stephen, Am 02.09.2015 um 00:16 schrieb Thomas Morley: [...] Hi Marc, I wrote some test [...] I hope it helps a bit, although I've found no convincing general value. png with your example is attached as well. thanks a lot for your investigations! Now I have something to work with

Re: stacking whole notes of different size

2015-09-02 Thread Marc Hohl
Hi again, Am 02.09.2015 um 00:16 schrieb Thomas Morley: Hi Marc, I wrote some test m = \relative c' { c1~ 1~ 2 s2 \bar "||" c1~ 1~ 1 \bar "||" c2~ 2~ 2~ 2~ 2~ 2 \bar "||" } \transpose c c \m \transpose c d \m \transpose c e \m \transpose c f \m \transpose c g \m \trans

Re: Move (arpeggio) tie - visibility of ties

2015-09-04 Thread Marc Hohl
Am 04.09.2015 um 15:23 schrieb Michael Gerdau: Dear ponders, I have an arpeggio which I'd like to engrave by adding ties as shown in snippet http://lsr.di.unimi.it/LSR/Item?id=408 However one of the ties (connecting the dis) is almost invisible Please see attached PDF. I've also attached the ly

Re: Unwanted barree finger in fret diagram

2015-09-08 Thread Marc Hohl
Am 08.09.2015 um 12:31 schrieb Thomas Morley: [...] Do we want \markup { \fret-diagram #"1-0;" } %% unwanted output keep working? I can't imagine a use-case right now. IIRC, 1-o means "display first string as open string", and it is common to mark open strings with a "0" (zero) within a score,

Re: OT: Barenreiter Plate Engraving Pictures

2015-09-10 Thread Marc Hohl
Am 10.09.2015 um 20:02 schrieb tisimst: Not sure how many of you follow Barenreiter-Verlag on Facebook, but if you don't you will have missed an awesome post today (English and German) showing a handful of beautiful hand-engraved plates and the tools they used. Thanks for sharing! Henle Verla

Re: restrainOpenStrings

2015-09-13 Thread Marc Hohl
Am 13.09.2015 um 14:07 schrieb BB: I read the manual. But please answer the question WHY should lilypond statements not do what the statement text straight implies? IIRC, we discussed quite a lot about the new restrainOpenStrings functionality and how to name this new property. There were some

Re: idea for fretboard-diagram chords

2015-09-18 Thread Marc Hohl
Am 18.09.2015 um 08:40 schrieb bart deruyter: Hi all, [...] For inversions one might choose a number based on the n'th note of a chord, for example 2 as the second note from the root note, which in the case of c:m would result in a ees as the lowest note and display a fretboard diagram accordin

Re: Chords and what they mean

2015-09-20 Thread Marc Hohl
Am 20.09.2015 um 09:58 schrieb BB: [...] The question is more like: if you saw Csus, would you know how to interpret it musically? Or would you be stuck in your tracks wondering, "is this a sus2, sus4, both? something else?" c:sus is working correctly getting root and 5, but indeed is an "unc

Re: Chords and what they mean

2015-09-20 Thread Marc Hohl
Am 20.09.2015 um 11:10 schrieb David Kastrup: [...] Interpreting c:sus as root and 5 feels strange IMHO. The rule I am using in my current patch (just writing up the documentation) is that c:sus will add a 4 if no step 2 or step 4 is added afterwards (step 2 can be 2+ or 2- as well as just 2).

Re: on-page procedure

2015-09-25 Thread Marc Hohl
Am 25.09.2015 um 10:05 schrieb Paul Scott: 2.19.27 I can get other procedures to work in \on-the-fly but not on-page. The NR suggests: \on-the-fly (on-page nmbr) ... IIUC, it has to be \on-the-fly #(on-page 2) "page-2-header-text" HTH, Marc __

Re: Bar numbers seem to be one off

2015-09-26 Thread Marc Hohl
Am 26.09.2015 um 13:02 schrieb David Kastrup: [...] Conductor: "Ok, let's start over from bar 1!" Viola section: "We don't have bar numbers in our sheets." :-) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listin

Re: quarter-tone tablatures notation

2015-10-26 Thread Marc Hohl
Am 26.10.2015 um 08:12 schrieb David Kastrup: Thomas Morley writes: Ok. I found a problem: you can't bend an open string ... Well, there is some "behind-the-nut" trickery ;-) Stanley Clarke bent a flageolet note (in his solo for "School Days" on a bass) by pressing the string behind the nu

Re: Linnstrument tablature

2015-10-27 Thread Marc Hohl
Am 27.10.2015 um 19:51 schrieb Michael Ellis: I just acquired a Linnstrument. It's a grid of 200 touchpads, each with independent sensing of pressure and finger motion in both x and y. More about it here . Wow, looks like a futuristic Chapman s

lyluatex and distance between systems

2015-11-05 Thread Marc Hohl
Hi list, I use the lyluatex package for my latest project. Everything looks fine, but unfortunately lyluatex does not support \preLilyPondExample, \postLilyPondExample and \betweenLilyPondSystem, respectively. I want to control the distance between staves, and adding a padding below the lyrics d

Re: lyluatex and distance between systems

2015-11-05 Thread Marc Hohl
Am 05.11.2015 um 21:05 schrieb David Wright: On Thu 05 Nov 2015 at 18:11:52 (+0100), Marc Hohl wrote: I use the lyluatex package for my latest project. Everything looks fine, but unfortunately lyluatex does not support \preLilyPondExample, \postLilyPondExample and \betweenLilyPondSystem

Re: lyluatex and distance between systems

2015-11-06 Thread Marc Hohl
Am 05.11.2015 um 18:11 schrieb Marc Hohl: Hi list, I use the lyluatex package for my latest project. Everything looks fine, but unfortunately lyluatex does not support \preLilyPondExample, \postLilyPondExample and \betweenLilyPondSystem, respectively. To answer my own question after a bit

Re: Colouring guitar strings

2015-11-06 Thread Marc Hohl
Am 07.11.2015 um 06:29 schrieb Jay Vara: Is there a way to have the guitar staff lines colour-coded? That is, have each line in a different colour? There is a snippet that allows you to change the thickness of staff lines. Something along the same lines perhaps could be available. Did you see

Re: Chords with "optional" notes

2015-11-10 Thread Marc Hohl
Am 10.11.2015 um 20:31 schrieb Alberto Simões: Hello There are musics where chords have a smaller note, that is optional. I found some logs from this mailing list in 2007, suggesting things like: \tweak #'font-size #-4 g Is there any easier way? (as in, less verbose). In fact, I

Strange LilyPond crash

2015-11-16 Thread Marc Hohl
Hi list, I am currently reworking some older stuff that compiled perfectly under 2.13.x Yes, I used convert-ly on all files, but nevertheless, I encountered a strange problem: I have a drum part, consisting of an upper and a lower DrumVoice, and if I try to compile the full Drum score, I g

Re: Strange LilyPond crash

2015-11-21 Thread Marc Hohl
Am 17.11.2015 um 00:24 schrieb David Kastrup: Marc Hohl writes: Hi list, I am currently reworking some older stuff that compiled perfectly under 2.13.x Yes, I used convert-ly on all files, but nevertheless, I encountered a strange problem: I have a drum part, consisting of an upper and a

Re: Strange LilyPond crash

2015-11-21 Thread Marc Hohl
Am 21.11.2015 um 10:53 schrieb David Kastrup: Marc Hohl writes: [...] Looks like there is some sequential iterator consulted for pending_moment that no longer has an iter_ to refer to. More likely than not, one of the fixes for addlyrics going off the deep end when its associated context

Re: Strange LilyPond crash

2015-11-22 Thread Marc Hohl
Am 21.11.2015 um 16:54 schrieb David Kastrup: Marc Hohl writes: Am 21.11.2015 um 10:53 schrieb David Kastrup: Marc Hohl writes: [...] Looks like there is some sequential iterator consulted for pending_moment that no longer has an iter_ to refer to. More likely than not, one of the fixes

function to replace notes by rests

2015-11-23 Thread Marc Hohl
Hi list, I have a melody with some spoken passages, written like this: c4 d e f \xNotes { b b b b } f e d c Now I need a midi file that contains the "normal" notes only: c4 d e f r r r r f e d c As the file is a bit lengthy, I think of a way to just redefine \xNotes to change every note to it

Re: Property/ies to control the shape of ties/slurs

2015-11-23 Thread Marc Hohl
Am 23.11.2015 um 10:45 schrieb Urs Liska: Am 23.11.2015 um 10:39 schrieb David Kastrup: Urs Liska writes: I don't seem to be able to find the right property to control the shape of ties. I would like to make the default appearance of ties less flat than what you see in the first attachment

Re: Strange LilyPond crash

2015-11-23 Thread Marc Hohl
Am 24.11.2015 um 00:12 schrieb Thomas Morley: [...] So, commit b416f10429d8d3881445d9000ff422dc67176df1 Author: David Kastrup Date: Wed Jul 15 23:30:30 2015 +0200 Issue 3693: Let Percent_repeat_iterator be unfazed by Timing changes There is still one shortcoming: the percent repea

Re: function to replace notes by rests

2015-11-23 Thread Marc Hohl
Am 23.11.2015 um 21:41 schrieb Malte Meyn: Am 23.11.2015 um 10:46 schrieb Marc Hohl: As the file is a bit lengthy, I think of a way to just redefine \xNotes to change every note to its corresponding rest, instead of rewriting the whole file (or using sed or any other external script). Has

Re: function to replace notes by rests

2015-11-23 Thread Marc Hohl
5 à 08:21, Malte Meyn mailto:lilyp...@maltemeyn.de>> a écrit : Am 24.11.2015 um 08:10 schrieb Marc Hohl: Thanks or sharing! The drawbacks in relative mode are neglectable, I'll use absolute mode. Alternatively you could use 1. another \relative block inside of notesToRests \relative

Re: function to replace notes by rests

2015-11-24 Thread Marc Hohl
Am 24.11.2015 um 09:52 schrieb David Kastrup: [...] Even better, thanks a lot! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: function to replace notes by rests

2015-11-24 Thread Marc Hohl
Am 24.11.2015 um 10:43 schrieb Marc Hohl: Am 24.11.2015 um 09:52 schrieb David Kastrup: [...] Even better, thanks a lot! Well, nearly there. Is it possible to use this function only within a certain Staff? If I write xNote = #(define-music-function (music) (ly:music?) (make-relative

Re: Strange LilyPond crash

2015-11-24 Thread Marc Hohl
Am 24.11.2015 um 17:11 schrieb David Kastrup: Marc Hohl writes: Am 24.11.2015 um 00:12 schrieb Thomas Morley: [...] So, commit b416f10429d8d3881445d9000ff422dc67176df1 Author: David Kastrup Date: Wed Jul 15 23:30:30 2015 +0200 Issue 3693: Let Percent_repeat_iterator be unfazed by

Re: chord tied to the next measure and then "slurred"/pulled-off

2015-12-26 Thread Marc Hohl
Am 26.12.2015 um 15:51 schrieb Federico Bruni: Hi LilyPonders How would you write the following music? My favorite is the first one... The second example is a bug or a limitation of doubleSlurs? Concerning the normal staff, I'd prefer 1, but in terms of tablature, I'd go for the second exampl

Re: Rotation.

2015-12-28 Thread Marc Hohl
Am 28.12.2015 um 08:44 schrieb Hwaen Ch'uqi: Greetings All, I see from the NR that there are ways of rotating individual objects or text markups. Is there a way of rotating an entire score? If you embed the score in a markup, this should work out of the box, IIRC. Marc Thank you for any hel

Re: Strings as variable names

2015-12-28 Thread Marc Hohl
Am 28.12.2015 um 18:49 schrieb David Kastrup: David Sumbler writes: [...] Using the syntax with quotes is rather ugly, I agree. But it is nonetheless potentially useful for two reasons: (1) it enables us to use numbers etc. in variable names Why would that be desirable? Well, speaking jus

Re: Notation snippets

2016-01-03 Thread Marc Hohl
Am 03.01.2016 um 17:05 schrieb Jayaratna: Ouch, I thought you could import glyphs from svg: my knowledge of Metafont is = 0 I did not follow this thread closely, but if you want to add glyphs that are similar to those that already exist, then working with Metafont should not be all that hard IM

<    1   2   3   4   5   6   7   8   9   >