Re: midi2ly failure

2012-12-18 Thread Ben Rudiak-Gould
I rewrote midi.c in Python and tested it on the largest midi file in IMSLP [1]. On my laptop it takes about 200 ms instead of 50 ms to load the file, but that's a small fraction of midi2ly's four-second runtime, and there are a lot of optimizations that can be done in midi2ly itself. (For example,

Re: midi2ly failure

2012-12-17 Thread Ben Rudiak-Gould
On Sat, Dec 15, 2012 at 11:07 PM, m...@mikesolomon.org wrote: > ImportError: > dlopen(/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so, > 2): no suitable image found. Did find: > > /Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/pytho

Re: Feature request: some way of manually breaking slurs, ties and lyric extenders

2012-12-16 Thread Ben Rudiak-Gould
I have hacked something up (see code below), but it doesn't work very well: * It works for slurs on either end as long as they span at least two notes. I can get it to work with single-note slurs at the end of the line by writing c'( s1*0) or c'( <>), but I get the warning "programming error: boun

Re: The end of a ligature bracket doesn't appear at the start of a line

2012-12-16 Thread Ben Rudiak-Gould
On Sun, Dec 16, 2012 at 12:31 AM, Eluze wrote: > http://www.lilypond.org/doc/v2.17/Documentation/notation/ancient-notation_002d_002dcommon-features#ligatures > > Known issues and warnings > > Ligatures need special spacing that has not yet been implemented. As a > result, there is too much space b

Re: Ligature brackets and suggested accidentals don't avoid each other well

2012-12-16 Thread Ben Rudiak-Gould
On Sun, Dec 16, 2012 at 12:42:16AM -0800, Eluze wrote: > here's a first tweak to improve the output: > > \override LigatureBracket.outside-staff-priority = #200 > \override AccidentalSuggestion.outside-staff-priority = #100 This is definitely an improvement, thanks. I also tried various values of

Ligature brackets and suggested accidentals don't avoid each other well

2012-12-15 Thread Ben Rudiak-Gould
% The flat symbol is unreasonably far above the note \version "2.17.8" { \set suggestAccidentals = ##t \[ a'2 bes' \] } (As a workaround, is there any way to make the brackets and accidentals not try to avoid each other at all? This seems to be the case with brackets and fermatas and it looks oka

The end of a ligature bracket doesn't appear at the start of a line

2012-12-15 Thread Ben Rudiak-Gould
% The end of the ligature bracket is not printed \version "2.17.8" { \[ c'1 \break d'1 \] } ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Feature request: some way of manually breaking slurs, ties and lyric extenders

2012-12-11 Thread Ben Rudiak-Gould
On Tue, Dec 11, 2012 at 2:11 PM, m...@mikesolomon.org wrote: > I'll be able to work on it in 2026 - if someone wants it done before then, I > can give pointers! Unless someone with more experience volunteers I'll try to hack together a Scheme proof of concept this weekend. I would definitely lik

Re: Feature request: some way of manually breaking slurs, ties and lyric extenders

2012-12-11 Thread Ben Rudiak-Gould
On Mon, Dec 10, 2012 at 10:59 PM, m...@mikesolomon.org wrote: > The website says that the file cannot be accessed for copyright reasons. > Could you post a public-domain score on a site that can be accessed by any > user? It must be restricted by country since I can view it without any special

Feature request: some way of manually breaking slurs, ties and lyric extenders

2012-12-10 Thread Ben Rudiak-Gould
I'd like to set rounds/catches in a part-parallel format, as seen here, for example: http://hdl.handle.net/2027/wu.89008759938?urlappend=%3Bseq=81 This format is standard in books of rounds/catches at least back to the 1800s, and it has obvious advantages (essentially the same as the advantag

Crash moving voice into Devnull context

2012-12-08 Thread Ben Rudiak-Gould
% This crashes with a null pointer access: \version "2.16.1" << \new Devnull = "a" { s } \new Staff { c' \change Staff = "a" c' } >> ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Funny alignment of different bar lines at the end of a system

2012-11-28 Thread Ben Rudiak-Gould
% The bar line in the upper staff is not flush right and probably should be \version "2.16.1" << { c'1 } { c'1 \set Staff.whichBar = "||" } >> ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

\RemoveEmptyStaves in StaffGroup context crashes

2012-11-28 Thread Ben Rudiak-Gould
% This crashes with a stack overflow (at least on the official Windows build): \version "2.16.1" \new StaffGroup \with \RemoveEmptyStaves { c' } ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Bugs with \set Staff.whichBar

2012-11-26 Thread Ben Rudiak-Gould
hichBar = "||" c' c' c' c' c' c' c' } >> On Sat, Nov 24, 2012 at 3:56 PM, Colin Hall wrote: > > On Sat, Nov 24, 2012 at 10:13:25PM +, Ben Rudiak-Gould wrote: >> The 2.16 documentation says that \set Staff.whichBar = "|:&quo

Bugs with \set Staff.whichBar

2012-11-24 Thread Ben Rudiak-Gould
The 2.16 documentation says that \set Staff.whichBar = "|:" "will create a start-repeat bar in this staff only". What it actually seems to do in 2.16.1 is insert a start-repeat bar after every note in that staff until the end of the score. I haven't looked at the code but I guess that it's clearing