Score Editor: Score Error 7 ( Crash file added)

Hi,

I just updated to C10.5.11 and tried to drag a triple clef across a measure, it suddenly made the score editor crash and gave me this non-sensical warning: Score Error 7.

It also jammed all 16 measures together, as you see in the score editor.


I spend 1 hour to write bass part of a piano in Score editor. I am so mad at you Steinberg!

I went to the safe mode ( disabled the preferences) and tried to open my project now it just makes the Cubase to crash. See the animation!


Here is a crash file.
Cubase 10.5_2020-02-12-184825_Cs-iMac.spin.zip (5 KB)
This crash file was generated around the time I worked on my project.

I just opened the project in C9.5 the project does not crash however, when I try to open score editor the “Score Error 7” window pops up! But the whole project crashes when I open it with C10 and C10.5. Below I add the project file for you to try!

CS

Score Error 7 has a nice ring to it at least. Not some random CPU Protools error.
That sucks, sorry man, I feel ya pain ova here

Here is the project file!
paiz.cpr.zip (24.8 KB)

Here is the crash file!
crash_scoreEditorError7.txt.zip (31 KB)

Thats a Cubase crash according to the error. Also, I saw this: pointer being freed was not allocated

OK, I just loaded this up here in 10.5.11 and it showed the notes when I opened the Score then it went POOF and crashed. The Project is more than likely corrupt. See if you have a backup anywhere of the project saved

I hear about corrupt project. Why should cubase create a corrupt project? Shouldn’t be a corrupt-detection for Cubase?

Well, I loaded up YOUR Project over here and it crashed so Id say its a Project that is in question.
Im no programmer though.

Were you able to find a backup saved?

I suspect the issue is recording with Instrument track. Here is what I did and will do for the future:

I create a fresh project.
Loaded the track from the corrupt project ( as shanabit says)
make a MIDI track and copy the midi events from the Instrument track ( the corrupt Instrument track),
delete the instrument track!
Once ready for rendering, recreate the instrument track and move them back to the MIDI track!

I guess the issue is with the Beta testers and list of use/test cases provided to them. Maybe Steinberg needs more beta testers who work with Score editors.

Nothing happened! I just dragged a note with my mouse and again, Cubase crashes.

Try resetting or deleting all score layouts in the original project file. The problem was likely a corrupt layout in the project created in an earlier Cubase version, not related to any of the other details you mentioned.

FWIW, score editor crashes my system say 5 times a day these days? Score error 7 comes up sometimes, sometimes it’s just a hard crash.

Should I start archiving crash reports?

I think crash reports are always good to send, so yes.

If these crashes are happening in a project or from a template that was started with a previous version, that might be a thing to look at.

Steve,

The file was created in C10.5.11. I didn’t know about the https://steinberg.help/cubase_pro_artist/v9/en/cubase_nuendo/topics/midi_editor_score_editor/designing_your_score_additional_techniques/score_editor_layout_reset_t.html. I will try it. Thank you.

CS

Steve,

The file was created in C10.5.11. I didn’t know about the https://steinberg.help/cubase_pro_artist/v9/en/cubase_nuendo/topics/midi_editor_score_editor/designing_your_score_additional_techniques/score_editor_layout_reset_t.html. I will try it. Thank you.

CS

I see… if deleting the layouts doesn’t do the trick, Another thing that could be involved are the items in Score Settings>Project

And of course, disabling prefs via safe start is another thing you can do to troubleshoot.

I had a look into the project file. For some reasons, there are several clefs at the same position - the scores can’t handle that

If you open the part in the list editor, you can delete these clefs (they appear in the list, clearly marked as “clefs”).

That’s an ugly workaround, but at least you can continue working with the project.

The programmers should not allow this happens!

Again seems at Steinberg developers need to sit with musicians and do exception handling.

I agree. There is code in place that prevents this kind of situation, though. For some reasons, you ran into a situation where the error-checking failed. If you have a hint for me how to force such a fault, I would be really grateful.

Hi Michael,

Thank you for taking the time to look into my problem.

Honestly, I recreated a new project, imported all track except that one and redid it. So, I don’t want to get back to that. But I don’t think it is ever late for enhancing user input validation and exception handling of old source codes.
Maybe, those clefs where places, after I changed the quantization value and added another clef with distance around say 1/16th note or something.

# most likely you have class method for this!
def addClef(track_id, time, clef_type): 
    neiboring_clefs = all clef on track "track_id" with distance 1 quarter ( or  4 PPQN , or whatever) // i guess sorted by time position
    if neighorig_clefs != NULL:
        print( "there is already a clef at that location")
    	return 
    else:
        track.addClef(track_if, clef_type);

For score editor, I can think of two things as posttests or cleanup feature, before asking users to run Cubase in Safe mode

You guys can do:

  1. Go over musical objects that needs to appear only once. clef, time signatures, etc.
def scoreCleanup_clef():
	tracks_with_clef_removed = set()
	for track in tracks:
	   for i in range(1, len(track.clef))
	        if track.clef[i].gettime() - track.clef[i-1].gettime() < 1 quarter:
	           del track.clef[i].gettime() # or whatever the developer team wishes
	           tracks_with_clef_removed.append(track.getId())
	 return tracks_with_clef_removed // let the user know what tracks are cleaned up.

Same issue exists for Marker track that is for project view and not score editor. I reported the same bug. One delete a marker track, then put it back, all the markers are there ( this is already reported and not fixed yet). There are other issues with Chord track, etc. These can fix them.

  1. Programmers/Developers can add another feature ( in preferences)

“checkbox” Enable user behavior Analyzer API and asking the Steinberg product user to enable that. Of course, when software is at production this must be enabled automatically.

basically, enabling this features enables Cubase/or another software to log all the mouse clicks (recorded pixel-by-pixel mouse movements to figure out how users might use different features), keyboard actions, and system signals every say 5 minutes. Then, when an error occurs, at steinberg can have access to that log and reproduce same error possibly with dummy content ( just like lorem ipsum for dummy text);
there are also ways for evaluation of users behaviors, statistical methods and tools like, Heat maps,

Not giving anybody advice for best practices in software engineering. But we should “Never assume anything. Never trust user input. Sanitation is okay, but validation/rejection is better.” and also where possible, users should be able to check their input and correct it if necessary.

After all, we are using Steinberg products to make our life easier as musicians and create good music. We expect Steinberg to give us products that we utilized them to write music more effective and quality than Mozart era!

Thanks you.

Hi,
by all that is right and fair: Cubase is an application dealing with real-time. The code is written in C/C++. Clearly, you have some experience in programming, but it’s also pretty clear to me that you have only little insight in the kind of problems I’m dealing with on a daily basis…

By the way: You wrote:

Again seems at Steinberg developers need to sit with musicians and do exception handling.

Go figure:
https://www.youtube.com/watch?v=qfcV7GXRz0Q

Friends, OK?