Lilypond output for the web?
Hi. I am working on a system to include braille music code in documents. I started with a preprocessed Markdown approach (see http://bmc.branchable.com/tutorial/) but recently moved to a reStructuredText directive (http://github.com/mlang/bmc/blob/master/python/bmc/rst.py) Obviously, I dont just include the braille music code, I also transcribe it to LilyPond, and make PDF/PNG and audio versions out of it. In both of these I am dealing with size issues. LilyPond typically always generates paper-sized PNGs. I luckily found the trim option to make it as small as possible.. That is very neat for small examples. But I just wondered, what do I do if music is on several pages? True, the user could just download the PDF, and maybe thats really what sighted users prefer. Problem is, I am blind, so I am a bit stuck on this question. Has anyone perhaps worked on some smallish "framework" for displaying LilyPond output on the web, maybe with a way to flip through pages? Alternatively, can I convince LilyPond to print on endless paper such that the user could just scroll the image? Or is that even practical? The whole point of my question is that the paper-size approach of LilyPond is sort of getting in my way, since I am not rendering for print, at least not when generating PNGs. Thanks for your input. -- CYa, ⡍⠁⠗⠊⠕ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond output for the web?
Mario Lang writes: > Alternatively, can I convince LilyPond to print on endless paper such > that the user could just scroll the image? Have you looked at the notation reference? Spacing issues -- Breaks -- One-line page breaking seems like it might be relevant for your use case. The function mentioned there is ly:one-line-breaking and can be found in the index. The URL is http://lilypond.org/doc/v2.18/Documentation/notation/one_002dline-page-breaking>. I don't see much in the form of explanations around it though. There is one regtest at http://lilypond.org/doc/v2.18/input/regression/collated-files.html#one-line-breaking.ly> that might give a bit more of a clue about the usage. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond for blind musicians
"Claudio Garanzini" writes: > Are there any blind musician or composer that’' use lilypond regularly? > Is there a software like Frescobaldi but more accessible using NVDA as my > default screen reader? > I’ve tryed Frescobaldi but simply can’t use it because of it’s complete > inaccessibility, at least for me. I don't use any specific LilyPond editing tool, I think Emacs (or your favourite text editor) suffice for LilyPond. What I do use, is a program to convert braille music code directly to LilyPond, which can save a lot of time, if you are familiar with braille music code. You can find some information about BMC (the braille music compiler) here: https://bmc.branchable.com/ -- CYa, ⡍⠁⠗⠊⠕ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Goldberg Variations for Guitar Ensemble
> Terrific work Steve. I love the idea of dividing it into duos, trios and > quartets. > Can I pass the URL along to others, or is the announcement just meant for > list members? Yes, allocating the appropriate resources to each variation is, I believe, the best way to preserve the structure(s) of the work. I have this posted on imslp.org and intend for it to be distributed as widely as possible under Creative Commons by-sa 3.0 Feel free to pass the URL to others. I think the notes and other fundamentals are in good shape, and working to make the engraving as good as possible. Of course, I encourage you and others to perform the work ;-). The LilyPond engraving is a beautiful work of art in its own right, but the greatest art is the music itself. We will be performing at least 7 or 8 variations at our annual guitar weekend on April 12. Ultimately I, would like to see all of the variations recorded, along with the individual parts for study and practice.. -steve > > > On Fri, Feb 14, 2014 at 2:52 PM, wrote: > >> Howdy! >> >> As per Janek's suggestion, I would like to announce my LilyPond >> project, the transcription and engraving of J. S. Bach's "Goldberg >> Variations" BWV 988 for >> Guitar Ensemble. >> >> http://www.gooeytar.com/projects/BWV-988/ >> >>The basics are mostly finished, and what remains is the fixing up >> of a few "lilypond" issues, >> fixing ties etc or whatever suggestions for improvement this forum >> and >> its experience can provide. >> >> I have an idea of how to approach the issue of ties and will >> elaborate in >> another post. >> >> -steve >> >> >> >> >> >> >> >> ___ >> 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
non italics in dynamic context
Is there a way to override the italicness of a dynamics context? I
have a huge file where I put all the indications in a separate
dynamics {} and converted it from lilypond 2.10 to 2.18 and I do not
wish to move the tempo markings If it is not necessary.
Shane
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: non italics in dynamic context
On Mon, Feb 17, 2014 at 2:32 PM, Shane Brandes wrote:
> Is there a way to override the italicness of a dynamics context? I
> have a huge file where I put all the indications in a separate
> dynamics {} and converted it from lilypond 2.10 to 2.18 and I do not
> wish to move the tempo markings If it is not necessary.
>
> Shane
>
I take care of this in the \score block by overriding the font-shape in the
layout block & dynamics context:
\score {
%% Music goes here
\layout {
\context {
\Dynamics
\override TextScrip.font-shape = #'upright
}
}
}
James Worlton
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: non italics in dynamic context
Sorry, copy/paste/edit error: that should be:
\override TextScript.font-shape ...
James W.
On Mon, Feb 17, 2014 at 2:42 PM, James Worlton wrote:
> On Mon, Feb 17, 2014 at 2:32 PM, Shane Brandes wrote:
>
>> Is there a way to override the italicness of a dynamics context? I
>> have a huge file where I put all the indications in a separate
>> dynamics {} and converted it from lilypond 2.10 to 2.18 and I do not
>> wish to move the tempo markings If it is not necessary.
>>
>> Shane
>>
>
> I take care of this in the \score block by overriding the font-shape in
> the layout block & dynamics context:
>
> \score {
> %% Music goes here
> \layout {
> \context {
>
> \Dynamics
>
> \override TextScrip.font-shape = #'upright
>
> }
>
> }
>
> }
>
>
> James Worlton
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Horizontalized scores
>> Chris Crossen: > > When I use GIMP to convert a pdf produced with Lilypond to a .png, I > > get nice crisp verticals and horizontals, no anti-aliasing. And, the > > note heads and other rounded parts are beautifully anti-aliased. > David Kastrup: > I don't think that GIMP does anything but call Ghostscript for the rendering > (though I might not me up-to-date with my knowledge). So this would boil > down to figuring out the options it uses. > Thank you, David, for pointing me in the right direction. And thanks to everyone who contributed to this thread for getting me this far along. The trick to getting the crisp horizontal and vertical lines while still getting anti-aliased curves is the ghostscript option -dGraphicsAlphaBits. When Lilypond produces a .png file it set this to 4. If you set it to 1 instead, you get horizontal and vertical lines that aren't anti-aliased. I have attached two images showing the difference. crisp.png was produced with -dGraphicsAlphaBits=1 and blurry.png was produced with -dGraphicsAlphaBits=4. My current workflow uses Lilypond to produce a .pdf. Then I convert the .pdf to .png with GIMP. I'm going to change this so that Lilypond produces a .ps file that I convert to .png with ghostscript. I won't save any steps, but I believe it will be faster and less error-prone. Chris Crossen <><>___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Horizontalized scores
"Chris Crossen" writes:
>>> Chris Crossen:
>> > When I use GIMP to convert a pdf produced with Lilypond to a .png, I
>> > get nice crisp verticals and horizontals, no anti-aliasing. And, the
>> > note heads and other rounded parts are beautifully anti-aliased.
>
>> David Kastrup:
>> I don't think that GIMP does anything but call Ghostscript for the
> rendering
>> (though I might not me up-to-date with my knowledge). So this would boil
>> down to figuring out the options it uses.
>>
>
> Thank you, David, for pointing me in the right direction. And thanks to
> everyone who contributed to this thread for getting me this far along.
>
> The trick to getting the crisp horizontal and vertical lines while still
> getting anti-aliased curves is the ghostscript option -dGraphicsAlphaBits.
> When Lilypond produces a .png file it set this to 4. If you set it to 1
> instead, you get horizontal and vertical lines that aren't anti-aliased.
Not just horizontal and vertical lines. Also things like circles. The
appearance of, say, { b\1 b\2 b\3 b\4 } is a downside to this approach.
I just remembered another option:
Convert to PDF with -dstrokeadjust and then convert PDF to PNG with
pdftocairo. This approach is likely one of the slowest, but it's
basically what I used to batch-test what PDF previewers like Evince
would be likely to deliver.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Printing Copyright on title page
Hello List,
I'm having trouble getting the copyright notice to show up on the first
page when I'm using the following (in the \paper block):
oddFooterMarkup = \markup \fill-line { \fontsize #2 \on-the-fly
#not-first-page \fromproperty #'page:page-number-string }
evenFooterMarkup = \markup \fill-line { \fontsize #2 \on-the-fly
#not-first-page \fromproperty #'page:page-number-string }
anybody have ideas? Thanks!
Sincerely,
Josh
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Horizontalized scores
> >Chris Crossen:
> > The trick to getting the crisp horizontal and vertical lines while
> > still getting anti-aliased curves is the ghostscript option ->
dGraphicsAlphaBits.
> > When Lilypond produces a .png file it set this to 4. If you set it to
> > 1 instead, you get horizontal and vertical lines that aren't
anti-aliased.
> David Kastrup:
> Not just horizontal and vertical lines. Also things like circles. The
appearance
> of, say, { b\1 b\2 b\3 b\4 } is a downside to this approach.
>
> I just remembered another option:
>
> Convert to PDF with -dstrokeadjust and then convert PDF to PNG with
> pdftocairo. This approach is likely one of the slowest, but it's
basically what I
> used to batch-test what PDF previewers like Evince would be likely to
deliver.
>
You're right. I tried your sample with my approach and see the problem.
Do you have any suggestions for options to use with pdftocairo?
I tried pdf2cairo -png input.pdf output.png
and the output wasn't anywhere near as good as what I see if I look at the
pdf with preview on my Mac.
It's frustrating that a PDF viewer does such a great job of rasterizing the
image and the only way I can get an equivalent .png is to take a screen shot
of it.
Chris Crossen
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Printing Copyright on title page
Joshua Nichols wrote
> Hello List,
>
> I'm having trouble getting the copyright notice to show up on the first
> page when I'm using the following (in the \paper block):
>
> oddFooterMarkup = \markup \fill-line { \fontsize #2 \on-the-fly
>
> #not-first-page \fromproperty #'page:page-number-string }
you only define what happens when /#not-first-page/ is true
you should also define what shall be inserted when it *is* the first page -
eg. (not tested exactly):
oddFooterMarkup = \markup \fill-line {
\fontsize #2
\on-the-fly #not-first-page \fromproperty #'page:page-number-string
\on-the-fly #first-page \fromproperty #'header ...
}
hth
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Printing-Copyright-on-title-page-tp159474p159477.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
