Re: Problem with Null Voice changing length of stems on beamed notes
Hi palartu,
> When using *NullVoice* in Staff context, it changes *length of stems on
> beamed notes*. Try to compile this example and see an output. When you
> *comment* line with Null Voice, *length of stems changes*. It depends on the
> *position of the notes in staff*. Sometimes, stems are shorter, and
> sometimes, longer.
>
>
> \version "2.18.2"
>
> aligner = { c'8 b16 c'16~ c'4 fis'2 }
> alt = { a8 g16 a16~ a4 a2 }
> sopran = { c'8 b16 c'16~ c'4 fis'2 }
>
> \score {
> \new Staff <<
> \partcombine \sopran \alt
> \new NullVoice = "null" \aligner
> >>
> }
> *
I tried this on 2.19.54 and there is no difference. Maybe you experience
a bug that's fixed?!
> Moreover, if you try to replace *part combine* line with
>
> ***
> \new Voice { \sopran }
> **
>
> the behaviour is the same.
Not sure I uderstand that correctly but again on 2.19.54 I've seen no
difference.
> Please, tell me that I can have consistent behaviour for this problem within
> Lilypond.
You can have consistent behaviour for this problem within Lilypond.
Kind regards,
Michael
--
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver
signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi segfault with PyQt4-
Hi Andrew, > I'm wondering if anybody is having recent issues with Frescobaldi. I run > a rolling-release distro (gentoo), so I install/update packages on an > ongoing basis. In this case, the only package in frescobaldi's > dependency tree that's been updated since mid-December is PyQt4, which > just saw the final release of 4.12 this last week. > > Now, Frescobaldi segfaults on startup, with no error message. > > Can anybody else on the list report similar or differing experiences? > Anybody else having issues? I'm also on a rolling release distro (ArchLinux) and they recently rolled out Python 3.6. As a consequence I had to manually reinstall some python packages (pyly and poppler integration) that are not part of the official repositories. After having done that all problems were gone. Kind regards, Michael -- Michael Gerdau email: m...@qata.de GPG-keys available on request or at public keyserver signature.asc Description: OpenPGP digital signature ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cannot use \layout in a variable
On 12.01.2017 05:07, David Wright wrote: \relative is a command that controls how LP interprets the notes' octavation, More precisely: a music function, i.e. a procedure which returns music. Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cannot use \layout in a variable
David,
Thanks for posting this. I was out most of yesterday and didn't have time to do
it. I'd intended to do it this morning (UK time) but found you'd got there
first.
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Thursday, January 12, 2017, 4:07:18 AM, you wrote:
> | I've added the missing text with a sidebar:
> On Wed 11 Jan 2017 at 05:03:21 (-0700), ptoye wrote:
>> Thanks all for putting me right. I have to say that the documentation is very
>> confusing as to the syntax. From the Learning manual:
> | A variable is assigned as follows:
> | namedMusic = { ... }
> So "..." is typically a sequence of notes or a sequence of music expressions.
> The {} indicate a seqeunce rather than simultaneous expressions << >>.
>> which implies that the brackets are needed, but it's followed by:
> | violin = \new Staff {
> | \relative {
> | a'4 b c b
> | }
> | }
> Here { a'4 b c b } is a music expression, \relative is a command that
> controls how LP interprets the notes' octavation, and \new is a
> command that wraps one expression in the Staff context.
> You could write
> violin = \new Staff
> \relative {
> a'4 b c b
> }
> just as you could write
> cello = \new Staff d'
> because d' is one expression.
>> and later by:
> | width = 4.5\cm
> Here you should read up the Notation Reference §3.1.5.
> width is not a music expression, so you couldn't write, say,
> { \namedMusic \width }
> So \width needs to be interpreted in something like \paper { \width
> and other things }. What you set a variable to (ie the right hand side)
> determines where you can later use it.
>> which don't have the brackets.
>> How does the parser know when the variable definition has finished if it can
>> be on multiple lines?
> If there are no braces (or equivalent), then it'll be a single item,
> but that item could be a command with its own argument following it.
> compiler = \markup Rutter
> I hope some of that makes sense.
> Cheers,
> David.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi segfault with PyQt4-
Hi Michael, On Thu, Jan 12, 2017 at 10:16 AM, Michael Gerdau wrote: > I'm also on a rolling release distro (ArchLinux) and they recently > rolled out Python 3.6. As a consequence I had to manually reinstall some > python packages (pyly and poppler integration) that are not part of the > official repositories. After having done that all problems were gone. > My version of python-poppler-qt4 no longer compiles against sip (version 4.12 apparently breaks the ABI). So I'm stuck. *sigh* and I just got back to working with Lily again (my system also moved to Guile-2 last summer, so I have *that* problem as well and have to run off the precompiled binaries of Lily that come with Guile-1.8 prepackaged). Or did you mean some other package when you referred to "poppler integration"? Is "pyly" the python-ly package? Cheers, A ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi segfault with PyQt4-
Hi Andrew, > My version of python-poppler-qt4 no longer compiles against sip (version > 4.12 apparently breaks the ABI). So I'm stuck. > > *sigh* and I just got back to working with Lily again (my system also > moved to Guile-2 last summer, so I have *that* problem as well and have > to run off the precompiled binaries of Lily that come with Guile-1.8 > prepackaged). > > Or did you mean some other package when you referred to "poppler > integration"? Is "pyly" the python-ly package? python-ly-0.9.4 and python-poppler-qt4-0.24.0 All other required packages are part of the regular ArchLinux archives. FWIW ArchLinux ships with sip-4.18.1 - not sure that will help you though. In response to the recent discussion in another thread as to whether we should fork guile-1.8.8 as guile1: ArchLinux ships with both versions - guile1.8 (version 1.8.8) - guile (version 2.0.13) as of writing this email. Kind regards, Michael -- Michael Gerdau email: m...@qata.de GPG-keys available on request or at public keyserver signature.asc Description: OpenPGP digital signature ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Global vs. local staff size
I discovered an oddity when changing the staff size. If I use
layout-set-staff-size certain chords produce an ugly alignment, whereas a
set-global-staff-size doesn't. In the following snippet, uncomment line 5 and
comment line 20 and the 3rd chord changes its layout. Oddly, the surrounding
chords are OK. Something to do with ledger-lines, maybe?
Also, I thought that the local staff size should take precedence over the
global, but if both lines are left in the chord is OK.
\version "2.19.52"
\language "english"
%#(set-global-staff-size 14)
\score {
\new Staff
{
\clef treble
\relative
{
}
}
\layout {
%comment out this line
#(layout-set-staff-size 14)
}
}
Regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Find out denominator of current time signature
11.01.2017 um 18:46 schrieb Malte Meyn:
You can get the duration from the context property timeSignatureFraction
or baseMoment:
%
\version "2.19.53"
{
\time 12/8
\applyContext
#(lambda (context)
(display (ly:context-property
context
'baseMoment)))
%'timeSignatureFraction)))
}
%
I don’t know how you can make a music function that uses this and
returns music. \applyContext #(lambda (context) (make-music …)) has no
visible output. But maybe it’s a start.
That's definitely going into the right direction - many thanks. I tried this:
\new Staff <<
{
c'4 d'4 e'4 f'4
}
{
\applyContext
#(lambda (context)
(make-music
'SkipEvent
'articulations
(list (make-music
'AbsoluteDynamicEvent
'text
"ff"))
'duration
(ly:make-duration 0 0 1 (cdr (ly:context-property
context
'timeSignatureFraction)
}
>>
which is apparently valid, but the created skip event is not inserted into the
music (which your reply already suggested). I guess the problem boils down to
how to get hold of the context without \applyContext.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi segfault with PyQt4-
Hi Michael, On Thu, Jan 12, 2017 at 11:22 AM, Michael Gerdau wrote: > python-ly-0.9.4 and python-poppler-qt4-0.24.0 > according to this bug: https://bugs.gentoo.org/show_bug.cgi?id=604472, the 0.24.0 version of python-poppler-qt4 does not compile against sip-4.19. I'm not even sure where they found the 0.24.0 version, as it's not in our regular repository. I also don't find a version of python-poppler-qt that uses qt5, so I'm not sure the solution over at the github issue (where frescobaldi-3* is being run against qt5, and apparently works ok when python-poppler-qt[5] is recompiled) would work for me. Cheers, A ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Midi output with highlighted voices
Dear Ponders,
I have a feature wish, and I hope this is the right channel to utter it:
I typeset choir pieces and in this field it is a big advantage of
LilyPond that producing MIDI files with highlighted voices for each
single voice is possible. Today I do this by defining a new book for
each voice and by "highlighting" the respective voice - by increasing
her volume and assigning her a distinct midiInstrument - see the
attached MWE. The result is good and very usable for choirs to improve
the individual practicing at home.
But the input is ugly. The MWE works with only 2 voices and yet has a
lot of repetitive code. Imagine a piece with 8 voices! The MIDI output
for 8 highlighted voices would need hundreds of highly repetitive lines
of LilyPond code. I wish there was a feature to produce the output with
one line of code in the \midi{}-section of the pdf producing \score.
LilyPond would have to loop over the voices in the score and produce a
book as described in the MWE.
I have tried to understand Scheme multiple times but I didn't make it
yet. That's why I would be thankful if someone could write the Scheme
function to achieve that. I think many typesetters of choir music would
appreciate an easy way to produce the MIDI as described. (Actually,
there are some guys around who do that with some other programmes, see
[1], [2]). I believe most typesetters don't know the way how to do it
with LilyPond today - that's why I think this would be a great benefit
for the community.
Kind regards,
Jonathan
[1] http://www.learnchoralmusic.co.uk/
[2] http://www.choraltech.us/midilibrary.htm
\version "2.19.22"
% preliminary definitions
staffToVoice = \midi {
\context {
\Staff
\remove "Staff_performer"
}
\context {
\Voice
\consists "Staff_performer"
}
}
backgroundVoice = {
\set midiInstrument = #"recorder"
\set Voice.midiMinimumVolume = #0.0
\set Voice.midiMaximumVolume = #0.3
}
highlightedVoice= {
\set midiInstrument = #"trombone"
\set Voice.midiMinimumVolume = #0.4
\set Voice.midiMaximumVolume = #1.0
}
global = {
\key c \major
\time 4/4
}
sopTune = \relative c' {
c4 d e f
g a b c
d1
}
altTune = \relative c' {
c8[ a] b[ d] a[ c] g[ b]
c4 r r f4
g2 a
}
% the book for pdf output
\book {
\score {
\new StaffGroup <<
\new Staff <<
\new Voice = "soprano" { \global \sopTune }
>>
\new Staff <<
\new Voice = "alto" { \global \altTune }
>>
>>
\layout {}
}
}
% the books for MIDI output
\book {
\bookOutputSuffix "soprano in context"
\score {
\unfoldRepeats
\new Staff <<
\new Voice = "soprano" { \highlightedVoice \global \sopTune }
\new Voice = "alto" { \backgroundVoice \global \altTune }
>>
\midi {
\staffToVoice
}
}
}
\book {
\bookOutputSuffix "alto in context"
\score {
\unfoldRepeats
\new Staff <<
\new Voice = "soprano" { \backgroundVoice \global \sopTune }
\new Voice = "alto" { \highlightedVoice \global \altTune }
>>
\midi {
\staffToVoice
}
}
}
\book {
\bookOutputSuffix "soprano solo"
\score {
\unfoldRepeats
\new Staff <<
\new Voice = "sop" { \global \sopTune }
>>
\midi {
\staffToVoice
}
}
}
\book {
\bookOutputSuffix "alto solo"
\score {
\unfoldRepeats
\new Staff <<
\new Voice = "alt" { \global \altTune }
>>
\midi {
\staffToVoice
}
}
}
% What I would like to have is a solution like this to achieve the same
%{
\book {
\score {
\new StaffGroup <<
\new Staff <<
\new Voice = "soprano" { \global \sopTune }
>>
\new Staff <<
\new Voice = "alto" { \global \altTune }
>>
>>
\layout {}
\midi{
\makeMidiWithHighlightedVoices
\makeMidiSolos
}
}
}
%}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Which Linux distro for Lilypond
Hi Werner et al.!
*If* we bundle guile 1.8 with lilypond, I strongly prefer static
linking of the library (this is, adding `--disable-shared' to guile's
configure script, together with a proper argument to the
`--datarootdir' option to install the .scm files under a lilypond
directory). This avoids *any* problems with different guile library
versions, and the created lilypond binary can peacefully coexist with
guile 2.0 even in the `/usr' tree.
After a loser look at the sources and the build system I think it's better
(= much easier) to stay with shared libraries.
At runtime we do need both libguile and guile itself (it is used by
lilypond-invoke-editor), and all of our guile must be invisible to the
rest of the system.
That means:
+ there must be no entry in PATH leading to our private guile, guile-config etc.
+ there must be no entry leading to libguile etc in the system library search
path.
All that is possible without major changes to the sources... attached find a
bash
script as a proof of concept. The requirements described above are met.
It passes the "full make" test without problems:
knut@golem:~/sources>./mknewlily
Building GUILE 579b6041730357abcbb01e1f259e37c6e573cb7c first ...
First we add a library search path to libguile/dynl.c
exec ./autogen.sh in /home/knut/sources/guile ... succeeded after 14 seconds
exec ./configure --disable-error-on-warning
--prefix=/home/knut/sources/lilybuilt/share/lilypond in
/home/knut/sources/guile ... succeeded after 10 seconds
exec make -j 11 in /home/knut/sources/guile ... succeeded after 10 seconds
exec make -j 11 install in /home/knut/sources/guile ... succeeded after 1
seconds
Building LILYPOND 5bfd1e31928841704c5e5913290b948f6a480b09...
exec ./autogen.sh --noconfigure in /home/knut/sources/lily ... succeeded
after 1 seconds
exec ../configure --prefix=/home/knut/sources/lilybuilt in
/home/knut/sources/lily/build ... succeeded after 5 seconds
exec make -k -j 11 CPU_COUNT=11 all in /home/knut/sources/lily/build ...
succeeded after 92 seconds
exec make -j 11 CPU_COUNT=11 install in /home/knut/sources/lily/build ...
succeeded after 1 seconds
exec make -j 11 CPU_COUNT=11 doc in /home/knut/sources/lily/build ...
succeeded after 838 seconds
exec make -j 11 CPU_COUNT=11 install-doc in /home/knut/sources/lily/build ...
succeeded after 18 seconds
Total guile and lilypond build time: 990 seconds
cu,
Knut
#!/bin/bash
#
# Build lilypond and guile 1.8 in a way that
# -> guile is installed under PREFIX/share/lilypond
# -> guile does not need to be in PATH
# -> libguile does not need to be in the systems library search path
#
RED='\033[0;31m'
NOCOLOR='\033[0m'
STARTTIME=`date +"%s"`
#===
# Adapt the next three lines to your needs!
# LILYSOURCE is the local lilypond git repository
# GUILESOURCE is the local guile git repository
# LILYROOT is the install destination root directory
#===
LILYSOURCE=/home/knut/sources/lily
GUILESOURCE=/home/knut/sources/guile
LILYROOT=/home/knut/sources/lilybuilt
#===
# derived from the defintions above, there should be
# no need to change these:
#===
BUILDLOG=$LILYROOT/lilypond_buildlog
GUILEROOT=$LILYROOT/share/lilypond
GUILELIBDIR=$GUILEROOT/lib64
GUILEBINDIR=$GUILEROOT/bin
LILYLIBDIR=$LILYROOT/lib64/lilypond
LILYBINDIR=$LILYROOT/bin
#===
# options for make
#===
LILYMAKEPAR="-j 11 CPU_COUNT=11"
GUILEMAKEPAR="-j 11"
function doit {
AT=`date +"%s"`
echo -en " exec $RED$1$NOCOLOR in `pwd` ..."
$1 &>> $BUILDLOG
if [ $? -ne 0 ]; then echo -n " failed";cat $BUILDLOG;exit 1;else echo -n "
succeeded";fi
BT=`date +"%s"`
let "CT = $BT - $AT"
echo " after $CT seconds"
}
#
# ensure that our LILYROOT directory exists!
mkdir -p $LILYROOT
cd $GUILESOURCE
git checkout branch_release-1-8 &>> $BUILDLOG
git reset --hard &>> $BUILDLOG
git clean -dfx &>> $BUILDLOG
echo Building GUILE `git rev-parse HEAD` first ...
#
# We do not want our guile to be visible to other applications, so we
# need to tell our hidden libguile where it has to look for module libraries!
#
echo " First we add a library search path to libguile/dynl.c"
sed -i "s|lt_dlinit ();|lt_dlinit (); lt_dlsetsearchpath (\"$GUILELIBDIR\");|"
libguile/dynl.c
doit "./autogen.sh"
doit "./configure --disable-error-on-warning --prefix=$GUILEROOT"
doit "make $GUILEMAKEPAR"
doit "make $GUILEMAKEPAR install"
#===
# As our guile is hidden, our binaries need to know where
# guile and libguile is located ... during build we need
# guile-config etc to be in PATH.
#===
PATH=$GUILEBINDIR:$PATH
export LDFLAGS="-Wl,-rpath,$GUI
Re: chords name
Robert,Thank you for the link and explanation about the chordsImmanuel,Ming From: Robert Schmaus To: MING TSANG Cc: Lilypond-usermailinglist Sent: Thursday, January 12, 2017 12:43 AM Subject: Re: chords name Ming, That would be g : m7.5- / f or alternatively g : min7.5- / f Cf here: http://lilypond.org/doc/v2.18/Documentation/notation/common-chord-modifiers Best, Robert On 12 Jan 2017, at 04:26, MING TSANG wrote: dear lilyponders, I transcribe a score, I encounter Gm7(b5)/F and don't know how to code it.Any help is appreciated. Immanuel,Ming ___ 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: Midi output with highlighted voices
Hi Jonathan.
Fredobaldi v2.19.0 can do what you are looking for.Here below is score wizard
of frecobaldi generated skeleton code. If you want pinano midi as background,
you can move "rehearsalMidi" section after "% Rehearsal MIDI files:" section
and add pinano staff after SATB staff. The midi generated whill have what you
need.
Immanuel,Ming
%start\version "2.19.53"
\header { title = "highlighted midi output"}
global = { \key c \major \time 4/4 \tempo 4=100}
soprano = \relative c'' { \global % Music follows here. }
alto = \relative c' { \global % Music follows here. }
tenor = \relative c' { \global % Music follows here. }
bass = \relative c { \global % Music follows here. }
verse = \lyricmode { % Lyrics follow here. }
rehearsalMidi = #(define-music-function (parser location name midiInstrument
lyrics) (string? string? ly:music?) #{ \unfoldRepeats << \new Staff =
"soprano" \new Voice = "soprano" { \soprano } \new Staff = "alto" \new
Voice = "alto" { \alto } \new Staff = "tenor" \new Voice = "tenor" { \tenor
} \new Staff = "bass" \new Voice = "bass" { \bass } \context Staff =
$name { \set Score.midiMinimumVolume = #0.5 \set
Score.midiMaximumVolume = #0.5 \set Score.tempoWholesPerMinute =
#(ly:make-moment 100 4) \set Staff.midiMinimumVolume = #0.8 \set
Staff.midiMaximumVolume = #1.0 \set Staff.midiInstrument =
$midiInstrument } \new Lyrics \with { alignBelowContext = $name
} \lyricsto $name $lyrics >> #})
right = \relative c'' { \global % Music follows here. }
left = \relative c' { \global % Music follows here. }
choirPart = \new ChoirStaff << \new Staff \with { midiInstrument = "choir
aahs" instrumentName = \markup \center-column { "Soprano" "Alto" } } <<
\new Voice = "soprano" { \voiceOne \soprano } \new Voice = "alto" {
\voiceTwo \alto } >> \new Lyrics \with { \override VerticalAxisGroup
#'staff-affinity = #CENTER } \lyricsto "soprano" \verse \new Staff \with {
midiInstrument = "choir aahs" instrumentName = \markup \center-column {
"Tenor" "Bass" } } << \clef bass \new Voice = "tenor" { \voiceOne \tenor
} \new Voice = "bass" { \voiceTwo \bass }
pianoPart = \new PianoStaff \with { instrumentName = "Piano"} << \new Staff =
"right" \with { midiInstrument = "acoustic grand" } \right \new Staff =
"left" \with { midiInstrument = "acoustic grand" } { \clef bass \left }>>
\score { << \choirPart \pianoPart >> \layout { } \midi { }}
% Rehearsal MIDI files:\book { \bookOutputSuffix "soprano" \score {
\rehearsalMidi "soprano" "soprano sax" \verse \midi { } }}
\book { \bookOutputSuffix "alto" \score { \rehearsalMidi "alto" "soprano
sax" \verse \midi { } }}
\book { \bookOutputSuffix "tenor" \score { \rehearsalMidi "tenor" "tenor
sax" \verse \midi { } }}
\book { \bookOutputSuffix "bass" \score { \rehearsalMidi "bass" "tenor
sax" \verse \midi { } }}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: OOoLilyPond
Klaus Blum wrote > Hi Henning, > > SVG mode should work as long as you don't use lilypond-book-preamble which > is "hidden" in most of the templates. > > Cheers, > Klaus Klaus, This extension is working great on my XFCE LibreOffice, thank you so much for modifying this and sharing with us. - composer | sound designer | asmr artist LilyPond Tutorials (for beginners) --> http://bit.ly/bcl-lilypond -- View this message in context: http://lilypond.1069038.n5.nabble.com/OOoLilyPond-tp185560p199133.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 segfault with PyQt4-
Hi Andrew,
> according to this bug: https://bugs.gentoo.org/show_bug.cgi?id=604472,
> the 0.24.0 version of python-poppler-qt4 does not compile against
> sip-4.19. I'm not even sure where they found the 0.24.0 version, as it's
> not in our regular repository.
The AUR package for arch gets it from
https://github.com/wbsoft/python-poppler-qt4/archive/v0.24.0.tar.gz
> I also don't find a version of
> python-poppler-qt that uses qt5, so I'm not sure the solution over at
For python-poppler-qt5 the AUR retrieves
https://github.com/wbsoft/python-poppler-qt5/archive/v0.24.2.tar.gz
and then applies the attached patch to it.
Kind regards,
Michaelw
--
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver
diff -aur python-poppler-qt5-0.24.2.pristine/poppler-qt5.sip python-poppler-qt5-0.24.2.new/poppler-qt5.sip
--- python-poppler-qt5-0.24.2.pristine/poppler-qt5.sip 2016-02-07 14:36:03.574983819 +0100
+++ python-poppler-qt5-0.24.2.new/poppler-qt5.sip 2016-02-07 14:37:37.955122246 +0100
@@ -6,10 +6,13 @@
*/
+%Feature QTXML_AVAILABLE
+
%Import QtCore/QtCoremod.sip
%Import QtGui/QtGuimod.sip
-
-%Feature QTXML_AVAILABLE
+%If(QTXML_AVAILABLE)
+%Import QtXml/QtXmlmod.sip
+%End
%Timeline {
POPPLER_V0_20_0
signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Gregorian chant augmentum with pes
The combination of pes and augmentum doesn't appear to typeset
correctly:
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
\version "2.19.43"
\include "gregorian.ly"
music = {
\[ \augmentum c\pes \augmentum d1 \]
}
\score {
<<
\new VaticanaVoice <<
\clef "vaticana-fa1" \music
>>
>>
}
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
The dots seem to be in the wrong places. Any suggestions?
Richard
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Midi output with highlighted voices
On 2017-01-12 02:58 AM, Jonathan Scholbach wrote:
Dear Ponders,
I have a feature wish, and I hope this is the right channel to utter it:
I typeset choir pieces and in this field it is a big advantage of
LilyPond that producing MIDI files with highlighted voices for each
single voice is possible. Today I do this by defining a new book for
each voice and by "highlighting" the respective voice - by increasing
her volume and assigning her a distinct midiInstrument - see the
attached MWE. The result is good and very usable for choirs to improve
the individual practicing at home.
But the input is ugly. The MWE works with only 2 voices and yet has a
lot of repetitive code. Imagine a piece with 8 voices! The MIDI output
for 8 highlighted voices would need hundreds of highly repetitive lines
of LilyPond code. I wish there was a feature to produce the output with
one line of code in the \midi{}-section of the pdf producing \score.
LilyPond would have to loop over the voices in the score and produce a
book as described in the MWE.
I have tried to understand Scheme multiple times but I didn't make it
yet. That's why I would be thankful if someone could write the Scheme
function to achieve that. I think many typesetters of choir music would
appreciate an easy way to produce the MIDI as described. (Actually,
there are some guys around who do that with some other programmes, see
[1], [2]). I believe most typesetters don't know the way how to do it
with LilyPond today - that's why I think this would be a great benefit
for the community.
Kind regards,
Jonathan
Have you had a look at Frescobaldi? It has a feature in its score wizard
which turns on rehearsal MIDI output. The result is a set of files, one
per voice, with the highlighted voice set to volumes between 0.8 and 1.0
while all other voices are set lower. When coding the voice in a Voice
context, you can assign a midi instrument per voice. I like to modify
the template and set Staff.midiPanPosition to put the solo voice on the
right. Other options are also possible, and relatively easy to use.
Cheers,
Colin
--
Shall I tell you the secret of the true scholar? It is this: Every man I
meet is my master in some point, and in that I learn of him.
- Ralph Waldo Emerson, The Complete Works of Ralph Waldo Emerson,
Volume VIII - Letters and Social Aims (1876)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
How to adjust space between ChordNames and Staff?
Hi all,
The spacing between ChordNames and Staff seems a bit tight by default. I've
been trying to adjust it but I haven't figured out the right magic words
yet. The IR says *) that there should be
nonstaff-nonstaff-spacing.padding and
nonstaff-relatedstaff-spacing.padding
available and I have tried those + some more (see the example below).
However, there's no change in the spacing.
Am I missing something obious?
BR,
Risto
*) http://lilypond.org/doc/v2.19/Documentation/internals/chordnames
---
\version "2.19.49"
chordStuff = \chords { c1 d:m }
melody = \relative c'' { c4 c c c | d d d d }
\score {
<<
\new ChordNames \with {
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding =
#10
\override VerticalAxisGroup.nonstaff-nonstaff-spacing.padding = #10
\override VerticalAxisGroup.staff-staff-spacing.padding = #10
} { \chordStuff }
\new Staff { \melody }
>>
\layout { }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Midi output with highlighted voices
Jonathan:
> I typeset choir pieces and in this field it is a big advantage of
> LilyPond that producing MIDI files with highlighted voices for each
> single voice is possible. Today I do this by defining a new book for
> each voice and by "highlighting" the respective voice - by increasing
> her volume and assigning her a distinct midiInstrument - see the
> attached MWE. The result is good and very usable for choirs to improve
> the individual practicing at home.
>
> But the input is ugly. The MWE works with only 2 voices and yet has a
> lot of repetitive code. Imagine a piece with 8 voices! The MIDI output
> for 8 highlighted voices would need hundreds of highly repetitive lines
> of LilyPond code. I wish there was a feature to produce the output with
> one line of code in the \midi{}-section of the pdf producing \score.
> LilyPond would have to loop over the voices in the score and produce a
> book as described in the MWE.
...
I do it by having a separate program to generate score files with the
music in a separate file, like in:
http://turkos.aspodata.se/git/musik/bin/midiscore_gen.pl
///
You can also point your choists to midiplayers where they can adjust
things themselfs. It looks like the choirist can cange volume,
instrument other things like in
http://www.chrishills.org.uk/midiplay/
http://www.ronimusic.com/swmiplmac.htm.
There is a list of different midi players at:
http://www.learnchoralmusic.co.uk/PlayMidi.html
Regards,
/Karl Hammar
---
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Global vs. local staff size
On 12.01.2017 11:23, Peter Toye wrote: If I use layout-set-staff-size certain chords produce an ugly alignment, whereas a set-global-staff-size doesn't. I don’t know about this particular problem (and can’t look into it right now), but generally it’s known that layout-set-staff-size unfortunately doesn’t work without shortcomings (bugs). Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to adjust space between ChordNames and Staff?
2017-01-12 21:13 GMT+01:00 Risto Vääräniemi :
> Hi all,
>
> The spacing between ChordNames and Staff seems a bit tight by default. I've
> been trying to adjust it but I haven't figured out the right magic words
> yet. The IR says *) that there should be
> nonstaff-nonstaff-spacing.padding and
> nonstaff-relatedstaff-spacing.padding
> available and I have tried those + some more (see the example below).
> However, there's no change in the spacing.
>
> Am I missing something obious?
>
> BR,
> Risto
>
> *) http://lilypond.org/doc/v2.19/Documentation/internals/chordnames
>
> ---
>
> \version "2.19.49"
>
> chordStuff = \chords { c1 d:m }
>
> melody = \relative c'' { c4 c c c | d d d d }
>
> \score {
> <<
> \new ChordNames \with {
> \override VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding =
> #10
> \override VerticalAxisGroup.nonstaff-nonstaff-spacing.padding = #10
> \override VerticalAxisGroup.staff-staff-spacing.padding = #10
> } { \chordStuff }
> \new Staff { \melody }
> >>
> \layout { }
> }
Do it in \layout
chordStuff = \chords { c1 d:m }
melody = \relative c'' { c4 c c c | d d d d }
\score {
<<
\new ChordNames { \chordStuff }
\new Staff { \melody }
>>
\layout {
\context {
\ChordNames
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding = #10
}
}
}
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
How can I get a repeat symbol in the chord names part of lead sheet?
I'm trying to figure out what to use for a chord name to get a "repeat"
(percent) sign over one of the measures. Below is a complete small
example. I want C over the first measure, repeat over the second measure,
and D over the third measure. I'm sure this is trivial - I just can't find
it!
\version "2.18.2"
chordNames = \chordmode {
c1
% What goes here to get the repeat sign above the second measure of the
staff?
d1 % i want the d chord on top of the third measure
}
melody = \relative c'' {
c4 d e f
g a, b c
c d e f
}
\score {
<<
\new ChordNames \chordNames
\new Staff { \melody }
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Which Linux distro for Lilypond
> After a loser look at the sources and the build system I think it's > better (= much easier) to stay with shared libraries. OK, thanks for working on this. However, it would be still valuable to know why module loading fails with a static version of guile. This might be either a bug or missing information in the documentation. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
