Just got an S88 MK3 and running into performance issues. Anytime a track is changed it gets hung up on MIDI or something… Selecting events, tracks, etc. result in a big lag spike. When I remove the keyboard everything is fine. Is this a Steinberg issue or NI issue?
Hi,
Once you select the track, the Record Enable becomes active by default (Preferences > Project & MixConsole > Enable Record on Selected MIDI Track). That means the track switches to the “live” mode. It doesn’t use the ASIO Guard and all data are processed in real-time. The switch from the non- to the real-time probably causes the spike.
This is not regarding dropouts with ASIO Guard. I fully understand this feature, and appreciate it.
It may be safe to say this is isolated to NI’s S88 MK3 keyboard. When selecting any track, it results in a full DAW freeze. This is most likely from the keyboard analyzing the track selection for compatibility. Audio, groups, instru, etc. are all affected by this
Hi,
If it’s Cubase freeze, try the following, please:
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 behavior (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.
DMP file here
I did not notice the text change as freezes took place. For added clarity, here is a video of the freezes.
When the keyboard is removed everything is responsive.
Hi,
There is a recursive NVIDIA driver operation after a call to baseheadSKIx64.dll (which I don’t really know what it is).
Please, focus on your NVIDIA driver and explore, what the baseheadSKIx64.dll is.
I am very confident this is not related to my GPU or Basehead (same freezes happening with it closed). Can you please take a look at the video again? Frame.io
Hi,
First of all, I don’t know what the baseheadSKIx64.dll is, and what is it doing. You should first investigate on this.
Second, if there is any recursive operation on NVIDIA, it means, the GUI might not be responsive, because it’s doing something (in a very long loop). So the Cubase GUI might not be updated, because the graphic card is doing something different.
1 Like
Was this fixed ? I don’t want to buy the S88 Mk3 if im going to have issues .
Hi,
The issue has nothing to do with the S88 mk3.
No, this is still affecting my larger template. I assume this is related to how the keyboard is interfacing with the DAW’s tracks as count is 1700+. I created a more optimized template from scratch and it is more responsive.
The keyboard is still far behind in development fyi.
1 Like
I have a 2000 track template and am worrying about the lag. It seems the direct intergration is not a positive at all for users like us.