Re: Mapping pitches to other pitches when generating MIDI files for percussion?

On 2018-11-12 7:22 pm, Vinicius Mascarenhas wrote: TLDR: I need to map different pitches displayed in the layout block / PDF file to a single sound in the midi block / file (like say map both c and a to b,) but I can’t to that to the whole staff — I need to be able to map other sets of pitches to

Re: Edition Engraver in 2.19

Hi,I, like the original poster, was also intrigued, by people's enthusiastic comments about the power of OpenLilyLib and the Edition Engraver. And like the O.P. I never really got started.I guess the question is: How complex a LilyPonds score has to be before EE really starts making things easier i

Re: Configuring home/bin PATH directory

What OS are you using? For Linux your $PATH is usually set in one of the shell . files, for Windows it is set in ControlPanel\System. David Bowen On Mon, Nov 12, 2018 at 7:34 PM Keizen Li Qian wrote: > Hello, > > I installed 2.18.2 on a drive with a partitioned home directory which had > an old

Mapping pitches to other pitches when generating MIDI files for percussion?

Hey y’all, TLDR: I need to map different pitches displayed in the layout block / PDF file to a single sound in the midi block / file (like say map both c and a to b,) but I can’t to that to the whole staff — I need to be able to map other sets of pitches to another single sound. Can Lilypond do

Configuring home/bin PATH directory

Hello, I installed 2.18.2 on a drive with a partitioned home directory which had an old ~home/bin/lilypond. Somewhere the path had been set to this directory so even after convert-ly successfully converted my old files to 2.18, running lilypond still grabbed an old version in home/bin. After renam

Re: Edition Engraver in 2.19

Hi Reggie, > is that all the documentation for such a powerful tweak tool in lilyPond? Yes, unfortunately. And, to be accurate, it’s not "in" Lilypond — it’s a separate library. > How do new users learn this tool and all its possibilites? I learned by looking at the examples, trial and error, a

Re: Triangle Arrow shape above Staff

Or combine something like: { \mark\markup \override #'(baseline-skip . 2.7) \center-column { \draw-line #'(0 . 5) \n-agon #3 #-3 \bold\fontsize #1.5 "3" } c' } Cheers, Pierre Le mar. 13 nov. 2018 à 00:51, Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com> a écrit : > H

Re: Triangle Arrow shape above Staff

Hi Reggie, For the triangle, see https://archiv.lilypondforum.de/index.php/topic,1279.msg7040.html#msg7040 e.g. : \version "2.19.80" #(define-markup-command (n-agon layout props corners radius arg) (number? number? markup?) #:category graphic #:properties ((thickness 1)) (let* ((th (* (ly

Triangle Arrow shape above Staff

How do you put a triangle shape with duration beat number inside above staff in 2.19 please as well as a standard conductor arrow thank you I cannot find how to. shapee.png -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f

Re: Edition Engraver in 2.19

Karlin High wrote > On Sun, Nov 11, 2018 at 2:55 PM Reggie < > reegistoop@ > > wrote: > > > So far, the best information I've seen for getting started with the > Edition Engraver is this post by Stéfano Troncaro. > > ; is

Re: Bug? \clef makes Staff disappear

Thomas Morley writes: > Am Mo., 12. Nov. 2018 um 20:30 Uhr schrieb David Kastrup : > >> It sounds rather shaky to rely on that for code intended to be used as a >> starting point or example. "It's ok if you know what you are doing" is >> not ok when intended to be helpful for people who haven't

Re: Bug? \clef makes Staff disappear

Am Mo., 12. Nov. 2018 um 19:02 Uhr schrieb Torsten Hämmerle : > It really starts getting funny if you change the c' into a d' (the c' just > didn't show up somewhere because it did not change the C major chord): > > %% > << > \chords { c } > \relative { \clef bass d' } > >> > %

Re: Bug? \clef makes Staff disappear

Am Mo., 12. Nov. 2018 um 20:30 Uhr schrieb David Kastrup : > > Torsten Hämmerle writes: > > > David Kastrup wrote > >> If you want a Staff, create it rather than rely on somebody else doing > >> that, maybe. > > > > That is basically what I thought (and wrote), too. > > But, admittedly, these shor

Re: Combining lyric verses onto one line

No, I had not gotten the replies sent to my email. Thanks, Rohan On Sun, Nov 11, 2018 at 11:53 PM Thomas Morley wrote: > Am Mo., 12. Nov. 2018 um 05:36 Uhr schrieb Rohan Srinivasan > : > > > > Friendly bump. > > Hi, > > this was asnwered already: > > http://lilypond.1069038.n5.nabble.com/Combin

Re: Bug? \clef makes Staff disappear

Torsten Hämmerle writes: > David Kastrup wrote >> If you want a Staff, create it rather than rely on somebody else doing >> that, maybe. > > That is basically what I thought (and wrote), too. > But, admittedly, these shortcuts used to work in prior releases and even can > be found in the Notation

Re: Bug? \clef makes Staff disappear

Am 12.11.18 um 19:00 schrieb Torsten Hämmerle: Hi Malte, You'll have to introduce a \new Staff. Otherwise, the \relative clause (pun, pun…) will just be parallel music in ChordNames mode and in ChordNames, there are no clefs. Thanks to both of you, David and Torsten, for the explanations. I

Re: Bug? \clef makes Staff disappear

David Kastrup wrote > If you want a Staff, create it rather than rely on somebody else doing > that, maybe. That is basically what I thought (and wrote), too. But, admittedly, these shortcuts used to work in prior releases and even can be found in the Notation Reference Manual: http://lilypond.or

Re: Bug? \clef makes Staff disappear

Malte Meyn writes: > Hi list, > > I’m not sure whether the following comes from my missing knowledge or > a bug. In the code below, adding the clef makes the Staff > disappear. Why? > > % > \version "2.19.82" > > << > \chords { c } > \relative { \clef bass c' } >>>

Re: Bug? \clef makes Staff disappear

Am 12.11.18 um 18:51 schrieb Michael Hendry: On 12 Nov 2018, at 17:30, Malte Meyn wrote: % \version "2.19.82" << \chords { c } \relative { \clef bass c' } % It works correctly for me, but I’m using Lilypond version 2.18.2. It

Re: Bug? \clef makes Staff disappear

Hi Malte, You'll have to introduce a \new Staff. Otherwise, the \relative clause (pun, pun…) will just be parallel music in ChordNames mode and in ChordNames, there are no clefs. It really starts getting funny if you change the c' into a d' (the c' just didn't show up somewhere because it did not

Re: Bug? \clef makes Staff disappear

> On 12 Nov 2018, at 17:30, Malte Meyn wrote: > > % > \version "2.19.82" > > << > \chords { c } > \relative { \clef bass c' } > >> > % It works correctly for me, but I’m using Lilypond version 2.18.2. I’ve always used “\relative” with a

Bug? \clef makes Staff disappear

Hi list, I’m not sure whether the following comes from my missing knowledge or a bug. In the code below, adding the clef makes the Staff disappear. Why? % \version "2.19.82" << \chords { c } \relative { \clef bass c' } >> %