Re: Help with unexpexted double barline trouble and \markup

[Urs Liska]

Am 15.01.2016 um 08:07 schrieb Carl-Henrik Buschmann:
> I'm working on a lead sheet but being a novice i'm hitting my head
> against the wall at some noob problems. 
>
> Bar 1) 
> Stemlets. Do it have to be this hard creating them? Is there a way to
> make it global? Also, i want the stemlet to reach down towards the
> rest. How?

Try
  \override Stem.stemlet-length = 2
play around with the value and see if that's what you want.
> How do i make custom rehersal marks?
> When using \markup { ... } the whole score looses it layout and to add
> insult it does not display any text. I must have done something wrong.

It's not really clear what you want to achieve.
If you want some text instead of the boxed letter you can write
  \mark \markup { Some text or markup commands }

But if you're looking for printing some additional text somewhere then
you have to attach the \markup to some music, like

  r8 -\markup { Some text }

Instead of the hyphen you can also use ^ or _ to force the markup to be
above or below the staff.

>
> Bar 8)
> Why does the double barline not exend equaly through both staffs?

Obviously this is because you have made the lower staff smaller, this
also affects the barlines.
If you look closely you'll see that this also happens to the other barlines.

I'm not sure how to fix that, though. Maybe you can enlarge just the
barlines for the lower staff to revert the effect of \magnifyStaff.
OTOH it may also be that this is an issue that should/could be fixed
with \magnifyStaff (a very new function).

>
> Bar 37)
> Why does it not show a double bar line?
>

I *think* this is because the barline at the end of a line and the one
at the beginning of the next is semantically just one item. So the \bar
".|:" simply overwrites the \bar "||".

Don't know either how to fix, but there are tools to handle how items
are displayed around line breaks.

> And finally: I feel my score is a mess. How can i clean up/simplify my
> input? Also, inputing this takes alot of time considering how long use
> on inputing this in Sibelius (added as pfd). What can i do to speed
> this up? Help and encouragement is much obliged.

What one can say is basically: Be patient and learn. How long did it
take you to get to a state where inputting this in Sibelius takes you
less time? In a way the problem is that learning LilyPond is like
learning a new instrument as an adult. Factually it's not that hard and
progress is not so slow, but you're already used to what you can achieve
with the tools you're familiar with.

Some suggestions for your file.

\comp
is just a rest (as Kieren mentions I'm not sure if you really need the
music function for that).
There's no need to put all those barchecks in this case as it is
completely clear that you *do* have complete measures in between.
So at rehearsal mark B you could equally have written
  \comp31 r4
to reach rehearsal mark C.

Then you should put the manual breaks and the rehearsal marks in a
separate music variable (that is then used in parallel to the music). So
actually what you need in that part of the music (from B to the
beginning of F) would be:

\comp31 r4
\comp28
\time 2/4
\comp2
\time 4/4
\rs r4 r2
\comp15 r4
\comp31 r4

For the repeated written chords you could have made more use of  \repeat
unfold, and/or of the "q" shorthand for repeating the previous pitch/chord.

These are just some hints. If you get familiar with LilyPond input you
can use this kind of techniques and others to simplify the files and
speed the inputting process.
But as Kieren said: speed of music entry is not the primary selling
point of LilyPond.

HTH
Urs

>
> Images of lilypond and sibelius (reference) outout.
> http://imgur.com/a/Izl8D 
>
> .ly attached. 
>
>
>
>
>
>
> ___
> 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

Re: Help with unexpexted double barline trouble and \markup

[Chris Yate]

On 15 January 2016 at 07:07, Carl-Henrik Buschmann 
wrote:

> I'm working on a lead sheet but being a novice i'm hitting my head against
> the wall at some noob problems.
>
> Bar 1)
> Stemlets. Do it have to be this hard creating them? Is there a way to make
> it global? Also, i want the stemlet to reach down towards the rest. How?
> How do i make custom rehersal marks?
> When using \markup { ... } the whole score looses it layout and to add
> insult it does not display any text. I must have done something wrong.
>
>
1) Stemlets: why do you want to write them like this? Normal quavers are
fine

2) use \mark "A", not \markup "A"


> Bar 8)
> Why does the double barline not exend equaly through both staffs?
>


You've made the lower staff smaller with   \magnifyStaff #5/7, so its
barline will be a different size too.  I've had this with instrumentname
recently (answered on here, it's by design)



> Bar 37)
> Why does it not show a double bar line?
>

I think that's because there's a double bar in the Volta section following,
but I'll concede that's unexpected.


> And finally: I feel my score is a mess. How can i clean up/simplify my
> input?
>

I'd split it into separate files, and pull them together in a master .ly
file using the
/include "music.ily"
command.

I also think barlines on separate lines helps.

So rather than

a4 b c d |
e f g a |

instead

a4 b c d
|
e f g a
|


You can also label bar numbers with comments:

a4 b c d
| %1
e f g a
| %2

but this gets tiresome after a while.


> Also, inputing this takes alot of time considering how long use on
> inputing this in Sibelius (added as pfd). What can i do to speed this up?
> Help and encouragement is much obliged.
>

Well, you need to get fast at your keyboard skills and touch-typing! I
think Lilypond is much faster than manual entry in Sibelius -- using a MIDI
keyboard may be faster but it's also more prone to errors if you're trying
quantized direct music entry.

Chris
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Help with unexpexted double barline trouble and \markup

[Chris Yate]

On 15 January 2016 at 14:37, Kieren MacMillan  wrote:

> Hi Carl-Henrik,
>
> > Bar 1)
> > Stemlets. Do it have to be this hard creating them? Is there a way to
> make it global? Also, i want the stemlet to reach down towards the rest.
> How?
>
> This may be related to the issue Urs is working on at the moment. In any
> case, I’m sure there are automatic ways to make your preference global.
>

According to the documentation, no...

http://www.lilypond.org/doc/v2.19/Documentation/notation/beams#automatic-beams

"Beams *must* be entered manually if beams are to be extended over rests."

But I have seen a snippet through which you can avoid the slur AND beam in
the following:
a8 ([ b c d ]) a ([ b c d])

I can't remember where I saw it!

Chris
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Help with unexpexted double barline trouble and \markup

[Kieren MacMillan]

Hi Carl-Henrik,

> Bar 1) 
> Stemlets. Do it have to be this hard creating them? Is there a way to make it 
> global? Also, i want the stemlet to reach down towards the rest. How?

This may be related to the issue Urs is working on at the moment. In any case, 
I’m sure there are automatic ways to make your preference global.

> How do i make custom rehersal marks?

Did \mark \markup { … } not work for you?

> Bar 8)
> Why does the double barline not exend equaly through both staffs?

That looks like a bug to me: all SpanBars should [IMO] be printed at the 
largest applicable size.

> Bar 37)
> Why does it not show a double bar line?

:
In addition, you can specify ".|:-||", which is equivalent to ".|:" except at 
line breaks, where it gives a double bar line at the end of the line and a 
start repeat at the beginning of the next line.

> And finally: I feel my score is a mess. How can i clean up/simplify my input?

It’s not that messy, to my eye.

But it does seem like a lot of code for such a simple score. For example, I am 
very surprised that you needed to do all that Scheme programming… did \repeat 
percent not work? (I don’t have time to test right now.)

> inputing this takes alot of time considering how long use on inputing this in 
> Sibelius

Now that I’m adept, I find that the input phase for my Lilypond code is about 
75-80% of the input time required when I was a Finale guru, and 50% of the time 
required when I used Sibelius (but admittedly was not a guru).

Where the big time savings comes is in the “tweaking” phase: I figure Lilypond 
requires about 5-10% of the tweaking time that my Finale and Sibelius scores 
did. And now that I know how beautiful computer-engraved scores can actually 
look [because of Lilypond], I would probably spend even more time tweaking 
Finale/Sibelius files if I ever had to use those applications.

Hope this helps and/or encourages!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Help with unexpexted double barline trouble and \markup

[Kieren MacMillan]

Hi Chris,

> According to the documentation, no…
> […]
> But I have seen a snippet through which you can avoid the slur AND beam

That’s what I meant by “there are automatic ways to make your preference 
global”.  ;)
It’s probably a Scheme function/callback.

I hope it gets found!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Help with unexpexted double barline trouble and \markup

[Urs Liska]

Am 15.01.2016 um 15:37 schrieb Kieren MacMillan:
>> Bar 1) 
>> > Stemlets. Do it have to be this hard creating them? Is there a way to make 
>> > it global? Also, i want the stemlet to reach down towards the rest. How?
> This may be related to the issue Urs is working on at the moment. In any 
> case, I’m sure there are automatic ways to make your preference global.
>

This is related but I won't touch anything for this use case.

As I mentioned somewhere the decision about *what* to beam has been
already done at the stage I'm dealing with.

Urs

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Help with unexpexted double barline trouble and \markup

[Simon Albrecht]

On 15.01.2016 17:50, Urs Liska wrote:

Am 15.01.2016 um 17:46 schrieb Simon Albrecht:

On 15.01.2016 16:58, Carl-Henrik Buschmann wrote:

1) My experience is that reading rhythms with the stemlets over the
rests helps alot. It is a tad "modern" but generally approved. Is
there a way to make it global?

No problem: just insert

\context {
 \Voice
 \override Stem.stemlet-length = 2
   }

into any layout block, e.g. alongside with the tweaks for \ChordNames.

No, that's not what he needs.
The question is to automatically extend the beam itself over the rest.


Ah, that’s the reason. Sorry for the misconception.

Best, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Help with unexpexted double barline trouble and \markup

[Simon Albrecht]

On 15.01.2016 16:58, Carl-Henrik Buschmann wrote:
1) My experience is that reading rhythms with the stemlets over the 
rests helps alot. It is a tad "modern" but generally approved. Is 
there a way to make it global? 


No problem: just insert

\context {
\Voice
\override Stem.stemlet-length = 2
  }

into any layout block, e.g. alongside with the tweaks for \ChordNames.

HTH, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Help with unexpexted double barline trouble and \markup

[Urs Liska]

Am 15.01.2016 um 17:46 schrieb Simon Albrecht:
> On 15.01.2016 16:58, Carl-Henrik Buschmann wrote:
>> 1) My experience is that reading rhythms with the stemlets over the
>> rests helps alot. It is a tad "modern" but generally approved. Is
>> there a way to make it global? 
>
> No problem: just insert
>
> \context {
> \Voice
> \override Stem.stemlet-length = 2
>   }
>
> into any layout block, e.g. alongside with the tweaks for \ChordNames.

No, that's not what he needs.
The question is to automatically extend the beam itself over the rest.

Urs

>
> HTH, Simon
>
> ___
> 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

Re: Help with unexpexted double barline trouble and \markup

[Chris Yate]

On 15 January 2016 at 15:58, Carl-Henrik Buschmann 
wrote:

>
> 15. jan. 2016 kl. 15.32 skrev Chris Yate :
>
>
>
> On 15 January 2016 at 07:07, Carl-Henrik Buschmann 
> wrote:
>
>> I'm working on a lead sheet but being a novice i'm hitting my head
>> against the wall at some noob problems.
>>
>> Bar 1)
>> Stemlets. Do it have to be this hard creating them? Is there a way to
>> make it global? Also, i want the stemlet to reach down towards the rest.
>> How?
>> How do i make custom rehersal marks?
>> When using \markup { ... } the whole score looses it layout and to add
>> insult it does not display any text. I must have done something wrong.
>>
>>
> 1) Stemlets: why do you want to write them like this? Normal quavers are
> fine
>
> 1) My experience is that reading rhythms with the stemlets over the rests
> helps alot. It is a tad "modern" but generally approved. Is there a way to
> make it global?
>

I'd agree that's the case for rhythms like ` a16 [ r b c ] d [ r c b ] `
but I don't *think* I've ever seen quavers written as you have done ` r8 [
a ] r [ b ] ` in commercial printed music. Just looks strange to me, but I
appreciate you want it a certain way and that's fine.

As for making it global, I don't know of a way, but I am sure it's possible
to write a function to make it happen. Not my expertise unfortunately.

Chris
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Help with unexpexted double barline trouble and \markup

[Carl-Henrik Buschmann]

> 
> 15. jan. 2016 kl. 15.32 skrev Chris Yate :
> 
> 
> 
> On 15 January 2016 at 07:07, Carl-Henrik Buschmann  > wrote:
> I'm working on a lead sheet but being a novice i'm hitting my head against 
> the wall at some noob problems. 
> 
> Bar 1) 
> Stemlets. Do it have to be this hard creating them? Is there a way to make it 
> global? Also, i want the stemlet to reach down towards the rest. How?
> How do i make custom rehersal marks?
> When using \markup { ... } the whole score looses it layout and to add insult 
> it does not display any text. I must have done something wrong.
> 
> 
> 1) Stemlets: why do you want to write them like this? Normal quavers are fine
> 

1) My experience is that reading rhythms with the stemlets over the rests helps 
alot. It is a tad "modern" but generally approved. Is there a way to make it 
global? 


> 2) use \mark "A", not \markup "A"
>  

2) Thank you!


> Bar 8)
> Why does the double barline not exend equaly through both staffs?
>  
> 
> You've made the lower staff smaller with   \magnifyStaff #5/7, so its barline 
> will be a different size too.  I've had this with instrumentname recently 
> (answered on here, it's by design)
> 
>  

3) Is it perhaps better do make an ossai staff? I'm a little scared by ossias. 
Seems like a lot of work to get it done. 
> 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Help with unexpexted double barline trouble and \markup

[Thomas Morley]

2016-01-15 15:37 GMT+01:00 Kieren MacMillan :
> Hi Carl-Henrik,

>> Bar 8)
>> Why does the double barline not exend equaly through both staffs?
>
> That looks like a bug to me: all SpanBars should [IMO] be printed at the 
> largest applicable size.

Well, then it's by design, because `magnifyStaff' affects
BarLine.kern/segno-kern/hair-thickness/thick-thickness explicitely.
This is desireable for standalone staves, ofc

In this light we should do a fix as you suggested: "all [Bars and]
SpanBars should be printed at the largest applicable size", not sure
where/how to fix it, though.
Or we shouldn't point users in the NR to use it in a score with
different sizes at all (only for ossia-examples) and/or add a remark
about "known issues", maybe with the first workaround below.

Two workarounds:
(1)
Set your own BarLine.kern:

m = { c'1 \bar "||" }

\score {
  \new StaffGroup
  <<
\new Staff \with {
  \magnifyStaffs #7/4
  \override BarLine.kern = #3
}
  \m
\new Staff \with {
  \magnifyStaffs #1
  \override BarLine.kern = #3
}
  \m
\new Staff \with {
  \magnifyStaffs #4/7
  \override BarLine.kern = #3
}
  \m
  >>
}


(2)
Use `staffSize' from
http://lsr.di.unimi.it/LSR/Item?id=862
instead:

staffSize = #(define-music-function (parser location new-size) (number?)
  #{
\set fontSize = #new-size
\override StaffSymbol.staff-space = #(magstep new-size)
\override StaffSymbol.thickness = #(magstep new-size)
  #})

m = { c'1 \bar "||" }

\new StaffGroup
<<
  \new Staff \with { \staffSize #6 }
\m
  \new Staff \with { \staffSize #0 }
\m
  \new Staff \with { \staffSize #-6 }
\m
>>

HTH,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user