Bug - Cubase 13 crashing when copying MIDI parts

Cubase
1

Sometimes, but not always, the program crashes when I copy a MIDI region from one track to another. Both tracks are enabled. The project was not playing.

I first saw this last week with 8dio Majestica, and am now seeing it with Spitfire BBC SO Pro.

Does anyone know what might cause this?

Memory use seemed quite low.

TIA
Lee

Cubase Pro 13.0.41 Build 256 (x64) June 5 2024

Intel(R) Core™ i7-6700 CPU @ 3.40GHz 3.40 GHz
64 GB
Windows 10 Home, version 22H2 build 19045.4529, Windows Feature Experience Pack 1000.19058.1000.0

2

Hi,

Attach the DMP file, please.

Win: %userprofile%/Documents/Steinberg/Crash Dumps

3

I thought about that but couldn’t find an option to do so in this editor, so assumed I didn’t have such a privilege.

Thanks for asking!

Cubase 13.0.41 64bit 2024.7.5 7.58.37.411-freezedump.dmp (1.1 MB)

5

Hi,

You are mentioneg a crash, but the file is a freeze. Does it crash or freeze? Could you confirm, the DMP file is related to your description (does the date and time match)?

6

Hi,

This crash is in the:
focusriteusbasio64

Please, make sure, the driver is up to date. If this is the case, get in touch with Focusrite support.

8

Cubase freezes for about a minute then closes without warning.

I will contact Focusrite, thank you for your assistance.

1 Like
9

Hi! I have started to experience this crash as well. No freeze, just a crash. I’m currently creating Midi CC Reset regions for all instruments in my template (+1700 tracks). First I thought it could be to re-using the same name on the midi region, so I tried renaming them a bit - what instrument etc. but still crashing. I can’t remember ever having this sort of problem before.

MacOS: Sonoma 14.5 (Apple Silicon)
Cubase: 13.0.41
Mac Studio Ultra M2
Universal Audio Apollo mk2 (latest update)

10

Hi,

Could you attach the *.ips file(s), please?

Mac: macOS Console utility > Crash Reports (or ~user/Library/Logs/Diagnostic Reports).
Win: %userprofile%/Documents/Steinberg/Crash Dumps

2 Likes
11

Cubase 13-2024-09-18-133626.ips (299.0 KB)

12

Sent @Martin.Jirsak

Thanks for having a look!<3

14

Hi,

The crash is in Cubase. Reported to Steinberg. Thank you.

2 Likes
15

No problem! Thank you, and hopefully we can get a fix for it!
Appreciated you taking the time.

16

Using the latest Focusrite drivers, on a freshly booted machine, I am seeing the same bug when dragging MIDI regions between tracks.

I am able to open a dump file, but do not know where to look to locate the error - does anyone reading know of any useful documentation?

Also, what to do when the dump file is 0 bytes in length…?

TIA
Lee

17

Hi,

Mostly, you can see the error in the call stack area. Or you can attach the *.dmp file here and we can resolve it/them.

This is weird, but it happens sometimes. Unfortunately, there is no clear reason for this, and the files don’t bring any information.

1 Like
18

So it just crashed again, copying MIDI from one Spitfire BBC SO Pro track to another.

Nothing left in Documents/Steingberg/Crash Dumps.

Restarted: I got the familiar ‘start without prefs’ screen, but no option to send logs to Steinberg. Selected to carry on as usual, and the program shut down - again with no dump file produced.

I’m in the habit of CTRL+S from using Windows’ code editors in the '90s, but just lost an hour’s work.

And the forum software here is telling me the ‘topic has been solved’ - which it hasn’t.

Very frustrating.

Should I buy a new audio interface or switch to Studio One?

19

Same here yesterday, copying one MIDI region upwards to another VST.

Crashfile :
Cubase 13-2024-10-16-135250.ips (372.5 KB)

20

Hi,

Reported to Steinberg. Thank you.

21

Hi @Soundthrills ,

Can I get an example project with a MIDI Part where the issue is happening with? You can put it to a Dropbox (or similar service) and send me the link via Private Message.

Thank you.