RE: musicxml2ly enhancements

[Curt McDowell]

How about allowing bar numbers as a letter+number, parsed similar to musical 
note+duration:
        B78 a,4 ( a4 ) ( b4 ) d4 |
        B79 e,4 ( f4 ) ( g4 ) a4 |
Perhaps they could also double as bar checks:
        B78 a,4 ( a4 ) ( b4 ) d4
        B79 e,4 ( f4 ) ( g4 ) a4
Or alternately, augment the existing bar check to allow an optional value:
        a,4 ( a4 ) ( b4 ) d4 |78
        e,4 ( f4 ) ( g4 ) a4 |79
Or (to taste):
        |78  a,4 ( a4 ) ( b4 ) d4
        |79  e,4 ( f4 ) ( g4 ) a4
The actual bar numbers might be ignored initially, but eventually 
- they might be the numbers printed
- bar checks might also verify that bar numbers match across staves, voices, 
\alternatives.

Having already entered some large pieces, I only recently discovered 
Frescobaldi. What a wonderful program. The point-and-click cursor matching 
between source and PDF nearly obviates the need for measure numbers. I wish I'd 
found it sooner!

Cheers,
-Curt

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Urs Liska
Sent: Tuesday, April 09, 2013 4:26 AM
To: address@hidden
Subject: Re: musicxml2ly enhancements

Am 09.04.2013 13:19, schrieb Janek Warchoł:
> 2013/4/9 Werner LEMBERG <address@hidden>:
>>> Putting the bar number at the start of the line would require
>>>
>>>    %{ 5 %} a,4 ( a4 ) ( b4 ) d4 |
>>>
>>> instead.
>> I like that.  It's tedious to type manually, but a computer program 
>> doesn't know that word :-)
> Indeed, but i find it unreadable, especially if it was placed at every line.
> I think that the best way to mark bar numbers in source is to make a 
> separate-line comment every 5 or so measures:
>
>>      \clef "treble" \key c \major \numericTimeSignature \time 4/4
>>      a4 ( a4) ( b4 ) d4 |
>>      \key c \major a4 ( a4 ) ( b4 ) d4 |
>>      a4 ( a4 ) ( b4 ) d4 |
>>      g1 |
>>      % m.5
>>      a,4 ( a4 ) ( b4 ) d4 |
>>      g1 |
>>      a,4 ( a4 ) ( b4 ) d4 |
>>      g1 |
>>      a,4 ( a4 ) ( b4 ) d4 |
>>      % m.10
>>      g1 |
>>      a,4 ( a4 ) ( b4 ) d4 |
> etc.
> Janek
I have come to the conclusion that it is a _very_ good idea to make a measure 
number for _every_ measure.
That way you have a measure indicator in each Git diff.
Which proves useful to map the change to the location in the file if the line 
numbers have changed considerably in the meantime.

Urs
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user


_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user