Open NowaNowa-2 opened 1 week ago
I have opened the file. Seems to be a pretty ordinary empty orchestral score - only 38 bars, no notes, although there are a bunch of hidden staves. i don't experience any particular issues opening it or navigating it or entering notes etc. Is there some specific series of steps we should follow in order to see a problem occur?
I have opened the file. Seems to be a pretty ordinary empty orchestral score - only 38 bars, no notes, although there are a bunch of hidden staves. i don't experience any particular issues opening it or navigating it or entering notes etc. Is there some specific series of steps we should follow in order to see a problem occur?
In terms of the hidden staves yes that's intended, because I use this score for film etc.
For me, this problem of it slowing down happens almost immediately upon opening the score. My laptop goes starts saying "Not Responding", so I don't really know what's going on.
I also haven't been able to reproduce any sort of issue with the score
@cbjeukendrup could you take a look at the diagnostic files when you get a chance?
@NowaNowa-2 Might be helpful to know your device specs
Heya,
Here are my device specs
Processor AMD A4-9120e RADEON R3, 4 COMPUTE CORES 2C+2G 1.50 GHz Installed RAM 4.00 GB (3.83 GB usable) System type 64-bit operating system, x64-based processor Windows 10
It's old, but again, 4.4.0 works perfectly fine so idk what is wrong there :/
If theres anythin else I need to include lmk.
In one of the log files, I see many messages like
2024-10-29T21:55:41.362 | INFO | 5016 | MuseSamplerWrapper::initSampler | Successfully initialized sampler, sampleRate: 44100, blockSize: 1024
over a time span of more than a minute. That would suggest that the initialisation of Muse Sounds for all staves is taking a lot of time. After that, the mixer was opened, and there is 30 seconds between the open action was initiated and the usual QML warnings appear, suggesting that the whole system has slowed down very significantly.
The other log files don't seem to show anything remarkable.
@NowaNowa-2 It surprises me that MuseScore is usable at all with 4GB RAM, but if 4.4.0 is, then 4.4.3 should be too, so we'll try to sort this out.
It might also be useful if you could run 4.4.0, 4.4.1, and 4.4.2, to determine in which version exactly the slowdowns started. Those versions can be downloaded from https://github.com/musescore/MuseScore/releases. You might want to use the .paf.exe versions instead of the .msi versions, because the .paf.exe doesn't need installation. (I believe that sometimes trying to install an older version of already-installed software causes problems, with MSI installers.) If you could also upload the diagnostic files of these versions, so that we can compare, that would be extra helpful. Thanks in advance!
Alrighty will do, I'll keep you posted.
Alrighty, 4.4.2 was where it was at it's worst, it slowed down incredibly badly 4.4.1 was where it started I think. Anyway here's the diagnostic files
MuseScore Diagnostics 4.4.0.zip MuseScore Diagnostics 4.4.1.zip MuseScore Diagnostics 4.4.2.zip
Issue type
Opening/saving issue
Description with steps to reproduce
Current behaviour: MuseScore is unusable because of how slow it becomes.
Supporting files, videos and screenshots
MuseScore_Diagnostics.zip Link to the score that slows down my laptop: https://drive.google.com/file/d/1vg1XuNGM_z_oVmbZctjpVrmpAO8OVc6V/view?usp=sharing
What is the latest version of MuseScore Studio where this issue is present?
4.4.3
Regression
No.
Operating system
Windows 10
Additional context
This issue doesn't happen with 4.4.0, I am able to use that same empty score without experiencing this bad of a slowdown. By slowdown I am referring to my laptop slowing down while using 4.4.3, and not the actual score itself.
Checklist