consistent segfault creating large score 0.9.5 svn
OS= Gentoo linux
when trying to create a large score using the wizard, i get a consistent segfault, and the app crashes.
Paper Size = A3, or A2.
Instrument set
piccolo
flute1
flute2
alto flute
oboe1
oboe2
english horn
clarinet1
clarinet2
bass clarinet
bassoon1
bassoon2
contrabassoon
horn1
horn2
horn3
horn4
trumpet1
trumpet2
trumpet3
trombone1
trombone2
bass trombone
tuba
tympani
percussion
harp
piano
1stviolins
2ndviolins
violas
cellos
contrabasses
I seem to get as far as the 1st trombone using the paper sizes described above, and the whole lot crashes.
This used to happen back in 0.8 days,and it was fixed, so maybe something went awry since then.
My default paper size is A3
I'm not interested in condensing similar instruments into 1 stave and using voices. That may be your preffered method of working, but it's not mine, so don't bother suggesting it.
Alex.
p.s. any news on the jackmidi implementation?
Comments
I dare to suggest a workaround.
Select A4 and reduce the scaling in Layout->page settings ?
In reply to Suggestion by [DELETED] 5
And what will this achieve in terms of visibility. and day in day out usage?
In reply to ? by alex stone
Does this actually avoid the crash for you? If so then you could save as PDF and then print to A3 or A2 from the PDF reader. At least on Windows Adobe PDF reader gives the option to expand or shrink to any page size.
In reply to Does this actually avoid the by David Bolton
It might deal with the problem if i'd written any notes in the first place. As the first post says, this is at the beginning of the process, setting up a full template, using the wizard. It's the same crash with the manual addition of instruments.
And i'd ask the question of anyone who suggested i condense a full score to A4 size, then embark on a zooming saga to write with.
Why?
In reply to visibility by alex stone
Suggesting a workaround doesn't mean we deny the existence of a problem or bug. Lasconic and I were just trying to help. The purpose of workaround is to allow you to continue your work until a bug is fixed.
I can't actually reproduce the crash in r.1987 (Windows XP). What revision number are you using? There was a bug in the prereleases around r.1860. See http://www.musescore.org/en/node/1827
In reply to I can't actually reproduce by David Bolton
It may not have been clear in the first post, but i'm using the svn version. I've just thrown out the existing .ini file and updated to 1992.
Same crash.
I'm pleased it works for you chaps on windows. I guess this means as a bug report it's null and void.
Just a bit of a challenge on my linux build at the moment.
Very busy at the moment, so i'll shelve this, and have another look in further down the road, if i have the time to do so.