|Subject:||Re: 2.13.40 regtests|
|Date:||Tue, 30 Nov 2010 20:44:56 -0000|
"Phil Holmes" <address@hidden> wrote in message news:address@hiddenI think the best bet is that I'll knock something up and run it over .41 when it arrives. We can then see whether it's of use before working out whether and how to progress it.Done this - comparing .39 with .40. I did a pixel-by-pixel comparison, allowing a leeway of 1 in pixel brightness (range is 0 to 255) before flagging an error. My program took about 30 minutes to run, plus about an hour for LilyPond to create the files. Don't think it's worth bothering to optimise it further. The only "trickery" I had to use was to exclude the bottom 44 pixels from the comparison, to avoid the "Music engraving by LilyPond" version number flagging a change. I tried to find how to stop this from being generated from the command line and failed, but if anyone does know....It identified 21 files with changes. 9 were vertical spacing changes, one quite a bad near collision in 39 corrected in 40. 5 were annotated page spacing pages. 4 were probable false alarms, but worth a quick look at. One was the figured bass correction, another the deliberate spacing variation page and one was something else I can't remember.Would anyone like me to put together a web page with them all on, to see if it could be useful?
Now completed some updates to this. It now works properly as a multi-threaded version, so it runs the lot in about 30 minutes elapsed. It rings differences where there are less than 10 pixels different. It crops the output files. It works properly with multi-page output, identifying where one regtest generates more pages than others, and also identifies where no output is generated at all (i.e. midi-only regtests). I'm quite pleased with it. Waiting for .41 to see if it shows anything of interest.
-- Phil Holmes Bug Squad
|[Prev in Thread]||Current Thread||[Next in Thread]|