Playback causes crash once the View>Synthesiser window has been opened and closed
On Windows 7 computer, playback causes a crash once the View>Synthsiser window has been opened and closed:
Run Beta 2 with "-F" factory settings on Windows 7 computer
Create a simple new score with a few measures of a single voice
Playback works OK
Now open the synthesiser window with View>Synthesiser, then close the window
MuseScore now always crashes after playing back the first measure
May be related to:
On WindowsXP computer View>Synthsiser window content is solid black.
Comments
I just tried a completely "clean" re-installation:
Uninstalled MuseScore2
Deleted folder and contents C:\Users\\AppData\Roaming\MuseScore\
Deleted folder and contents C:\Users\\AppData\Local\MuseScore\
Downloaded and installed MuseScore2 Beta 2 from:
http://musescore.org/en/download/musescore-2.0-beta.msi
Problem remains!
Can you try again with the current nightly build? It's possible a bug fixed since then might be responsible.
I can't reproduce, following these very steps, so there got to be something else going on
Exactly the same with: MuseScoreNightly-2015-01-02-1509-f471d31.7z
Strange. Since you mention running with "-F", does that mean you are running from a comand prompt / terminal window? If so, is there any interesting output there? I don't suppose anyone knows how to get a stack trace for a crashed application on Windows?
Anything special in the subdirectories of C:\Users\USERNAME\Documents\MuseScore2\ (for Beta) or C:\Users\USERNAME\Documents\MuseScoreDevelopment (for nightly)?
Like some special soundfont (I believe you mentioned something like this elsewhere)?
I can't reproduce on Windows7 with the same Nightly.
@steveeh: Can you try to open this Nightly, instead the "Bin" file", via "Special File",
and then opening via "RevertToFactorySettings" command file.
Exactly the same when run from "revertToFactorySettings"
Further details:
View>Synthesiser>Zerberus tab: OK
View>Synthesiser>Master effects tab: Crash immediately
View>Synthesiser>Tuning tab: Crash immediately
If the Synthesiser window is simply opened and closed, adding a note will crash the programme. (I have "Play notes when editing" enabled)
I don't know whether this is related, but on my WindowsXP computer I get no crash, just a blank (black content) Synthesiser window. This was also reported by another user on his Windows 8.1 computer.
Install on removable media (USB key)?
This could narrow down the problem to the setting of the PC (sound card / Antivirus & C.)?
Just as a reminder, Beta 1 runs fine on the same Windows XP and Windows 7 computers.
I notice that a "Play metronome during playback" switch and slider have been added to the Synthesiser window between the two versions. Could that be relevant?
Could you please report in detail the precise steps to reproduce this issue:
1)
2)
3)
4)
etc.
What you do exactly (in mode N or not, and so on)
With an attached score and screenshots, step by step, better even... Thanks.
Since this only seems to affect your system, it is likely going to require you to do some additional detective work to help track this down. In particular, you could start installing nightly builds - say, starting from half-way between beta 1 and beta 2 - to find out at what point the problem started. By continuing to pick halfway points, you can hopefully zero in on the commit that triggered the problem. Then we can look at the code and try to see if anything looks suspect. I know it's a pain, but until someone else can reproduce, I don't know what else to suggest. Except maybe if it's less of a pain for you to get a build environemtn going and build it yourself then run under the debugger, which will let you see exactly where the crash occurs and then you can report that. Or, at least, as I suggested earlier, see if you can figure out how to get a crash log.
Building it yourself would get you a stack trace, which should give the hint where it crashes
OK - precise steps:
1) Uninstall MuseScore 2 Beta 2
2) Delete folder C:\Users\\AppData\Roaming\MuseScore\
3) Delete folder C:\Users\\AppData\Local\MuseScore\
4) Download and extract MuseScoreNightly-2015-01-02-1509-f471d31.7z
5) Run "revertToFactorySettings" batch file
6) See "Nightly Build" cymbal splash screen
7) See "Start Centre" window
8) Click "Create new score"
9) Click "Next" (leaving title etc blank)
10) Click Treble Clef
11) Click "Next" (Default key signature C)
12) Click "Finish" (Default time signature 4/4)
13) "Create New Score" window closes
14) In Main window click View>Synthesiser
15) Synthesiser window opens
16) Click "Master effects" tab (or "Tuning tab")
17) Synthesiser window greyed out
18) OS error window opens: "nightly.exe has stopped working"
Alternatively, after 15)
16) Close Synthesiser window
17) Click "note entry" symbol
18) Drop crotchet anywhere on staff
19) OS error window opens: "nightly.exe has stopped working"
I'll try my best to help, but please note I'm no computer expert, and we're about at the limit of my knowledge!!
If I try Marc's suggestion of a "binary search" on nightly builds, where do I find the complete archive, and which would be the first version with changes from Beta 1?
"If I try Marc's suggestion of a "binary search" on nightly builds, where do I find the complete archive, and which would be the first version with changes from Beta 1?"
Can anyone point me to an archive of nightly builds?
Steve
these?
http://musescore.org/en/developers-handbook/compilation
Maybe this is my lack of understanding, but I don't see an archive of nightly builds at that link. I was expecting to see a long list of .7z files of the form:
MuseScoreNightly-2015-01-02-2007-f78aca0.7z
???
Steve
Indeed. I believe there is none, except maybe some private archive
@Steveeh, have patience, the only list that I know is the ordinary: http://musescore.org/en/download#Nightly-versions
Does this still happen after Werner's change in commit f22515c0e ?
Werner's change in commit f22515c0e solved the problem!
I wasn't sure what the formal procedure was for changing the status of an Issue; do I need to do it as the originator of the Issue?
Either you or the person having fixed it. Or anyone else :-)
Automatically closed -- issue fixed for 2 weeks with no activity.