Re: Stem.stem-begin-position not giving desired output on beamed stems (tablature)

2016-12-18 Thread Carl Williams
Thanks Harm,  Then remove it there.  Yes, for some reason that flew over my head. Probably because it wasn't styled correctly ;) One question on styling, which is correct?  I think the first, considering rule 3: closing parenthesis close the line.  (/ (+ start-in (- (abs length-in)  

Re: Stem.stem-begin-position not giving desired output on beamed stems (tablature)

2016-12-18 Thread Thomas Morley
Hi Carl, 2016-12-18 8:26 GMT+01:00 Carl Williams : > One more little adjustment, for anyone who will benefit from it. > The previous version only overrode Beam.positions on the first line. After a > line break they go back to how they were if by default. > I don't

Re: Stem.stem-begin-position not giving desired output on beamed stems (tablature)

2016-12-17 Thread Carl Williams
One more little adjustment, for anyone who will benefit from it.  The previous version only overrode Beam.positions on the first line. After a line break they go back to how they were if by default.  I don't quite understand why, but the solution was to move that section under a

Re: Stem.stem-begin-position not giving desired output on beamed stems (tablature)

2016-12-17 Thread Carl Williams
To anyone who's interested,  I've tidied up the workaround for this. It now takes two inputs; stem-start and stem-length.  It also now allows for above or below staff positioning.  %% \version "2.18.2" beam-stem-height = #(define-music-function (parser location

Re: Stem.stem-begin-position not giving desired output on beamed stems (tablature)

2016-12-16 Thread Carl Williams
Thanks Harm,  That's just what I was after.  I'm keen to learn more about how beam positions and stems are calculated. Then maybe I can calculate it using only 2 input variables.  I think I'll have a look in the .scm files, and see what I can find. I'm not sure yet which one it'll be in.

Re: Stem.stem-begin-position not giving desired output on beamed stems (tablature)

2016-12-14 Thread Carl Williams
So I figured a little workaround that does the job.  I use 2 voices, one which shows only the Stems and Beams, the other which shows only the TabNoteHeads.  Unfortunately, it's doesn't always compile when I use extra complex combinations of rests, notes and spacers. Says it has an internal

Stem.stem-begin-position not giving desired output on beamed stems (tablature)

2016-12-13 Thread Carl Williams
Hi Everyone,  First time using a mailing list.  I've raked through the documentation pages all today and yesterday (and learnt a lot), but still couldn't solve this.  So I want to create (ukulele) tablature where all the stems and beams are above the staff.  I use the \override