Re: Lilypond 2.24.3 / iMac Sonoma / GS -dNODISPLAY fatal error
On Tue, 2023-11-28 at 01:33 -0500, Eric wrote: > Installed 2.24.3 -docs using Macports, used convert-ly on a couple of > files I'd last worked on in June, and received the following (see > attached text file) after trying lilypond on one of those files and > adding the -V flag. I know that several solutions have been proposed, > including on this list back in June, e.g., but I can't figure out how > to apply them in my own case, sorry... Hi, your log file says that you are actually running LilyPond 2.24.2, which is incompatible with Ghostscript 10.02.1. Please update to the very latest version 2.24.3 that contains a fix, either via MacPorts or by downloading our official binaries. Cheers Jonas signature.asc Description: This is a digitally signed message part
Re: Lilypond 2.24.3 / iMac Sonoma / GS -dNODISPLAY fatal error
> Installed 2.24.3 -docs using Macports, No, you didn't. In the very first line of your log file I can see '2.24.2'. The problem vanishes if you *really* install version 2.24.3 – or if you fix up your system setup so that the correct LilyPond version gets found. Werner
Lilypond 2.24.3 / iMac Sonoma / GS -dNODISPLAY fatal error
Installed 2.24.3 -docs using Macports, used convert-ly on a couple of files I'd last worked on in June, and received the following (see attached text file) after trying lilypond on one of those files and adding the -V flag. I know that several solutions have been proposed, including on this list back in June, e.g., but I can't figure out how to apply them in my own case, sorry... Eric Schissel lilypond -V robertfuchsquartetno4_i.ly Log level set to 287 GNU LilyPond 2.24.2 (running Guile 2.2) Relocation LilyPond binary has absolute file name: /opt/local/libexec/lilypond-bin Setting INSTALLER_PREFIX to '/opt/local' Using run-time value for datadir, setting it to '/opt/local/share/lilypond/2.24.2' Using run-time value for libdir, setting it to '/opt/local/lib/lilypond/2.24.2' Using run-time value for localedir, setting it to '/opt/local/share/locale' Using compile-time value for relocdir, setting it to '' Prepending '/opt/local/libexec' to PATH Setting PATH to '/opt/local/libexec:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/opt/X11/bin' Setting GUILE_AUTO_COMPILE to '0' Setting GUILE_WARN_DEPRECATED to 'detailed' Setting XDG_CACHE_HOME to '/opt/local/share/lilypond/2.24.2' Setting GC_INITIAL_HEAP_SIZE to '40M' Setting GC_NPROCS to '1' Setting GC_FREE_SPACE_DIVISOR to '1' Effective prefix: '/opt/local/share/lilypond/2.24.2' PATH="/opt/local/libexec:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/opt/X11/bin" [/opt/local/share/lilypond/2.24.2/scm/lily/lily.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/lily-library.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/output-lib.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/markup-macros.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/parser-ly-from-scheme.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/file-cache.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/define-event-classes.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/define-music-callbacks.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/define-music-types.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/define-note-names.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/c++.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/chord-entry.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/skyline.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/markup.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/define-markup-commands.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/stencil.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/modal-transforms.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/chord-ignatzek-names.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/music-functions.scm [/opt/local/share/lilypond/2.24.2/scm/lily/define-music-display-methods.scm] ] [/opt/local/share/lilypond/2.24.2/scm/lily/part-combiner.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/autochange.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/define-music-properties.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/time-signature.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/time-signature-settings.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/auto-beam.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/chord-name.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/define-context-properties.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/translation-functions.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/breath.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/script.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/midi.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/layout-beam.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/parser-clef.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/layout-slur.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/font.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/font-encodings.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/bar-line.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/flag-styles.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/fret-diagrams.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/tablature.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/harp-pedals.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/define-woodwind-diagrams.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/display-woodwind-diagrams.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/predefined-fretboards.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/define-grob-properties.scm] [/opt/local/share/lilypond/2.24.2/scm/lily/define-grobs.scm]
Re: Alternate, parenthesised chord names
Thank you Ernie, that looks like just the thing.
Laurie Savage
https://www.queensofthewest.com/
On Tue, 28 Nov 2023 at 16:26, Ernie Braganza
wrote:
> Here's how I've handled it by creating a new Chordnames staff.
>
> \version "2.24.3"
>
> Harmonies = \chordmode {
> a1:maj
> a1:maj
> a1:maj
> }
> AltHarmonies = \chordmode {
> \override ChordName.font-size = #-1
> s1
> b2:m7 e:7
> s1
> }
>
> \score {
> <<
> \new ChordNames \AltHarmonies
> \new ChordNames \Harmonies
> \new Staff {
> R1
> R1
> R1
> }
> >>
> }
>
> For parentheses around Chords, I use this code
> %% Parentheses for Chords %%
>
> #(define (left-parenthesis-ignatzek-chord-names in-pitches bass
> inversion context)
>(markup #:line ("( " (ignatzek-chord-names in-pitches bass inversion
> context
>
> #(define (right-parenthesis-ignatzek-chord-names in-pitches bass
> inversion context)
>(markup #:line ((ignatzek-chord-names in-pitches bass inversion
> context) " )")))
>
> #(define (parenthesis-ignatzek-chord-names in-pitches bass inversion
> context)
>(markup #:line ("( " (ignatzek-chord-names in-pitches bass inversion
> context) " )")))
>
> %aliases
> LParen = { \set chordNameFunction = #left-parenthesis-ignatzek-chord-names
> }
> RParen = { \set chordNameFunction =
> #right-parenthesis-ignatzek-chord-names }
> NoParen = { \unset chordNameFunction }
> OneParen = { \set chordNameFunction = #parenthesis-ignatzek-chord-names }
> %Parentheses around a single chord
>
> and call the function like this:
>
> AltHarmonies = \chordmode {
> s1
> \LParen b2:m7
> \RParen e:7
> \NoParen
> s1
> }
>
>
>
> On Mon, Nov 27, 2023 at 7:41 PM Laurie Savage
> wrote:
>
>> Hi,
>>
>> In jazz lead sheets one often comes across alternate chord names in
>> parentheses written above the standard chord to signify an alternative
>> harmony that can be played. I have tried doing that using this as a simple
>> example of an alternative IIm7-V7 back to Imaj:
>>
>> \version "2.25.4"
>>
>> Harmonies = \chordmode {
>> a1:maj
>> <<
>> { \voiceOne \parenthesize b2:m7 e2:7 }{ \voiceTwo a1:maj }
>> >>
>> \oneVoice
>> a1:maj
>> }
>>
>> \score {
>> <<
>> \new ChordNames \Harmonies
>> \new Staff {
>> R1
>> <<
>> {\voiceOne R1}{\voiceTwo R1}
>> >>
>> \oneVoice R1
>> }
>> >>
>> }
>>
>> but it only produces this (I've also tried the << {..}//{..}>> notation)
>>
>> [image: image.png]
>>
>> Laurie Savage
>> https://www.queensofthewest.com/
>>
>
Re: Alternate, parenthesised chord names
Here's how I've handled it by creating a new Chordnames staff.
\version "2.24.3"
Harmonies = \chordmode {
a1:maj
a1:maj
a1:maj
}
AltHarmonies = \chordmode {
\override ChordName.font-size = #-1
s1
b2:m7 e:7
s1
}
\score {
<<
\new ChordNames \AltHarmonies
\new ChordNames \Harmonies
\new Staff {
R1
R1
R1
}
>>
}
For parentheses around Chords, I use this code
%% Parentheses for Chords %%
#(define (left-parenthesis-ignatzek-chord-names in-pitches bass
inversion context)
(markup #:line ("( " (ignatzek-chord-names in-pitches bass inversion
context
#(define (right-parenthesis-ignatzek-chord-names in-pitches bass
inversion context)
(markup #:line ((ignatzek-chord-names in-pitches bass inversion
context) " )")))
#(define (parenthesis-ignatzek-chord-names in-pitches bass inversion
context)
(markup #:line ("( " (ignatzek-chord-names in-pitches bass inversion
context) " )")))
%aliases
LParen = { \set chordNameFunction = #left-parenthesis-ignatzek-chord-names }
RParen = { \set chordNameFunction = #right-parenthesis-ignatzek-chord-names
}
NoParen = { \unset chordNameFunction }
OneParen = { \set chordNameFunction = #parenthesis-ignatzek-chord-names }
%Parentheses around a single chord
and call the function like this:
AltHarmonies = \chordmode {
s1
\LParen b2:m7
\RParen e:7
\NoParen
s1
}
On Mon, Nov 27, 2023 at 7:41 PM Laurie Savage
wrote:
> Hi,
>
> In jazz lead sheets one often comes across alternate chord names in
> parentheses written above the standard chord to signify an alternative
> harmony that can be played. I have tried doing that using this as a simple
> example of an alternative IIm7-V7 back to Imaj:
>
> \version "2.25.4"
>
> Harmonies = \chordmode {
> a1:maj
> <<
> { \voiceOne \parenthesize b2:m7 e2:7 }{ \voiceTwo a1:maj }
> >>
> \oneVoice
> a1:maj
> }
>
> \score {
> <<
> \new ChordNames \Harmonies
> \new Staff {
> R1
> <<
> {\voiceOne R1}{\voiceTwo R1}
> >>
> \oneVoice R1
> }
> >>
> }
>
> but it only produces this (I've also tried the << {..}//{..}>> notation)
>
> [image: image.png]
>
> Laurie Savage
> https://www.queensofthewest.com/
>
Alternate, parenthesised chord names
Hi,
In jazz lead sheets one often comes across alternate chord names in
parentheses written above the standard chord to signify an alternative
harmony that can be played. I have tried doing that using this as a simple
example of an alternative IIm7-V7 back to Imaj:
\version "2.25.4"
Harmonies = \chordmode {
a1:maj
<<
{ \voiceOne \parenthesize b2:m7 e2:7 }{ \voiceTwo a1:maj }
>>
\oneVoice
a1:maj
}
\score {
<<
\new ChordNames \Harmonies
\new Staff {
R1
<<
{\voiceOne R1}{\voiceTwo R1}
>>
\oneVoice R1
}
>>
}
but it only produces this (I've also tried the << {..}//{..}>> notation)
[image: image.png]
Laurie Savage
https://www.queensofthewest.com/
forgotten how to get system separator on both sides
Long ago I was an active user but it's gotten so far away that I use an older version 2.22.1 longer ago my conductor (at the time) wanted slash separators on both sides of the system that was for 1.16.x I think. But is this possible again? If so please either direct me to the snippet or page in the manuals. thanks Sam -- Thank you Sound & Silence 1814 Lake Washington Blvd. So., Seattle, Wa. 98144 _206-328-7694 or messages at 206-308-8189_ _www.soundand.com_
Re: How do I arpeggiate across voices?
On Mon, Nov 27, 2023 at 11:16 AM Michael Werner wrote: > On Mon, Nov 27, 2023 at 7:43 AM Kevin Cole wrote: > >> Thanks. Not sure how I missed that in my search... That seems the best >> answer -- though, alas, the MIDI arpeggiator cannot take advantage of it. >> (I may be able to suss that out "the hard way" manually though.) >> > > Sorry, but MIDI is an area I know almost nothing about, as I almost never > use it. My main focus is hardcopy. Best I can come up with is to do > something a little like what is shown in > > >> MIDI arpeggiator: >> https://lists.gnu.org/archive/html/lilypond-user/2020-12/msg00036.html >> > > It would involve basically making a parallel version of your music that, > while not looking like what you want the printed output to look like, will > sound right (or close to it) once run through the MIDI system. > That's essentially the direction I've gone. (I already regularly split / duplicate the score into a print layout version and a MIDI version. It's just a matter of figuring out what, if anything, will sound "right" to my amateur ear.)
Re: How do I arpeggiate across voices?
Hi Kevin,
On Mon, Nov 27, 2023 at 7:43 AM Kevin Cole wrote:
> Thanks. Not sure how I missed that in my search... That seems the best
> answer -- though, alas, the MIDI arpeggiator cannot take advantage of it.
> (I may be able to suss that out "the hard way" manually though.)
>
Sorry, but MIDI is an area I know almost nothing about, as I almost never
use it. My main focus is hardcopy. Best I can come up with is to do
something a little like what is shown in
> MIDI arpeggiator:
> https://lists.gnu.org/archive/html/lilypond-user/2020-12/msg00036.html
>
It would involve basically making a parallel version of your music that,
while not looking like what you want the printed output to look like, will
sound right (or close to it) once run through the MIDI system. The two
versions would then be decided on via the tags as shown in the
linked example. It'll be a bit of a tedious PITA, but it'll get the job
done. Sorta kinda. Anyway, something like:
\version "2.25.10"
\language "english"
\include "../include/arpeggioMIDI.ly"
music = \relative c' {
\set Staff.connectArpeggios = ##t % Need to tell Lilypond to play connect
the dots with the arpeggios
e4 e e
\tag #'layout {
<<
{ e4\arpeggio e4 b4 | e2 b8[ b8] | }
\\
{ 2.\arpeggio | \stemUp gs2 \stemNeutral s4 | }
>>
}
\tag #'midi {
<<
{ \midiArpeggio 12 4 e b | e2 b8 b }
\\
{ 2. | gs2 s4 }
>>
}
d'4 d d
}
\score {
\new Staff \with {
\consists "Span_arpeggio_engraver" % Could also be done in a layout
block
} {
\time 3/4
\new Voice {
\removeWithTag #'midi \music
}
}
\layout {}
}
\score { % Added this one out of curiosity - wanted to see what it would
look like.
\new Staff \with {
\consists "Span_arpeggio_engraver" % Could also be done in a layout
block
} {
\time 3/4
\new Voice {
\removeWithTag #'layout \music
}
}
\layout {}
}
\score {
\new Staff {
\time 3/4
\new Voice {
\removeWithTag #'layout \music
}
}
\midi {}
}
That's the rough approach. And I'm not real sure just how close that MIDI
output sounds compared to what it should be. There's bound to be a better
way to do this. I just don't know what that better way might be.
--
Michael
Re: How do I arpeggiate across voices?
On Mon, Nov 27, 2023 at 12:33 AM Michael Werner wrote: > Hi Kevin, > > On Sun, Nov 26, 2023 at 7:38 PM Kevin Cole wrote: > >> I'm looking at a pice of music that shows an arpeggio between two >> dotted half-notes in one voice and a quarter-note in the other voice. >> Specifically, in the wee snippet below, the first e4 in the first >> voice is at the top of the arpeggio above the 2 in the second >> voice. >> > > Having a look at > http://lilypond.org/doc/v2.25/Documentation/notation/arpeggio#index-arpeggio_002c-cross_002dvoice > it turns out there's a Span_arpeggio_engraver you can add to take care of > this. Also, a Staff.connectArpeggios property to set. Adding those in, your > example becomes: > Thanks. Not sure how I missed that in my search... That seems the best answer -- though, alas, the MIDI arpeggiator cannot take advantage of it. (I may be able to suss that out "the hard way" manually though.) MIDI arpeggiator: https://lists.gnu.org/archive/html/lilypond-user/2020-12/msg00036.html https://lists.gnu.org/archive/html/lilypond-user/2020-12/msg00039.html
