MuseScore with MDL has long startup
I install MDL and now musescore take up to 40 seconds to show the main window.
if uninstall MDL its only up on 3 o 4 seconds. I suppose it is due to the loading of samples.
Maybe, this task should be run in background (if possible).
Console output:
ragnarok@ragnarok:/tmp$ musescore
initScoreFonts 0x55c60b34c190
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
SfzRegion: unknown opcode
libpng warning: iCCP: known incorrect sRGB profile
QString::arg: Argument missing: 961 Kb, 539.08
QString::arg: Argument missing: 961 Kb, 501.71
QString::arg: Argument missing: 961 Kb, 401.91
QString::arg: Argument missing: 961 Kb, 0.31
QString::arg: Argument missing: 961 Kb, 92.96
QString::arg: Argument missing: 961 Kb, 401.33
QString::arg: Argument missing: 961 Kb, 93.28
QString::arg: Argument missing: 961 Kb, 58.05
QString::arg: Argument missing: 961 Kb, 118.14
QString::arg: Argument missing: 961 Kb, 517.67
QString::arg: Argument missing: 961 Kb, 539.43
QString::arg: Argument missing: 961 Kb, 520.72
QString::arg: Argument missing: 961 Kb, 319.76
QString::arg: Argument missing: 961 Kb, 495.24
QString::arg: Argument missing: 961 Kb, 521.00
QString::arg: Argument missing: 961 Kb, 438.63
QString::arg: Argument missing: 961 Kb, 490.06
QString::arg: Argument missing: 961 Kb, 7.41
QString::arg: Argument missing: 961 Kb, 377.41
QString::arg: Argument missing: 961 Kb, 320.74
QString::arg: Argument missing: 961 Kb, 223.86
QString::arg: Argument missing: 961 Kb, 220.71
QString::arg: Argument missing: 961 Kb, 485.98
QString::arg: Argument missing: 961 Kb, 498.75
QString::arg: Argument missing: 961 Kb, 541.71
QString::arg: Argument missing: 961 Kb, 142.15
QString::arg: Argument missing: 961 Kb, 544.76
QString::arg: Argument missing: 961 Kb, 535.93
QString::arg: Argument missing: 961 Kb, 231.50
QString::arg: Argument missing: 961 Kb, 13.67
QString::arg: Argument missing: 961 Kb, 95.17
QString::arg: Argument missing: 961 Kb, 491.11
QString::arg: Argument missing: 961 Kb, 273.97
QString::arg: Argument missing: 961 Kb, 75.04
QString::arg: Argument missing: 961 Kb, 1.17
QString::arg: Argument missing: 961 Kb, 530.15
QString::arg: Argument missing: 961 Kb, 418.66
QString::arg: Argument missing: 961 Kb, 29.19
QString::arg: Argument missing: 961 Kb, 0.35
QString::arg: Argument missing: 961 Kb, 361.88
QString::arg: Argument missing: 961 Kb, 194.91
QString::arg: Argument missing: 961 Kb, 24.45
QString::arg: Argument missing: 961 Kb, 2.88
QString::arg: Argument missing: 961 Kb, 46.19
QString::arg: Argument missing: 961 Kb, 418.16
QString::arg: Argument missing: 961 Kb, 539.38
QString::arg: Argument missing: 961 Kb, 0.27
QString::arg: Argument missing: 961 Kb, 522.31
QString::arg: Argument missing: 961 Kb, 337.96
QString::arg: Argument missing: 961 Kb, 525.58
QString::arg: Argument missing: 961 Kb, 404.98
QString::arg: Argument missing: 961 Kb, 507.08
QString::arg: Argument missing: 961 Kb, 394.03
QString::arg: Argument missing: 961 Kb, 391.17
QString::arg: Argument missing: 961 Kb, 118.16
QString::arg: Argument missing: 961 Kb, 307.76
QString::arg: Argument missing: 961 Kb, 494.36
QString::arg: Argument missing: 961 Kb, 78.11
QString::arg: Argument missing: 961 Kb, 109.73
QString::arg: Argument missing: 961 Kb, 414.88
QString::arg: Argument missing: 961 Kb, 10.55
QString::arg: Argument missing: 961 Kb, 466.29
QString::arg: Argument missing: 961 Kb, 290.41
QString::arg: Argument missing: 961 Kb, 313.37
QXcbConnection: XCB error: 3 (BadWindow), sequence: 2810, resource id: 12364790, major code: 40 (TranslateCoords), minor code: 0
Comments
See #270748: [Regression] Playback slow to engage
No, that is a different issue, this here is about startup time, not the delay until you can start playback, that other one is in #289893: Playback initialization problem, delay until playback starts, with SF3 soundfonts
Yes, of course! But I still seem to remember this issue as well?
In reply to Yes, of course! But I still… by Louis Cloete
Unpacking sf3 sounds makes starting playback not possible for a time after starting MuseScore, but MDL doesn't use sf3. I think that's what you remember Louis.
In reply to No, that is a different issue by Jojo-Schmitz
Exactly, i'm talk about the delay time to take from exec the command and show the main window
thanks!
In reply to Exactly, i'm talk about the… by Ragnarok Toledo
Loading the sound files used by MDL takes time because they are large. Computers like mine, and maybe yours, are very slow loading. I don't have MDL loaded on my computer because I rarely would use it and I don't want to wait an entire minute or more to load MDL every time I start MuseScore, especially when I'm helping trouble shoot and purposely crash the program.
Relates to #297854: [EPIC] MDL issues
Still an issue, came up again inhttps://musescore.org/de/node/321059