On 2018-12-18 10:51 pm, Urs Liska wrote:
This UI is populated by running LilyPond with the
-dshow-available-fonts option, so it actually displays what LilyPond
can really use.
Ah, that greatly reduces confusion.
However, my point still stands that one needs to be aware that the fonts
Am 19.12.18 um 07:49 schrieb Aaron Hill:
On 2018-12-18 10:39 pm, Urs Liska wrote:
I have no idea about the WSL, but in general I can't imagine there
should be any source of confusion here. Frescobaldi wouldn't need to
access anything font-like when it comes to LilyPond…
But doesn't
On 2018-12-18 10:39 pm, Urs Liska wrote:
I have no idea about the WSL, but in general I can't imagine there
should be any source of confusion here. Frescobaldi wouldn't need to
access anything font-like when it comes to LilyPond…
But doesn't Frescobaldi have a UI for enumerating/previewing
Am 19.12.18 um 07:17 schrieb Aaron Hill:
2) Is it possible to run Lilypond under WSL from Frescobaldi?
Possibly; however I do not use Frescobaldi, so I cannot speak from
experience. Theoretically, you should only need to configure
Frescobaldi to launch LilyPond as "wsl /path/to/lilypond"
On 2018-12-18 9:26 pm, Saul Tobin wrote:
1) Is there a technical obstacle or other reason preventing a Windows
64-bit build?
I would presume that GUB can target 64-bit MinGW, but I gather that this
has not been a priority to deliver. Perhaps one of the developers could
speak to this more
Thanks so much for the confirmation. A couple questions:
1) Is there a technical obstacle or other reason preventing a Windows
64-bit build?
2) Is it possible to run Lilypond under WSL from Frescobaldi?
On Tue, Dec 18, 2018 at 8:36 PM Aaron Hill wrote:
> On 2018-12-18 7:24 pm, Saul Tobin
On 2018-12-18 7:24 pm, Saul Tobin wrote:
It looks like the Fatal realloc error happens after the score finishes
compiling while it's being written to a temporary file. At that point,
the
Lilypond process is using ~1.8 G of RAM. Is it possible I'm running
into a
32 bit size limitation in Guile
It looks like the Fatal realloc error happens after the score finishes
compiling while it's being written to a temporary file. At that point, the
Lilypond process is using ~1.8 G of RAM. Is it possible I'm running into a
32 bit size limitation in Guile or something like that?
On Sun, Dec 16, 2018
On 2018-12-18 2:22 PM, Kieren MacMillan wrote:
scoreTitleMarkup = ##f
That did it. Thanks.
--
✝✝
Br. Samuel, OSB
(R. Padraic Springuel)
St. Anselm’s Abbey
4501 South Dakota Ave, NE
Washington, DC, 20017
202-269-2300
(c) 202-853-7036
PAX ☧ ΧΡΙΣΤΟΣ
Hi there,
> What is the best way to suppress the default scoreTitleMarkup?
I believe
scoreTitleMarkup = ##f
will do what you want.
Hope that helps!
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
What is the best way to suppress the default scoreTitleMarkup? I've
been using `scoreTitleMarkup = \markup \null` but this is creating an
extra space above the score (which, with lilypond-book-preamble.ly,
comes out as an empty "system"). I'm defining a custom titling format
in which I want
On Mon, Dec 17, 2018 at 7:45 PM Brent Annable
wrote:
> Is the Merge_rests_engraver broken? I just copied and pasted the example
> from the Lilypond manual into Frescobaldi (Lilypond version 2.19.65), and
> the rests did not merge like they do on the relevant page of the manual
>
Michael Gerdau wrote
>> I understand your math now but I do not understand how you began to know
>> how
>> to use math from the beginning. How did you determine which note NEEDED
>> the
>> math to it? Is there a sort of study sheet where we can look to find out
>> which notes need math for each
> I understand your math now but I do not understand how you began to know how
> to use math from the beginning. How did you determine which note NEEDED the
> math to it? Is there a sort of study sheet where we can look to find out
> which notes need math for each time we use?
I'm not sure what
Gianmaria Lari writes:
> Ok, tried to substitute "add-score" with "print-book-with-defaults" but I
> didn't see any midi file in the default folder. But
> print-book-with-defaults works for midi output?
> This is the code I tried:
>
> \version "2.19.82"
> test = #(define-void-function (music
On Tue, 18 Dec 2018 at 16:23, David Kastrup wrote:
> Gianmaria Lari writes:
>
> > This is just an example.
> > I would like that my scheme function "test " generates a midi file with
> the
> > name I passed to it.
> > This is what I have been able to do. It compiles but it does not work:
> >
>
Gianmaria Lari writes:
> This is just an example.
> I would like that my scheme function "test " generates a midi file with the
> name I passed to it.
> This is what I have been able to do. It compiles but it does not work:
>
> \version "2.19.82"
> test = #(define-void-function (music filename)
Thomas Morley-2 wrote
> {
> \time 1/4
> b16*4 | % i.e. 1/16 lasts 1/4
> b16*4/3 b b | % b16*4 is 1/4, so b16*4/3 is a third of 1/4
> %% similar for 1/32,
> b32*2 %{is 1/16%} *4 |
> b32*2*4/3 b b |
> %% etc
> }
>
> HTH,
> Harm
>
> ___
>
This is just an example.
I would like that my scheme function "test " generates a midi file with the
name I passed to it.
This is what I have been able to do. It compiles but it does not work:
\version "2.19.82"
test = #(define-void-function (music filename) (ly:music? string?)
#(add-score
19 matches
Mail list logo
