Am 14. April 2017 16:04:31 MESZ schrieb David Nalesnik
:
>On Fri, Apr 14, 2017 at 1:38 AM, Urs Liska wrote:
>>
>>
>> Am 13.04.2017 um 16:48 schrieb David Nalesnik:
>>> On Tue, Apr 11, 2017 at 5:54 PM, Urs Liska
>wrote:
Am 11.04.2017 um 21:04 schrieb tisimst:
On Tu
Am 15.04.2017 um 02:36 schrieb Stan Mulder:
> Thanks for the clarification on the reply-all. I wasn't sure what to do.
> Is there some place on the web were I can see other discussions?
There are several archives, f. e.
http://lists.gnu.org/archive/html/lilypond-user/ (this is the mailing
lists
Thomas,
Got it. I used your first solution with the addendum. If at some point
in the future I need more chords, I will construct a more extensive file
for guitar chords. I did construct a fingering file for plectrum banjo a
while back. It's got 25 chords for each of 12 keys, but I don't have
2017-04-15 0:05 GMT+02:00 Daniel Rosen :
> \version "2.19.56"
>
>
>
> \relative c'' {
>
> c4 c c c
>
> \bar "[|:"
>
> c4 c c c \break
>
> \bar ".|:-||"
>
> c4 c c c
>
> }
>
>
>
>
>
>
>
> I would like the first line in the above example to end with a double bar
> (\bar "||"),
\version "2.19.56"
\relative c'' {
c4 c c c
\bar "[|:"
c4 c c c \break
\bar ".|:-||"
c4 c c c
}
I would like the first line in the above example to end with a double bar (\bar
"||"), and the second line to begin with a winged begin-repeat bar (\bar
"[|:"). How can I acco
Hi David,
> That thread is now 8 months old, and I wondered what has happened since.
Unfortunately, not as much as one would hope…
> Is some of it yet incorporated into the development version of LilyPond?
I’d have to look more closely, but my intuition is “yes”.
> Is it likely to be included
On Thu, 2017-04-13 at 14:37 +0100, David Sumbler wrote:
> On Thu, 2017-04-13 at 09:19 -0400, Kieren MacMillan wrote:
> >
> > Hi David,
> >
> > >
> > >
> > > At the moment I cannot really see how to deal with this sort of
> > > problem, other than having completely separate input for the
> > > s
On 4/14/17 5:55 AM, "Jérôme Plût" wrote:
>Are there any other ways to tune the vertical spacing between staffs
>other than the \paper block? What I want is the following: on the same
>page,
> - first a score A (single-staff, no groups) with successive staffs
> extremely close together (about
On Fri, Apr 14, 2017 at 1:38 AM, Urs Liska wrote:
>
>
> Am 13.04.2017 um 16:48 schrieb David Nalesnik:
>> On Tue, Apr 11, 2017 at 5:54 PM, Urs Liska wrote:
>>>
>>> Am 11.04.2017 um 21:04 schrieb tisimst:
>>>
>>>
>>>
>>> On Tue, Apr 11, 2017 at 1:00 PM, Urs Liska [via Lilypond] <[hidden email]>
>>
- Original Message -
From: "Jérôme Plût"
To:
Sent: Friday, April 14, 2017 12:55 PM
Subject: Staff grouping
Are there any other ways to tune the vertical spacing between staffs
other than the \paper block? What I want is the following: on the same
page,
- first a score A (single-staff
Are there any other ways to tune the vertical spacing between staffs
other than the \paper block? What I want is the following: on the same
page,
- first a score A (single-staff, no groups) with successive staffs
extremely close together (about 2 or 3 staff lines of separation
should be enou
2017-04-14 12:25 GMT+02:00 Thomas Morley :
> Sollution(s):
>
> (1)
> Define it yourself, search the NR for 'storePredefinedDiagram'. Leading to:
>
> \version "2.19.56"
>
> \language "english"
>
> \storePredefinedDiagram #default-fret-table \chordmode {e-flat:m6}
> #guitar-t
2017-04-14 5:18 GMT+02:00 Stan Mulder :
>
> Thomas,
>
> Here's your example, but with fretboards added. The error is there.
> Apparently it has to do with fretboards. Also, I am running 2.19.59:
>
> \version "2.19.56"
> \language "english"
> \include "predefined-guitar-fretboards.ly"
>
> m = \chor
Thanks so much to both! I ended up using X-offset, and it works like a
charm.
You're absolutely correct, Andrew. The score isn't particularly nice right
now. The break is actually my bad, I'm pretty sure I failed to copy over
something from my include files - since the bin had to be a self-contain
Hi Malte,
Sure, depends which side you want to adjust of course, I am merely
indicating a possible technique.
Michiel, speaking as a player myself, your example score seems fairly
cramped and lacking what I call 'air', making it a bit hard to read. And
there is definitely something wrong with the
Am 14.04.2017 um 06:45 schrieb Andrew Bernard:
> Hi Michiel,
>
> Use shorten-pait to taste.
>
> %\once \override TupletBracket.positions = #'(3.1 . 3.4)
> \once \override TupletBracket.shorten-pair = #'(0 . 0.5)
Shouldn’t this be #'(0.2 . 0) or similar but not #'(0 . 0.5) i
16 matches
Mail list logo