Re: Chapter 2.1 Vocal music of LPNR
David, Now I see the point : if the two eighths were more distant, the extender would have to be displayed anyway - and this may depend on what other voices play during the first eighth, such a a large number of shorter notes. JM > Le 29 août 2019 à 18:19, Jacques Menu a écrit : > > Hello folks, > > Thanks to all for your help and comments. > > My use case is that of converting MusicXML to LilyPond, and I’ve learned in > this experience that: > - if the MusicXML data is of good quality, such as exported by GUI > scores editors, alignment of lyrics can be manual as musicxml2ly does; > - otherwise, such as when the data is obtained by scanning, one is much > better off re-creating the lyrics from scratch in automatic mode. > > A nice day! > > JM > >> Le 27 août 2019 à 18:52, David Wright a écrit : >> >> On Mon 26 Aug 2019 at 20:36:53 (+0200), Simon Albrecht wrote: >>> Hi Jacques, >>> >>> this doesn’t exactly answer your question, but I’ve always found that >>> manual alignment of lyrics is a huge pain to get working and thus >>> never use it… >> >> The only piece I've used them in was as an exercise in writing code >> that would generate a correctly notated score containing repeats, but >> would also generate correctly repeating MIDI output from the same code >> merely by adding \unfoldRepeats. I started a thread about the problem: >> https://lists.gnu.org/archive/html/lilypond-user/2015-09/msg00499.html >> but I don't remember how the thread evolved, if at all. >> >> Suffice it to say, I don't make a habit of this, preferring to set the >> score and the MIDI separately. Attached is the code I came up with. >> To compile it properly, you'd need some library files. "Midi-satb.lily" >> is the boilerplate code to produce MIDI "teach tapes" for each part. >> The attached score used the unmangled source, with \unfoldRepeats >> commented out, and the libraries included of course. >> >>> On 26.08.19 17:39, Jacques Menu wrote: Hello folks, The more I read this chapter, and the more I feel it is a kind of imbroglio, mixing automatic and manual alignment of lyrics to the voice. Do you also feel this would merit a rewrite? >> >> (I'd have to read it in its new incarnation.) >> >> Cheers, >> David. >> > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Chord accidental size in substituted fonts
Hello,
I'm writing a big band chart and having difficulty getting the main
chords involving accidentals--B-flat, C-sharp, etc.--to look good with
the lilyjazz font.
MWEs:
%OK size with defaults
\version "2.19.83"
\score {
\new ChordNames {
bes1
}
}
%NOT OK size using lilyjazz
\version "2.19.83"
\paper {
#(define fonts
(set-global-fonts
#:music "lilyjazz"
#:factor (/ staff-height pt 20)
))
}
\score {
\new ChordNames {
bes1
}
}
I can't find an override for the accidental size here after looking for
the last couple of hours. Is there a way to reduce and/or move the flat
in the second example?
Thanks,
James Worlton
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Change position of first bar of melody
Hi Mike,
just for completeness’ sake:
On 28.08.19 23:03, Michael Wagner wrote:
\partial 8 {c8}
there’s no need for these braces (they don’t do any harm either, though…
;-) ). If you’re going to write them, it is good practice to always
enclose them in spaces, even if not technically necessary. It tends to
improve legibility of the code.
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Trouble with Triplets (Corrected)
>>> Ideas on how to fix these issues are greatly appreciated. >> Your pattern does not fit 4 times in a line. That's creating some of >> your problems. To circumvent that you could switch between spacing >> settings inside the notes as in the attached example. > > Thank you very much. Could you please elaborate on why this works? > > In particular, why not fitting 4 times on a line creates some of the > problem? Wouldn't the repeat measures alleviate that spacing > constraint? That was the intent for this example anyway. If I recall correctly you wrote you wanted strict spacing such that equal time uses equal space. That will then apply to repeat bars likewise. My suggested modification waives that requirement for the repeated bars. When you request strict ruler like time to space relationship then how do you expect Lilypond to know when repeated bars are allowed to use less space and when not so unless you explicitly say so? > I understand that the pattern does not fit 4 times on a line. How to > do so is one of my questions. You have looked at my code? Which part don’t you understand? I do waive the requirements for strict time to space relation for the repeated bars. > I feel that it should be possible to scale "something" in lilypond to > do the same thing, but I haven't figured that out yet. magnifyStaff is your friend. Or globally changing the size. There are plenty examples in the documentation. Kind regards, Michael ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Nesting levels in the source code - why do I have to use one level more than I thought?
Hi David, That's a very helpful answer, thanks! It's a bit of syntax I've not really understood, and so end up "coding by coincidence". Chris ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Trouble with Triplets (Corrected)
On 29/08/2019 20:57, Stefano Antonelli wrote:
I understand that the pattern does not fit 4 times on a line. How to
do so is one of my questions. Increasing the length of the line
doesn't appear to have any effect. Though theoretically with a large
enough paper size it should fit. Followed by a "fit to paper size"
when printing to letter size. I intend to explore that option next.
I feel that it should be possible to scale "something" in lilypond to
do the same thing, but I haven't figured that out yet.
Increasing the paper width will achieve what you want, if I understand
your requirement correctly.
\paper {
#(set-paper-size "a3")
indent = 0
left-margin = 5\mm
line-width=#287
ragged-right = ##f
ragged-bottom = ##t
}
Alternatively, reduce the font size
\paper {
#(set-paper-size "a4")
#(layout-set-staff-size 13.0)
indent = 0
left-margin = 5\mm
line-width=#200
ragged-right = ##f
ragged-bottom = ##t
}
--
Timothy Lanfear, Bristol, UK.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: stopStaff - startStaff End-of-System Staves
Thanks, Robin, for your suggestion. I checked for auxiliary voices and found none. After some experimenting, I learned that by including \override Staff.StaffSymbol.line-count = #0 right after \stopStaff properly displays the barlines. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Trouble with Triplets (Corrected)
On Thu, 2019-08-29 at 12:06 +0200, Michael Gerdau wrote: > Hi Stefano, > > > > > Ideas on how to fix these issues are greatly appreciated. > Your pattern does not fit 4 times in a line. That's creating some of > your problems. To circumvent that you could switch between spacing > settings inside the notes as in the attached example. Thank you very much. Could you please elaborate on why this works? In particular, why not fitting 4 times on a line creates some of the problem? Wouldn't the repeat measures alleviate that spacing constraint? That was the intent for this example anyway. I understand that the pattern does not fit 4 times on a line. How to do so is one of my questions. Increasing the length of the line doesn't appear to have any effect. Though theoretically with a large enough paper size it should fit. Followed by a "fit to paper size" when printing to letter size. I intend to explore that option next. I feel that it should be possible to scale "something" in lilypond to do the same thing, but I haven't figured that out yet. Thanks, Stef ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Re: DrumVoice Polyphony and MIDI
On Thu, 2019-08-29 at 09:53 +0200, Mats Bengtsson wrote:
> I can confirm that the problem appears in 2.18.2, but seems to have
> been
> fixed in 2.19, several years ago. As has already been stated many
> times
> on this list, there's no reason whatsoever to avoid the "unstable"
> version 2.19.83. If you really want to keep 2.18.2 for some strange
> reason, just add the following at the top of your file
>
>
> %%% Corrected definitions of the DrumStaff and DrumVoice performers,
> from version 2.19.x:
> \midi{
> \context {
> \Staff
> \name DrumStaff
> \alias Staff
> midiInstrument = #"drums"
> \denies Voice
> \accepts DrumVoice
> \defaultchild DrumVoice
> }
> \context {
> \Voice
> \name DrumVoice
> \alias Voice
> \remove "Note_performer"
> \consists "Drum_note_performer"
> }
> }
Many thanks Mats. This worked great.
I'm not avoiding 2.19.x by the way. This just happens to be the
version available in my repo.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics extend question
Hello David, The other thread was about a score I’m adapting for our oboes band for concerts to come. This lead me to compare how various applications import MusicXML, and I found this difference. And you’re right, my interest is in the algorithms for such import. JM > Le 29 août 2019 à 20:43, David Wright a écrit : > > On Thu 29 Aug 2019 at 19:27:15 (+0200), Jacques Menu wrote: >> Hello folks, >> >> In a MusicXML version of Amazing Grace I have, there is the syllable ‘Was’ >> on a first eighth, and then another eighth without lyrics beamed with the >> first one: >> >> >> >> E >> -1 >> 4 >> >>6 >>1 >>eighth >>up >>begin >> >> single >> Was >> >> >> >> >> >> F >> 4 >> >>6 >>1 >>eighth >>up >>end >> >> >> musicxml2ly and museScore produce an extender such as: >> >> >> >> while Finale and Sibelius don’t: >> >> >> >> Is one way ‘better’ than the other? > > Better in what way, as printed music or as a precise translation of > the XML code? > > Conventionally, and in conventional music, you'd expect an extender > unless the word (Was) covers the notes, when an extender might look > like a period or some stray ink. Some publishers might use a slur, > or a slur where the notes weren't beamed as they are here, but I'd > expect the XML code to describe that. > > I'm not sure I'm seeing everything in the second graphic. Apart from > the red notes, there's something kind of partly underlining the words. > But anyway, this version obviously requires no extender, and I'd > remove any that was there. > > Much depends on the size of the lyrics. Almost all my scores are for > amateur singers rather than library publication, so I make my lyrics > larger than was common in the past, and make other editorial changes. > > I read your use case in the other thread. Are these converted scores > for personal use or are you compiling some sort of publicly > available resource? Or is the conversion program code itself your target? > (Your "deliverable", as they say.) > > Cheers, > David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics extend question
On Thu 29 Aug 2019 at 19:27:15 (+0200), Jacques Menu wrote: > Hello folks, > > In a MusicXML version of Amazing Grace I have, there is the syllable ‘Was’ on > a first eighth, and then another eighth without lyrics beamed with the first > one: > > > > E > -1 > 4 > > 6 > 1 > eighth > up > begin > > single > Was > > > > > > F > 4 > > 6 > 1 > eighth > up > end > > > musicxml2ly and museScore produce an extender such as: > > > > while Finale and Sibelius don’t: > > > > Is one way ‘better’ than the other? Better in what way, as printed music or as a precise translation of the XML code? Conventionally, and in conventional music, you'd expect an extender unless the word (Was) covers the notes, when an extender might look like a period or some stray ink. Some publishers might use a slur, or a slur where the notes weren't beamed as they are here, but I'd expect the XML code to describe that. I'm not sure I'm seeing everything in the second graphic. Apart from the red notes, there's something kind of partly underlining the words. But anyway, this version obviously requires no extender, and I'd remove any that was there. Much depends on the size of the lyrics. Almost all my scores are for amateur singers rather than library publication, so I make my lyrics larger than was common in the past, and make other editorial changes. I read your use case in the other thread. Are these converted scores for personal use or are you compiling some sort of publicly available resource? Or is the conversion program code itself your target? (Your "deliverable", as they say.) Cheers, David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Nesting levels in the source code - why do I have to use one level more than I thought?
On Thu 29 Aug 2019 at 17:09:09 (+0200), Petr Pařízek wrote:
> Hello,
>
> I'm currently learning to use LilyPond. I've finally succeeded in
> writing a short piece of music but there's one thing I don't
> understand. In my source code, there was one line that said "\score
> {". In order it worked at all, I had to keep a single left brace { on
> the immediately following line, which meant that I later had to use a
> single right brace } on two consecutive lines.
>
> To me, this seems like an additional level of nesting which I didn't
> think was necessary. So I wanted to know why it has to be there or why
> the compiling process fails if I don't keep that.
>
> To be more specific, I'll quote a shortened version of my code to give
> you a better idea of what I'm talking about.
>
> -
>
> \version "2.19.83"
>
> \language "deutsch"
>
> \score {
>
> {
>
> \key g \major
>
> \time 4/2
>
> <<
>
> \relative \new Staff {
>
> % The top voice goes here.
>
> }
>
> \relative \new Staff {
>
> % The middle voice goes here.
>
> }
>
> \relative \new Staff {
>
> % The bottom voice goes here.
>
> }
>
> > >
>
> }
>
> \layout { }
>
> \midi { }
>
> }
>
> -
>
> Thank you for your suggestions or comments.
Indented code is easier to understand.
\version "2.19.83"
\language "deutsch"
\score {
{
\key g \major
\time 4/2
<<
\relative \new Staff {
%% The top voice goes here.
}
\relative \new Staff {
%% The middle voice goes here.
}
\relative \new Staff {
%% The bottom voice goes here.
}
>>
}
\layout { }
\midi { }
}
I think your question is "Why do I need the second { and the }
before \layout?" The technical answer is that \score { … } accepts
a *single* musical expression. Because you've started your music with
\key g \major, that's your lot:
\score { \key g \major }
and any more requires to be made part of sequential or simultaneous
music, by enclosing in {} or <<>>. You've chosen the former:
\score {
{ \key g \major \time 4/2 … }
}
More likely what you want is something like:
\score {
\new GrandStaff <<
\new Staff <<
…
>>
\new Staff <<
…
>>
>>
\layout { }
\midi { }
}
and the expression \new GrandStaff << … >> is singular.
Cheers,
David.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Lyrics extend question
Hello folks, In a MusicXML version of Amazing Grace I have, there is the syllable ‘Was’ on a first eighth, and then another eighth without lyrics beamed with the first one: E -1 4 6 1 eighth up begin single Was F 4 6 1 eighth up end musicxml2ly and museScore produce an extender such as: while Finale and Sibelius don’t: Is one way ‘better’ than the other? Thanks for your help! JM ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Chapter 2.1 Vocal music of LPNR
Hello folks, Thanks to all for your help and comments. My use case is that of converting MusicXML to LilyPond, and I’ve learned in this experience that: - if the MusicXML data is of good quality, such as exported by GUI scores editors, alignment of lyrics can be manual as musicxml2ly does; - otherwise, such as when the data is obtained by scanning, one is much better off re-creating the lyrics from scratch in automatic mode. A nice day! JM > Le 27 août 2019 à 18:52, David Wright a écrit : > > On Mon 26 Aug 2019 at 20:36:53 (+0200), Simon Albrecht wrote: >> Hi Jacques, >> >> this doesn’t exactly answer your question, but I’ve always found that >> manual alignment of lyrics is a huge pain to get working and thus >> never use it… > > The only piece I've used them in was as an exercise in writing code > that would generate a correctly notated score containing repeats, but > would also generate correctly repeating MIDI output from the same code > merely by adding \unfoldRepeats. I started a thread about the problem: > https://lists.gnu.org/archive/html/lilypond-user/2015-09/msg00499.html > but I don't remember how the thread evolved, if at all. > > Suffice it to say, I don't make a habit of this, preferring to set the > score and the MIDI separately. Attached is the code I came up with. > To compile it properly, you'd need some library files. "Midi-satb.lily" > is the boilerplate code to produce MIDI "teach tapes" for each part. > The attached score used the unmangled source, with \unfoldRepeats > commented out, and the libraries included of course. > >> On 26.08.19 17:39, Jacques Menu wrote: >>> Hello folks, >>> >>> The more I read this chapter, and the more I feel it is a kind of >>> imbroglio, mixing automatic and manual alignment of lyrics to the voice. >>> >>> Do you also feel this would merit a rewrite? > > (I'd have to read it in its new incarnation.) > > Cheers, > David. > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Nesting levels in the source code - why do I have to use one level more than I thought?
- Original Message -
From: "Petr Pařízek"
To:
Sent: Thursday, August 29, 2019 4:09 PM
Subject: Nesting levels in the source code - why do I have to use one level
more than I thought?
Hello,
I'm currently learning to use LilyPond. I've finally succeeded in writing
a short piece of music but there's one thing I don't understand. In my
source code, there was one line that said "\score {". In order it worked
at all, I had to keep a single left brace { on the immediately following
line, which meant that I later had to use a single right brace } on two
consecutive lines.
I don't see a right brace on two consecutive lines?
To me, this seems like an additional level of nesting which I didn't think
was necessary. So I wanted to know why it has to be there or why the
compiling process fails if I don't keep that.
To be more specific, I'll quote a shortened version of my code to give you
a better idea of what I'm talking about.
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Nesting levels in the source code - why do I have to use one level more than I thought?
Hello,
I'm currently learning to use LilyPond. I've finally succeeded in writing a
short piece of music but there's one thing I don't understand. In my source
code, there was one line that said "\score {". In order it worked at all, I
had to keep a single left brace { on the immediately following line, which
meant that I later had to use a single right brace } on two consecutive
lines.
To me, this seems like an additional level of nesting which I didn't think
was necessary. So I wanted to know why it has to be there or why the
compiling process fails if I don't keep that.
To be more specific, I'll quote a shortened version of my code to give you a
better idea of what I'm talking about.
-
\version "2.19.83"
\language "deutsch"
\score {
{
\key g \major
\time 4/2
<<
\relative \new Staff {
% The top voice goes here.
}
\relative \new Staff {
% The middle voice goes here.
}
\relative \new Staff {
% The bottom voice goes here.
}
}
\layout { }
\midi { }
}
-
Thank you for your suggestions or comments.
Petr
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Easy way for converting .ly to svg document
> On 29 Aug 2019, at 05:09, k.l. wrote: > > > Where to find the SVG file? I only get .pdf and .ps > > The missing part for you can be found in the user manual (http://lilypond.org/doc/v2.19/Documentation/usage/command_002dline-usage#advanced-command-line-options-for-lilypond) but is maybe not clear enough (don't know if you already found it but failed to see how to do it) To get an svg you need to call lilypond with the -dbackend=svg lilypond -dbackend=svg .ly should yield you the SVG kind regards, Hans___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Trouble with Triplets (Corrected)
Hi Stefano,
> Ideas on how to fix these issues are greatly appreciated.
Your pattern does not fit 4 times in a line. That's creating some of
your problems. To circumvent that you could switch between spacing
settings inside the notes as in the attached example.
For simplicity I've merged all files into one file.
Kind regards,
Michael
--
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver
\version "2.18.2"
%% http://lsr.di.unimi.it/LSR/Item?id=838
%LSR completed by P.P.Schneider on Feb. 2014 for v2.18
% These two lines are needed to force LilyPond to break only when
% YOU tell it to, via \break and \page Break. You may not need the page-break one.
%\layout {
% \override Score.NonMusicalPaperColumn.line-break-permission = ##f
% \override Score.NonMusicalPaperColumn.page-break-permission = ##f
%}
#(define ((bars-per-line-engraver bar-list) context)
(let* ((working-copy bar-list)
(total (1+ (car working-copy
`((acknowledgers
(paper-column-interface
. ,(lambda (engraver grob source-engraver)
(let ((internal-bar (ly:context-property context 'internalBarNumber)))
(if (and (pair? working-copy)
(= (remainder internal-bar total) 0)
(eq? #t (ly:grob-property grob 'non-musical)))
(begin
(set! (ly:grob-property grob 'line-break-permission) 'force)
(if (null? (cdr working-copy))
(set! working-copy bar-list)
(begin
(set! working-copy (cdr working-copy
(set! total (+ total (car working-copy
% place inside a layout context like so:
%\score {
% \layout {
%\context {
% \Score
% %use the line below to insist on your layout
% %\override NonMusicalPaperColumn.line-break-permission = ##f
% \consists #(bars-per-line-engraver '(4))
%}
% }
%}
%horizontal-spacing-5.ly
%\include "bars-per-line-engraver.ily"
first = \drummode {
\set Score.proportionalNotationDuration = #(ly:make-moment 1/20)
\override Score.SpacingSpanner.uniform-stretching = ##t
\override Score.SpacingSpanner.strict-note-spacing = ##t
<<
{
\voiceOne
cymr8 cymr8
\tuplet3/2{hh16 hh hh}
hh8
\tuplet3/2{tomh16 tomh tomh}
\tuplet3/2{tomh16 tomh tomh}
\tuplet3/2{tomh16 tomh tomh}
tomh8
}
\\
{ \voiceTwo
\repeat unfold 8 bd8
}
>>
\set Score.proportionalNotationDuration = #(ly:make-moment 1/4)
\override Score.SpacingSpanner.uniform-stretching = ##f
\override Score.SpacingSpanner.strict-note-spacing = ##f
}
second = \drummode {
\set Score.proportionalNotationDuration = #(ly:make-moment 1/20)
\override Score.SpacingSpanner.uniform-stretching = ##t
\override Score.SpacingSpanner.strict-note-spacing = ##t
<<
\voiceOne \repeat unfold 8 tomh8
\\
\voiceTwo \repeat unfold 8 bd8
>>
\set Score.proportionalNotationDuration = #(ly:make-moment 1/4)
\override Score.SpacingSpanner.uniform-stretching = ##f
\override Score.SpacingSpanner.strict-note-spacing = ##f
}
spacing = \drummode {
% \hideNotes
\override TupletBracket.bracket-visibility = ##f
\override TupletNumber.text = #""
\voiceThree
\repeat unfold 8 {
\repeat unfold 8 { \tuplet3/2{ tomh16 tomh tomh } }
}
}
\score {
\new DrumStaff {
<<
\new DrumVoice {
\drummode {
\repeat percent 4 { \first }
\repeat percent 4 { \second }
}
}
% \new DrumVoice { \spacing }
>>
}
\layout {
\context {
\DrumStaff
\remove Time_signature_engraver
}
\context {
\DrumVoice
}
\context {
\Score
\override NonMusicalPaperColumn.line-break-permission = ##f
\consists #(bars-per-line-engraver '(4))
}
}
}
\paper {
indent = 0
left-margin = 5\mm
line-width=#200
ragged-right = ##f
ragged-bottom = ##t
}
horizontal-spacing-5a.pdf
Description: Adobe PDF document
signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Easy way for converting .ly to svg document
That works, thanks a lot. Andrew Bernard wrote > Ah. OK. If you use Frescobaldi (and if you don't, it's highly > recommended) its a preference setting. > > Compiling from the command line, it's an option for the back end. > > e.g.: > > $ lilypond -dbackend=svg -o test svg.ly > > Have a read of the Notation Reference (NR) on command line usage. > > I strongly urge people to use 2.19.83 by the way. > > So, output to SVG is built in to lilypond. The only caveat is that if > you include Postscript paths in your lilypond I don't believe they can > get converted to SVG, so avoid that. > > > Andrew > > > On 29/8/19 1:09 pm, k.l. wrote: >> Where to find the SVG file? I only get .pdf and .ps >> > > ___ > lilypond-user mailing list > lilypond-user@ > https://lists.gnu.org/mailman/listinfo/lilypond-user -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: stopStaff - startStaff End-of-System Staves
nagymusic wrote: I attached a screenshot from the ending of my score in which I used \stopStaff and \startStaff to completely hide staves at the end of the piece for performance purposes. Would anyone be willing to have a look at the attached screenshot and explain why there're small segments of staves visible at the very end of each of the the four systems. Maybe you have an auxiliary voice which is one measure too long. Cheers, Robin ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Re: DrumVoice Polyphony and MIDI
Sorry, I pushed "Send" before finishing. Here comes the correct version
of the email.
On 2019-08-28 13:14, Stefano Antonelli wrote:
On Wed, 2019-08-28 at 09:01 +0200, Federico Bruni wrote:
Il giorno lun 26 ago 2019 alle 20:08, Stefano Antonelli
ha scritto:
That is not always a convenient format for working with drum parts
though. I would like to be able to use a syntax more like the
following:
test = \drummode {
<<
{ \voiceOne cymc4 cymc4 cymc4 cymc4 }
{ \voiceOne s4sn4 s4sn4 }
\\
{ \voiceTwo bd4 s4bd4 s4}
>>
}
\score {
\new DrumStaff {
<<
\set Staff.instrumentName = #"Drums"
\new DrumVoice {
\test
% \morePolyphonicPieces
}
>>
}
\layout { }
\midi {
\tempo 4 = 84
}
}
\version "2.18.2"
The above code generates a score just fine, but the MIDI file is
empty
(aside from a header).
I don't actually know much about MIDI. I'm just using the play
button
in Frescobaldi. It's helpful when transcribing.
The MIDI file is not empty when I compile above snippet.
And I don't see why it should happen to you.
Did you check carefully? Are you working on a saved file or a draft
in
Frescobaldi?
Operating system?
...
OS is Windows 7 on a computer I don't use often. Frescobaldi is
version 3.0.1. Lilypond is 2.18.2.
I also just tried it on my primary linux machine. Similar results.
Bad file is 162 bytes and the good file is 216 bytes. The bad file
doesn't work in audacity, but the good file does. Using lilypond from
the command line. Version is 2.18.2.
Seems to be consistent with this version of lilypond. What version are
you using?
I can confirm that the problem appears in 2.18.2, but seems to have been
fixed in 2.19, several years ago. As has already been stated many times
on this list, there's no reason whatsoever to avoid the "unstable"
version 2.19.83. If you really want to keep 2.18.2 for some strange
reason, just add the following at the top of your file
%%% Corrected definitions of the DrumStaff and DrumVoice performers,
from version 2.19.x:
\midi{
\context {
\Staff
\name DrumStaff
\alias Staff
midiInstrument = #"drums"
\denies Voice
\accepts DrumVoice
\defaultchild DrumVoice
}
\context {
\Voice
\name DrumVoice
\alias Voice
\remove "Note_performer"
\consists "Drum_note_performer"
}
}
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Re: DrumVoice Polyphony and MIDI
On 2019-08-28 13:14, Stefano Antonelli wrote:
On Wed, 2019-08-28 at 09:01 +0200, Federico Bruni wrote:
Il giorno lun 26 ago 2019 alle 20:08, Stefano Antonelli
ha scritto:
That is not always a convenient format for working with drum parts
though. I would like to be able to use a syntax more like the
following:
test = \drummode {
<<
{ \voiceOne cymc4 cymc4 cymc4 cymc4 }
{ \voiceOne s4sn4 s4sn4 }
\\
{ \voiceTwo bd4 s4bd4 s4}
>>
}
\score {
\new DrumStaff {
<<
\set Staff.instrumentName = #"Drums"
\new DrumVoice {
\test
% \morePolyphonicPieces
}
>>
}
\layout { }
\midi {
\tempo 4 = 84
}
}
\version "2.18.2"
The above code generates a score just fine, but the MIDI file is
empty
(aside from a header).
I don't actually know much about MIDI. I'm just using the play
button
in Frescobaldi. It's helpful when transcribing.
The MIDI file is not empty when I compile above snippet.
And I don't see why it should happen to you.
Did you check carefully? Are you working on a saved file or a draft
in
Frescobaldi?
Operating system?
...
OS is Windows 7 on a computer I don't use often. Frescobaldi is
version 3.0.1. Lilypond is 2.18.2.
I also just tried it on my primary linux machine. Similar results.
Bad file is 162 bytes and the good file is 216 bytes. The bad file
doesn't work in audacity, but the good file does. Using lilypond from
the command line. Version is 2.18.2.
Seems to be consistent with this version of lilypond. What version are
you using?
I can confirm that the problem appears in 2.18.2, but seems to have been
fixed in 2.19, several years ago. As has already been stated many times
on this list, there's no reason whatsoever to avoid the "unstable"
version 2.19.83. If you really want to keep 2.18.2 for some strange
reason, just add the following at the top of your file
%%%\midi{
\context {
\Staff
\name DrumStaff
\alias Staff
midiInstrument = #"drums"
\denies Voice
\accepts DrumVoice
\defaultchild DrumVoice
}
\context {
\Voice
\name DrumVoice
\alias Voice
\remove "Note_performer"
\consists "Drum_note_performer"
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Easy way for converting .ly to svg document
Ah. OK. If you use Frescobaldi (and if you don't, it's highly recommended) its a preference setting. Compiling from the command line, it's an option for the back end. e.g.: $ lilypond -dbackend=svg -o test svg.ly Have a read of the Notation Reference (NR) on command line usage. I strongly urge people to use 2.19.83 by the way. So, output to SVG is built in to lilypond. The only caveat is that if you include Postscript paths in your lilypond I don't believe they can get converted to SVG, so avoid that. Andrew On 29/8/19 1:09 pm, k.l. wrote: Where to find the SVG file? I only get .pdf and .ps ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
