Re: One staff, two voices, two lyrics --> one above, one below

Hi Wilhelm, > I have one staff, two voices and two lyrics. The bassOnewords should be > placed above and the bassTwowords below the staff. But my solution > places both words below the score. > > \version "2.18.2" > > ... > > \score { ><< > \new Staff << > \new Voice = "bassOne

Re: One staff, two voices, two lyrics --> one above, one below

Hi Wilhelm, Just a stab in the dark (I'm not in reach of LP right now): Context "staff" does not seem to exist at all. Does \new Staff = "staff" ... Solve the problem? Also, I'm not sure if the Lyrics contexts should be inside the staff context or rather outside of it ... and in the desired s

Re: One staff, two voices, two lyrics --> one above, one below

Hello, you will have to give your Staff a name and use it as reference for alignAboveContext: \score { << \new Staff = "bass" << \new Voice = "bassOne" << \bassOneNotes >> \new Lyrics \with { alignAboveContext = "bass" } \lyricsto "bassOne" \bassOneWords \n

Re: One staff, two voices

Hi Wim, Please reply to the whole list, so that others might benefit from our discussion. On Thu, Nov 1, 2012 at 11:48 AM, Wim van Dommelen wrote: > The other discussion would be: Are you going to use the Tiny Examples as a > way of showing small pieces of code doing some specific action? Is tha

Re: One staff, two voices

On Thu, Nov 1, 2012 at 10:03 AM, David Kastrup wrote: > Janek Warchoł writes: > > You mean > > \include "english.ly" > > in the page about tiny examples? Actually, english.ly is a file > > bundled with Lilypond, which allows to spell note names with english > > names ('fsharp' or 'fs' instead of

Re: One staff, two voices

Janek Warchoł writes: > Hi, > > sorry for delay, i was very busy... > > On Sun, Oct 28, 2012 at 11:21 AM, Wim van Dommelen wrote: >> But the top part of the example shown uses an include-file. >> That is not "tiny", anything can happen there. So I would add >> to the rules for a tiny example no

Re: One staff, two voices

Hi, sorry for delay, i was very busy... On Sun, Oct 28, 2012 at 11:21 AM, Wim van Dommelen wrote: > But the top part of the example shown uses an include-file. > That is not "tiny", anything can happen there. So I would add > to the rules for a tiny example no use of include files. You mean \in

Re: One staff, two voices

Hi Janrek,Thanks for pointing to the Tiny Examples section. Didn't know this existed, good idea. In programming it is a common method to squeeze your problem to something as small as possible. Also a good start for any regression test.But the top part of the example shown uses an include-file. That

Re: One staff, two voices

On Sun, Oct 28, 2012 at 3:25 AM, Daniel Rosen wrote: >[...] > This is the first time I've answered a question on the list That's great! I find your answer clear and helpful - hopefully Mark will like it, too :) > but I don't think I'd be out of line by asking you to use tiny examples in > the

Re: One staff, two voices

Also, the Mutopia project (www.mutopiaproject.org/) hosts most of the WTC in lilypond format. You're probably going to need to move that second voice down to the bass clef at some point and then back. Taking a look at the samples at Mutopia helped me quite a bit. -- View this message in context:

Re: One staff, two voices

On 28/10/12 12:57, Mark Stephen Mrotek wrote: > > Fellow Users: > > > > I am encoding a three part fugue (Bach). Two of the voices should be > in the treble staff. The instructions in the on-line manual were > followed (1.5.2 Multiple Voices /Explicitly instantiating voices)./ > > > > When I en

RE: One staff, two voices

You always need to enclose simultaneous music in <>. Here's how the third bar of your fugue might look: \new PianoStaff << \new Staff = "upper" << \new Voice { \relative c' { \voiceOne \key cis \major cis8 cis'16 bis cis dis eis fis gis16 fisis eis fisis gis fis eis di