Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern

2010-08-09 Thread lilypond
Updates: Status: Verified Comment #10 on issue 1083 by brownian.box: subdivideBeams fails at the beginning of a pattern http://code.google.com/p/lilypond/issues/detail?id=1083 Thank you. convert-ly produces: [...] Not smart enough to convert beatLength. Use baseMoment and beatStruct

Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern

2010-08-09 Thread lilypond
Comment #9 on issue 1083 by percival.music.ca: subdivideBeams fails at the beginning of a pattern http://code.google.com/p/lilypond/issues/detail?id=1083 IIRC this is a non-convert-ly'd syntax change. Running convert-ly on an old file should produce a warning, but it will not update the sy

Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern

2010-08-09 Thread lilypond
Comment #8 on issue 1083 by tdanielsmusic: subdivideBeams fails at the beginning of a pattern http://code.google.com/p/lilypond/issues/detail?id=1083 Carl's patch changed the syntax. Instead of beatLength we must now use baseMoment. If you convert the minimal example with convert-ly you s

Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern

2010-08-09 Thread lilypond
Comment #7 on issue 1083 by brownian.box: subdivideBeams fails at the beginning of a pattern http://code.google.com/p/lilypond/issues/detail?id=1083 2.13.29 says: warning: cannot find property type-check for `beatLength' (translation-type?). perhaps a typing error? warning: doing assignm

Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern

2010-07-18 Thread lilypond
Updates: Status: Fixed Labels: fixed_2_13_29 Comment #6 on issue 1083 by Carl.D.Sorensen: subdivideBeams fails at the beginning of a pattern http://code.google.com/p/lilypond/issues/detail?id=1083 (No comment was entered for this change.)

Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern

2010-06-19 Thread lilypond
Updates: Owner: Carl.D.Sorensen Comment #5 on issue 1083 by Carl.D.Sorensen: subdivideBeams fails at the beginning of a pattern http://code.google.com/p/lilypond/issues/detail?id=1083 (No comment was entered for this change.) ___ bug-lilyp

Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern

2010-06-19 Thread lilypond
Updates: Status: Started Comment #4 on issue 1083 by Carl.D.Sorensen: subdivideBeams fails at the beginning of a pattern http://code.google.com/p/lilypond/issues/detail?id=1083 This is fixed by the new autobeam patch. As soon as it's accepted, I'll mark this as fixed. _

Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern

2010-06-19 Thread lilypond
Updates: Cc: Carl.D.Sorensen Comment #3 on issue 1083 by joeneeman: subdivideBeams fails at the beginning of a pattern http://code.google.com/p/lilypond/issues/detail?id=1083 Actually, this has nothing to do with subdivideBeams, but rather with beatLength (and, AFAICT, with the way

Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern

2010-05-13 Thread lilypond
Comment #2 on issue 1083 by Carl.D.Sorensen: subdivideBeams fails at the beginning of a pattern http://code.google.com/p/lilypond/issues/detail?id=1083 See also http://lists.gnu.org/archive/html/lilypond-user/2010-05/msg00122.html ___ bug-lil

Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern

2010-05-11 Thread lilypond
Updates: Labels: -Priority-Low Priority-Critical Regression Comment #1 on issue 1083 by pnorcks: subdivideBeams fails at the beginning of a pattern http://code.google.com/p/lilypond/issues/detail?id=1083 This behavior broke between 2.10 and 2.12, so it will block 2.14. _

Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern

2010-05-10 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Low New issue 1083 by pnorcks: subdivideBeams fails at the beginning of a pattern http://code.google.com/p/lilypond/issues/detail?id=1083 http://lists.gnu.org/archive/html/bug-lilypond/2010-05/msg00107.html % workaround: use \override