Slow Down
I am using r2908 nightly on a Windows XP machine. I am inputting a full concert band score (with parts for flute, 2 clarinets, alto/tenor/bari saxes, 2 trumpets, F horn, trombone, tuba, snare drum, bass drum, and cymbal), and the more I input, the slower things seem to run. It's as if the program is bogging down, and I haven't seen this on any previous version of MuseScore.
Comments
Please attach the score that is acting slow for you.
Here is the copy of the score that causes the slow down. I haven't tried it on the latest nightly yet.
When does it slow down for you? I tried added notes and it affect was immediate.
I was seeing it most when doing a control-arrow octave transpose, and adding dynamics and articulations. Strangely on the latest nightly, I'm not seeing it anymore. Seems to be working fine now.
My muse score program is inoperable, almost. I have version 1.1 with windows XP and what I think is some kind of Athlon processor in my computer (over three years old--never had a problem before, but this is the biggest composition I've worked on.) The difficulty I'm having has to do with note entry, rests, etc. For instance, a note entered may play for several seconds. Everything must be waited for, even saving is a longer than usual, though not as intolerable as note entry. Playback, however, is fine (occasional static, blue line late in following the score[or maybe early?], and a brief skip, maybe. saving as a .wav file, though, is a long wait, though it sounds fine once it's done.)
In reply to Slow program--what can be done? by Stefanokud
more like a slow computer.
Regards,
In reply to I don't think what you are describing is a slow program, by xavierjazz
I hit this thread with a search for 'slow input'. I have the same problem as described by Stephen M. Kudlo. I've created a multi-instrument score that's now more than 200 bars long. Input (from a MIDI keyboard) has rallentando'd to a crawl. If I play a three note chord it takes a full second for each note to register. Really a painful experience. Then I read your "more like a slow computer" comment.
Well, my computer is a fairly expensive, fast job so I did a simple scientific experiment. I left the big score still open and created another new score, with just 32 bars and a piano staff. With this I can play chords in real time on the MIDI keyboard and the program just laps up the input like lightning. It seems MuseScore operates by revisiting almost the entire existing score every time a new note is input (look what happens if you change a key signature to see the way the program responds to a change). This is bound to mean the input slows down as a score grows bigger.
MuseScore is wonderful in many ways, but I've commented elsewhere that the MuseScore experience would be vastly improved if there were a separate interface for note and lyric input that holds reasonably steady on the screen till you press a "now go ahead and format it" button. The near snail's pace input that comes along with lengthy or large scores would also be obviated with separate input and format/edit interfaces.
In reply to No, it's not the computer that's slow; it's the software. by FrankO
Thanks for sharing your experiences. Its indeed true that MuseScore needs performance improvements for inputting large scores. The MuseScore 2.0 release will come already with some improvements but it is an ongoing effort, as MuseScore is step by step reaching out to more professional users.
In reply to No, it's not the computer that's slow; it's the software. by FrankO
Less a solution but more a work-around, could you break your score into sections/movements and put them in different files? The separate files wouldn't be as big, and then you could either print them as separate sections/movements or piece them together when your done.
In reply to Work-Around by newsome
Great suggestion: thanks a lot
I did replace my computer with a newer model (Windows 7, with an E6700 Intel Pentium Processor $300.00.) Musecore works fine now. By the way, in the interim, I downloaded a demo of a less expensive version of Sibelius, which musescore resembles, and it did not have as many available staves. I couldn't tell if it was slow though.--Steve.
I revisited my old score , and it's still very slow with 2.0, though not as slow as before . Makes for difficult composition of large orchestra scores , though I will withhold judgment till I try it with 2.2.
In reply to I revisited my old score , by Stefanokud
Be sure not to generate parts until you're done; that makes a big difference. There really have not been any major changes that should affect performance. It is something being considered for the future though.