On 08/25/2011 10:16 AM, Robert Schmaus wrote: > i.e. an environment where all tweaking can be done by very simple > statements like \break and such. Otherwise they would need to employ a > Professional LilyTweaker (career opportunities guys!).
Unfortunately, it's not just the ease of the code to make the tweak (although that is a major issue): as Kieran emphasized, it's the validation of the tweak -- checking that it's correct -- that makes it a real problem. In Finale you see straight away if it's right or wrong. In Lilypond you have to recompile each time. Again, scale that up across a 50-page score, and multiple rounds of recompiling to get each single custom tweak right, and you see the problem. Yes, you can work around it often by working on individual passages separate from the rest of the score, but it's still a major issue. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
