Re: Arpeggio under a note
A final question related to tuplets:I am using the following code snippet to produce a triplet: arpFix = \once \override Arpeggio #'extra-offset = #'(1.6 . -2) << { \times 2/3 { e8 e e }
} \\ { \hideNotes \arpeggioUp \arpFix \times 2/3 { 8\arpeggio \arpeggioDown 8\arpeggio \arpeggioUp 8\arpeggio} } >>But as can be seen from the pic, I get a 3 above & below that is the lower 3 is not hidden.
Also, the arpeggios are not under the notes.How can this be fixed?On 8/18/06, Kieren MacMillan <
[EMAIL PROTECTED]> wrote:Hi, Kamal:> I'm having trouble drawing chords with eighth notes as in the
> attached pic.Don't know why you're having trouble -- it's almost identical code...!Best regards,Kieren.%%% CODE BEGINS\version "2.9.14"\paper{ragged-right = ##t
}arpFix = \once \override Arpeggio #'extra-offset = #'(1.6 . -2)stuff = \relative{\clef treble<< { 8[ f'] } \\ { s8 \hideNotes \arpeggioDown \arpFix f'>\arpeggio } >>}\score{\stuff}%%% CODE ENDS
triplet.png
Description: PNG image
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Arpeggio under a note
Hi Kamal,
use this to suppress the tuplet number:
...
\hideNotes \arpeggioUp \arpFix
\once \override TupletNumber #'transparent = ##t % This is NEW
\times 2/3 { 8\arpeggio \arpeggioDown ...
Cheers,
Markus
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
ossia trick solved
Hi list !
I've been working hard ;o) on my ossia trick, and I've found how to reproduce a
french cantata
excerpt.
Using lily 2.8.3 on XP.
What I have to engrave :
The piece of music is a french recitative, introduced buy the viol on a single
line (10 measures).
Then, we have the recitative itself (viol + voice)
Then the viol alone again
Then the voice and the viol.
The last 9 measures are played only buy the viol.
I have a viol, a voice, and lyrics.
When the viol plays alone, the voice line on the fac simile disappear.
How i managed this :
I have used the 8.3.2 hiding staves trick, which is described for instruments
without lyrics.
Here's the structure of my ly file :
\version "2.8.3"
\layout {
indent = 0.0\cm -> let me explain this below...
\context { \RemoveEmptyStaffContext }
}
<<
\new Staff = soprano {
\override Score.VerticalAxisGroup #'remove-first = ##t
\clef G
\time 2/2
\relative c'' {
R4---> R and not r !!!
R1*10 ---> doesn't appear on the final score
(that's what i want !)
r2 r4 g
c c8 d e4 e8 c (...)
}}
\addlyrics { (...)}
\\new Staff = bass {
\time 2/2
\clef alto
\relative c' {
\partial 4*1 g4
c c8 d e4 c (...)
}}
>>
<<
the same thing for the second part
>>
Some comments :
- I'd like to have the whole score between << >> but I had to split the score
into two parts to get
it work. That's why I have put indent = 0.0\cm (otherwise, I had an ident for
the second part)
Is there a way to do so ?
- the order of the staves is important to get the lyrics below the soprano and
not below the bass
(THIS is the main point I've working on !)
I hope this will help somebody !
Best regards
Jmarc
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Accidentals tied over a line break
Hello, Currently, if a note with an accidental is tied over a line break, the accidental is repeated on the new line. Is there any way to turn off this behavior? I looked in the manual; "9.1.1 Automatic accidentals" would seem to be the relevant section, but it doesn't say anything about tied accidentals. There's a regression test called accidental-tie.ly, but it merely explains that "an accidental is present if the line is broken at the tie, which happens for the G sharp", without mentioning any way of turning off this behavior. It took me a while to find an instance of a note with accidental tied over a line break in the Henle edition of the Bach Well-Tempered Clavier, but when I eventually found one, the accidental was not repeated after the line break. (Book I, Fugue in B minor, measures 56-57. It happens to be a G-sharp.) So if my own desire to not repeat the accidental isn't enough, there's an example from G. Henle Verlag.* Thanks, Marcus (In fairness, the second instance I found did repeat the accidental: Book I, Fugue in C-sharp minor, measures 40-41, an A-sharp. Anyway, I think the user should be able to choose whether or not accidentals are displayed in these situations. And if they are repeated, the ties should not collide, as the currently do. The aforementioned A-sharp provides a good example of how a tie can avoid an accidental in such a case.) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: key change with repeat bar
Kieren MacMillan wrote:
Hi, Nigel:
I had forgotten to say that there was also a piano part in the full
score;
but adding the same command to the relevant place (before the key
change)
in the left and right hand parts dealt with that too.
Just a suggestion... If you keep all key changes, time changes, etc.,
in an identifier (variable), then you can insert such fixes only once
-- e.g.,
global =
{
\time blah
\commandToFixSpacing \key blah
\bar "|."
}
singerStuff =
{
suchandsuch
}
pianoRH = { soandso }
pianoLH = { xyzpdq }
\score
{
\new GrandStaff
<<
\new Staff << \global \singerStuff >>
\new PianoStaff
<<
\new Staff << \global \pianoRH >>
\new Staff << \global \pianoLH >>
>>
>>
}
Best regards,
Kieren.
Thank you for the suggestion. I'll try experimenting with this for
future use.
Many thanks,
Nigel Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Midi lyrics
Hi, is it possible to create CR and LF events and spaces in the midi lyrics output of lilypond? At the moment the created lyric events don't contain any spaces or CR and LF events which is problematic with many appications which display the lyrics. For the recommended format of the lyrics events: http://www.midi.org/about-midi/smf/rp017.shtml Alexander Feigl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals tied over a line break
Hi Marcus,
see this:
%%% Begin ly snippet
\version "2.9.15"
noAcc = \once \override Staff.Accidental #'transparent = ##t
\score { {
cis''1 ~ \noAcc \break
cis''1
cis''1 ~ \break
cis''1
}
\layout {
ragged-right = ##t }
}
%%% End ly snippet
This involves a certain amount of typing, though. I wasn't able to cook up a
function for after-line-breaking or before-line-breaking to do this
automatically, nor modifying
tildeSymbol = { #(make-music 'TieEvent) \noAcc }
Maybe someone can give a hint?
Cheers,
Markus
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals tied over a line break
Hi, Markus (and Marcus): Maybe someone can give a hint? Is the example in "Section 9.3.7: Difficult Tweaks" of any help? Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
On Tue, Aug 22, 2006 at 10:55:05AM +0200, Han-Wen Nienhuys wrote: >>it's easiest to add a property so you can do >> >>cost: 65 EUR. Werner LEMBERG then asked: >Just wondering what the much simpler syntax > >costs... Han-Wen Nienhuys responded: > I can put it in for 35 eur extra, I hope. > (the tie engraver is quite tricky, and handling offers more > potential for bugs) After thinking about it for awhile, I agree with Werner and like his idea better also, if it can be done. Aside from being clear and simple (to the end user), it can save a lot of typing, especially because when lots of partially-tied chords appear in a piece of music as the result of a rhythmic or other motive. SO-- would mean that only the c and b-flat would be tied ~ would mean that the whole chord would be tied ~ would mean--well, LilyPond would issue an error message? The whole-chord tie would take precedence? ;-) Werner, would you be willing to split the sponsorship of this feature with me 50%/50%? I'll commit to its sponsorship, if Han-Wen approves, right now. Steve Steve Doonan New Mexico, US http://www.xscd.com/pub/ -- Good judgement comes from experience. Unfortunately, the experience usually comes from bad judgement. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--cross-staff chords, ties
On Tue, Aug 22, 2006 at 10:29:49PM -0500, Trevor Bača wrote: > On 8/22/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > >Hello, > >I once made an estimate for doing x-staff chords, for 400 EUR. I think > >that would be the most difficult task. If the stems + noteheads work > >correctly, adding arpeggios and ties should be relatively easy. > >For reference, I insert what I wrote to Hans Forbrich: > > < snip > > Well I had always wondered why the pricing on cross-staff stuff was so > high. I thought it might be because it breaks the Voice model, but I > wasn't sure ... > Well, if Steve or Vivian or Hans or somebody is willing to help out, > then I'm willing to pitch in on the sponsoring too. I am definitely willing and will commit to sponsoring this feature, preferably on an equal basis (2 sponsors, 50%, 3 sponsors, 33.3%, etc.). Thanks Trevor-- Steve D New Mexico US -- We have just enough religion to make us hate, but not enough to make us love one another. -Jonathan Swift ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Prevent Collision of Tuplet Brackets ???
Hi, I have a PianoStaff and there is a triplet bracket at the top stave overlapping a triplet bracket at the bottom stave :-(( What can I do to prevent any collision between the two brackets? Could you please give me some hints or show me some tricks to copy with that problem? (I use Lilypond Version 2.8.6). Thanks very much in advance! Have a nice day! Sincerely, Ben. How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates.___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
stopStaff, whitespace and forcing a clef reprint for CODA? (help)
%{
I hope someone can help me with this...
I typically use the following code to insert some horizontal whitespace in
front of my final ending CODA's. But sometimes I need the clef to force
re-print after the whitespace even though it has not really changed.
How can I change the code below to force the clef to re-print on the final
ending measure just past the whitespace break? I know this has to be simple
but I'm stumped. (the example below will execute as is)
Notice I'm restating the \clef directive but the clef is not re-printing.
%}
% BEGIN sample code
myKey = \key f \major
myTime = \time 4/4
myMarkCoda = \mark \markup { \musicglyph #"scripts.coda" }
myMarkDcAlCoda = { \once \override Score.RehearsalMark #'self-alignment-X =
#right
\mark "D.C. al Coda " }
myMarkEndCoda = {
\stopStaff
\cadenzaOn \skip1 \cadenzaOff
\clef treble
\myKey
\bar ""
\startStaff
\mark \markup { \musicglyph #"scripts.coda" }
}
myNotes = \relative c' {
c4 d e f
|
g a b c
|
g, a b c
\myMarkCoda
|
c4 d e f
|
c4 d e f
|
\myMarkDcAlCoda
\myMarkEndCoda
g a b c
|
}
% the staff below is in a separate .ly file template (simplified for example
here)
\new Staff
{
\clef "treble"
\myKey
\myTime
\myNotes
}
--
View this message in context:
http://www.nabble.com/stopStaff%2C-whitespace-and-forcing-a-clef-reprint-for-CODA--%28help%29-tf2136862.html#a5897016
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: Prevent Collision of Tuplet Brackets ???
On 8/23/06, Ben Hoefer <[EMAIL PROTECTED]> wrote: Hi, I have a PianoStaff and there is a triplet bracket at the top stave overlapping a triplet bracket at the bottom stave :-(( What can I do to prevent any collision between the two brackets? Could you please give me some hints or show me some tricks to copy with that problem? (I use Lilypond Version 2.8.6). Thanks very much in advance! Hi Ben, Can you send an example? (Please make sure to cc the lily list like you're done here in your first post.) Also, try setting \once \override TupletBracket #'staff-padding = #8 or \once \override TupletBracket #'padding = #2 and play with the numbers following the hash marks. -- Trevor Bača [EMAIL PROTECTED] ... like the dew, or like lightning ... ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Prevent Collision of Tuplet Brackets ???
Quoting Trevor Bača <[EMAIL PROTECTED]>: On 8/23/06, Ben Hoefer <[EMAIL PROTECTED]> wrote: Hi, I have a PianoStaff and there is a triplet bracket at the top stave overlapping a triplet bracket at the bottom stave :-(( What can I do to prevent any collision between the two brackets? Could you please give me some hints or show me some tricks to copy with that problem? (I use Lilypond Version 2.8.6). Thanks very much in advance! Hi Ben, Can you send an example? (Please make sure to cc the lily list like you're done here in your first post.) Also, try setting \once \override TupletBracket #'staff-padding = #8 or \once \override TupletBracket #'padding = #2 and play with the numbers following the hash marks. From the question, it rather seems that the staves are too close together, so if you increase the padding, then the brackets will probably overlap even more. Rather, you might want to use \tupletUp or \tupletDown (which is reset by \tupletNeutral), to place the tuplets in the upper stave above the stave or those in the lower stave below the stave. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Prevent Collision of Tuplet Brackets ???
Ben Hoefer <[EMAIL PROTECTED]> wrote: > Hi, > > I have a PianoStaff and there is a triplet bracket at the top stave > overlapping a triplet bracket at the bottom stave :-(( > > What can I do to prevent any collision between the two brackets? You will want to look at the #'direction, #'positions and #'padding properties of TupletBracket. For example: \override TupletBracket #'direction = #UP For all the properties look at http://lilypond.org/doc/v2.8/Documentation/user/lilypond-internals/TupletBracket.html#TupletBracket /henrik ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--cross-staff chords, ties
Trevor Bača wrote: On 8/22/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Hello, I once made an estimate for doing x-staff chords, for 400 EUR. I think that would be the most difficult task. If the stems + noteheads work correctly, adding arpeggios and ties should be relatively easy. For reference, I insert what I wrote to Hans Forbrich: Well I had always wondered why the pricing on cross-staff stuff was so high. I thought it might be because it breaks the Voice model, but I wasn't sure ... no, there are 2 issues: how to deal with the Staff/Voice model, and how to keep the typesetting engine free of cyclic-dependencies. The latter problem needs to be solved first, then we can invent ways for the Staff/Voice model to control the typesetting engine. Well, if Steve or Vivian or Hans or somebody is willing to help out, then I'm willing to pitch in on the sponsoring too. I'm about to have cross-staff stuff all over some piano music and also between different *string* staves as well. So a question. QUESTION: will the proposed cross-staff implementation path enable cross-staff stemming and beaming between *nonadjacent* staves (eg, 1st violins and basses, passing over the 2nd violins, violas and cellos)? This is fraught with cyclic dependencies. It might be possible, but you have to have some restrictions, eg. * the distances between these staves have been fixed in advance. or * all x-staff beams are horizontal or * stem directions have no influence over spacing. In general: * spacing depends on stem directions, * line breaks depend on spacing * y-distance between staves depends on line breaks * beam configurations depend on y-distances * stem directions depend on beam configurations hence, if we want x-staff stems, we must have restrictions: currently, the y-distance between staves is fixed, and this works pretty well for x-staff beams. There might be other ways to break this cycle, but there might be other cycles as well. -- 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
Re: Sponsored feature request--cross-staff chords, ties
On 8/23/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Trevor Bača wrote: > On 8/22/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: >> >> Hello, >> >> I once made an estimate for doing x-staff chords, for 400 EUR. I think >> that would be the most difficult task. If the stems + noteheads work >> correctly, adding arpeggios and ties should be relatively easy. >> >> For reference, I insert what I wrote to Hans Forbrich: > Well I had always wondered why the pricing on cross-staff stuff was so > high. I thought it might be because it breaks the Voice model, but I > wasn't sure ... no, there are 2 issues: how to deal with the Staff/Voice model, and how to keep the typesetting engine free of cyclic-dependencies. The latter problem needs to be solved first, then we can invent ways for the Staff/Voice model to control the typesetting engine. Got it. > Well, if Steve or Vivian or Hans or somebody is willing to help out, > then I'm willing to pitch in on the sponsoring too. > > I'm about to have cross-staff stuff all over some piano music and also > between different *string* staves as well. So a question. > > QUESTION: will the proposed cross-staff implementation path enable > cross-staff stemming and beaming between *nonadjacent* staves (eg, 1st > violins and basses, passing over the 2nd violins, violas and cellos)? This is fraught with cyclic dependencies. It might be possible, but you have to have some restrictions, eg. * the distances between these staves have been fixed in advance. Fixed staff distance is perfectly good for me because of my way of working. In every score the first thing I do is turn on proportional notation to regularize horizontal spacing regular and the second thing is to fix staff distances to do the same thing for vertical spacing. So would that particular restriction (ie, that you only get "nonadjacent stemming" or "nonadjacent beaming" or whatever we wind up calling this sorta thing with fixed staff distances) cause a problem for anyone else? (If so, that's OK; we'll take one of the other paths.) or * all x-staff beams are horizontal What's an x-staff? Oh wait. Cross-staff. Got it. No. This won't do. There still has to be beam slant for cross-staff beams. or * stem directions have no influence over spacing. I don't think I understand. (But maybe that's OK; if the fixed-staff-y-distance restriction turns out to be acceptable then I'm fine not grokking this point completely. On the other hand, if we can't do the fixed-staff-y-distance thing then maybe more explanation here would be good.) In general: * spacing depends on stem directions, * line breaks depend on spacing * y-distance between staves depends on line breaks * beam configurations depend on y-distances * stem directions depend on beam configurations hence, if we want x-staff stems, we must have restrictions: currently, the y-distance between staves is fixed, and this works pretty well for x-staff beams. Right because the PianoStaff context allows cross-staff beams (but not stems) today, under the restriction that we fix the distance between the staves before all the other layout stuff happens. I think we should just continue this same restriction for the other cross-staff stuff (ie, for cross-staff *stems*, and for nonadjacent beams and stems). Two reasons: 1. We already have the restriction with cross-staff beams in a PianoStaff so the restriction already exists in (at least part of) the model (and nobody seems to complain) 2. My past experience laying out cross-staff stuff in SCORE always started with first fixing the exact vertical position of the staves and only then doing all the beaming stuff, and this worked extremely well, even for Takemitsu-looking stuff that beamed different string sections together There might be other ways to break this cycle, but there might be other cycles as well. -- Trevor Bača [EMAIL PROTECTED] ... like the dew, or like lightning ... ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
lilypond-book
Hello everyone again!Recently I am making some tests about LaTeX + lilypond in order to learn to integrate text and music but I am having -like usually I do- some problems. Here you have the original document that I called "
prueba.lytex":\documentclass[a4paper,12pt,spanish]{article}\usepackage[utf8]{inputenc}\usepackage[spanish]{babel}\usepackage[T1]{fontenc}
\usepackage[dvips]{graphicx}\date{23-08-06}\begin{document}Vamos a probar para ver qué tal queda esto... ¿Qué pasa con las tildes?Por otro lado podemos cajón español\begin{lilypond}
staffViolin = \new Staff {\set Staff.instrument="Violin"\set Staff.midiInstrument="violin"\key c \major\clef treble\relative c' {
g1 d' a' e'\bar "|."}}harmonies = \new ChordNames \chordmode {g1 d a e}\score {<<\harmonies
\staffViolin>>\midi {}\layout {\context {\Scoretimming = ##f }\context {
\Staff\remove "Time_signature_engraver"\remove "Bar_engraver"}}}\paper {linewidth = 160 \mm -
2.0 * 9.0 \mmindent = 10.0\mmraggedright = ##t}\end{lilypond}\end{document}%%Well, the point is that when I call to lilypond-book everything seem to be right but in the directory of results I can find, between the many elements created, two files .eps. One of them seems to be the right one and the other one is defective or faulty because de score is not right. The point is that when I run latex over the file
prueba.tex created, the eps called is the faulty one, not the right. I enclose the file obtained on my pc to be crearlier. I wait some help because I don't know if it is because of my clumsiness.Thank you very much for the help ;)
prueba.dvi
Description: TeX dvi file
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
warning: can't find or create `Timing' called `'
I figured now was the time to jump from 2.8.5 to 2.9.x. The transition has been mostly smooth. One message, though, floods the console: warning: can't find or create `Timing' called `' The code processes and looks perfectly fine. My theory is that parsing of apostrophes in one or more context items -- e.g., #'padding -- has changed in the new version, but I can't find any documentation of this shift. I tried running anything applicable through convert-ly, but nothing changed. Have any of the following changed? Become obsolete entirely? Or heck, would you happen to outright know what's causing this message? \override Score.InstrumentName #'padding = #3.0 \override Score.MetronomeMark #'transparent = ##t \override Score.TupletBracket #'bracket-visibility = ##f \override Score.Hairpin #'padding = #5 \override Score.Hairpin #'minimum-length = #5 \override Score.DynamicText #'padding = #5 \override Score.RehearsalMark #'padding = #6 \override Score.RehearsalMark #'self-alignment-X = #LEFT \override Score.TextScript #'padding = #2 \override Score.TrillSpanner#'padding = #2.5 \override Score.BarNumber #'padding = #2.5 \override Score.BarNumber #'font-size = #0.8 I don't dare succeed if change always comes first -- _ | WILL ORAM ASCII ribbon campaign ( ) | spamguy (at) foxchange . com - against HTML email X | wro1 (at) cwru . edu & vCards / \ | | AIM spamguy21 -- (ABOVE: Magnetic poetry #5) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
