Re: barline problem
On 12-Jun-06, at 9:09 PM, Dewdman42 wrote: I am a brand new Lilypond user. I installed Lilypond and ran the test .ly file that is included with the installation. It produced a PDF file. however, I notice that the barlines stick up above and stick down below just a little bit beyond the top and bottom ledger line. Surely this must be a bug or some mistake or something? I tried both the current stable version and the current beta..they both do it. What gives? I'm running on Windows XP. It could be a problem with your PDF viewer. Did the line appear broken if you printed it out, or if you zoomed in? Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
Doubt its a problem with my PDF viewer. I tried the experiment on my laptop too. Same problem. Using Adobe reader 7.0.7. When its zoomed in to 100%, the line is not broken. Zoomed in to 400% the line is still not broken, but at that resolution the ends of the barlines do meet squarely with the top and bottom ledger lines without overlapping...but zoomed in this far...some ledger lines are thicker than others At 800% ledger lines are even, barlines still not broken and they connect squarely to to the ledger lines Also, at 100%, the note stems are inconsistent thickness. Some are ridiculously too thick and some are really thin. -- View this message in context: http://www.nabble.com/barline-problem-t1778120.html#a4841663 Sent from the Gnu - Lilypond - User forum at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
On 12-Jun-06, at 11:34 PM, Dewdman42 wrote: Doubt its a problem with my PDF viewer. I tried the experiment on my laptop too. Same problem. Using Adobe reader 7.0.7. You're probably using the same program on your laptop as well, so it could well be a problem with your PDF viewer. When its zoomed in to 100%, the line is not broken. Zoomed in to 400% the line is still not broken, but at that resolution the ends of the barlines do meet squarely with the top and bottom ledger lines without overlapping...but zoomed in this far...some ledger lines are thicker than others Please try printing a page. This really sounds like a PDF viewer problem. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics problem ... Bug? Feature? ???
On 12-Jun-06, at 6:04 AM, Mats Bengtsson wrote: Anthony Youngman wrote: And I'll download and read the 2.9 docu at some point. Although I get the impression it might not be a good idea to upgrade for a while ... Actually, the manuals for 2.8 and 2.9 are (almost) identical for the moment. At this moment, I would consider the 2.9 docs significantly better than the 2.8 docs. Off the top of my head, I think that I've completely reorganized and added new stuff to scheme, changing defaults, and spacing. Some of the material in chapters 3-5 might be new in the 2.9 docs as well. In addition, there are no 2.9-only features in the 2.9 docs yet. Everything in the 2.9 docs should work in 2.8, and many things are explained much better. New features will probably be added to the documentation soon; I'm not going to bother with the separate chapter idea for the next release Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
Printing looks fine. I tried installing 3 different third party pdf viewers, none of which looked any good at all..they all had drastic line connection and line width issues. Perhaps someone can explain this to me or tall me a pdf viewer that knows how to display properly PDF's which have been rendered by lilypond. I have created many PDF's myself through other programs that looked WYSIWYG perfect. Apparantly lilypond is not that greatest at producing PDF's. The printer output was excellent though. -- View this message in context: http://www.nabble.com/barline-problem-t1778120.html#a4842001 Sent from the Gnu - Lilypond - User forum at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
On 13-Jun-06, at 1:15 AM, Dewdman42 wrote: Printing looks fine. I tried installing 3 different third party pdf viewers, none of which looked any good at all..they all had drastic line connection and line width issues. Perhaps someone can explain this to me or tall me a pdf viewer that knows how to display properly PDF's which have been rendered by lilypond. I have created many PDF's myself through other programs that looked WYSIWYG perfect. Apparantly lilypond is not that greatest at producing PDF's. The printer output was excellent though. I don't know much about PDF rendering, but over the years I've used about half a dozen different programs to display PDFs. They're all fine for displaying text, but when it comes to lines (like staff lines in lilypond) every program displays different things. I don't think it's specifically lilypond's fault, since graphics with lines produced by other programs are also displayed in different ways. The most important thing is the printed output, though, so I've never really looked into this issue. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
If you're using Acrobat viewer, then this is your PDF viewer. Onscreen, it doesn't always display very accurately, possibly something to do with the resolution at which it displays the image. But try printing the document out; everything will look fine. You just have to learn to take Acrobat's display with a small pinch of salt. - Original Message - From: Dewdman42 [EMAIL PROTECTED] To: lilypond-user@gnu.org Sent: Tuesday, June 13, 2006 7:34 AM Subject: Re: barline problem Doubt its a problem with my PDF viewer. I tried the experiment on my laptop too. Same problem. Using Adobe reader 7.0.7. When its zoomed in to 100%, the line is not broken. Zoomed in to 400% the line is still not broken, but at that resolution the ends of the barlines do meet squarely with the top and bottom ledger lines without overlapping...but zoomed in this far...some ledger lines are thicker than others At 800% ledger lines are even, barlines still not broken and they connect squarely to to the ledger lines Also, at 100%, the note stems are inconsistent thickness. Some are ridiculously too thick and some are really thin. -- View this message in context: http://www.nabble.com/barline-problem-t1778120.html#a4841663 Sent from the Gnu - Lilypond - User forum at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
You can also play with the settings in Acrobat. There's usually some settings related to anti-alias or so. /Mats Quoting Stewart Holmes [EMAIL PROTECTED]: If you're using Acrobat viewer, then this is your PDF viewer. Onscreen, it doesn't always display very accurately, possibly something to do with the resolution at which it displays the image. But try printing the document out; everything will look fine. You just have to learn to take Acrobat's display with a small pinch of salt. - Original Message - From: Dewdman42 [EMAIL PROTECTED] To: lilypond-user@gnu.org Sent: Tuesday, June 13, 2006 7:34 AM Subject: Re: barline problem Doubt its a problem with my PDF viewer. I tried the experiment on my laptop too. Same problem. Using Adobe reader 7.0.7. When its zoomed in to 100%, the line is not broken. Zoomed in to 400% the line is still not broken, but at that resolution the ends of the barlines do meet squarely with the top and bottom ledger lines without overlapping...but zoomed in this far...some ledger lines are thicker than others At 800% ledger lines are even, barlines still not broken and they connect squarely to to the ledger lines Also, at 100%, the note stems are inconsistent thickness. Some are ridiculously too thick and some are really thin. -- View this message in context: http://www.nabble.com/barline-problem-t1778120.html#a4841663 Sent from the Gnu - Lilypond - User forum at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
Hello, I've noticed that Adobe Reader 7.0.7 shows head and stem of a quarter note as two separate items - a small notch at the point where the stem is attached to the head. As the notch stays the same size on the screen, even when zooming in to 6400%, I doubt it is really there. I have yet to see it on a printed sheet. Let's just assume that even Adobe's eyes are not perfect ;-). No problems with barlines sticking out, though, not even at the largest magnification. Regards, Matthijs ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
Graham Percival schreef: The most important thing is the printed output, though, so I've never really looked into this issue. there are some PS commands to introduce hinting for line-art, but I've never bothered to investigate if it might help with this. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
old-style pedals working, but brackets not?
Hello, all --
I've got a weird issue (v2.8) that I can't track down -- any hints
would be appreciated.
I've got piano with centred dynamics and pedal, as given by the tip/
example in the docs:
\new PianoStaff = piano
\new Staff = pfUpper
{ \keepWithTag #'score \global \pfNotesUpper }
\new Dynamics = pfDynamics
{ \keepWithTag #'score \pfDynamics }
\new Staff = pfLower
{ \keepWithTag #'score \global \pfNotesLower }
\new Dynamics = pfPedal
{ \keepWithTag #'score \pfPedal }
But odd things are happening -- here's the symptom list.
1. When I leave everything as is, the pedal markings (old style
sheep and star) are correct.
2. When I use
pfPedal =
{
\set pedalSustainStyle = #'bracket
...
}
or any variation I can think of, the pedal markings disappear
completely.
3. When I put the \pfPedal in the pfLower Staff (instead of in its
own Dynamics context), the pedal markings (as brackets) appear
sporadically, corresponding (I think) to the skips in the music of
the \pfNotesLower variable.
Can anyone think of what might be causing such behaviour?
Thanks,
Kieren.
p.s. All the people who have been looking at my scores are amazed by
the quality -- kudos, as always, to the development and support teams!
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: old-style pedals working, but brackets not? [MINIMAL EXAMPLE]
Hi, all --
I was able to reproduce the behaviour I'm seeing in the attached
minimal example -- any help on the solution would be appreciated.
Thanks,
Kieren.
___
%%% CODE SNIPPET BEGINS
\version 2.8.4
\layout
{
\context
{
\name Dynamics
\alias Voice
\type Engraver_group
\consists Output_property_engraver
\consists Piano_pedal_engraver
\consists Script_engraver
\consists Dynamic_engraver
\consists Text_engraver
\consists Skip_event_swallow_translator
\consists Axis_group_engraver
\override VerticalAxisGroup #'minimum-Y-extent = #'(-1 . 1)
\override TextScript #'font-size = #2
\override TextScript #'font-shape = #'italic
\override DynamicText #'extra-offset = #'(0 . 2.5)
\override Hairpin #'extra-offset = #'(0 . 2.5)
pedalSustainStrings = #'(Ped. *Ped. *)
pedalUnaCordaStrings = #'(una corda tre corde)
}
\context
{
\PianoStaff
\accepts Dynamics
\override VerticalAlignment #'forced-distance = #5
}
}
global =
{
\key c \major
\time 4/4 s4*4*3
}
pfNotesUpper = \relative c''
{
\clef treble
c4 c c c c c c c c c c c
c4 c c c c c c c c c c c
}
pfDynamics =
{
}
pfNotesLower = \relative c'
{
\clef bass
c4 c c c c c c c c c c c
c4 c c c c c c c c c c c
}
pfPedal =
{
s4\sustainDown s4\sustainUp\sustainDown s4\sustainUp\sustainDown s4
\sustainUp
s4\sustainDown s4\sustainUp\sustainDown s4\sustainUp\sustainDown s4
\sustainUp
s4\sustainDown s4\sustainUp\sustainDown s4\sustainUp\sustainDown s4
\sustainUp \break
\set pedalSustainStyle = #'bracket
s4\sustainDown s4\sustainUp\sustainDown s4\sustainUp\sustainDown s4
\sustainUp
s4\sustainDown s4\sustainUp\sustainDown s4\sustainUp\sustainDown s4
\sustainUp
s4\sustainDown s4\sustainUp\sustainDown s4\sustainUp\sustainDown s4
\sustainUp \break
}
\score
{
\new PianoStaff = piano
\new Staff = pfUpper \global \pfNotesUpper
\new Dynamics = pfDynamics \pfDynamics
\new Staff = pfLower \global \pfNotesLower
\new Dynamics = pfPedal \pfPedal
}
%%% CODE SNIPPET ENDS
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
chordnames vs lyrics problem
I'm trying to typeset a SATB piece, with chords for pianoThe problem: the sopranos partially have their own lyrics (three verses, so it takes a lot of room) If I put the ChordNames above the lyrics, the placement of the chords looks rather stupid where the sopranos sing the same as the rest, I tried putting the cords under the lyrics and tweak the cordnames up above the lyrics where necessary, but this also moves the lyrics upI tried putting the ChordNames under the lyrics, and moving up, but this was not successful. * I tried doing the moving with \once \override ChordNames.ChordName #'Y-offset = #6and%\once \override ChordNames.ChordName #'Y-offset = #-6respectivelyAttached2, and chords above with tweak, and chords below with tweak What I would like: I want the chordnames under where there are no special soprano lyrics, but over the special soprano lyrics. How can I accomplish such a thing?regards, SimonPS. lily 2.8.4 on winxp lily-moving-down2.png Description: PNG image lily-moving-up2.png Description: PNG image ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
Well ,for whatever its worth... I can produce fine looking PDF's with another program I use for guitar tablature. It produces excellent looking guitar tabs that look as good as anything printed in guitar player magazine..with even lines, thin lines, thick lines, consistent, no funny aliasing in fonts or lines ANYWHERE. They look as good in PDF form as they do printed out.. Well except for the fact that its 72dpi on the screen instead of 300dpi in the printer, so you might see a few more jaggies in the curves, but that is to be expected...and its consistent. I am going to try to produce some PDF's with Finale and Overture to see if they are unable to produce a quality PDF. I can't see any technical limitation of PDF that would prevent lilypond from being able to also produce a quality PDF..unless the truth is that lilypond is producing a higher resolution postscript and then relying on acrobat to try to downsample it to 72 dpi PDF display. That's what it feels like to me..that the issues are all about screen resolution vs print resolution and resulting in mishap. In the end, what does matter most is the printing, but I hope that the developers of lilypond will consider that PDF output is mattering more and more to many of us. I believe its possible for lilypond to produce better output in PDF filesunless there is some setting somewhere that needs to be tweaked for this...I'm inclined to think at this point that lilypond is not appropriate for PDF generation. cheers -- View this message in context: http://www.nabble.com/barline-problem-t1778120.html#a4850585 Sent from the Gnu - Lilypond - User forum at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
ok, ran an experiment. for whatever its worth... Overture produced very clean and decent looking PDF files. No aliasing or weird artifacts. Finale2006 produced crapola...even worse than lilypond. I wonder what the difference is? I'm guessing that somehow the finale PDF and Lilypond PDF are encoded in such a way that you can print those PDF's to a high resolution printer and get excellent results. But somehow their collection of vectors does not display well at lower 72dpi resolution in PDF viewers. For whatever the reason, the pdf produced from Overture looks just fine in PDF viewer, but I doubt its print is as good as Finale or Lilypond. (Shrug)?? However I zoomed the Overture PDF in to 200% and 400% and it still looked great. It looked great and evenly great at all resolutions. By the way, I used pdf995 to produce the PDF's from Finale and Overture (and that other guitar tab program I sometimes use). The point of this post is that it *IS* possible to get better looking music notation in PDF form. The PDF viewer is not neccessarily the limiting factor. My believe is that finale and Lilypond are perhaps leaning too heavily on postscript, and expecting the PDF readers to sort it out at view time..while overture is probably not using poscript directly in the program, but rather relying on the print driver to generate what works best. Same with my guitar tab program. Hence, the pdf995 can produce a quality PDF in both of those two cases, but with Finale and lilypond suffer in this area. Again, maybe there is some setting somewhere, but I think this probably related more to the fact that lilypond is postscript in its core. -- View this message in context: http://www.nabble.com/barline-problem-t1778120.html#a4851070 Sent from the Gnu - Lilypond - User forum at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: old-style pedals working, but brackets not? [MINIMAL EXAMPLE]
On Tuesday 13 June 2006 16:00, Kieren MacMillan wrote: Hi, all -- I was able to reproduce the behaviour I'm seeing in the attached minimal example -- any help on the solution would be appreciated. FYI, this is probably not a minimal example. Usually you can shrink problematic examples down to 5 lines of code; the minimisation process is often useful to understand what's going wrong (e.g.: if you have verified that the Dynamics context in your example has anything to do with the problem, I would remove lines from the context definition, one by one, until there are no lines that are absolutely necessary to reproduce the problem). -- Erik ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: old-style pedals working, but brackets not? [MINIMAL EXAMPLE]
Hi, Erik:
FYI, this is probably not a minimal example.
Usually you can shrink problematic examples down to 5 lines of code
Okay,
\version 2.8.4
\layout {
\context {
\name Dynamics
Now what? ;-)
Seriously... I prefer bug demos which include WORKING examples as
well as BROKEN ones: it makes comparison possible. By way of a
relevant example: in the reduced code below, it is impossible to tell
whether the pedal engraver is working (present) AT ALL, because
there's no working (pre-\set) code. [FWIW, the engraver *is* working...]
I would remove lines from the context definition, one by one, until
there are
no lines that are absolutely necessary to reproduce the problem
What I came up with is attached below -- it still doesn't work as
expected, of course, but I don't think I can remove anything else
without *adding* breakage behaviour! =)
Thanks,
Kieren.
_
%%% CODE SNIPPET BEGINS
\version 2.8.4
\layout {
\context {
\name Dynamics
\type Engraver_group
\consists Piano_pedal_engraver
\consists Skip_event_swallow_translator
\consists Axis_group_engraver
}
\context { \PianoStaff \accepts Dynamics }
}
pfPedal = {
\set pedalSustainStyle = #'bracket s4\sustainDown s4\sustainUp
\sustainDown s4\sustainUp\sustainDown s4\sustainUp
}
\score {
\new PianoStaff = piano
\new Staff = pfUpper \relative c'' { c4 c c c }
\new Staff = pfLower \relative c' { \clef bass c4 s c s }
\new Dynamics = pfPedal \pfPedal
}
%%% CODE SNIPPET ENDS
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: chordnames vs lyrics problem
Problematic! My best proposal is to typeset the ChordNames below the lyrics. When there is lyrics, you move the ChordNames up and the lyrics down (I would have used the extra-offset property, but it seems that you have found another option). /Mats Simon Dahlbacka wrote: I'm trying to typeset a SATB piece, with chords for piano The problem: the sopranos partially have their own lyrics (three verses, so it takes a lot of room) If I put the ChordNames above the lyrics, the placement of the chords looks rather stupid where the sopranos sing the same as the rest, I tried putting the cords under the lyrics and tweak the cordnames up above the lyrics where necessary, but this also moves the lyrics up I tried putting the ChordNames under the lyrics, and moving up, but this was not successful. * I tried doing the moving with \once \override ChordNames.ChordName #'Y-offset = #6 and %\once \override ChordNames.ChordName #'Y-offset = #-6 respectively Attached2, and chords above with tweak, and chords below with tweak What I would like: I want the chordnames under where there are no special soprano lyrics, but over the special soprano lyrics. How can I accomplish such a thing? regards, Simon PS. lily 2.8.4 on winxp ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: chordnames vs lyrics problem
My best proposal is to typeset the ChordNames below thelyrics. When there is lyrics, you move the ChordNames up and the lyrics down (I would have used the extra-offsetproperty, but it seems that you have found another option).I found another option, yes, but it did not work (Y-offset that is)But thanks for steering me in the right direction, it seems changing Y-offset also affects surrounding grobs, while extra-offset just moves the one affected.(Looking again in the reference, the extra-offset seems obvious now: This offset is added just before outputting the symbol, so the typesetting engine is completely oblivious to it. but that Y-offset affects surrounding grobs is not obvious from the reference (for me at least) The vertical amount that this object is moved relative to its Y-parent)I now solved it by typesetting the ChordNames below the lyrics, andtweak the chord with\once \override ChordName #'extra-offset = #'(0 . 10)and tweaking each of the lyric verses with \override LyricText #'extra-offset = #'(0 . -4)and after that I get the output I want (see attachment) I mention this in the event it benefits another user..regards,Simon Simon Dahlbacka wrote: I'm trying to typeset a SATB piece, with chords for piano The problem: the sopranos partially have their own lyrics (three verses, so it takes a lot of room) If I put the ChordNames above the lyrics, the placement of the chords looks rather stupid where the sopranos sing the same as the rest, I tried putting the cords under the lyrics and tweak the cordnames up above the lyrics where necessary, but this also moves the lyrics up I tried putting the ChordNames under the lyrics, and moving up, but this was not successful. * I tried doing the moving with \once \override ChordNames.ChordName #'Y-offset = #6 and %\once \override ChordNames.ChordName #'Y-offset = #-6 respectively Attached2, and chords above with tweak, and chords below with tweak What I would like: I want the chordnamesunder where there are no special soprano lyrics, but over the special soprano lyrics. How can I accomplish such a thing? regards, Simon PS. lily 2.8.4 on winxp ___lilypond-user mailing listlilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user--=Mats BengtssonSignal ProcessingSignals, Sensors and Systems Royal Institute of TechnologySE-100 44STOCKHOLMSwedenPhone: (+46) 8 790 8463Fax: (+46) 8 790 7260Email: [EMAIL PROTECTED]WWW: http://www.s3.kth.se/~mabe= wanted-output.png Description: PNG image ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
On Tue, Jun 13, 2006 at 01:15:35AM -0700, Dewdman42 scripsit: Printing looks fine. I tried installing 3 different third party pdf viewers, none of which looked any good at all..they all had drastic line connection and line width issues. Perhaps someone can explain this to me or tall me a pdf viewer that knows how to display properly PDF's which have been rendered by lilypond. kpdf -- which won't do you any good if you're not running linux -- works fine for the lilypond output I generate. I have created many PDF's myself through other programs that looked WYSIWYG perfect. Apparantly lilypond is not that greatest at producing PDF's. The printer output was excellent though. PDF's display elements are a proper subset of postscript, and you can (wiht the right software) go round-trip from each format through the other one without loss. Many display programs don't handle _all_ the postscript vector constructs; it's the usual tradeoff between fast and complete. Printer drivers, on the other hand, are expected to handle all of it. They're not going to _add_ information that isn't there in the original PDF, after all. -- Graydon ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
Which gets us to the crux of the problem. Finale and lilypond use all of the nuances of postscript that they possibly can..perhaps even using parts of it that the PDF subset does not support very well. For this reason, all the PDF viewers I have tried look like crap. Sad. -- View this message in context: http://www.nabble.com/barline-problem-t1778120.html#a4855143 Sent from the Gnu - Lilypond - User forum at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
First time running, cannot get to work. Request help
I have not yet been able to get LilyPond to work. For even the test
file, I get: parser error. braces don't match. This happens even though
I have directly cut and pasted from .ly files available on your web
site. I have tried numerous ways of adjusting the curly braces, but
still can't get it to work. I have tried other files available from the
website, but yet no success.
Here is the test file I have used:
{ c'4 e' g' }
Here is the response I get from Terminal:
lilypond test.ly
lilypond (GNU LilyPond) 2.2.5
Running lilypond-bin...
Now processing `test.ly'
Parsing...
/Users/michaelm/test.ly:1:1: error: parse error:
{
c'4 e' g' }
/Users/michaelm/test.ly:1:9: warning: Braces don't match:
{ c'4 e'
g' }
Failed files: test.ly
lilypond: error: LilyPond failed on input file test (exit status 1)
lilypond: warning: Running LilyPond failed. Rerun with --verbose for a
trace.
Any ideas what I am doing wrong? Thank you for your help.
Michael
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: First time running, cannot get to work. Request help
On 13-Jun-06, at 3:05 PM, Michael J Millett wrote:
{ c'4 e' g' }
Here is the response I get from Terminal:
lilypond test.ly
lilypond (GNU LilyPond) 2.2.5
Please use LilyPond 2.4 or above -- I highly recommend 2.8. If for
some reason you must use lily 2.2.5, please read the manual for that
version.
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: First time running, cannot get to work. Request help
On Tue, Jun 13, 2006 at 05:05:58PM -0500, Michael J Millett wrote:
Here is the test file I have used:
{ c'4 e' g' }
Here is the response I get from Terminal:
lilypond test.ly
lilypond (GNU LilyPond) 2.2.5
Running lilypond-bin...
Now processing `test.ly'
Parsing...
/Users/michaelm/test.ly:1:1: error: parse error:
{
c'4 e' g' }
/Users/michaelm/test.ly:1:9: warning: Braces don't match:
{ c'4 e'
g' }
Failed files: test.ly
lilypond: error: LilyPond failed on input file test (exit status 1)
lilypond: warning: Running LilyPond failed. Rerun with --verbose for a
trace.
Any ideas what I am doing wrong? Thank you for your help.
Michael
2.2.5 is quite ancient (can you upgrade?) and uses a slightly longer
syntax. Try this:
\notes{
\score{c'4 e' g'}
}
and see how you go!
--
=
Cameron Horsburgh
http://web.netcall.com.au/horsburgh
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
arpeggio curve and generic 1 sided bracket mark
I am currently a new user and I'm typesetting my first work for mutopia. :) This is from Grieg's Wedding-day at Troldhaugen if you're curious.I would like to get symbols like those pictured:
http://www.flickr.com/photos/[EMAIL PROTECTED]/166806703/This is a type of arpeggio made with a curved line between the two lines. A hack could be a sideways slur. I play piano and I've seen this a few times generally when you have a two note chord that is greater than an octive (play the bottom and then the top like an arpeggio). I haven't figured out any way to do this.
http://www.flickr.com/photos/[EMAIL PROTECTED]/166806721/This is just a half bracket. A hack I could think of is using an \arpeggioBracket like the code below. I've tried both
2.8.4 and 2.9.8 on windows and it hasn't come out right. If the arpeggioBracket has some kind of position overrides I might be able to use that but I'm not familiar enough with it to come up with anything.I appreciate for any thoughts on this.
\score { \new PianoStaff %\set PianoStaff.connectArpeggios = ##t \new Staff = upper { \relative c'' { \clef treble{ \arpeggioBracket f2\arpeggio } \\ {
\arpeggioBracket b, d\arpeggio } } } \new Staff = lower { \relative c'' { \clef bass{ \arpeggioBracket b,8\arpeggio
a4\arpeggio g8 } \\ { g, d'2 } } } }\version 2.8.4
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
