>> Or am I still missing the one place where that explanation is
>> provided?
>
> It's here:
>
> https://lilypond.org/doc/v2.24/Documentation/usage/other-programs
I've added links.
https://gitlab.com/lilypond/lilypond/-/merge_requests/1901
Werner
Le jeudi 30 mars 2023 à 23:09 -0600, Jeff Olson a écrit :
> Both are properly cropped, as opposed to whole (tall?) pages.
The name "-dtall-page" could perhaps be clearer. It means that all
normal pages are taken and squashed together vertically.
If you also specify -dno-use-paper-size-for-page,
> Going back to the manuals didn't help explain tall-page-formats:
> [...]
>
> Maybe the documentation of separate- and tall-page-formats
> should elaborate more.
This is very likely. May I invite you to provide improvements to the
text? You have first-hand experience :-)
Werner
tputName "Abc"
\score { { a' } \layout { } \midi { } }
}
\book {
\bookOutputName "Bar"
\score { { b' } \layout { } \midi { } }
}
Each book has a layout and a midi, with the layout rendered both
as png and svg, properly cropped and with no -1 suffix in any file names:
-rwx
On 3/30/2023 10:11 AM, David Wright wrote:
32 -rwxrwxrwx+ 1 J None 32199 Mar 29 22:25 Foo-1.svg*
32 -rwxrwxrwx+ 1 J None 32190 Mar 29 22:25 Abc-1.svg*
32 -rwxrwxrwx+ 1 J None 32231 Mar 29 22:25 Bar-1.svg*
That looks like a linux platform.
But it's Windows 10 running the cyg
Le jeudi 30 mars 2023 à 18:31 -0600, Jeff Olson a écrit :
> Understood, but, like midi, the first file could (should) still have
> been un-suffixed.
> And the current mismatch between layout files and midi files is a
> good reason for the opposite:
> Consider this MWE named MidiMismatch.ly that ge
On 3/29/2023 11:57 PM, Jean Abou Samra wrote:
These "-1" suffices are messing with my URLs for the SVG files,
so I'd appreciate any ideas on how to get rid of them. Thx.
They are there for good reason. If any of your |\book|s got output on
multiple pages, there would indeed be multiple files
On Thu 30 Mar 2023 at 07:57:23 (+0200), Jean Abou Samra wrote:
> Le mercredi 29 mars 2023 à 22:56 -0600, Jeff Olson a écrit :
> > I've got to generate a thousand+ cropped SVG files with specified file
> > names
> > from one lilypond compilation, so I'm wrap
Le mercredi 29 mars 2023 à 22:56 -0600, Jeff Olson a écrit :
> I've got to generate a thousand+ cropped SVG files with specified file names
> from one lilypond compilation, so I'm wrapping each score in a \book with
> its own \bookOutputName as in this MWE:
>
> \vers
I've got to generate a thousand+ cropped SVG files with specified file names
from one lilypond compilation, so I'm wrapping each score in a \book with
its own \bookOutputName as in this MWE:
\version "2.24.1"
#(ly:set-option 'backend 'cairo)
#(ly:set-option 's
Is there a file like makam.ly for the standard accidentals? If so what is
its name?
What is the name of the file that translate text to Unicode?
Thank you,
ƒg
Op vrijdag 30 oktober 2009 schreef Ian:
> I've noticed that LilypondTool and Frescobaldi can get fooled using
> their internal pdf viewers about where the successfully compiled output is.
>
> I wonder if you editor guys can take an enhancement to make your PDF
> viewers sensitive to the code wr
This is a heads up for those like Bert and Wilbert who write editing
support environments for Lilypond.
I currently have a patch in for review which will allow Lily to redirect
the backend output to another file for particular \book blocks.
Currently you do this by setting environment variable
Is it possible to specify the name of the midi file being created? (I
remember some talk about this in the past but I couldn't find the
result of the conversation.) For example let's say I have a book with
a bunch of short scores (i.e. an etude book)
example.ly:
===
\book
{
\score
{
lilypond the.bottom.bracket.ly
produces a midi file named:
the.bottom.midi
It chops off the third part of the name. Any way round this ?
Not using dots in the name?
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailma
Please,
lilypond 2.6.3:
lilypond the.bottom.bracket.ly
produces a midi file named:
the.bottom.midi
It chops off the third part of the name. Any way round this ?
Joe
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman
Sorry for no follow up.
For some reason there were no apparent parse errors. Just couldn't find
dvi etc.
I assumed that the files were ok, but when I lifted the notation and
dumped it into a template I knew parsed, voila the errors appeared.
So for now I retract my question. If this becomes a prob
On Thu, 04 Dec 2003 18:13:37 +0200
Aaron <[EMAIL PROTECTED]> wrote:
> The problem lilypond won't parse them.
> Now is the problem the length or the use of periods??
What operating system are you using?
- Graham
___
Lilypond-user mailing list
[EMAIL PR
Aaron <[EMAIL PROTECTED]> writes:
> Now is the problem the length or the use of periods??
> example:
> b16b8.b4bb16b8.a4ga4.g8aba2e4.ly won't parse but renamed to test.ly it
> does parse.
It works for me.
What is the parse error that you get?
What version of lilypond do you use?
Jan.
--
Jan N
> The problem lilypond won't parse them.
> Now is the problem the length or the use of periods??
> example:
> b16b8.b4bb16b8.a4ga4.g8aba2e4.ly won't parse but renamed to test.ly it
> does parse.
>
And so does b16b8b4bb16b8a4ga4g8aba2e4.ly
so is there a way to use periods in a name??
Thanks
Aaro
Hi all,
I have a large amount of notation in lilypond format.
Many of the songs have no name and no text. I also have audio examples
and written introductions to each song.
I thought that giving each song the first few measures of ly text would
be a great way of absolutly tagging each song and th
21 matches
Mail list logo
