[jmsl] LilyPond issues

[jmsl at music.columbia.edu]

    Thank you, Nick, for helping track down this simple problem.  The score
now looks great!

Best,
J Starpoli


On 3/25/08 3:19 PM, "jmsl at music.columbia.edu" <jmsl at music.columbia.edu>
wrote:

> J Starpoli  provided me with an example score that showed the LilyPond
> layout problem. Unbalanced start/end repeats were the culprit. I have
> created a Score Operator which will check a score for this problem.
> JMSL's LilyPond exporter calls it automatically and generates a warning
> if it finds a problem.
> Thanks J!
> Nick Didkovsky
> 
> jmsl at music.columbia.edu wrote:
>> Hello J Starpoli
>> 
>> The LilyPond exporter is one area where I tend to discover little
>> problems and add fixes & tweaks here and there. For example, most
>> recently I was made aware that LilyPond does not handle more than one
>> text mark per measure, which spurred me to rewrite the #repeats
>> indication symbol, and that fixed some text justification problems. So
>> there are a number little fixes in my prerelease that you are welcome
>> to try out. Contact me off list and I will send it to you if you like.
>> 
>> But your issues sound far more extreme.  There are two things I know
>> of that can cause truly crazed layout by LilyPond:
>> 1) If you have unmatched repeat bars (for example, if a measure has an
>> end repeat bar but not a start repeat bar). All bets are off on this
>> one. LilyPond goes nuts. I should check for and generate a warning for
>> this issue.
>> 2) If measures do not have the right sum of durations in them.  A
>> staff in a measure should either be empty (in which case the exporter
>> will substitute a measure rest), or contain exactly the right total
>> durations.  If you export to LilyPond with this problem, it will
>> generate a warning. You can check you score first with the menu item
>> "Score" -> "Check all measure durations". This will generate a report
>> in a new window which you can follow to fix the score.
>> 
>> So my questions for you are:
>> 1) Did you check your score for correct durations in each measure?
>> 2) Are you using repeats and if so, are they matched?
>> 3) Can you send me a problematic score offlist so I can inspect it? If
>> you contact me off list I will let you know how to best send it to me.
>> 
>> Thanks
>> Nick Didkovsky
>> 
>> jmsl at music.columbia.edu wrote:
>>> Hi List,
>>>     I have been making much use of the LilyPond export feature since
>>> it was
>>> recently added to JScore.  Lately, however, I am experiencing
>>> increasingly
>>> frustrating results converting my scores, which do utilize a good
>>> deal of
>>> dynamics, marks, and text comments.  At first, I was able to glean a
>>> couple
>>> of tips from the LilyPond manual to correct certain global layout
>>> issues,
>>> but my latest score has measures printing in reverse order, barlines
>>> in the
>>> middle of nowhere, etc.  I have checked for measure duration errors,
>>> "contiguous tempi" and the like, but so far this has not helped.  I
>>> am not
>>> even sure if I should direct this post here or to the LilyPond list,
>>> but my
>>> programming skills are not advanced enough to fully inspect the .ly
>>> files
>>> that Jscore outputs.  I don't want to have to go back to cutting and
>>> pasting
>>> screen shots of Jscore (it didn't look nearly as professional), but I am
>>> limited to free- and shareware.  Any suggestions will be greatly
>>> appreciated.
>>> 
>>> Thanks,
>>> J Starpoli
>>> 
>>> 
>>> _______________________________________________
>>> jmsl mailing list
>>> jmsl at music.columbia.edu
>>> http://music.columbia.edu/mailman/listinfo/jmsl
>>>   
>> _______________________________________________
>> jmsl mailing list
>> jmsl at music.columbia.edu
>> http://music.columbia.edu/mailman/listinfo/jmsl
> _______________________________________________
> jmsl mailing list
> jmsl at music.columbia.edu
> http://music.columbia.edu/mailman/listinfo/jmsl