|
From: | Urs Liska |
Subject: | Re: figured bass in staff context |
Date: | Sun, 08 Mar 2020 16:46:48 +0100 |
User-agent: | Evolution 3.34.1-4 |
Hi Derek, great to see you took immediate action (both in terms of that file and for subscribing) :-) Well, the remainder of my comments has been short-circuited by Lukas ;-), and I'm happy to see that also someone else has laready chimed in (to prove my point of the helpful community ...) One additional tip is also about code layout: It is usually a good idea to write only one measure per line, which improves readability and also will greatly improve the "targetting" of Git commits, like so: left = \relative c { \global a cis e | a8. b16 a8 | e cis e a16 b cis8 r8 | a, cis e | a8. b16 a8 Or even more extreme, giving generous space to make stuff even more readable. Note that at one point I start to add barnumber comments, which is of course not necessary but may be taken as an additional reading aid. Another useful pattern is spelling out all groups over indented lines as I did with the tuplets (although in such short snippets it may be skipped). | e cis e a16 b cis8 r8 | gis a dis,_"(a)" | %8 e4 e,8 gis'8 | %9 a gis \tuplet 2/3 { fis8 e } | Best, and have fun (and hopefully not too much obstacles) Urs Am Sonntag, den 08.03.2020, 14:43 +0100 schrieb Derek Remeš:
|
[Prev in Thread] | Current Thread | [Next in Thread] |