Op 18 maart 2017 21:49:17 schreef Joseph Austin :
But thinking about it, I'm wondering why one would want to notate a
different duration than is actually played,
A reason can be to make room in the bar for something else. For example, I
use it to engrave grace-like notes at the end of a
On 18/03/17 21:21, Colin Campbell wrote:
On 2017-03-18 10:28 AM, CieMaKat . wrote:
Hello everyone!
I would like to place custom header for piece, i.e.: hymn number and
authors of music and lyrics aligned to both sides of the page:
Obraz w treści 2
I tried to do it with fill-line, but then pa
On 19/03/17 07:20, Engraver wrote:
> Op 18 maart 2017 21:49:17 schreef Joseph Austin :
>
>>
>> But thinking about it, I'm wondering why one would want to notate a
> different duration than is actually played,
>>
>
>
> A reason can be to make room in the bar for something else. For example,
> I u
Hi Joseph,
> I'm wondering why one would want to notate a different duration than is
> actually played
There are any number of reasons:
1. creating Schenker graphs (and other "non-traditional” use of traditional
notation elements);
2. exploding vs. imploding tuplets;
3. contemporary notation
Huge thanks to Timothy Lanfear! That solution works perfectly.
I can pass multiple parameters in like this:
lilypond -e '(define-public title "my song")(define-public
copyrightyear "2017")(define-public ismn "12345-678-90-5")' tmp.ly
and then my header looks like:
\header {
I'm trying to create my own predefined chords and I'm wondering about
the shape definition
In predifined-guitar-freatboards.ly there is this
\addChordShape #'f #guitar-tuning #"1-1-(;3-3;3-4;2-2;1-1;1-1-);"
This shape-definition doesn't follow the
|\fret-diagram|definition-stringspecification
The best I've managed to do is to show the clef and keysig. However, I
haven't managed to fix the brackets, or reposition the coda or clefs.
See the attached images for details.
Is there some way to do this?
___
lilypond-user mailing list
lilypond-use
On Sun, Mar 19, 2017 at 4:14 PM, wrote:
> The best I've managed to do is to show the clef and keysig. However, I
> haven't managed to fix the brackets, or reposition the coda or clefs. See
> the attached images for details.
Could you add a minimum example of that LP code, too?
It might be hard
2017-03-18 23:36 GMT+01:00 David Kastrup :
>
> Well, lute tablature has the obvious advantage(?) to be using letters
> instead of fret numbers.
>
> I went totally annoyed over entering the first few measures of the
> following tablature appended as PDF
>
>
>
> so I finally decided that this wasn't
Alright, here's a small example. The Devnulls are my workaround for
multiple marks at the same place. Other than those, there's nothing too
remarkable.
On 03/19/17 21:34, Jeffery Shivers wrote:
On Sun, Mar 19, 2017 at 4:14 PM, wrote:
The best I've managed to do is to show the clef and keysi
Thomas Morley writes:
> I didn't proofread.
> Though some observations.
>
> (1)
> Why not
>
> "|" = \bar "|"
>
> instead of
>
> content = #(map-some-music
> (lambda (m)
> (and (music-is-of-type? m 'bar-check)
> #{ \bar "|" #}))
> content)
Beat you to it: it alr
"Trevor Daniels" writes:
> David Kastrup wrote Saturday, March 18, 2017 10:36 PM
>
>
>> So here is a sketch of entering this score by tab:
>
> Looks good and seems to work well.
>
>> Pretty sure I entered stuff wrong here (there is some programming error,
>> too) and probably did not decipher a
On Sun, Mar 19, 2017 at 4:55 PM, wrote:
> Alright, here's a small example. The Devnulls are my workaround for multiple
> marks at the same place. Other than those, there's nothing too remarkable.
Oh, this might be useful at least for the brackets:
http://lists.gnu.org/archive/html/lilypond-user/
Hey guys,
Anyone knows how to align music staff to the middle of the page instead of
the top?
Best,
Allen
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
2017-03-19 22:41 GMT+01:00 David Kastrup :
> Given how annoying I found the process of figuring out the notes from a
> tablature source, I am somewhat surprised that nobody considers this
> aspect of the example I posted worth commenting on.
Speaking only for me, probably because I am a classical
> On 19 Mar 2017, at 23:54, Trevor Daniels wrote:
>
> David Kastrup wrote Sunday, March 19, 2017 10:11 PM
>
>> Here is my version using
>>
>> \new TabStaff \with { stringTunings = \lute-tuning
>> tablatureFormat = #fret-letter-tablature-format
>> fretLabels = \markuplist \bold \fontsize #3 \
"Trevor Daniels" writes:
> David Kastrup wrote Sunday, March 19, 2017 10:11 PM
>
>> Here is my version using
>>
>> \new TabStaff \with { stringTunings = \lute-tuning
>> tablatureFormat = #fret-letter-tablature-format
>> fretLabels = \markuplist \bold \fontsize #3 \lower #0.2
>> { 𝔞 𝔟 𝔠 𝔡 𝔢
Hans Åberg writes:
>> On 19 Mar 2017, at 23:54, Trevor Daniels wrote:
>>
>> David Kastrup wrote Sunday, March 19, 2017 10:11 PM
>>
>>> Here is my version using
>>>
>>> \new TabStaff \with { stringTunings = \lute-tuning
>>> tablatureFormat = #fret-letter-tablature-format
>>> fretLabels = \ma
On 3/19/17 8:24 AM, "Anders Eriksson" wrote:
>
>
>
>I'm trying to create
>my own predefined chords and I'm wondering about the shape
>definition
>In
>predifined-guitar-freatboards.ly there is this
>\addChordShape #'f
>#guitar-tuning #"1-1-(;3-3;3-
> Re font-embedding, the attached uses the characters you suggested
> above,
Note that there is a fundamental problem with the transcription:
It's not clear how long accidentals are valid. For such unmetered
music it probably makes most sense to always write accidentals.
A problematic place is
20 matches
Mail list logo
