I’m using the latest version of Cubase 13 Pro on a fully-updated Windows 10 Pro x64 machine. When I enable the re-record feature it works fine as long as I hit the record button to re-record either on my PC keyboard or my Steinberg CC-121 automation controller. But when I’m trying to use my Native Instruments S88 mk2 controller keyboard for sake of workflow, I can start recording by hitting the record button on the S88 but Cubase will freeze and never respond if I hit the record button on the S88 again to take advantage of the re-record feature. Help?!
Hi,
Generate a DMP file and share it via Dropbox or a similar service, please.
Use the Microsoft ProcDump utility to generate a DMP file, please.
-
Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your hard disk.
-
Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)
-
Navigate (in the Command Prompt) to the folder with the extracted procdump file.
For example:
cd C:\ Users \ \ Downloads \ Procdump
Note: the dmp file will be written into that folder. -
Launch Cubase/Nuendo. You can work as usual. At any time, change to the command prompt and start procdump, to monitor Cubase/Nuendo for unexpected behaviour (see next step).
-
Launch procdump64 via Command Prompt:
Cubase 13:
procdump64 -e -h -t Cubase13
Nuendo 13:
procdump64 -e -h -t Nuendo13
The -h option will write a dmp file in case of an application hang. This might kick in too early sometimes, in case some action takes a little longer. Feel free to skip the “-h” option, if you are only up for fetching crashes.
The option -e will catch exceptions and the option -t terminations of the application.
- Prodump is now monitoring the Cubase/Nuendo process and will write a crash log, in case Cubase/Nuendo crashes or hangs. Perform the action that causes Cubase/Nuendo to crash and send us the generated crash dmp.
ZIP and share the DMP file via Dropbox or a similar service, please.
Hi, could you please check if the DAW port of the Komplete Kontrol is visible in the ALL MIDI Inputs? If so, you have to uncheck it and retry. By the way, do you use any MIDI remote with the KK MK2, in parallel with the default NI’s integration?
Thanks for the speedy reply. Here’s a link to the archive in which I stored the generated dump file: Dropbox - Cubase13.exe_240226_143425.zip - Simplify your life
I’ll attach a screenshot of my expanded all MIDI inputs because I see three different entries for my NI KK S88 mk2. As to your question, I have three other MIDI related devices plugged into the same computer: my Steinberg CC121 automation controller, Line 6 Helix, and my mioXL iConnectivity MIDI patch bay. Only the CC121 is being used with Cubase though as the error occurs.
OK, please remove the Komplete Kontrol DAW-1 port from the All MIDI Inputs. Open Studio→Studio Setup→MIDI Port Setup, locate this port and uncheck the In ‘All MIDI Inputs’.
Not sure if this will fix the issue described, however, it will make sure that NI’s integration does not conflict with tracks’ operations handling.
This is very interesting for two reasons. First and foremost, it fixes the problem, so thank you for that! I don’t know what that MIDI input is even for. But even after unchecking it in the MIDI port setup as you described, that port still appears when I expand the “All MIDI Inputs” section in the track inspector. So I don’t get that at all. Maybe somebody can tell me what that port is for? And why it keeps showing up in the all MIDI inputs when I’ve explicitly unchecked it in the MIDI port setup as such?
UPDATE: I’ve subsequently learned this does not solve the problem, it only makes it less reliable. I’ll keep adding to my latest post below.
It’s for a type of MCU integration of NI with Cubase.
Yes, you can always choose a port even if it’s not set as “in all midi inputs”. The “in all midi inputs” is a set of the ports we instruct Cubase to listen to when we don’t explicitly choose a port. So maybe another wording would fit, I really don’t know.
Ah, interesting. I’d suggest verbiage more like “Listen by Default” or something along similar lines, but hey maybe it’s obvious to normal people. To me it looks literally self-contradictory, but then I’m a logic nerd among other things. Thanks for the explanation! That’s very helpful!
I guess I should also ask: what am I losing by disabling that MCU integration? Or am I? So far, it seems like the NI KK S88 mk2 keeps working normally in every other respect. I thought maybe I’d lose the transport control functionality and what not, but that still seems to work.
UPDATE: Ah, nuts. As soon as I started using the Komplete Kontrol plugin on a track, the problem is back. After further playing around, I find it doesn’t matter whether I’m using the Komplete Kontrol plugin or not. With the " Komplete Kontrol DAW-1" item unticked in the “All MIDI Inputs” column, the problem now occurs more like 50% of the time rather than 100% of the time. Hmm…
Hi,
Reported to Steinberg. Thank you
1 Like
No, thank YOU. Here’s hoping it’s an easy fix for them.
Hi @Phileosophos ,
Could you please try to unplug CC121 and try again with your NI S88 mk2? Just exclude a conflict.
As far as I know, there is also some kind of NI cleaning process (something like trashing Cubase preferences). Could you please try to do it on your system?
Whenever you restart Cubase, NI’s dedicated dll for it reassigns the DAW ports to its MCU integration. The only way you can get rid of this integration, is to rename (or totally remove, but I don’t suggest it) the file (Windows path, but it’s similar for MacOS):
C:\Program Files\Common
Files\Steinberg\Shared Components\KOMPLETE KONTROL S-
Series.dll
I usually just add a number after the dll suffix.
At the same time, whenever you update Komplete Kontrol, this dll will get rewritten, so it needs a rename again.
As a side note, how about doing the above, and then trying my own script for KK MK2?
Sorry I missed your reply. I tried again with the CC121 unplugged and have the same issue, so I don’t think it’s that. As to the NI cleaning process, I wiped and rebuilt the Komplete Kontrol database from scatch, and that doesn’t make any difference either.
Hi,
Thank you for the update. I have updated the report in the Steinberg’s system.
Hi,
Could you please update to the latest Cubase 13.0.30 and test it again? If it’s still crashing, provide a new DMP file from Cubase 13.0.30, please.
Yay! Sorry for the delay as I’ve been hammered at work. But I can confirm that with the latest build of Cubase 13 Pro installed I no longer have the issue. Steinberg has restored my ability to leverage my NI S88 MK2 with KK workflow! Yay!
1 Like