Re: LSR is not at the stable release level

Eluze wrote > it's a shame - the LSR still works with an old stable version (actual > stable is 2.16.0, LSR is 2.14.2) > > this means > > - new snippets using newer functions can't be added > - old snippets must be convert.ly-ed before you can use them in the stable > release > > is there a way

LSR is not at the stable release level

it's a shame - the LSR still works with an old stable version (actual stable is 2.16.0, LSR is 2.14.2) this means - new snippets using newer functions can't be added - old snippets must be convert.ly-ed before you can use them in the stable release is there a way to improve this? Eluze -- V

Re: [musicxml2ly] unwanted staves and voices [was: missing -element in chorded note leads to unwanted additional staff]

Sorry, this is killing me. :( Am 29.09.2012 um 13:19 schrieb pls: > > Am 28.09.2012 um 12:09 schrieb pls: > >> A -element containing a - and a -element but no >> -element causes an additional empty staff above the defined one. >> >> Tiny example: >> >> >> (unwanted) result: >> >> >> The w

Re: [musicxml2ly] unwanted staves and voices [was: missing -element in chorded note leads to unwanted additional staff]

Am 28.09.2012 um 12:09 schrieb pls: > A -element containing a - and a -element but no > -element causes an additional empty staff above the defined one. > > Tiny example: > > > (unwanted) result: > > > The wrong MusicXML-markup was caused by Sibelius 7.0.0. > > In this case musicxml2ly pu