Our choir has developed some "in-house" markings which I'm trying to
replicate in LilyPond. One is the use of a double slash to visually
indicate the last section of a piece when the musical pattern changes
for that last part.
I can replicate that by using a markup like the following:
a2^\mar
Notice that in my example I included spacer rests in the tuplet. This allow
room for the bracket.
On Fri, Dec 21, 2018 at 2:47 PM Ld2020 wrote:
> Thank you - this is extremely helpful.
>
> One issue I am still trying to solve: how to get tuplet brackets to
> appear as part of the metronome mark.
SoundsFromSound wrote
> What are your system specs? I can compile the file on my Linux Mint x64
> laptop with 16GB of RAM, rockin' an 8th gen i7 but it took about 10
> minutes almost. That seems very very slow.
>
> Did you experience the same wait times?
Not Harm obviously but here's my data:
On 12/21/2018 7:46 PM, Thomas Morley wrote:
Am Sa., 22. Dez. 2018 um 00:48 Uhr schrieb Reggie :
I am trying to understand theoretically why this is failing. It's only 16
pages. I am a minimalist composer so as a test I tried this extreme
situation. But yet I don't quite agree rather that it's t
On 2018-12-21 4:53 pm, Aaron Hill wrote:
I tried the following approach to break up the piece into three scores:
\score {
{ \time 4/4 \repeat unfold 1000 { c4 d e f } }
}
\score {
{ \set Score.currentBarNumber = #1001 \bar ""
\time 4/4 \repeat unfold 1000 { f1 } }
\layout { indent
-- Forwarded message --
> From: Reggie
> To: lilypond-user@gnu.org
> Cc:
> Bcc:
> Date: Fri, 21 Dec 2018 15:08:32 -0700 (MST)
> Subject: Re: Re:Combine these segments for same score
> Flaming Hakama by Elaine wrote
> > Yes, you can use tags for segmenting large works into smaller c
Am Sa., 22. Dez. 2018 um 00:48 Uhr schrieb Reggie :
>
> I am trying to understand theoretically why this is failing. It's only 16
> pages. I am a minimalist composer so as a test I tried this extreme
> situation. But yet I don't quite agree rather that it's that extreme. It's
> only 16 pages and Li
Hi Reggie,
What OS are you on?
Andrew
On Sat, 22 Dec 2018 at 10:48, Reggie wrote:
> I am trying to understand theoretically why this is failing. It's only 16
> pages. I am a minimalist composer so as a test I tried this extreme
> situation. But yet I don't quite agree rather that it's that ex
On 12/21/2018 5:56 PM, Kieren MacMillan wrote:
It's
only 16 pages and LilyPond crashes.
That looks like a [serious] bug to me. I’ve cc'ed the bug list.
Reproduced crash on LilyPond 2.19.80, Windows 7 Pro 64-bit SP1, Intel
Core i5-3450, 24GB RAM.
At crash, lilypond-windows.exe in Task Manage
Hi Reggie,
> I am trying to understand theoretically why this is failing. It's only 16
> pages. I am a minimalist composer so as a test I tried this extreme
> situation. But yet I don't quite agree rather that it's that extreme. It's
> only 16 pages and LilyPond crashes.
That looks like a [seriou
Am Fr., 21. Dez. 2018 um 23:18 Uhr schrieb Reggie :
>
> Is there a way in LilyPond to simply add a beam line without changing the
> time or anything else behind the elements? I mean, visually say I had a c16
> feather beam measure that had all the math and checks OK. But I wanted 3
> lines for my
I am trying to understand theoretically why this is failing. It's only 16
pages. I am a minimalist composer so as a test I tried this extreme
situation. But yet I don't quite agree rather that it's that extreme. It's
only 16 pages and LilyPond crashes.
\version "2.19.82"
{
\time 4/4
\repeat un
> -- Forwarded message --
From: Reggie
> To: lilypond-user@gnu.org
> Cc:
> Bcc:
> Date: Fri, 21 Dec 2018 12:10:12 -0700 (MST)
> Subject: Re: feathered beam calculations
> Aaron Hill wrote
> > Given the current implementation, it would be necessary to use an
> > approximate rationa
Thank you - this is extremely helpful.
One issue I am still trying to solve: how to get tuplet brackets to
appear as part of the metronome mark.
I.E. triplet eighth = eighth (triplet under the tuplet bracket with the 3.)
Right now I'm doing:
\rhythmMark "" {\tuplet 3/2 {b'8}} {b'8}
I get the tu
Hi Reggie,
> I am intrigued. How does one use the tag system for concatenating sections
> of the same piece for easy working and compiling speed during edit phase?
> Please, can you provide some code showing how to use tags like this I have
> only seen tags used for differences in music of the sco
On 20.12.18 12:21, Lukas-Fabian Moser wrote:
Folks,
this is mostly to give a reference to those who might hit the same problems
that I had:
I decided to switch from my ancient Linux Mint 17.3 to Linux Mint 19.1
yesterday. In order to set up a working build environment, I had to provide a
wor
Thomas Morley-2 wrote
>> Do you think it's even possible to write a function to automatically
>> space
>> according to the feather beam length and duration?
>
> As said, likely it's possible.
> Speaking only for myself, I doubt I've the time to try.
>
> Cheers,
> Harm
>
> _
Flaming Hakama by Elaine wrote
> Yes, you can use tags for segmenting large works into smaller chunks.
>
> And it is possible to use them for other things as well. Besides
> segmenting the work, I use them for MIDI vs PDF, as well as Score vs Parts
> (vs Lead Sheet), and sometimes for instrument-
Trevor Daniels wrote
> "Reggie" <
> reegistoop@
> > wrote 21/12/2018 19:10:12
>>\relative c'
>>{
>> \override Beam.grow-direction = #LEFT
>> \featherDurations #(ly:make-moment 2/1)
>> c32[ d e f g f e f d f g f d e d f] c4~c | c1 |
>>}
>>
>>My CODE has no errors. And yet the 2/1 does NOT sp
Am Fr., 21. Dez. 2018 um 19:26 Uhr schrieb Reggie :
>
> Thomas Morley-2 wrote
> > \featherDurations changes durations, nothing more!! It does not change
> > spacing on it's own.
> > The changed spacing is more a side-effect. Doing note-spacing is a
> > very involved process, durations are only one
Reggie wrote
> Aaron Hill wrote
>> Given the current implementation, it would be necessary to use an
>> approximate rational like 50/63 as the moment in order to get 'f' to be
>> half of 'c'. Why that number? Well, it's a close approximation to the
>> irrational cube root of one half. We dete
On 12/21/18, 12:10 PM, "Reggie" wrote:
\relative c'
{
\override Beam.grow-direction = #LEFT
\featherDurations #(ly:make-moment 2/1)
c32[ d e f g f e f d f g f d e d f] c4~c | c1 |
}
My CODE has no errors. And yet the 2/1 does NOT space out
"Reggie" wrote 21/12/2018 19:10:12
\relative c'
{
\override Beam.grow-direction = #LEFT
\featherDurations #(ly:make-moment 2/1)
c32[ d e f g f e f d f g f d e d f] c4~c | c1 |
}
My CODE has no errors. And yet the 2/1 does NOT space out any notes at ALL
it's just normal beamed notes wit
On 2018-12-21 11:10 am, Reggie wrote:
\relative c'
{
\override Beam.grow-direction = #LEFT
\featherDurations #(ly:make-moment 2/1)
c32[ d e f g f e f d f g f d e d f] c4~c | c1 |
}
My CODE has no errors. And yet the 2/1 does NOT space out any notes at
ALL
it's just normal beamed notes wi
Am Fr., 21. Dez. 2018 um 20:10 Uhr schrieb Reggie :
>
> Aaron Hill wrote
> > Given the current implementation, it would be necessary to use an
> > approximate rational like 50/63 as the moment in order to get 'f' to be
> > half of 'c'. Why that number? Well, it's a close approximation to the
> >
On 12/21/18, 11:25 AM, "Reggie" wrote:
I would hope beg love for someone to write a function that simply put spaced
out notes according to the speed of the feathers. Finale Sibelius do this
for years now. Hack yes but doable every time it works. What's LilyPond work
around
Aaron Hill wrote
> Given the current implementation, it would be necessary to use an
> approximate rational like 50/63 as the moment in order to get 'f' to be
> half of 'c'. Why that number? Well, it's a close approximation to the
> irrational cube root of one half. We determine this exact va
Reggie,
On 12/21/18, 11:30 AM, "Reggie" wrote:
The fractions do NOT always accelerando, while fractions greater than one
generate a
ritardando as intended. That is why I began this mess in the first place :))
Please show us a specific example that does not work the way you wa
On Fri, Dec 21, 2018 at 7:24 PM Urs Liska wrote:
>
> Why do you want this? Is there any specific reason not to use lualatex? I
> know you already run lyluatex in the Kayser project.
>
Well, because in this case it's in a chapter in my dissertation, the whole
of which is in Lyx. I'd rather avoid
On Fri, Dec 21, 2018 at 07:06:43PM +0100, Urs Liska wrote:
>
> Am 21.12.18 um 09:06 schrieb Urs Liska:
> > Hi Lukas,
> >
> > thanks for putting this together. Indeed since installing a distro
> > that doesn't Guile 1.8 anymore I hadn't been able to compile
> > LilyPond anymore. Once I managed to
On 12/21/2018 11:54 AM, Aaron Hill wrote:
On 2018-12-21 5:14 am, Reggie wrote:
Hello. I see what you are saying thank you. I just feel that feather
beaming
is so confusing it all depends on so much, it's not simple like "select
these notes and change beam style to feather left or right". It's f
Aaron Hill wrote
> This means your score really should be bar check clean *before* you ever
> use \featherDurations.
>
> At the end of the day, there is no real need to use any math for the
> \featherDurations moment. Any positive rational less than one will
> produce an accelerando, while fr
Aaron Hill wrote
> At the end of the day, there is no real need to use any math for the
> \featherDurations moment. Any positive rational less than one will
> produce an accelerando, while fractions greater than one generate a
> ritardando. The best thing to do is to listen to the MIDI output
Thomas Morley-2 wrote
> \featherDurations changes durations, nothing more!! It does not change
> spacing on it's own.
> The changed spacing is more a side-effect. Doing note-spacing is a
> very involved process, durations are only one element of the
> calculation.
>
> So I ensure you \featherDuara
Am 21. Dezember 2018 19:19:21 MEZ schrieb "N. Andrew Walsh"
:
>Hi Federico,
>
>according to release notes, Lyx has had support for lilypond-book for
>some
>time now. See here:
>
>https://wiki.lyx.org/LyX/NewInLyX20#lb
>
>That's where it says it requires the "lilypond-book→(pdf)latex"
>package,
>
Hi Federico,
according to release notes, Lyx has had support for lilypond-book for some
time now. See here:
https://wiki.lyx.org/LyX/NewInLyX20#lb
That's where it says it requires the "lilypond-book→(pdf)latex" package,
which my Lyx says it can't find.
Any advice? Are there any Lyx users who go
Il giorno ven 21 dic 2018 alle 11:24, "N. Andrew Walsh"
ha scritto:
Hi List,
dumb question: I'm trying to integrate lilypond into my Lyx document,
and while it has the lilypond-book module, it says it can't find the
"lilypond-book→(pdf)latex" package. Where do I find this package?
I have
Am Fr., 21. Dez. 2018 um 17:51 Uhr schrieb Reggie :
>
> Thomas Morley-2 wrote
> > Meanwhile I think you didn't understand that feathered beams, done with
> > \override Beam.grow-direction = #RIGHT
> > and
> > \featherDurations
> > are _independant_ from each other. See:
> >
> > \version "2.19.82"
>
Am 21.12.18 um 09:06 schrieb Urs Liska:
Hi Lukas,
thanks for putting this together. Indeed since installing a distro
that doesn't Guile 1.8 anymore I hadn't been able to compile LilyPond
anymore. Once I managed to compile Guile 1.8 and do a build but for
some reason I lost this option. I thi
On 2018-12-21 5:14 am, Reggie wrote:
Hello. I see what you are saying thank you. I just feel that feather
beaming
is so confusing it all depends on so much, it's not simple like "select
these notes and change beam style to feather left or right". It's
first,
math. Then, trial error. Then, settl
Hi list,
I use lilypond 2.18 on OpenSuse Tumbleweed (the rolling distro from
Suse). On that combination, displaying chord names in .pdf-form gives
error messages grom ghostscript (gs) in the transition from a .ps-file
to a .pdf-file. When for example the snippet from
http://lilypond.org/doc/v
Thomas Morley-2 wrote
> Meanwhile I think you didn't understand that feathered beams, done with
> \override Beam.grow-direction = #RIGHT
> and
> \featherDurations
> are _independant_ from each other. See:
>
> \version "2.19.82"
>
> {
> r2..
> \featherDurations #(ly:make-moment 1 2)
> { c''3
Hi Reggie,
It's impossible to have feather
beams cross barlines and look correect why is this?
I’m confused… How, exactly, does this not output the kind of thing you want?
%%% SNIPPET BEGINS
\version "2.19.80"
{
r2..
\override Beam.grow-direction = #RIGHT
\featherDurations #(ly:mak
Am Fr., 21. Dez. 2018 um 17:18 Uhr schrieb Reggie :
>
> Thomas Morley-2 wrote
> > Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie <
>
> > reegistoop@
>
> > >:
> >
> >> It's impossible to have feather
> >> beams cross barlines and look correect why is this?
> >
> > ??
> >
> > What's wrong with:
>
Kieren MacMillan wrote
> Hi Reggie,
>
>> the notes are not spaced out according to the feathered tempo. […]
>> They should be spaced out to show slow fast change
>
> Why is that necessary? I mean, you obviously *want* that… but I’m not sure
> they "should" be spaced out like that, necessarily.
>
Kieren MacMillan wrote
> Hi Reggie,
>
>> the notes are not spaced out according to the feathered tempo. […]
>> They should be spaced out to show slow fast change
>
> Why is that necessary? I mean, you obviously *want* that… but I’m not sure
> they "should" be spaced out like that, necessarily.
>
Hi Federico and Lukas,
Am 21.12.18 um 09:59 schrieb Federico Bruni:
Il giorno ven 21 dic 2018 alle 9:06, Urs Liska
ha scritto:
[...]
A warning about missing URW fonts was the only issue I encountered.
make doc took the expected ages but worked without errors too!
So I can confirm that th
Hi Reggie,
> the notes are not spaced out according to the feathered tempo. […]
> They should be spaced out to show slow fast change
Why is that necessary? I mean, you obviously *want* that… but I’m not sure they
"should" be spaced out like that, necessarily.
> How do you do that?
There are do
Hi Reggie,
> Thomas Morley wrote
>> What's wrong with:
> as I earlier mentioned over and over, the bar lines fail.
> Your example does not work unless you ignore bar checks.
Harm’s example works fine for me; no bar line "failure".
What’s the log output when you try it?
Cheers,
Kieren.
_
Thomas Morley-2 wrote
> Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie <
> reegistoop@
> >:
>
>> It's impossible to have feather
>> beams cross barlines and look correect why is this?
>
> ??
>
> What's wrong with:
>
> \version "2.19.82"
>
> {
> r2..
> \override Beam.grow-direction = #
Thomas Morley-2 wrote
> Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie <
> reegistoop@
> >:
>
>> It's impossible to have feather
>> beams cross barlines and look correect why is this?
>
> ??
>
> What's wrong with:
>
> \version "2.19.82"
>
> {
> r2..
> \override Beam.grow-direction = #
Thomas Morley-2 wrote
> Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie <
> reegistoop@
> >:
>
>> It's impossible to have feather
>> beams cross barlines and look correect why is this?
>
> ??
>
> What's wrong with:
>
> \version "2.19.82"
>
> {
> r2..
> \override Beam.grow-direction = #
Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie :
> It's impossible to have feather
> beams cross barlines and look correect why is this?
??
What's wrong with:
\version "2.19.82"
{
r2..
\override Beam.grow-direction = #RIGHT
c'32[ \repeat unfold 6 c'' c'] r2..
}
Cheers,
Harm
__
kontrapunktstefan wrote
> Dear Phil,
> thanks for Your explanations.
> I do have now another problem.
> What can I do, when I want to have feathered beams across barlines, like
> e.g.:
>
> \version "2.12.3"
> upper = {
> \override Beam #'grow-direction = #RIGHT
>
> \featherDurations #(ly:make-m
Michael Gerdau wrote
> First thing you have to answer for yourself is:
> What do I need feathered beams for?
> The answer should be something along the line "to visually notate an
> accellerando or rallentando".
> Assuming that's your answer then you should have a rough idea as to how
> strongly yo
Hi List,
dumb question: I'm trying to integrate lilypond into my Lyx document, and
while it has the lilypond-book module, it says it can't find the
"lilypond-book→(pdf)latex" package. Where do I find this package?
I have lilypond installed in its own subdirectory, as well as my texlive
installati
Gianmaria Lari writes:
> This works perfectly and print ciccio:
>
> \version "2.19.82"
> test = #(define-scheme-function () () #{ \markup "ciccio" #} )
> \test
>
>
> but if i specify two markups instead of one like here
>
> \version "2.19.82"
> test = #(define-scheme-function () () #{ \marku
On Fri, 21 Dec 2018 at 09:51, Gianmaria Lari
wrote:
> This works perfectly and print ciccio:
>
> \version "2.19.82"
> test = #(define-scheme-function () () #{ \markup "ciccio" #} )
> \test
>
>
> but if i specify two markups instead of one like here
>
> \version "2.19.82"
> test = #(define-sc
Il giorno ven 21 dic 2018 alle 9:06, Urs Liska
ha scritto:
[...]
A warning about missing URW fonts was the only issue I encountered.
make doc took the expected ages but worked without errors too!
So I can confirm that the steps work on Linux Mint 19.
Hi Urs
this was discussed before b
Am 21. Dezember 2018 09:37:42 MEZ schrieb Michael Gerdau :
>
>>> I'm on a 64bit Windows 10, the copy commands needs to be:
>>> cp /c/Program\ Files\ \(x86\)/Frescobaldi/...
>>
>> Do you think it would be sufficient to state something like "adjust
>paths to your actual installation"?
>
>Given tha
This works perfectly and print ciccio:
\version "2.19.82"
test = #(define-scheme-function () () #{ \markup "ciccio" #} )
\test
but if i specify two markups instead of one like here
\version "2.19.82"
test = #(define-scheme-function () () #{ \markup "ciccio" \markup "ciccio"
#} )
\test
th
>> I'm on a 64bit Windows 10, the copy commands needs to be:
>> cp /c/Program\ Files\ \(x86\)/Frescobaldi/...
>
> Do you think it would be sufficient to state something like "adjust paths to
> your actual installation"?
Given that 64Bit is likely to be the rule I’d suggest to have that as defau
Hi Lukas,
thanks for putting this together. Indeed since installing a distro that
doesn't Guile 1.8 anymore I hadn't been able to compile LilyPond
anymore. Once I managed to compile Guile 1.8 and do a build but for some
reason I lost this option. I think the point was that after compiling
Gui
63 matches
Mail list logo
