Crashing 3.6 - Guitar with linked TAB staff
Musescore 3.6 on Win 7
Keeps crashing while working on scores. In particular, Guitar with linked TAB staff.
Anyone else run into this?
Attachment | Size |
---|---|
Crashing Score.mscz | 8.25 KB |
Musescore 3.6 on Win 7
Keeps crashing while working on scores. In particular, Guitar with linked TAB staff.
Anyone else run into this?
Attachment | Size |
---|---|
Crashing Score.mscz | 8.25 KB |
Do you still have an unanswered question? Please log in first to post your question.
Comments
Better attach the score and someone will be able to take a look.
In reply to Better attach the score and… by Shoichi
done. thank you.
Maybe one of those in https://musescore.org/en/faq#faq-312352 ?
In reply to Maybe one of those in https:… by Jojo-Schmitz
Thank you.
But, it's not on start, it's while working on file. And possibly only when using this linked staff.
Doesn't crash here. What operations in particular makes it crash for you?
In reply to Doesn't crash here. What… by Jojo-Schmitz
Note input. Interesting. Maybe it's not playing nice with other open apps. hmmm.
EDIT: I tried with only Musescore open, still crashed. Only with linked staff. It did this with both 3.5 and 3.6
In reply to Note input. by Jon Garner
A me funziona benissimo (io uso Mac OS Catalina 10.15.5
In reply to A me funziona benissimo (io… by Claudio Riffero
I wish I was you then.
In reply to Note input. by Jon Garner
Again, what operations in particular make it crash.
You say note input. That's kind of general.
So... you open your attached file. and then what?
Please enumerate exact steps so someone here can replicate..
In reply to Again, what operations in… by Jm6stringer
Interesting. The last time it crashed is as follows. I enter note input mode. I select quarter note. I press the letter E. Fine. I move to next measure, I press A. All Good. I move to next measure, I press D. It crashes.
I don't open my attached file and then it crashes. It crashed while I was inputting notes. It has done this quite a few times recently. Musescore 2 never crashed on my machine.
thank you.
In reply to Interesting. The last time… by Jon Garner
You wrote:
I don't open my attached file and then it crashes.
What does this even mean?
In reply to You wrote: I don't open my… by Jm6stringer
jm6stringer: "So... you open your attached file. and then what?"
Me: I don't open my attached file and then it crashes. It crashed while I was inputting notes.
I'm just following you're thread. All good.
In reply to I'm just following you're… by Jon Garner
In order to begin investigating, we need precise steps. Like:
1) open score
2) click measre ????, staff ????
3) enter note input mode
4) press ????
We need to know the ????, and anything else relevant to allow us to reproduce the problem.
In reply to In order to begin… by Marc Sabatella
The exact sequence of the last crash is in a comment of mine above.
I am having a very similar issue, I was looking to see if any others were experiencing this. When working on guitar with both standard sheet and tabs attached to one another, I experience frequent crashes. This does not happen every time I do this, but the precise steps that causes it to crash are as follows:
(1) Input notes either through the standard sheet or tabs.
(2) Exit the note input mode.
(3) Select one of the previously input notes on either of the linked staves.
(4) Attempt to adjust the duration of the note through the number shortcuts.
After a crash like this has occurred, the score will frequently be listed as corrupted. I've included the sheet music of my most recent project where this is occuring.
In reply to I am having a very similar… by zestra12345
Sore is in coninuous view and contains a start repeat barline, so see #315529: MuseScore 3.6 crashes on open of a file with start repeat in continuous view and update to 3.6.1 to have that crash fixed
Edit: I take that back, score stems from 3.6.1
In reply to Sore is in coninuous view… by Jojo-Schmitz
There is something weird with attached score, "Peg"
I isolated the Electric guitar (keeping problematic measures, or 1 page)
A. With this excerpt: Electric3.mscz
1) Select the penultimate measure, both standard and Tab staff - > Copy-paste (or press"R") in the last measure
2) Select the last note eg in standard staff, C note -> press "5" to receive a quarter note
Result : crash
B. Other shorter excerpt: Electric4.mscz
1) Range selection: measure 2 to last measure (the only with notes)
2) Do: Ctrl + Del
Result: crash
In reply to There is something weird… by cadiz1
Thanks for the investigation.
This has happened to multiple different scores. And, on my install, only happens with the linked TAB staff.
So perhaps this is corrupting the score.
In reply to Thanks for the investigation… by Jon Garner
"This has happened to multiple different scores. And, on my install, only happens with the linked TAB staff.
So perhaps this is corrupting the score."
Please, we need you attach one of your "real" scores, (and not a part of the file you created specially, when opening this thread, "Crashing Score")
There may be a few different reasons for a crash to occur. But the kind of file like Guitar + linked TAB staff has been used and tested enough now for many years to say that works fine, and so, there is something else for you, which you may not be aware of.
It takes some experience and habit to spot the origin of the problems.
So, again, we need to check one of "your" scores, one of those where you observe what you say (with, if possible, detailed and precise steps - but the most important right now is to can check/open/test this score )
Otherwise we'll be going around in circles for a long time, I'm afraid.
In reply to *"This has happened to… by cadiz1
I'm unclear on what you want. I attached the exact score that crashed. it is above.
In reply to I'm unclear on what you want… by Jon Garner
OK. So, I open your attached score, "Crashing score"
I follow your steps here: https://musescore.org/en/node/316328#comment-1056508
Result: just fine, see below:
In reply to OK. So, I open your attached… by cadiz1
Ok. Well, thank you for investigating.
If you can't recreate it, then you can't solve it.
I should have mentioned I'm on Win 7 machine. Maybe that's part of it.
Who knows. Thanks for trying.
On to another app for the time being I guess
In reply to Ok. Well, thank you for… by Jon Garner
It might, although I doubt it. Still Windows 7 is unsupported (by Microsoft) since a year now
In reply to It might, although I doubt… by Jojo-Schmitz
That's what they are saying, but I'm still getting updates. At least Security Essentials updates.
In reply to That's what they are saying,… by Jon Garner
You could try downloading a Linux ISO and installing it alongside Windows. It's not hard,even I managed it...
In reply to You could try downloading a… by Shoichi
Yeah, I've had a Linux machine before.
Thanks for reminder.
i'm just going to use GP7 for now. It lacks a few formatting options, but otherwise is crushing it.
In reply to There is something weird… by cadiz1
I quote myself in a previous comment: "I conclude, for the moment, that the score has suffered somewhere, that it is corrupted in one way or another"
Well, I'll come back to that (I'm surprised myself I missed it) 😳! The fatigue of one evening probably, sorry! 😴
So, got it, this morning... The Lead guitar part was simply and clearly (now!) corrupt - image below.
I guess it had escaped me at first glance, because it involved two measures, one of which was at the very end of the system, and on top of that, they were separated by another "apparently" correct measure. (while I look at these problems by disabling multi-measure rests/2 measures default... out of habit!) And so I didn't see it immediately.
In short, problem solved. Just delete and recreate the faulty part: Peg(3).mscz