msk...@ansuz.sooke.bc.ca writes:
> On Thu, 17 Dec 2015, Kieren MacMillan wrote:
>> I just read through the Essay in its entirety, and found nothing which
>> suggests to me that Lilypond ever sacrifices clarity or functionality
>> for "visual artistry”.
>
> That is not what I said.
>
> A focus on c
Tim Reeves writes:
>>"LilyPond's focus is creating good, readable scores. That's what
> typography is about. Not creating visual artworks. The boundary
> conditions for bulk manufacturing work (like engraving once was) are not
> that dissimilar: skilled and effective workers are not the same a
Kieren MacMillan writes:
> Hi all,
>
>> I am starting to think there are two general classes of musicians,
>> the functionalists, and the aestheticists.
>> […] I suspect these groupings may be mutually exclusive!
>
> I think a binary view like that is limiting, and in general unhelpful.
>
> I, fo
Gilberto Agostinho writes:
> Hi all,
>
> I created a simple function which helps handle chords when using
> \autochange, but although the function works great I get some warning
> messages. This is the code:
>
> \version "2.19.32"
>
> autochord = #(define-music-function
> (parser location ch
Am 18.12.2015 um 00:51 schrieb Gilberto Agostinho:
> Hi all,
>
> I created a simple function which helps handle chords when using
> \autochange, but although the function works great I get some warning
> messages. This is the code:
>
> \version "2.19.32"
>
> autochord = #(define-music-function
>
With apologies for continuing to flog this subject...
I've taken David Kastrup's advice, and upgraded to 2.19.32, and I might
now be able to simplify this problem quite radically, and eliminate some
limitations, with a small change of syntax.
Below is the germ of the idea. The thing I'm missing
Graham King writes:
> With apologies for continuing to flog this subject...
>
> I've taken David Kastrup's advice, and upgraded to 2.19.32, and I might
> now be able to simplify this problem quite radically, and eliminate some
> limitations, with a small change of syntax.
>
> Below is the germ of
Hi Matthew,
Too many straw men, ad absurdums, and other fallacies here.
I’m officially out of the conversation.
As indicated before, “Patches are always welcome."
Regards,
Kieren.
On Dec 17, 2015, at 11:03 PM, msk...@ansuz.sooke.bc.ca wrote:
> On Thu, 17 Dec 2015, Kieren MacMillan wrote:
>> I
Hi Dominic,
i already had to deal with this particular prolem in many cases and
don't know of any reasonable workaround.
As others have mentioned, you can use either Y-offset in the Dynamics
context or attach the dynamic signs to particular staves/ notes.
Both ways have annoying side effects
Hi,
> Both ways have annoying side effects as blurring the visual and structural
> representation of the musical content in your code
… unless you use the edition-engraver. ;)
> maybe some of the experienced contributors can sketch a possible way to
> create this.
In the extreme, this featur
+1 for the edition-engraver,
but it's not possible to reflect the actual structure of connected
dynamics...
it's more a "tweak every single element" and because of the
"outsourcing" (which is great for the "redability" in many cases)
it's easy to loose the mind control about the musical struct
thanks David,
I guess I'm flogging a dead horse, at least until my understanding is
much deeper. I'm really grateful for your explanation though.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
musicus writes:
> +1 for the edition-engraver,
> but it's not possible to reflect the actual structure of connected
> dynamics...
> it's more a "tweak every single element" and because of the
> "outsourcing" (which is great for the "redability" in many cases)
> it's easy to loose the mind contro
Graham King writes:
> thanks David,
> I guess I'm flogging a dead horse,
More like an unborn horse.
> at least until my understanding is much deeper. I'm really grateful
> for your explanation though.
--
David Kastrup
___
lilypond-user mailing lis
Hi all,
I am so sorry, I pasted the wrong code in my first post... :-( Obviously the
function needs a second argument, and that's the correct code below:
\version "2.19.32"
autochord = #(define-music-function
(parser location chordDown chordUp)
(ly:music? ly:music?)
#{
<<
??? I just pasted the correct code and it appeared messed up again (the first
argument of the function is missing). This is the correct code:
http://kl1p.com/Ssse
Sorry but I really don't know what's happening...
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/breaking-c
Hello Gilberto,
> Le 18 déc. 2015 à 17:10, Gilberto Agostinho a
> écrit :
>
> ??? I just pasted the correct code and it appeared messed up again (the first
> argument of the function is missing). This is the correct code:
> http://kl1p.com/Ssse
Event that is very strange: there are missing bac
Hi all,
musicus wrote:
> +1 for the edition-engraver,
=)
> but it's not possible to reflect the actual structure of connected dynamics…
Oh, I agree: Just as there are \noBreak, \noBeam, etc., there should be general
\connect and \split options "between” arbitrary grobs. I just have no idea wha
Perfectly right in my opinion!
Of course, the current layout is already based on objects relative to
certain other objects (in other words: polar coordinates), but the
possibilities to tweak a position is mostly limited to basic
X-/Y-offsets to ONE specific object.
I think the ultimate goal o
Hi Jacques,
Jacques Menu-3 wrote
> Event that is very strange: there are missing backslashes…?
How annoying... so it seems that the website I used to paste the code takes
two backlashes and transform them into one
As for the problem here with Nabble is that if you have "<" + "a" without
any
20 matches
Mail list logo
